poop

As Gomer Pyle used to say: "Surprise, surprise, surprise!"

Only 4 months to go before the "fix"

According to what Steinberg has officially announced way back when, we shoud be seeing an update with the fixxes in the next 6 to 8 weeks.

Hummm, Now it is the end of July maybe later.
You posted this on the 12th of April. Now the 21st of June.

Doesn't sound very promising. It never does.
The extended waits often disappoint.

It is really, really sad.
So close, yet they just don't get it.

LEX

This thread needs to be DELETED as it is OFF TOPIC.

Nuendo solo/mute getting fixed ?? Oxymoron?? I dont think this issue is real since I use Cubase

Off Topic???? I think you're the one who's off topic! Working for them now or something? There is plenty good reason to keep this thread alive seeing as how they are now saying the fix is going to be later than promised.

Must be a little THICK upstairs. Re-Read my post there bro

Pre-caffeine retort........ sorry dude.

That's a good question. LOL.
I am on Cubase 5, and here's how it works here: the SOLO button, if activated in the project window, or the mixer, by mouse or control surface, doesn't mute any other tracks. However, an automated mute, will mute the track or other function. Sometimes automating 'mute off' can fail in a mixdown, but this is remedied by making sure the inspector and/or mixer SOLO button IS ON, for a track.
SOLO means, 'track on'. 'Soloing a track' is meaningless, as it causes no muting of other tracks. It DOES mean, 'mute off' in MOST cases.

I'm literally stunned to read this. What kind of mixer won't allow you to SOLO your tracks? This limitation would truly hurt my mixes.

Absolutely unacceptable.

Laser

Yup. ANd it took months of petitioning before they would even acknowledge the problem and another 8 months for them to fix it and counting.

If my timeline is correct (and, I'm not sure it is), the acknowledgement came during Nuendo 4, but BEFORE the release of Cubase 5.

And, IF my timeline is correct, this means Steinberg released Cubase 5 knowing they had this limitation. If true, this is as bush-league as it gets.

I'm beyond stunned. Please, tell me I'm wrong.

Laser

I tend to agree! I work around it, I automate any muting, but in mixing it's a slow go some times to have to mute couple dozen things to hear something solo'd. I don't think the bug behaves exactly like this on other systems, I have seen it described very differently, but, that's a caveat emptor thing if there ever was.

I think they can't find the lines of code where it went wrong.

OOH, and you'll love this: a lot of tracks will show both mute and solo buttons lit up! Even where the track does either as you want it to, it's hard to know just by a visual!

You're partially wrong. As far as the timeline goes it's actually worse than you think.....

So I have NEVER had this issue at all. I use N4 and solo and mute all of the time, both from my control surface, and with the mouse. I do this from the project window as well as the mixer window. I use command click for a/b style soloing, which also works exactly as expected. I have very minor issues with solo occasionally not soloing an fx return, but no issues with mute.

This must be heavily influenced by workflow.

Here are a couple of things that I believe minimize the appearance of and "mute/solo bugs" (I am not saying that these are things that anyone else should or shouldn't adopt as workarounds, I am simply saying that I think these things seem to make the issue less obvious):

1) I, as well as several others I have run into seem to use mute and solo differently than most people here. I NEVER use mute or solo as a mix function. For me, Mute, Solo, and Listen are just tools used to aid the mix process. If there is a mute or solo on, I forgot to unmute it. I have lost track of what is temporarily muted and what is permanently muted too many times to trust the mute button anyway. (also, #2 works out really well...read below)

2) Using Key commands for clearing all solos, mutes, and listens. This seems to really help me. It offers an easy way to reset the mix to the normal state. (This only works if you are using mute/solo as described in number 1)

3) Control Room. I could be way off on this, but it seems to me that using control room minimizes the effects of this bug.

You guys are probably gonna hate on me a lot for this, but please understand that I am in no way saying that this is even remotely acceptable behavior. I'm only saying what has worked for me. Also, while I don't agree with the amount of time it has taken to resolve this issue, to my understanding, this was a VERY deeply rooted bug with the actual logic used to decide what should be soloed/muted. I spoke with someone from SB who said that they had hoped to include it in 4.2.2.274, but that the problem was much more fundamental than originally perceived. Once again, I am not siding with SB, nor trying to make excuses. Just sharing what I know to try and offer perspective.

