Hi there great developers, just some requests after playing with Unify for some weeks now:
CPU performance meter
Closing the visible plugin windows when minimize UnifyTranspose function for VSTi
Save bypass state in the saved Unify patch
Multiple outputs
Make subsets with i.e. only VST2 or VST3 plugins categorized in manufacturer folders
So much fun with Unify. The possibilities are INFINITE!!
Cheers!
Hello @rotong,
Transpose function for VSTi
Look at the Unify manual here:
https://pluginguru.net/unify/manual/doku.php?id=layer-stack-view#midi_controls
MIDI transpose works per Instrument layer. It's the control under IN that is usually 0. You can shift or transpose by +/- 48 semitones.
Greetings and God bless, Marius
Thanks @rotong, these are all useful suggestions.
- CPU performance metering is actually very complex, but is definitely on our to-do list
- Save/recall of effect bypass state is done, and will be in the next update
- Multiple outputs is on the to-do list
Auto-closing plug-in windows when Unify itself is minimized is an interesting idea, but I have two questions:
- Does this only apply to the Unify stand-alone app, or are there any plug-in hosts which allow minimizing (as opposed to closing) plug-in windows?
- You would expect all auto-closed windows to automatically re-open when Unify is de-minimized, no? (This is the hard part.)
As for your suggestion about subsets for VST, VST3 etc., I suspect this will become moot when Unify allows you to specify your preferred format. When you have two or three versions of a given plug-in, you would normally prefer just one of them. (Can anyone suggest a case where it might be otherwise?)
You can get around the multiple-formats issue now, by manually removing any redundant versions from the Known Plug-Ins list. I admit that's not ideal, but I'm not sure that your suggestion to "make subsets with i.e. only VST2 or VST3 plugins categorized in manufacturer folders" is the best answer.
I'm open to further suggestions on all these matters. Discussing possibilities is much less work than implementing them, and should lead to more optimal approaches.
-shane
When you have two or three versions of a given plug-in, you would normally prefer just one of them. (Can anyone suggest a case where it might be otherwise?)
I think interchangeability / portability (sharing sounds across operating systems ) is the most preferable way as it was intended with Unify.
Regarding plugin formats: If one format uses better operability (exposing parameter names and values) so that they can be read even by visually impaired people this could really benefit us, but if Unify itself would provide good presets without having to tweak parameters that are just mouse tweakable that would even be better.
I mean Pads/Basses/Leads/whatever programmed by the community but approved by John for the 'masses' that just want to step through presets instead of tweaking presets themselves...
Greetings and God bless, Marius
Auto-closing plug-in windows when Unify itself is minimized is an interesting idea, but I have two questions:
- Does this only apply to the Unify stand-alone app, or are there any plug-in hosts which allow minimizing (as opposed to closing) plug-in windows?
- You would expect all auto-closed windows to automatically re-open when Unify is de-minimized, no? (This is the hard part.)
You can get around the multiple-formats issue now, by manually removing any redundant versions from the Known Plug-Ins list. I admit that's not ideal, but I'm not sure that your suggestion to "make subsets with i.e. only VST2 or VST3 plugins categorized in manufacturer folders" is the best answer.
Hi Shane,
Thanks for your reply....
Saw you life on NAMM. Very nice performance dude!!!
ad.1 Yes it's apply just for the standalone. As plugin it's ok. All related windows are closed when minimized.
ad.2 Indeed as I open the minimized Unify again all previously opened VST windows should be recovered.
You can get around the multiple-formats issue now, by manually removing any redundant versions from the Known Plug-Ins list. I admit that's not ideal, but I'm not sure that your suggestion to "make subsets with i.e. only VST2 or VST3 plugins categorized in manufacturer folders" is the best answer
That's not preferable but one can live with that!
I'd wish sone improved on/off buttons. Maybe a green or blue lit LED type ring for on and something darker for off/bypassed. These dark and light grey graphics are hard to distinguish for me.