Notifications
Clear all
Topic starter
March 27, 2020 6:46 pm
Great plugin but I have some issues with the user interface.
First of all. normally there is enough space on the screen
so why do I have to switch between show midi (keyboard) or Macro knobs or Transport controls. It would be much better to be able to enable all three.
everybody needs the browser permanently. And everytime I have to switch it on after starting unify. Please kill the browse button.
CPU Meters
the left one is CPU usage what is the Right one?
March 27, 2020 8:07 pm
Thank you for the feedback concerning the GUI. I'll bear those suggestions in mind.
Re CPU meters, check the manual page: https://pluginguru.net/unify/manual/doku.php?id=cpu-meters
Topic starter
June 27, 2020 10:13 am
@getdunne sometimes to bear is not enough.
sorry the browse function is booooooooooooring !!
never ever saw a unify window in one of Johns videos with closed browser - because you need it all the time. If you want to keep this functionality you only have to set the browse parameter to on as default. And if anyone wants to close it ( which I don’t believe ) he could klick the browse button.
I have klicked this button at least a thousand times - it is only wasted time.
I appreciate your work very much and unify is a brilliant piece of software but some small details drive me crazy.
June 27, 2020 2:16 pm
I have klicked this button at least a thousand times - it is only wasted time.
I would say that it saved me a lot of time - I don't need the browser once the patch is loaded - I spend most of the time tweaking plugins parameters. Also, I'm very happy with the compact view when I use the Unify as a plugin inside my DAW.
Topic starter
June 27, 2020 5:09 pm
@robert-p so to make all of us happy a litte addition in the settings „show by default“ for browser would work - can’t be much effort I think. I’ll turn it on and you can turn it off.
June 27, 2020 8:49 pm
I'll definitely think about a Settings option. Unfortunately, due to the way the browser opening/closing is implemented, it's actually quite a big effort. (If it were easy, I'd have done it already.)
I don't like the way it keeps closing either. The idea was not to show the browser when clicking on a patch would not have any effect on the GUI, but in practice it's annoying.
I plan to re-think the whole open/close thing and try to make it simpler and cleaner.
