Thanks! , and yes please I’d love to read that link!
I guess this is the post you’re referring to.
I had this issue as well but it seemed to have fixed itself. I am on a PC and did a bunch of outstanding Windows 7 updates and it went away.
I also discovered that if you clicked on the fader and held the button (even if you didn’t move the fader) the audio would come back but as soon as you let go, it would disappear again. The project did not exhibit the same issue in 8.0.3. So strange but it seems to be fixed now.
Thanks Grim. That was indeed it.
… I’m telling you today the ‘silence on automated tracks’ and ‘flickering when using slice/pencil/line tools’ issues are fixed in 8.5.10 …
From a moderator in that post.
Additionally, someone else posted that they heard (read?) from Steinberg that 8.5.10 is expected to come out within the next two weeks or so. That is of course 2nd/3rd-hand info to me.
But all in all, very hopeful and encouraging, in terms of functionality and communication.
Damn I’m getting this,and it,makes Cubase impossable to Mix in,this is really a drag,means I have to render all my tracks and export so I can mix in Pro Tools.
When is this going to get fixed?
BAAAAH… buggered again by the automation mute. Been creatively blocked for days… no time, no ideas, etc.
Finally have a minute, open a project, and get an idea. Start play hit a chord… POOF… sound stops on that channel.
Keep this thread alive and hot with reports people. It’s obviously on the list for a patch… but no reason to not report our “experiences” to the developers.
This is taken out of context. The moderator was saying he CANT promise the above as it might not be delivered when the software team deliver the update. However, I hope your right. Its a massive problem
I’ll add another footnote about this… Right now a project has the bug on just one track. Other tracks are not effected. I can duplicate the effected track, and the problem remains.
So this isn’t a project wide effect… apparently it can effect only one track at a time.
Also… renaming the project doesn’t help. Opening in 8.0.20 did fix the problem. I saved and tested with 8.5.0 again… the problem remains.
Can someone with 8.5.10 check to see if this is fixed now?
8.5.1 has not been released yet
I cannot reproduce the issue anymore with 8.5.10. Seems to be fixed.
Shouldn’t Steinberg be TELLING us its fixed? As far as I know, they have not answered ANY support emails on this subject, seemingly they have chosen to totally ignore anyone who has approached them about it. Bizarre.
Umm - it’s in the version history (pdf) file? It seems to me B-14887 (page5) and B-15605 (page 6) are referring to it?
I could be wrong though.
The update is released today, and is announced on the forum. You will probably see it soon in your start screen when you launch Cubase, so it will be hard to miss. I don’t know if they will send a personal mail to everybody that had this bug, but I doubt it. They would need a database about every bug and every user that has been “connected” to it to keep track of that.
I’m experience a different form of the bug. The problem will occur but not lock-out for the remainder of the session. Right now, I’ve been playing a piano patch and while recording or working in the key editor… sound will just stop for that channel.
BUT… hit stop. Close the editor or choose a different channel and return… sound is back to normal.
I guess this is another and different problem/bug than the VCA linked fader problem?
BON-14543 in the Cubase buglist is what I believe describes this, https://www.steinberg.net/forums/viewtopic.php?f=231&t=85575 .
I don’t see that as one of the fixes in the official Steinberg pdf document, http://download.steinberg.net/downloads_software/Cubase_Pro_8.5_and_Cubase_Artist_8.5/8.5.10/Cubase_8.5.10_Version_History.pdf .
So I guess that means it is not officially fixed???
I’m probably installing 8.5.10 next weekend, assuming I can do the trial (I’m not sure if the trial is just for 8.0, or 8.10). If so, I’ll check it out and if it is fixed for me will post back here.
This is officialy fixed. Both issues are linked (the same, in fact).
Thanks for that Martin! I see you’ve posted that you no longer have the bug. Is it listed in the Steinberg website or official .pdf of bug fixes, that BON-14543 was fixed?