Subject pretty much says it all. Really enjoying S1 so far EXCEPT for this problem, which is beyond infuriating. I'm hoping I'm just missing something obvious, rather than S1 trying to "help" me in an awful way I can't override.
If I have an instance of Kontakt present that has, say, 4 instruments in it going to 4 different output channels, I can't separate those channels in the mixer. That is, if I have another instrument/channel, say Sylenth, I can't put that Sylenth channel in between the Kontakt channels. It'll go to one side or the other, period. I organize my song tracks by part and I can't do that in S1 because it forces me to group the multi-outs. Is there seriously no way to just turn off S1 managing my console organization altogether? I don't want it to do ANYTHING automatically, just let me put whatever channel wherever I want it instead of where it *thinks* I should want it.
Yes this is by design.
It was a trade off behavior that was a results of nearly four years of frustration with channels having very inconsistent location behavior in 2.6. They actually fixed over a dozen channel position issue in 3.0.
The locked order of multi out instruments is a results of that work.
I am ok with it but maybe the can satisfy both issue without losing control of the positions in the future. Possible an option for people who want that capability.
OVERVIEW of how to get your issue fixed.
Search the ONLINE MANUAL, Create a SUPPORT TICKET and or Post Issue.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.
My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
Oh nuts That's what I was afraid of. I write software for a living too, so I know how hard it is to satisfy every user at once. I do wish they'd implement an option for totally-hands-off console arrangement though since it's easier code-wise to do that than any other method. Huge bummer for me now though. Fell in love with how great S1 does everything else, but I can't really justify spending the money and time to permanently switch to it when it conflicts with such a fundamental part of my workflow
Anywho, thanks for the answer! Glad to know it wasn't me just being dense. Cheers!
Users browsing this forum: No registered users and 1 guest