[sdiy] Sines

[Adam (synthDIY)]

It must be hard to find a happy medium for these interfaces. Cherry have this “focus” tab that makes things a bit easier to see, and at least the drop downs are context-based, but I take your point. The eyes just glaze over after a while… there’s something about using a mouse to do this stuff that really irks me. I believe it has to do with the parts of the brain involved. Too much cortex, not enough cerebellum. It distracts the part of the brain that should be focussed on the sound.
I suppose if you took the trouble of mapping the interface to a lovely big hardware controller, it then may allow you to get deep inside the sound being programmed, the way you can with hardware synths. But my limited experience with this approach, even using overlays or some other mnemonics, has been pretty underwhelming.

A

> On 9 Oct 2022, at 6:30 am, brianw <brianw at audiobanshee.com> wrote:
> 
> I hate to pile on the criticisms, but the demo shows two-level-deep menu diving on a plugin that should have near-infinite virtual screen real estate. Why do we need pop-up menus full of submenus? Just put all the controls on separate screens, and allow two or more screens to be visible at once.
> 
> If the design involves two-level menus, then I'd say it would be better to aim for a minimal interface that's not so busy. You're going to have to dive into a couple of levels of menus anyway, so why have a giant virtual interface that still is incomplete?
> 
> Brian
> 
> 
> On Oct 7, 2022, at 6:16 PM, Adam wrote:
>> Did one of the list’s better-known members collaborate on this I wonder, or are they using his name without permission ;-)  ?
>> 
>> https://cherryaudio.com/products/sines
>> 
>> 
>> I must say Cherry audio do make lovely sounding/looking soft synths (I’ve used the Eight Voice and the Polymoog in commercial releases) but I still can’t get terribly excited about these things!! 
>> Yawn.
>> I’m spoilt by hardware I guess
>> 
>> A
>