Ok. I’m not sure if that says anything counter to what I was trying to say. When I’m saying it’s fine for mid level work what I meant was that if you have a medium size project in a medium size facility with a medium size team it’s all fine as long as everyone is using the same DAW. Once you start moving into bigger budgets and scopes you start running into problems using Nuendo. I’m not saying you can’t work around whatever it is that Nuendo is lacking, I’m saying that people see no reason to work around it when they can just use PT instead.
So like I said, practically, can you do high-end work? Obviously yes. Will most high-end work be done in Nuendo? Doesn’t seem like it.
Not calling PT the industry standard doesn’t change much. It is what it is. Plenty of PT users are fed up with its problems (no DAW is perfect) and many are fed up with Avid. I’ve seen people thinking about switching and I’ve seen people who use Nuendo in post-production circles.
But regardless there is still a bit of a problem. When you have a big budget / large scale job you want the best people you can get for the money. A larger pool of available engineers means higher odds of finding those people. PT has a larger user base. Then you have to consider the “width” of the job. When I said mid-level earlier I count myself in that category, doing mostly one-man jobs. If it’s a theatrical fiction feature motion picture the audio team is going to be really large. You then probably want them to all be on the same DAW because it’s easier.
Then you’re also stuck with the questions you get as a Nuendo engineer trying to advocate Nuendo to PT users asking about differences and thinking about switching. What about “glide” automation? What about speech-to-text? What about this? What about that? When they ask about “clip-effects” and I tell them about the theoretically superior (?) DOP what is their reaction when I add “Oh, but also, you get clicks if you use some plugins because the function to extend processing beyond event boundaries is broken… oh, and also RX plugins, the ones everyone uses, break functionality and can screw up a timeline of thousands of processed events… so like, be careful using it”? Or when I say “Yeah, we got a way to punch to loop. You just enable Preview, set Fill to Loop, capture automation data, press Punch, and it’s written to Loop. Just make sure you don’t locate on the timeline by jumping to the next event boundary before stopping playback like you might normally do all the time because if you do the “Fill Loop” command will remain lit and even though you proceed to write in Latch one minute later in the timeline it’ll write that automation to the loop range, which can suck if you’re not aware of it”… (got a client note on that this week… thanks Nuendo)
Any single “issue” that seems ridiculous (and those are) will be a reason for PT users to shake their heads and stick with PT. Yes, I understand that there will be similar things in reverse, but then again that wasn’t the point here, the point was increasing the Nuendo user base.
I’m just a bit tired of the lack of official participation here, the lack of fixing clear design flaws, clear bugs, and being behind on significant functionality.
“End of rant”.
PS: that was a bit of an uncontrolled stream of consciousness so probably some of it could have been worded better.