Yea I stopped using SX after 2 cause of the problem with my my boards automated faders.. they were flying all over the place I thought that the motors would fry cause I was always fighting them!! The major problem w sx is that when you try to re record over the old automation you run into major problems!!! Yea you can't beat XT fo sho!! XLUtop is a bit jyanky lots of crashes with certain plugs!! There are several fx only hosts that do a whaaay better job and allow me to plug my board into directly like real a effect rack.. I'd say XT all the way yo!
C
Cubase automation! - I'm sick of this sh*t!
-
- KVRAF
- 13446 posts since 14 Nov, 2000 from Hannover / Germany
Has been said numerous times already, but I'll just repeat it: Energy XT!
And, while most people are complaining about low MIDI resolution (which actually is not a big deal at all in case the plugin in question offers proper internal parameter smoothing), for anything "creative" I prefer MIDI CCs over VST/host-automation.
Why? Because most hosts (at least Logic and Cubase, these are the ones I'm familiar with) handle automation data as if those routines were programmed by f**king clueless morons.
Okay, let's see.
Let's assume I'm gonna record a simple thing such as a filter cutoff sweep. One bar, filter cutoff goes up and down. Fine. In case I can't assign a MIDI CC to the appropriate knob, I'll activate automation write mode and tweak away. Again fine.
Now, later on I may want to have that filtersweep go faster (without MIDI note data being altered). Twice as fast. Shit, in case I'd been using automation data, I'd have to rerecord or redraw all the stuff. Not so with MIDI data - I'd simply use MIDI timestretch! You can tell by yourself which is faster, can you?
The same goes for about anything. With MIDI automation I could as well cut a part into even steps, say, 16ths, then fool around with those steps. Or simply mute it for a while (something automation only allows for on a per track base).
Anything in the "creative" department becomes way, way easier using all the common MIDI techniques, rather than host automation.
And fwiw, this is also one of the very reasons why I'm still using Logic. In Logic, I can just decide whether I want a parameter tweak to be recorded as automation or as plain MIDI data. Heck, this is even valid for all mixer parameters. So I can just record, say, an FX send as MIDI data. Brilliant, should I use it creatively.
Don't get me wrong, automation is fine for mixing tasks. For anything else MIDI file handling comes in way more natural. There might be hosts treating automation data differently - but as said, Logic and Cubase don't.
That's why Energy XT is a must for me under Cubase (of course, I still won't be able to MIDI automate some Cubase FX send with it...).
And, while most people are complaining about low MIDI resolution (which actually is not a big deal at all in case the plugin in question offers proper internal parameter smoothing), for anything "creative" I prefer MIDI CCs over VST/host-automation.
Why? Because most hosts (at least Logic and Cubase, these are the ones I'm familiar with) handle automation data as if those routines were programmed by f**king clueless morons.
Okay, let's see.
Let's assume I'm gonna record a simple thing such as a filter cutoff sweep. One bar, filter cutoff goes up and down. Fine. In case I can't assign a MIDI CC to the appropriate knob, I'll activate automation write mode and tweak away. Again fine.
Now, later on I may want to have that filtersweep go faster (without MIDI note data being altered). Twice as fast. Shit, in case I'd been using automation data, I'd have to rerecord or redraw all the stuff. Not so with MIDI data - I'd simply use MIDI timestretch! You can tell by yourself which is faster, can you?
The same goes for about anything. With MIDI automation I could as well cut a part into even steps, say, 16ths, then fool around with those steps. Or simply mute it for a while (something automation only allows for on a per track base).
Anything in the "creative" department becomes way, way easier using all the common MIDI techniques, rather than host automation.
And fwiw, this is also one of the very reasons why I'm still using Logic. In Logic, I can just decide whether I want a parameter tweak to be recorded as automation or as plain MIDI data. Heck, this is even valid for all mixer parameters. So I can just record, say, an FX send as MIDI data. Brilliant, should I use it creatively.
Don't get me wrong, automation is fine for mixing tasks. For anything else MIDI file handling comes in way more natural. There might be hosts treating automation data differently - but as said, Logic and Cubase don't.
That's why Energy XT is a must for me under Cubase (of course, I still won't be able to MIDI automate some Cubase FX send with it...).
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
- 3617 posts since 28 Jan, 2006 from Phoenix, AZ
Ok, I just tried Surge and Filterbank2, both have no sign of smoothing. Looks like I gotta stick with the non-midi automation.
BTW, with eXT you can't control midi parameters via non-midi, but with Chainer you can set CC1 to anything, and then modulate the "CC1 parameter" with the non-midi and there will be smoothing. Quite awesome.
BTW, with eXT you can't control midi parameters via non-midi, but with Chainer you can set CC1 to anything, and then modulate the "CC1 parameter" with the non-midi and there will be smoothing. Quite awesome.
-
- KVRian
- 903 posts since 14 May, 2003
Leave the coat.bullshark wrote:How could Steinberg survive without any users whatsoever?Lord Snarebottom wrote:Gee, I'll bet Cubase wouldn't be half as bad as everyone says it is if ALL THE IDIOTS STOPPED USING IT!
I'll get me coat
-
- KVRer
- 13 posts since 15 Dec, 2003 from Madison, Wisconsin
Okay okay...
So, if not Cubase... what are y'all using as your host then?
Logic? Sonar? DP? PT?
Just curious.
Seriously, which one handles this better, then? Personally, I do like Live a LOT but... that's a bit different than the other I listed above.
cp
So, if not Cubase... what are y'all using as your host then?
Logic? Sonar? DP? PT?
Just curious.
Seriously, which one handles this better, then? Personally, I do like Live a LOT but... that's a bit different than the other I listed above.
cp
-
- KVRist
- 95 posts since 22 Aug, 2001 from US
EnergyXT also has a "Parameter Mapper" which does this.Architeuthis wrote:Ok, I just tried Surge and Filterbank2, both have no sign of smoothing. Looks like I gotta stick with the non-midi automation.
BTW, with eXT you can't control midi parameters via non-midi, but with Chainer you can set CC1 to anything, and then modulate the "CC1 parameter" with the non-midi and there will be smoothing. Quite awesome.
-
- KVRAF
- 3617 posts since 28 Jan, 2006 from Phoenix, AZ
ok, i set something to CC1 and thenn i modulate "param1" and nothing happenes. even if it did work, it only has a resolution of 100, LESS THAN MIDI'S 128! what the hell? I must be missing something.