Some thoughts about the 1.3 update

I played around with 1.3. and overall its a very impressive and valuable update. I especially like the support for colorblind users, which gives everyone else a lot of nice colors to customize their Synth’s appearance.

In practice I noticed a few minor inconveniences that might be addressed in a future update.

The new DWA engine highlights the fact that the Synth is in dire need of better sample management. The limitation to 250 samples, and the lack of folders for samples really makes experimenting with sample-based engines a lot more tedious than it needs to be. What’s the use of a 16GB on the SD card when you can’t use the space?

I also noticed a massive lag that occurs when stepping through the DWA patches, it seems that samples are loaded immediately, which blocks advancing to the next preset. A slight delay when loading samples might do the trick. There’s also something that appears to prevent auditioning some of the presets when notes are latched, but I haven’t yet figured out the pattern for what happens exactly (on my Synth that affected Death Flute, Spring Arp and Throne Room).

With the MIDI Engine, I find it a little too simple to accidentally change the controller number when I want to tweak the value, because it’s all on one page. Happened to me a few times already when I used the encoder for switching pages, which seemed natural because I had the other hand hovering over the knobs. I can see how that happens with the current implementation where the configuration takes the place of the mod matrix, but the encoder simply should not go there in that engine.

2 Likes

So I am loving you can actually use the synth as a keyboard in a live setting, I have been crying out for this for ages. Only gripes I have on. that is, why doesn’t it save the delay and reverb? Also, when using keypad with a sample sound, why doesn’t it save the sample you’re using when playing the keyboard. You turn it off an reverts back to the first sample in the pack. Highly irritating

1 Like