Using mixbus 32c Pc#

i'm not saying i'd never do that to be able to use mixbus instead, because the trade off would be a better interface (at least for mixing.not so much for editing), and the harrison compression algo is better than the stock cubase compressors.

Using mixbus 32c Pc#

as to the pc bottlenecking.i can run vegas 17 and cubase 10.5 flawlessly with tons of effects. seems like at the end of the day, that's a smarter nsidering we're on version 6 and i've had this problem since ver 3. I'm going to stick with my first suggestion for Harrison: release your summing algo and proprietary plugs all as vsts. especially considering on the same computer i can run all the synths and plugs i want at 128 latency and never have to worry about the guitar not feeling right when i play it. and 2 considering i write with guitar in mind, constantly playing with the latency/audio buffer settings to record an 'in the box' guitar track seems like another time waster. also, does mixbus have anything like a 'freeze' function or am i missing that? i can bounce to another track.but man that would slow everything down (again). and unless i want to bounce down every one during the writing process (cumbersome), that's not really an option. but at that point i'd still need to be able to run more than 5 tracks of synths. there's a pretty big difference between 64/32 bit processing too. BIG NOTICABLE hit in fidelity by doing that. but i have two comments: 1 in Cubase, unless it's absolutely necessary, i NEVER bounce down/freeze synth tracks. In your case I wold do the midi task in cubase then export the track in wave and use them in Mixbus to get a great mix.Īll good suggestions. Is to drums like EZdrummer I also spread and record the part in wave and always mix only waves. When I used to compose music in MIDI, never effected the midi tracks, I edited them then exported to wave and mixed all waves as normal. There exist not so many plugins that cannot be changed for another with the same result.Ĭubase MIDI is the best I have ever met in the golden SX times from all regards a MIDI may have When I used to meet this overload thing I spent time experimenting with my VSTs which needs the lowest DSP need and prefer using them. Some MB plugins use also more DSP than others of the similar kind. MB also saves/calculates some DSP need if a plugin is just inserted and not used in order not to get surprised when used and overload may appear.

MB mixbuses and other built in features start DSP load higher than other daws that do not have these features. Is it really CPU not the DSP that overruns?