In my opinion a FX-Container doesn´t need to be as complex as Patcher (graphics, cords.) Action: Freeze Track including Pre Fx Chain and Main Fx Chain to new versionĪlso: Preset is preset however it's implemented. Action: Freeze Track including Pre Fx Chain and Main Fx Chain So IMO it just look better with no real benefit.Īlso the approach i described and (last 2 posts) + operator mockup gives benefits like this: No arrows inputs/outputs and blablabla, that in the end do the same, with more work and taking more screen space. I prefer how Ableton/Bitwig implements this then FL Studio style. Is my point of view :) and in my point of view i prefer like this. It is not even close to what it should be with a modular fx routings where you can write and read amazing presets. Pretty powerful for complex inter-track routings. also, you can just hide the "FX tracks" if you don't want to see them. Tho it works on high-level as it creates a track whenever you add an FX (or chain) but basically, on the view, they look like containers.
#Mulab 7 mux video windows#
Only sad point is that there's no way to load JS plugins on it (at least on macOS, should be doable on Windows with the ReaJS plugin).Īnother solution is sai'ke's Buzz Machines extension (part of an almost perfect rendition of Jeskola Buzz). I'm using the open source app Element mentioned above (or you can just pay 2$ if you don't want to bother compiling the master app and the plugins), it's pretty powerful actually and has macros + oversampling, a Lua scripting module, OSC sender/receiver modules and, to connect to the outside, a matrix pin system, just like in Reaper. sometimes you actually have to write down pin numbers in order to not get lost. I understand some prefer the old-fashioned way (i like it too sometimes, for less complex tasks) but when dealing with rather complex routings, it becomes pretty cumbersome. The tree view above is all that's needed! would also be a good idea for the devs to go develop on MPL's Wired Chain extension, there's a huge demand for that and this kind of view has become a standard in many routing applications nowadays. Or at least, in the meantime, the possibility to colour FX names in the chain. maybe I´m wrong with this.Īnother thing Patcher is lacking is simple Crossovers to create MultibandFX. In the beginning of Patcher it didn´t supported PDC (when using it outside of FL as VST), if I´m not changing up memories. but something like this would only be usable if it would support PDC. I need to agree that Image Line Patcher is quite sweet. :-P) is an Ableton-FX-Container-Preset from Dada Life that got turned into a plugin. FunFact: the VST "Sausage Fattner" (if anybody knows it. Just look at all the creative Ableton FX-Container-Devices (Presets) which are out there. the Reverb Layer then can be shaped further with EQ, Side-Chain-Compression from Dry Signal, Compression, StereoFX, or whatever. In electronic music most artists work already mostly with individual reverbs on every singel track for better control (except maybe for some tracks there is only a tiny little bit of reverb on the folder-track for some glueing effect).Īn FX-Container would allow to have a 100% Dry Layer and a 100% Wet Reverb Layer. Maybe it wasn't necessary a while ago, but now things have gotten larger and more complex.Įspecially as Justin himself said in a recent podcast (that got posted somewhere in the forum), that when working with multicore processor it may be better to have individual reverbs (convolution) on every singal track than having routing and therefore dependencies going on. There are large sessions and it gets really messy to have that many parallel tracks/fx.