Nuendo 5.5 Update Q2?

Aha, thanks. I’ve been watching the “Announcements” section on this forum to see if there was an update. I see what you mean now. Looks like an update to accomodate Nuendo Live. Oh well, who needs to import an AAF nowadays anyway?

That’s a joke, right?

Ollie

This update is a complete joke.

…we are currently working on some AAF Fixes, which slightly delay the current maintenance.
Still we hope to be able to provide the next update before Christmas.

This was in December 2011.

Ollie

I was hoping to finally upgrade my Nuendo 3 to 5.5, but without proper AAF support I see no reason to do so at this point (since I already have Cubase 6.5 for all the “music” production needs). I wonder who is really the target customer base for Nuendo? Why the AAF support has been neglected for so long?

Well, AAF kind of works pre 5.5 so you can still upgrade to 5.1.
Success seems to depend on the version of AVID you are using.

Wow…

if this update is a joke, and it sure seems that it is, who is the joke on?
Steinberg or Nuendo Users?

Wait, are you guys saying AAF functionality got worse after 5.1?

At least if you want to import from media composer 5.x the answer is unfortunately yes.

Whenever I get an AAF I fire up 5.1 and import it. After saving it I load 5.5 and open the project. This works most of the time. If all fails I have copies of PT 9 and Pro Convert.

I must admit that’s pretty ridiculous for a DAW made for Post. One would assume AAF import would be top priority and would be fixed in a matter of days or weeks, at the most…

That is exactly my workflow. (don’t have pro convert, though)
It’s extremely annoying if you work on a project that comes in many seperate clips.

Ollie

Let’s hope for an AAF fix soon. Steinberg can’t just ignore the fact that a functioning AAF import is of paramount importance. Without it we’re dead in the water and we’ll have to turn elsewhere. They’re lucky Reaper doesn’t do OMF or AAF import, for now…

So what happens if you try the later versions?

I’ve had all sorts of strange stuff going on:
Just one track with one file of audio or takes out of sync. But to be quite honest it’s almost to long ago for my brain to remember correctly which errors occured. AAF has been buggy for a year now.
I cannot believe they don’t fix this with highest priority.

Ollie

not a good idea shortly before the N6 release… imho

Define “shortly”… :unamused:

I’ve honestly not had problems with soloing since they overhauled it big time a while ago. I’d suggest asking around to verify that it’s an actual problem with the software rather than you not liking the way it is designed. In the latter case a change of workflow would solve your problem (except that you have to work differently).

As for laying of stems/splits specifically I can highly recommend making use of the batch export in conjunction with Control Room. Setting up a “template” for this saves time and it’s a really really fantastic feature in my opinion, one of a few that is so great that had it not been for a few missing features Nuendo would be WAY ahead of PT in my opinion.

PS. I’m not writing this to tell you you’re wrong in any way, just to offer a thought on how to be more productive with the tool you have.

I expect 1-4 months? There were hints for N6 to come this year…

I was just in the same boat, and did roll. The thing is hope. I had no hope things would be any better based on history of Nuendo’s development cycle plus the value would drop if I was one version prior and wanted to sell it. If you have hope that things will get better after experiencing the contrary, awesome. The other thing is $$$$. N6 will cost something but you could demo it I suppose and save your money for the upgrade or move to a different software it the demo doesn’t perform too.

As far as stems goes. the batch export in Nuendo may be the ticket for you, Headlands. That is a feature I miss but M.E.A.P. gets me there mostly if I am using Cubase.

There is no price for piece of mind. If you need to move somewhere for it then you should. Especially if the software is more transparent to your workflow. If you haven’t shared your issues with the user base here, you may want to do so because other people may have a workflow you can adapt to that will ease your troubles and rebuild your confidence in Nuendo. If I was in your shoes, I would at least demo Nuendo 6 and see if things improve and demo the avenue you are considering right now which for me was exciting, eye-opening with a bit of adaptation. If Nuendo 6 is solid with your work flow then you are good. If it is buggy and doesn’t suit you, you know at least you will be waiting a number of months till the maintenance release is available, which seems to be the status quo, and even then there will be major questions of what will be fixed. Look at the last release.

Good luck, Headlands.

Nuendo has 3 levels of solo (SIP/AFL/PFL) which can lead to some confusion. The SIP solo is semi-intelligent in that it will try and take into account the signal flow and open up the appropriate channels.

Where some people claim that it’s broken is when there is convoluted routing going on so what the user expects might be different to what the software is guessing should be soloed. The way to ensure that what you get is what you expected is to make use of things such as solo safe for effects returns, various preferences which mute source tracks to groups etc.

For running off stems I have either made use of the features offered by the control room where you can monitor multiple stem tracks at once (thus hearing your full mix) and then when you’re happy just batch export the stem groups, or alternatively group things into folders and then mute the folders you don’t want to hear (effectively putting the ones you do want to hear into “solo” but without any unexpected results).