Hive 2 - save and load complete modulation and XY settings

[drzhnn]

If we look at this feature request at different angle, we could see that what SmartCat really wants is the ability to randomize everything except ModMatrix and XY settings

[SmartCat]

If we look at this feature request at different angle, we could see that what SmartCat really wants is the ability to randomize everything except ModMatrix and XY settings

No, not at all
Although interesting idea..
What I actually mean is, lets assume you browse for example the factory library and find a pad sound that sounds good to your ears, lets call it preset A. After a while, or another day while working on a new preset and you make a pad sound of it, you suddenly realize that the modulation matrix that made preset A so good would give the preset you are working at right now a great starting point.
Now if you were able to just save the mod matrix from preset A and load it into the blank mod matrix of preset B (the new one), you wouldn´t have to assign everything from scratch.
Just load the matrix preset, adjust the settings that you want and thats it!

[Funkybot's Evil Twin]

If we look at this feature request at different angle, we could see that what SmartCat really wants is the ability to randomize everything except ModMatrix and XY settings

No, not at all
Although interesting idea..
What I actually mean is, lets assume you browse for example the factory library and find a pad sound that sounds good to your ears, lets call it preset A. After a while, or another day while working on a new preset and you make a pad sound of it, you suddenly realize that the modulation matrix that made preset A so good would give the preset you are working at right now a great starting point.
Now if you were able to just save the mod matrix from preset A and load it into the blank mod matrix of preset B (the new one), you wouldn´t have to assign everything from scratch.
Just load the matrix preset, adjust the settings that you want and thats it!

I think the challenge the rest of us are trying to solve for are things like this:

1. What if the waveforms in Preset A don't even align at all with Preset B (e.g. modulating WT position when no WT is being used)? How should saving an entire Matrix chain deal with that situation?

2. What if the modulation depths no longer make any sense between Preset A and B? For example one matrix item has a mod depth of -100, and Preset B starts out a -100 setting already on that target. What do you do? Have a wasted mod slot? Or would you want the system to automatically adjust the range to something different (for instance, instead of -100, add +100).

3. What if they use different FX? Matrix slots include FX. Preset B may not use the same effects. Waste the slot? Turn the FX on?

4. What if they use different features? Example: Preset A was quantized to a defined scale, Preset B uses all defined notes. Should the scale get loaded from Preset A? Should certain types of mod slots get excluded? Or just waste the slot with the note quantizer even though it's not being used?

Etc.

There's so much opportunity to end up with mod slots that don't do anything, modulations that don't make sense, or even completely alter Preset B's sound. Unless you'd expect Hive 2 have a complicated set of IF/THENs buit into it to automatically address some of these (e.g. "If Osc type <> WT then don't load WT Mod Matrix slots").

Now, what you can do is save individual Matrix slots as presets and load them as needed, which I think makes more sense honestly.

[EvilDragon]

We all know what you mean, you don't need to make a video.

[drzhnn]

What I actually mean is, lets assume you browse for example the factory library and find a pad sound that sounds good to your ears, lets call it preset A. After a while, or another day while working on a new preset and you make a pad sound of it, you suddenly realize that the modulation matrix that made preset A so good would give the preset you are working at right now a great starting point.
Now if you were able to just save the mod matrix from preset A and load it into the blank mod matrix of preset B (the new one), you wouldn´t have to assign everything from scratch.
Just load the matrix preset, adjust the settings that you want and thats it!

Unfortunately, this won't work as you want it to. Because Hive has rather flexible routing features and different presets may have different osc routing and filter topology. Say, loading a ModMatrix preset from patch A, that has intense modulation of filter 2, won't do anything when applied to patch B, if it has filter 2 bypassed or not used at all.

[SmartCat]

If we look at this feature request at different angle, we could see that what SmartCat really wants is the ability to randomize everything except ModMatrix and XY settings

No, not at all
Although interesting idea..
What I actually mean is, lets assume you browse for example the factory library and find a pad sound that sounds good to your ears, lets call it preset A. After a while, or another day while working on a new preset and you make a pad sound of it, you suddenly realize that the modulation matrix that made preset A so good would give the preset you are working at right now a great starting point.
Now if you were able to just save the mod matrix from preset A and load it into the blank mod matrix of preset B (the new one), you wouldn´t have to assign everything from scratch.
Just load the matrix preset, adjust the settings that you want and thats it!

I think the challenge the rest of us are trying to solve for are things like this:

1. What if the waveforms in Preset A don't even align at all with Preset B (e.g. modulating WT position when no WT is being used)? How should saving an entire Matrix chain deal with that situation?

2. What if the modulation depths no longer make any sense between Preset A and B? For example one matrix item has a mod depth of -100, and Preset B starts out a -100 setting already on that target. What do you do? Have a wasted mod slot? Or would you want the system to automatically adjust the range to something different (for instance, instead of -100, add +100).

3. What if they use different FX? Matrix slots include FX. Preset B may not use the same effects. Waste the slot? Turn the FX on?

4. What if they use different features? Example: Preset A was quantized to a defined scale, Preset B uses all defined notes. Should the scale get loaded from Preset A? Should certain types of mod slots get excluded? Or just waste the slot with the note quantizer even though it's not being used?

Etc.

There's so much opportunity to end up with mod slots that don't do anything, modulations that don't make sense, or even completely alter Preset B's sound. Unless you'd expect Hive 2 have a complicated set of IF/THENs buit into it to automatically address some of these (e.g. "If Osc type <> WT then don't load WT Mod Matrix slots").

Now, what you can do is save individual Matrix slots as presets and load them as needed, which I think makes more sense honestly.

There's a lot of things that may not make any sense when transferring entire Matrix settings from A to B. What you can do is save individual Matrix slots and load them as needed, which I think makes more sense.
[/quote]

Thanks for this explanation, I really appreciate it.
You are 100% right and if it is technically not possible I have no problem with that and I will be glad to work with preset templates for my job.

This is what I call a professional, detailed and competent contribution.

[SmartCat]

What I actually mean is, lets assume you browse for example the factory library and find a pad sound that sounds good to your ears, lets call it preset A. After a while, or another day while working on a new preset and you make a pad sound of it, you suddenly realize that the modulation matrix that made preset A so good would give the preset you are working at right now a great starting point.
Now if you were able to just save the mod matrix from preset A and load it into the blank mod matrix of preset B (the new one), you wouldn´t have to assign everything from scratch.
Just load the matrix preset, adjust the settings that you want and thats it!

Unfortunately, this won't work as you want it to. Because Hive has rather flexible routing features and different presets may have different osc routing and filter topology. Say, loading a ModMatrix preset from patch A, that has intense modulation of filter 2, won't do anything when applied to patch B, if it has filter 2 bypassed or not used at all.

Thanks for the reply and your support!

[Howard]

No offense taken! Thanks to the "Hive Mind" for having more patience than me.

[EvilDragon]

This is what I call a professional, detailed and competent contribution.

Excellent passive-aggressiveness.