And that’s what I’d strongly whish also my software to be like… “MixChecker”, that alter my expensive monitors to an appreciated customers nasty boom box or iPhone sound, I’d be happy to have this in a - clearly separated! - “monitoring chain”, with inserts only to the monitoring, clearly different and separated from my master bus / audio processing chain.įor me, the sophisticated long-grown structure of good old consoles makes a lot of sense - it’s developed up to a maximum of handling comfort and a minimum of confusion. with referencing stuff, or with emulating plugins like e.g. I don’t need (or want) a special “solo” function for this special purpose, or having to “switch off” all other plugins instead of bypassing - if just simply “bypass” is the only thing I want, like a plane hardware bypass in a real console….!Īnd if I want to have only my monitoring altered, not the rendering result - e.g. to try it with CPU hog features that cannot reliably be pre-listened), I’m totally happy with “bypassing” all the other plugins in the chain and having only this one active. That’s what I expect - even if it fidgets with it’s meters - because I set it to “bypassed” mode just to have it not affecting my rendering results.Īnd if I intend to try out one special plugin, and further want not only to listen to it, but to render with only this single plugin for a test (e.g. No, I’m not getting confused if a plugin, clearly marked as “bypassed”, also doesn’t affekt the sound. I need the fundamentals to be simple and easy, to be handled ‘blind’ for concentration on the sound and tweaking my plugins’ knobs. I don’t want to have to struggle with “fundamental basics” whil working on audio, like having to think about different options to have a plugin “in” or “out” of the chain (or - worse - “nearly out” vs. I’d move off-hand with you to this best of worlds! Bypass should stay as Bypass and nothing else (…) In the heat of the production you need abolutely clear and precise meanings. A second Master/Monitoring Section could be for those with EQ monitoring, pre playback needs etc. In a better world there would be two solid Master sections: one which works plain simple and straightforward like in Nuendo/Cubase. I use dozens of apps and machines during production and cannot focus my work only on WL and its ‘specialities’. Rendering should render exactly what I hear NOW, partly in the region, in place or to a new file, otherwise it is a trap. To remember different rendering behaviours with “in place” or for a new file is crazy and prone to doing mistakes.Ĭould well be I missed something, but I only need playback with all bypassed plug ins, single or combination of bypassed plug ins and playback with all plug ins and all this as straightforward as possible.
In the heat of the production you need abolutely clear and precise meanings. Instead of doing this, render functions got different behaviours. Bypass should stay as Bypass and nothing else, no left or right click. Is it only me thinking that is going now somewhat messy? In a better world there would be two solid Master sections: one which works plain simple and straightforward like in Nuendo/Cubase. But that will only work for 1 plugin at a time, not for several plugins from a chain at once.
I can recognize which plugins were “on” / “off” in the master section, because the “switched off” ones get grey (the ‘bar’ and the letters also, no matter whether the plugin window is open or not)Īnd there is another way, if I only want to render with only one plugin included, by “soloing” this plugin in the master section (“solo button”). I can’t access the “on/off-Switch” from the master section to toggle on/off, but only from each plugin’s GUI window “Switching off” works when I open the plugin’s GUI window and click on the “power button” in the WL plugin window frame If I want to leave a plugin in the master section, but don’t want to have it included in the rendering process, I have to “switch it off” before rendering instead of “bypassing” it Clicking on “Bypass” in the master section will not hinder the plugin’s processing while rendering, it will remain active
0 kommentar(er)
