[RANT] Solo function in Cubase SX
-
- KVRAF
- 13444 posts since 14 Nov, 2000 from Hannover / Germany
Sorry, but I just need to vent off:
Which retarded person is responsible for the solo funtionalities in SX' mixer? I'd like to chop his head off!
Here's two things (there's QUITE something more, bit these should be good enough allready, I'm not brave enough to explore the rest of that bullshit...):
- Setup an FX track and have a few other channels sending to it.
- In your mixer, set the FX channel to "solo".
- Mute one of the channels sending to the FX track.
- "Un-solo" the FX channel.
=> Only the FX channel will now be "un-soloed" while the other channels sending to the FX channels will stay soloed. WTF?!?
In addition, if I switch the FX channel to solo again, the channel that I've *explicitely" muted before will all of a sudden become unmuted again!
Ok, and as if this wouldn't be way stupid enough allready, here's the next one:
- Select a VSTi audio channel in your "allways on top" mixer.
- Select another VSTi track in your arrange and solo it.
=> The VSTi channel selected in your mixer will play as well!!!
Actually, this is a mixture of two problems, namely the uber-lame solo functionality paired with SX' inability to actually select a VSTi audio channel in the mixer, should you select the appropriate track in your arrange (which will allways take you to the - usually not needed - MIDI channel).
All these things are multiplied as soon as you're using a screenset with project, float mixer and key editor windows at once. I'm not able to offer any details because I had to shut down this bugridden, jellybeanish piece of utter bullshit, developed by mentally challenged designers to avoid further heart attacks.
At least I can now enjoy Logics perfectly implemented solo function again...
Seriously, do they ever think about HOW to implement things before they start to programm blindly? It certainly doesn't look like!
They surely know how to code in the b0rghouse, but all too apparently they don't know how to make their code useable for musicians. And apparently their betatesters are just following them religiously, otherwise a piece of utter crap implementation like something as simple as a solo function wouldn't be released to the masses.
Had to get that off my chest. Now, where's my chainsaw?
Which retarded person is responsible for the solo funtionalities in SX' mixer? I'd like to chop his head off!
Here's two things (there's QUITE something more, bit these should be good enough allready, I'm not brave enough to explore the rest of that bullshit...):
- Setup an FX track and have a few other channels sending to it.
- In your mixer, set the FX channel to "solo".
- Mute one of the channels sending to the FX track.
- "Un-solo" the FX channel.
=> Only the FX channel will now be "un-soloed" while the other channels sending to the FX channels will stay soloed. WTF?!?
In addition, if I switch the FX channel to solo again, the channel that I've *explicitely" muted before will all of a sudden become unmuted again!
Ok, and as if this wouldn't be way stupid enough allready, here's the next one:
- Select a VSTi audio channel in your "allways on top" mixer.
- Select another VSTi track in your arrange and solo it.
=> The VSTi channel selected in your mixer will play as well!!!
Actually, this is a mixture of two problems, namely the uber-lame solo functionality paired with SX' inability to actually select a VSTi audio channel in the mixer, should you select the appropriate track in your arrange (which will allways take you to the - usually not needed - MIDI channel).
All these things are multiplied as soon as you're using a screenset with project, float mixer and key editor windows at once. I'm not able to offer any details because I had to shut down this bugridden, jellybeanish piece of utter bullshit, developed by mentally challenged designers to avoid further heart attacks.
At least I can now enjoy Logics perfectly implemented solo function again...
Seriously, do they ever think about HOW to implement things before they start to programm blindly? It certainly doesn't look like!
They surely know how to code in the b0rghouse, but all too apparently they don't know how to make their code useable for musicians. And apparently their betatesters are just following them religiously, otherwise a piece of utter crap implementation like something as simple as a solo function wouldn't be released to the masses.
Had to get that off my chest. Now, where's my chainsaw?
There are 3 kinds of people:
Those who can do maths and those who can't.
Those who can do maths and those who can't.
-
- KVRAF
- Topic Starter
- 13444 posts since 14 Nov, 2000 from Hannover / Germany
SX 2 and 3.Cryogenic wrote:What versions of Cubase are you using?
What exactly is working fine?All of this works fine here.
The solo functionalities I described are broken "by design", so to say. They just can't work any different than in my description.
There are 3 kinds of people:
Those who can do maths and those who can't.
Those who can do maths and those who can't.
-
- KVRAF
- 4265 posts since 21 Oct, 2001 from my bolthole in the south pacific
So what -- are you just roaming the forum looking for fights?Cryogenic wrote:What versions of Cubase are you using?
All of this works fine here.
Never "defective user" is it.
-
- KVRAF
- 3125 posts since 6 Dec, 2002 from Ljubljana/ Slovenia
-
- KVRist
- 471 posts since 18 Mar, 2004
For one, this isn't true, in my case:
- Select a VSTi audio channel in your "allways on top" mixer.
- Select another VSTi track in your arrange and solo it.
=> The VSTi channel selected in your mixer will play as well!!!
Anyone else tried?
- Select a VSTi audio channel in your "allways on top" mixer.
- Select another VSTi track in your arrange and solo it.
=> The VSTi channel selected in your mixer will play as well!!!
Anyone else tried?
History is full of two kinds of people.
-
- KVRist
- 471 posts since 18 Mar, 2004
And im not picking fights. But i do try to call out the BS, and people full of them themselves.
Tho not this thread's topic in particular.
Tho not this thread's topic in particular.
History is full of two kinds of people.
-
- KVRAF
- Topic Starter
- 13444 posts since 14 Nov, 2000 from Hannover / Germany
You must have a special version of SX then, as I could reproduce this on a number of machines, using both SX 2 and 3. Others could reproduce it as well.Cryogenic wrote:For one, this isn't true, in my case:
- Select a VSTi audio channel in your "allways on top" mixer.
- Select another VSTi track in your arrange and solo it.
=> The VSTi channel selected in your mixer will play as well!!!
Anyone else tried?
There are 3 kinds of people:
Those who can do maths and those who can't.
Those who can do maths and those who can't.
-
- jaaathmaster
- 2690 posts since 1 Jun, 2001 from Marlow, S. Bucks, UK
OK, that *does* annoy me a lot... Not come across Sascha's FX track problem, maybe because I use groups instead of FX tracks..egbert wrote:Not only that, soloing a track or an FX bus does not mute frozen tracks ... WTF? This stuff drives me nuts.
Anyway, top rant Sascha
Now, if they were to implement something comparable to the goddamn Cubase drum editor in Tracktion or EnergyXT, I might be rid of these annoyances... Not that they bother me greatly... But then, I don't do it for a living..
Music with dinner is an insult both to the cook and the violinist.
-
- KVRAF
- Topic Starter
- 13444 posts since 14 Nov, 2000 from Hannover / Germany
No, I'm not. My descriptions were just describing of what it'd require to do. And I can reproduce it right here, right now, on 2 machines, plus I'm also able to reproduce it on the local conservatory's G5s (which I am maintaining), so it's not hardware dependent either.
Make sure to have your preferences set to "mixer follows track selection" (or whatever it says in english), even if that shouldn't matter - at least it doesn't over here.
As said, whenever I select a VSTi channel (NOT the MIDI channel but the audio channel) in the (floating) mixer, then select another in the arrange/project, then solo that one, the one selected in the mixer will play as well, assuming your MIDI channels are hidden (which they allways are over here, they're just not making sense on 100% virtual projects).
Make sure to have your preferences set to "mixer follows track selection" (or whatever it says in english), even if that shouldn't matter - at least it doesn't over here.
As said, whenever I select a VSTi channel (NOT the MIDI channel but the audio channel) in the (floating) mixer, then select another in the arrange/project, then solo that one, the one selected in the mixer will play as well, assuming your MIDI channels are hidden (which they allways are over here, they're just not making sense on 100% virtual projects).
There are 3 kinds of people:
Those who can do maths and those who can't.
Those who can do maths and those who can't.
-
- Banned
- 1149 posts since 7 Mar, 2004
Hi Sasha:
If i buy a truck i can´t expect it to fly like a plane.
Many people say things about the solo functionallity, what you describe is correct but i don´t see it has a flaw, solo a track that track gets soloed not its audio path, that´s because of it that on export it´s allowed to choose multiple channels.
About VSTi it´s clear to me the solo function adresses audio only, be it soloed on the MIDI track or audio track.
I think SX3 is an outdated app still, and at it´s core functionallities should be reviwed instead choosing the easy way of give me more bells and whistles to overcome its flaws.
think the problem you talk about its a matter of preferences, probably that´s a fine way to deal with it, making the solo function you need and then people select it if needed.
Because if i need to export i can choose to export a selected track and i´ll export it with inserts and sends, or solo it and export it with inserts only.
About VSTi, considering a multi output one, if i solo on the MIDI track, all it´s audio channels will be soloed, but on the mixer i have to solo each individual audio output, wich will solo again its audio channel without any send, if i want to export the whole thing i select the respective output on the
export menu.
it seems to me an advantage, perhaps a question of perpective.
Bye
If i buy a truck i can´t expect it to fly like a plane.
Many people say things about the solo functionallity, what you describe is correct but i don´t see it has a flaw, solo a track that track gets soloed not its audio path, that´s because of it that on export it´s allowed to choose multiple channels.
About VSTi it´s clear to me the solo function adresses audio only, be it soloed on the MIDI track or audio track.
I think SX3 is an outdated app still, and at it´s core functionallities should be reviwed instead choosing the easy way of give me more bells and whistles to overcome its flaws.
think the problem you talk about its a matter of preferences, probably that´s a fine way to deal with it, making the solo function you need and then people select it if needed.
Because if i need to export i can choose to export a selected track and i´ll export it with inserts and sends, or solo it and export it with inserts only.
About VSTi, considering a multi output one, if i solo on the MIDI track, all it´s audio channels will be soloed, but on the mixer i have to solo each individual audio output, wich will solo again its audio channel without any send, if i want to export the whole thing i select the respective output on the
export menu.
it seems to me an advantage, perhaps a question of perpective.
Bye
Last edited by stag on Wed Aug 31, 2005 10:56 am, edited 1 time in total.