# Create presets of individual blocks

**URL:** <https://unity.neuraldsp.com/t/create-presets-of-individual-blocks/6181>\
**Category:** Feature Requests\
**Created:** [December 5, 2021, 4:29am UTC](https://unity.neuraldsp.com/t/create-presets-of-individual-blocks/6181 "2021-12-05T04:29:31Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![BenM](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/benm/32/3468_2.png) [@BenM](https://unity.neuraldsp.com/u/BenM)\
**Post date:** [February 4, 2023, 1:34pm UTC](https://unity.neuraldsp.com/t/create-presets-of-individual-blocks/6181/23 "2023-02-04T13:34:23Z")

</div>

From [Allow footswitch assignment when using "Set parameters as default"](https://unity.neuraldsp.com/t/allow-footswitch-assignment-when-using-set-parameters-as-default/9862) :

The post mentionned above was about the Footswitch default assignement (which is a bad thing , imho) , the discussion led to:

- By default a block shouldn’t have any footswitch assigned.
- Any block should have the ability to have multiple user-defined ‘configurations’ (_in addition to the ‘Factory configuration’ that would be read-only, in case we want to restore the initial default_)
- The User-Defined configurations should store the whole block settings, including the Footswitch assignement.

So, if the ‘block user-preset’ (_aka 'block user-defined configuration_’) become a reality, I hope that they will take this into consideration, as it would **solve two issues in one feature**!

---

_[View the full topic](https://unity.neuraldsp.com/t/create-presets-of-individual-blocks/6181)._