list of feature request

[chamwow]

Hello!  This is an amazing instrument and it's a joy to create patches on it.  I have a few feature requests that would be improvements for patch management and saving/loading sounds and then a couple of additional setting suggestions. 

Load Patch Menu
- When you rename a patch, the "Files" setting defaults back to "None" after each execute.  Having the "Files" function remember its last setting would make it easier to do batch operations.

- A confirmation pop-up when loading patches or the option to chose to confirm.  It's nice that patches can auto load, but there's also potential to erase your current sound design work by accidentally loading a patch and overwriting your current work.
 
- A "[insert patch name] Loaded" pop-up so you know when a patch has been reloaded.  I know you can see it in the Panel/Summary screen, but seeing it displayed on the screen would be good feedback.


Rename Patch Menu
- left and right cursor arrows for character position with an underline, colored character, or highlighted background to annotate what character position you are at for easier editing of names.

- ability to use an encoder to scroll through character position

- ability to use an encoder to scroll through character selection

- ability to set the style for the patch (you can only currently do this when pressing in the "Save" menu, not the "Rename" menu


Envelopes
- individual delay gate control per envelope.

LFOs
- attack stage for LFO Speed that interpolates between 0 and current set value

MPE/OSMOSE
- the initial pressure sensing feels like it starts halfway through the midi value instead of at 0.  It's definitely there but I'd be interested in it being

Sequencer
- individual probability for certain parameters(i.e. Latch can have a separate probability from Chord)

Modulations
- CC values as modulation source.  The waldorf iridium gives the user CC22-CC31 as sources for modulation.  It could be an interesting way to connect The Pool to outboard midi gear like the Low Frequency Expander.

[Baloran]

Hello!  This is an amazing instrument and it's a joy to create patches on it.

Thanks

When you rename a patch, the "Files" setting defaults back to "None" after each execute.  Having the "Files" function remember its last setting would make it easier to do batch operations.

OK

A confirmation pop-up when loading patches or the option to chose to confirm.  It's nice that patches can auto load, but there's also potential to erase your current sound design work by accidentally loading a patch and overwriting your current work.

Ok for a optional overwrite / remplacement confirm (init, rand, load etc..)

 

A "[insert patch name] Loaded" pop-up so you know when a patch has been reloaded.  I know you can see it in the Panel/Summary screen, but seeing it displayed on the screen would be good feedback.

Sorry, it's not clear to me Do you want some kind of permanent display of the last loaded file?
When you press load, the bar is positioned on that name, isn't that enough? 

left and right cursor arrows for character position with an underline, colored character, or highlighted background to annotate what character position you are at for easier editing of names.

Ok, I'll see what's possible, no guarantee

ability to set the style for the patch (you can only currently do this when pressing in the "Save" menu, not the "Rename" menu

Ok

individual delay gate control per envelope.

Not for analog envelopes. Already available for digital envelopes

attack stage for LFO Speed that interpolates between 0 and current set value

No  The amplitude and speed of the LFOs can be modulated by all sources, and that's enough. ENVM for LFO amplitude make a great job

the initial pressure sensing feels like it starts halfway through the midi value instead of at 0.  It's definitely there but I'd be interested in it being

I'll have to check, but I've never developed such a limit.

individual probability for certain parameters(i.e. Latch can have a separate probability from Chord)

It's a good idea, I've already had this questioning when I applied the same RANDOM to RATCHET and CHORD, but it's a question of ergonomics. Here, I've got one encoder = one function and I want to respect that.

values as modulation source

Adding a handful of configurable CCs would be very practical indeed. But it's a simple modification to make, but it's "heavy" (more calculations...).
As an alternative, I had imagined making MORPH 1 and 2 configurable for the CC of your choice (as Patch Options, not System). Wouldn't that be enough?
 

[chamwow]

Ok for a optional overwrite / remplacement confirm (init, rand, load etc..)

Yes, this could also help with the user feedback for the suggestion right below this one.

 

Sorry, it's not clear to me Do you want some kind of permanent display of the last loaded file?
When you press load, the bar is positioned on that name, isn't that enough? 

I figured it out. 

Pressing load using the physical button labeled "LOAD" does the following
-loads the synthesizer preset across the synthesizer architecture
-updates the PANEL/SUMMARY page to reflect the name of the patch just loaded
-flashes the PANEL/SUMMARY page on the screen for half a second or so

Pressing the load button on the touch screen doe the following
-loads the synthesizer preset across the synthesizer architecture

You can test this by booting up The Pool then loading any new patch using the touch screen, it gives no visual feed back and when you hit the PANEL/SUMMARY button you will see <INIT PANEL> OK

Not for analog envelopes. Already available for digital envelopes

fair enough

No  The amplitude and speed of the LFOs can be modulated by all sources, and that's enough. ENVM for LFO amplitude make a great job

oh yeah, that is also fair

I'll have to check, but I've never developed such a limit.

Yeah and maybe I can provide a video illustration so you understand what I'm saying, I'd like the onset of MPE Press activation to feel more linear, it current feels like the values ramp up quickly and so I have less control over the dynamics of MPE press.

This is my own fault, im getting used to all of the vcas.  With sufficient management of the vcas and master volume the dynamic range of MPE press is fully evident!

It's a good idea, I've already had this questioning when I applied the same RANDOM to RATCHET and CHORD, but it's a question of ergonomics. Here, I've got one encoder = one function and I want to respect that.

I can understand that, could be interesting as an option like we have the gate delays in OPT.  I also understand that the onboard sequencer isn't meant to replace a more robust sequencer, but it does feel like a logical application of The Pools onboard sequencer.

Adding a handful of configurable CCs would be very practical indeed. But it's a simple modification to make, but it's "heavy" (more calculations...).
As an alternative, I had imagined making MORPH 1 and 2 configurable for the CC of your choice (as Patch Options, not System). Wouldn't that be enough?

That could work. those would be per voice card?[/quote]
[/quote]

[Baloran]

MPE/OSMOSE
- the initial pressure sensing feels like it starts halfway through the midi value instead of at 0.  It's definitely there but I'd be interested in it being

I cant observe the same, can you send me a patch with your settings that show the problem ?

[Baloran]

Modulations
- CC values as modulation source.  The waldorf iridium gives the user CC22-CC31 as sources for modulation.  It could be an interesting way to connect The Pool to outboard midi gear like the Low Frequency Expander.

After much thought and testing, I'm not going to add multiple sources of modulation, as I think the whole package is already rich.
I've just mapped
CC22 to SEQ1
CC23 on SEQ2
CC24 to SEQ3
SEQ1, SEQ2 and SEQ3 are "smoothed" to avoid staircase effects, so the CCs will be too.

[chamwow]

I cant observe the same, can you send me a patch with your settings that show the problem ?

Sorry I realized this was a an issue with my volume management (many VCAs on The Pool!), I edited that post to reflect that but should have just made a new post.

After much thought and testing, I'm not going to add multiple sources of modulation, as I think the whole package is already rich.
I've just mapped
CC22 to SEQ1
CC23 on SEQ2
CC24 to SEQ3
SEQ1, SEQ2 and SEQ3 are "smoothed" to avoid staircase effects, so the CCs will be too.

Fair, and once we have a Midi CC guide we can do those things ourselves