Peace,
Brian

....ummm, if I'm partially wrong, which part of my post was wrong?

I'm really trying to determine what I'm dealing with. I was seriously considering switching over to Cubase 5.

Any way you can back off the rant and just share facts?

Laser

Thanks, Brian. I appreciate you approaching this from a fair perspective.

You do realize that very few people mix without using the SOLO function on a regular basis. I can't believe that one of the top DAWs in the industry can market a serious product without this functioning normally. What next, broken faders?

Laser

The solo/mute bug was first reported back in March of 2007 I believe.

Thanks, Animus. Obviously, Steinberg didn't give the report the attention it deserved. Frustrating, but most of the DAW manufacturers have been guilty of this at one time or another--though I admit that 2+ years is ridiculous.

What is REALLY concerning is IF they acknowledged the problem before the release of Cubase 5, then didn't address the problem before releasing it. I'm sorry, I just can't do business with a company that would do this.

That's why I'm curious. Any insight on this?

Laser

Yeah they knew about it before Cubase 5 came out but didn't fix it in time. My only insight is that this is just the way Steinberg is. I have been using their software since 1997 and it's always the same. I like the software a lot however so I just grin and bear it.


I might have been wrong about March 2007 btw. It could have been March 2008. It was a few months after Nuendo 4 came out whenever that was. I am getting old and time blurs.

Animus,

It wasn't March 2007, N4 wasn't released until late September 2007 , the first report of the solo/mute issue was within the first few weeks of release , by LEX from memory..

It didn't pick up momentum until early 2008 tho.., I agree , its all a blur from there on in... :-(

Well I use them all of the time, for WORKING on the mix, and listening to the channels independently, but never at mixdown.

Do you do a lot of group solo for post stuff? I use Nuendo mostly for music and find no use for mute or solo during mixdown. I always mute events if I am not going to be needing that part in the arrangement. Muting events is much more straight forward because you know exactly what you are hearing just by looking at the events on the project page. It's also harder to accidentally undo. (Once again, I'm not telling anyone how to work, just sharing my workflow to try to figure out what makes this bug so bad for some, and not so bad for others.)

I'm probably not as frustrated because I have not been using Nuendo since forever. For the way I work, I never experience problems. I solo ALL of the time, way more than I mute, surely hundreds of times a day. N4 always solos correctly, except for the occasional fx bus not being heard.


You guys have apparently waited for years for this to be fixed. Why sweat it now when it has been confirmed to have been fixed in the next maintenance update due in a month?

I agree it's total BS that it has taken this long, but if you are still using the product after it being broken for this long, there's really no room for complaining IMO. I mean, the problem obviously was not compelling enough to cause you to find a better solution. Compared to how long you have already waited, the fix is literally just around the corner.

No disrespect, but to me, having switched from crApple ilLogic 8, Nuendo is such a breath of fresh air that I guess I haven't started hating it... yet...

This should be Steinys slogan Love the app, hate the company

Real soon you Nuendo guys won't have to worry because Presonus Studio One will be out soon. This is the way to go.

You missed the relative part about how you have already been waiting for over a year (unacceptable)... I totally agree that this has taken way, way, way too long, but why bitch now when Steinberg is already testing a beta in which the bug has been fixed?

Maybe for the project studio, but commercially, I think it has a ways to go.

There is no guarantee it will be fixed, or fixed completely. Another bug was listed as "fixed" in 4.2.2, but the build either didn't include it, or broke it, so it wasn't included in the actual release (just the release notes).

Was Nuendo rebuilt and released with that fix the next day/week? No. It was simply rolled into the next development/fix cycle for the upcoming release (I assume, may not have been included here either).

Any normal software company would have rebuilt within a day or two to include that bug fix, but not with SB. Like bird migration, they only build fixes once a year, so we had to wait until the next season. That's a year for a fix that probably took 20 minutes to integrate.

Why be confident when history keeps teaching you to expect the very least?

I see your point. Like I said, I am pretty new to Nuendo/Steinberg, so I lack some perspective... Thanks for responding.

Peace,
Brian

Strange I have Nuendo 4 and Solo/mute works just fine ...