activate the scissors and cut both takes in 4 regions 1 bar longĤ. record 4 bars two times (not loop recording) so that you have two takes in the same 4 barsģ. Create an audio track and switch to lanes visualizationĢ. Workaround : isolate the two parts from the others to apply crossfadeġ.
Then it doesn't even put the xfade in the right spot. Even if I go back to the object select tool and select that part and the next. Not the new part that I have pasted on top. it applys the cross fade to the audio part thats underneath (ie, the poorly played note). use the range tool to select the range to apply a crossfade copy/pasted a part (ie, a correctly played bass note) over an old part (ie, a poorly played note) Official status : reported for further investigationĬrossfade problem of 2 parts on top of other layers (ie, bad takes) When I press Stop, Cubase stops responding for a minute or so, starts calculating something, there is a lot of disk activity, mouse is hardly moving, 120bpm that slowly ramps to 125bpm) inside loop Set L and R locators for something like 10 bar long loopĤ. Automation isn't read when nodes/values are all the sameĬlicks randomly on the first bar when playing in looped mode, especially on kick drums audio loops.Īudio Loop Recording with variable tempo results in temporary nearly frozen computerģ. no copy/paste of a single automation point (ok for 2 automation points) not editable via typing number in infobar (precise values are rounded, Cubase 4 converts all vst 2.x automation parameters to simple values between 1-100, then it's impossible to reach precise values and to match 2 points of automation) They haven't even fixed the bugs in Cubase 4, and if their track record is anything to go by, then they won't. Ok now I say something to make everyone happy: Sonar is bugfree. say something a little offending about Sonar in front of the most loyal forum users (Even if it´s pure shocking truth) and you will be labeled as idiot or "douche". LOL.īut I wanted to point out only a portion of what I was saying was quoted.ĭon´t worry. I've already been called a complete idiot tonight. Well I'm flattered that anyone agrees with anything I have to say.
I´m just a little more angry about losing precious time on finding that out.ĬW should switch to a 2 year release cycle, couldn´t be bad. Kind of an enless cycle in which many things never get the time they deserve. But this seems to lead to the next half year ironing out the serious bugs which leaves a short time to get the next release out.
Sometimes I feel as if there is too much pressure on Cakewalk to implement new features for the sake of marketing the next release and meeting the yearly deadline. So be nice and don´t call other people "douche". Automation runs very well in Nuendo 4, it´s in more than enough post production studios world wide including the one I´m buying all that soft and hardware crap for. And judging by your terminology you obviously even don´t know the difference between audio and midi tracks. Have you ever heard about using a template playing all Midi tracks at the same time? LMAO. You're obviously a douche, and I'm not going to bother with you any more.Ģ50 MIDI tracks sounding at one time? THAT´s about the most stupid thing I´ve ever heard. I've run over 500 midi tracks, with around 250 of them sounding at one time, and NEVER had it get out of sync, or give me a problem. Are you drunk or stupid? The first problem in the list is the problem with automation, and there are several.
0 kommentar(er)
