I was reading the X2 Reference Guide earlier with regards to the Console Emulation. I know nothing about this stuff so I have to believe what I read.

Basically, the "guidelines" are that you place an instance of Console Emulation on each track and bus and at the beginning of the chain, and this is even before you start listening to your recordings and start the mixing process.

And there is only one parameter to alter and that is Drive, so that is crucial to how the emulation will sound.

I'm a way of checking this out yet but I have made a note to self for the future.

synkrotron


I was reading the X2 Reference Guide earlier with regards to the Console Emulation. I know nothing about this stuff so I have to believe what I read.

Basically, the "guidelines" are that you place an instance of Console Emulation on each track and bus and at the beginning of the chain, and this is even before you start listening to your recordings and start the mixing process.

And there is only one parameter to alter and that is Drive, so that is crucial to how the emulation will sound.

I'm a way of checking this out yet but I have made a note to self for the future.

That's a pretty accurate understanding.  There is a little extra magic: The default settings are a console's "natural" state.  That drive control can be backed off, causing less impact than a hardware board would, and can be driven extra hard, resulting in a bigger impact than is possible with its hardware counterpart.  

Well one would hope it is subtle, if it is an accurate model of actual high end consoles. They aren't designed to colour the sound, they just do on account of imperfections inherent to analogue circuitry. So the sound you'd get with them and with a clean digital mix shouldn't be all that different.

Bill Jackson [Cakewalk
]

You definitely have "Use Multiprocessing Engine" checked in Edit > Preferences > Playback and Recording?  SONAR should definitely spread them pretty evenly across cores.

Yes that was checked.


I basically loaded a project from X1 which behaved perfectly for 2 hours until i followed the recommendation of using the console emulation on all channels/busses which overloaded core 1. 


However...... Having deleted all instances of console emulation, the project still overloads, which wasn't happening beforehand. As i only have 3 softsynths and 4 fx in total on various channels, all of which i have turned off to see if there is any difference, which there isnt, i can only conclude that X2 has somehow corrupted the project as even after pc restart etc it still overloads and is unplayable.


Maybe a bug? It seems that noone else has reported this behaviour so im not sure but i am very hesitant to use X2 again until the cause can be established.


Bibs

Sycraft


Well one would hope it is subtle, if it is an accurate model of actual high end consoles. They aren't designed to colour the sound, they just do on account of imperfections inherent to analogue circuitry. So the sound you'd get with them and with a clean digital mix shouldn't be all that different.

Exactly.  Funny... what we're doing here is trying to introduce something that companies spent years trying to eliminate/minimize in decades past.  I guess it's all a matter of perspective :)

wizard71

Bill Jackson [Cakewalk
]

You definitely have "Use Multiprocessing Engine" checked in Edit > Preferences > Playback and Recording?  SONAR should definitely spread them pretty evenly across cores.

Yes that was checked.


I basically loaded a project from X1 which behaved perfectly for 2 hours until i followed the recommendation of using the console emulation on all channels/busses which overloaded core 1. 


However...... Having deleted all instances of console emulation, the project still overloads, which wasn't happening beforehand. As i only have 3 softsynths and 4 fx in total on various channels, all of which i have turned off to see if there is any difference, which there isnt, i can only conclude that X2 has somehow corrupted the project as even after pc restart etc it still overloads and is unplayable.


Maybe a bug? It seems that noone else has reported this behaviour so im not sure but i am very hesitant to use X2 again until the cause can be established.


Bibs

Interesting.  I bet it's some other plug-in in the project.  Can you narrow it down by bypassing FX Bins, Synths in the rack, & ProChannel Modules?

Well I'll probably go down the road of using the CEMs as per the guidance and I'll accept the results pretty much as a leap of faith more than anything else. I'm 52 now and I've been to far too many rock concerts in my time, meaning that my ears are shot at, knackered, useless. In fact my left ear hears different stuff to my right ear and that's a fact.

Maximumpower's method is the best method to hear the difference between each emulation. It can be done as follows:

1: Load an audio track with loop added (for example a drum loop).
2: Clone the track so that you have two identical tracks routed to the same output bus (eg master).
3: Enable the console emulation on only one of the tracks.
4: Invert the phase of only one of the tracks. (this is done in the console view)
5: Now you can toggle between the different emulations on the track which it has been enabled and hear   exactly what each sounds like. (at this point also alter the trim and drive dials).

To me, it sounds that the N type is adding more presence to the top end. I set the trim to 0db and drive to +3db then toggled between each emulation.

Thanks for that tip Oddmeister

My experiment was limited to two different tracks. Guitar - clean sound through a 212 box and 57mic light reverb, subtle amount of delay. And Guitar - driven / crunch through same box and mic position... For me, A- Type provided the best, or most noticeable, improvement. And between the two sounds, CEM made the most impact on the Clean sound. A-B'd it about a dozen times or more just to see if I was really hearing the change. The crunch sound also smoothed out just a bit but was not as dramatic for me. In both instances the CEM was at the bottom of the chain. My setting was -1 db (trim) and plus 1.5 (drive). I can tell I"m going to love it on acoustic and vocal materials.