Messages

Ouppps !!! Sorry for the link broken and the late response   
Link is restored now...

Sorry I've been away! Life took me from music but I'm slowly taking some of that time back.  Hope to be around more

Laurent, this link is broken.  Can you fix it?

Thank you!

Good Day,

Just checking on an ETA for MIDI mapping, you had talked about it being on the list of to-do's, just seeing how far out it is potentially, thanks!

Currently the buttons don't do anything in this mode.  Using them to load the patch above (prev) and below (next) the cursor would be nice. 

Also to move the cursor to that patch of course.

[Findings]

Ran an update this morning:

Findings
++ Cursor & insert addition to naming, very elegant solution
++ Files operation remembering its state, great for file management in The Pool
++ Warning confirmations on Init, Panel, Random are great

* Load warning confirmation position could use tweaking (thoughts below)

High impact user experience tweaks, thank you!

*A thought on the load warning confirmation. It's subtle but I think worth pursuing:

In the instance of pressing the Init, Panel, and Random buttons, the warning confirmation generates precisely before the sound erasing function occur.

The Load button is different in that on its first pressing it displays a menu to choose a new sound and the sound erasing function is deferred until the user presses the physical load button again in the load menu or the digital load button on the screen.  What if the user is only going to the load screen to change a patch name or delete a patch?  If they confirm the warning here when they aren't loading a sound they could still put a finger on the touch screen, change the patch when they didn't mean to, and lose their work.

The load function's warning displaying after the "load preset" function is called would make the load warning experience closer to the init, panel, and random warning displays and cover these other legitimate reasons for going into the load menu.

Conclusion

I have a few other thoughts beyond the topic of the purpose of validation I'll share in another thread. Thanks for your hard work.

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  

Good Day!

I've noticed that sometimes The Pool Card 1 mod sources do not behave consistently. 

example:
FX1: Plate Reverb (FX2 is bypassed)
FX Lvl: 81
DRY Lvl: 100
Feedback: 40
Decay: 59
Predelay: 0
Damping: 65
Mod Dest: Feedback
Mod Src: The Pool Card 1
Modulations: None

Behavior:  A feedback loop occurred 
*Bypass FX 1*
Behavior: Feedback loop disappears (naturally)
*Enable FX 1*
Behavior:  A feedback loop occurred 
Mod Src: Tape
Behavior: Feedback loop disappears
Mod Src: The Pool Card 1
Behavior:  A feedback loop occurred 
*Power Cycle The Pool*
Mod Src: The Pool Card 1
M2:100
Behavior: Works as expected

Within the same power cycle I might setup another Pool Card 1 modulation with a Morph knob set at 100 to Feedback and it never quite reaches a feedback loop, only to power cycle the pool and create the same conditions and it result in a feedback loop when I set Morph 2 to 100 and turn the knob.  I've at least experienced this with both Morph knobs.

Good Day!  Is there a reference document that MAPs CC values to parameters on The Pool?

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]

[Load Patch Menu]

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.