[ISSUE] NUENDO 6.0.3: REALTIME MIXDOWN LOUDER?

One more confirmation here.

Did you guys try rebuilding preferences?

(Sorry for harping on about this. I understand it was probably lost or overlooked among the posts by the many SB employees chiming in on this)

sorry for being slow-witted: what do you mean with “preferences” ?
My project templates or the complete N6 App preferences ?

As for the templates: yes I always rebuild my templates after installing a new N version

Actual app preferences.

Trashed prefs. Still 6db louder on output.

Same situation, Guys form steinberg please, please check your products before upload it for us. I can;t belive you don’t do at least one mixdown for try if everythink is ok.

I lost few hour of this day with this fake!

:frowning:((((

No, the exported file is correct, it affects only the playback volume during the mixdown

I like your idea of having them check the software before they send it out. Heck, they might even want to check to make sure boxed version and download version is the same.

+100

Maybe the community should give them the time, then, to check e v e r y t h i n g ?
How about a Nuendo 6 release around 2015? As I see it now, N6 is comparatively well engineered and stabil.
For me, there are no real showstoppers in it, at least not for my shows…

And it couldn’t, since I have never been so valiant to install major upgrades on my
production machines, right away. At least, I don’t use them for production before
I know them well and the usual bugs have been revealed and fixed, like this one will be, soon.

I am quite sure that the first forum members are already copying and tweaking some of their older posts to read:
When will Nuendo 7 be released…(.LOL …). We need it urgently, because Cubase might be a millisecond earlier
on the market and all world breaks down …

:wink:

Big K

But in this case it worked with the initial release of N6. This error was introduced with the update…

Dude, seriously, you don’t think it’s an issue that realtime mixdown plays back louder in a flagship DAW for post-production? Or you don’t think it’s an issue that it works and then gets broken in an update?

I’m all for supporting software and being realistic, but what people are doing in this thread is EXACTLY what you’re proposing: They’ve waited for the previous “lesser” versions of Nuendo 6 to go through “maturation” - remember the release was 6.0.2, not .0. So we waited while Cubase users beta-tested the basic sequencer for us “in the wild”, and then we got our first release, bugs and/or issues were reported, and SB was pretty good at addressing them.

But it is NOT good to introduce issues in updates. Either someone is completely ignorant as to how people actually work with an application, or their testing is seriously lacking. (And seeing that they released seemingly different actual code in download versus boxed initial release, despite same naming, it’s not unreasonable to worry about their internal testing/validation). Many people will mix a show and then audition the “final” version while it runs in realtime. Imagine your outboard gear receiving a higher level once you start your realtime render.

I might have cut people some slack if this was the initial release with a fix coming shortly thereafter AND if someone at Steinberg thought it was worth their time to at least acknowledge that there’s an issue here.

Now? Not so much.

I overall like what I’ve seen of N6 and would be using it now. This bug is keeping me from doing that.

I might get this whole problem wrong…
Isn’t there the “export audio mixdown” fader popping up for adjusting the “audition volume”?
If this bug affects only the playback during realtime export and not the exported file, which is 100% o.k.,
why don’t you just pull the fader down to your liking?

Please explain, if there is more of a problem to it …
:question:
Big K

OK, if this is crucial for your work you have all the rights to be miffed.
Of course, introducing a bug to a new version is not in order.
I haven’t seen the problem for myself. I listen to the final mix and then export it
w/o listening to it. Instead, I check the whole works / the exported file thorougly afterwards.
I understand,for some tasks this might be just too time consuming.
Anyway, I am sure they’ll fix this a.s.a.p. and someone there will have to pay extra into the coffee box.
:wink:
Big K

I spent all morning seeing if I was missing something and came up with nothin’. This is a big deal for those of us who have to hit a certain spec for our deliverables.

In all honesty, I’ve never exported and monitored at the same time. Or if I have, I’ve dimmed my monitors.

For me the spec measurement is happening either when I print, so there’s no monitoring issue (and it’s realtime just like the export monitor), or after the file is completed I will drop into Dolby MM and run a faster than realtime measurement at that point.

What spec is dependent upon the volume that you’re listening to on export? I totally get that it’s disconcerting that the output monitoring volume changes from when you’re mixing and when you’re bouncing - this should work correctly. I’m more curious what measurements are being taken during the realtime export that is being monitored? SPL?

Personally, I think we all should get used to initial software releases being buggy - they always have been, and I think they always will be especially with the demand for bigger and better things. I’m running N6.0.3 on 10.7.4 in 64-bit, but have my N5.5/10.6.8 32-bit partition ready to go.

I’m not defending Steiny, but I certainly think we, as Nuendo users, have far more ears on what we’re asking for/what needs to be fixed than other communities. Feels like we users play a bigger role in the R+D for the next versions, and that has much value to me.

Cheers all -

kp

Some people will have metering on the main output. They may or may not use Control Room. So anyone who is checking the playback/render is going to have all levels all off. And I expect it’d be a rude awakening if you mix everything, take a break during which you “reset” your ears and “lose perspective”, then come back and everything seems way loud. What do you do at that point? You have to stop and investigate. Wasted time.

Why are you talking about “initial releases”? This is 6.0.3.

I think it’s not only reasonable to expect each update to improve upon the previous version by fixing bugs, but I think it’s fair to get a comment when crap breaks during an update!

What does this tell us about QC?



Break a key-command: I can work around it. It’d be annoying and would slow me down, but it’s just a key command. Monitoring and levels should NEVER be messed with. EVER!

I think it is sad that this get’s through the last QC test.

But let’s try to find the problem.
To temporarily test with clean prefs, hold down shift-alt-cmd (OSX) or shif-ctrl-alt (Windows) to get a menu allowing you to start N6 with clean prefs (one time only).

Let’s check if this +6dB on realtime mixdown listen volume problem still is there.

Also check project setup (shift+s) to see if you use the new +12dB faders or the old +6dB faders.

Pål

I understand the idea of losing perspective in that way, I just haven’t been subject to it as I neither monitor nor measure exports in this manner. But I think I see what you’re saying. Instead of asking them to fix the fader, why not just get rid of it completely so that it’s nulled? Is there a need for it? A bypass box to click?

In regards to 6.0.3 - I was referring to Nuendo 6.0.x as being the initial release with later versions (6.1 and forward) to be the versions we should really consider the first “stable” versions. That’s why I’m talking about initial releases. I don’t think it’s right, but I think that’s probably the reality moving forward. Perhaps I’m mistaken - I do not write software.

We can all assume even Steinberg doesn’t believe that monitoring levels should be messed with and wouldn’t release it this way if they knew of it. I would hope, and I believe we will, hear about a fixer update that will address this problem specifically. I would hope, even more so, that we hear from Steinberg on the plan, and that you all receive a response, which hopefully they are strategizing for right now. STRATEGERY!

Cheers all.

kp