Cubase instruments12/23/2023 ![]() I'm have no idea how anyone can work like this. Sometimes, just clicking the active track in the arranger fixes the issue. When switching tracks has activated the track's record mode, unselected 'record enabled' makes the magically-muted track audible again. Then I paint some MIDI notes, copy/paste some blocks, and when I activate 'monitor' on one of the two tracks, the other is muted. Some combination of clicking solo/mute seemed to work. In any case, when no solo or mute lights were lit, only one track sounded. The problem started after muting one of the tracks, then accidentally muting the other, then using the 'all mute'/'all solo' buttons, which I may have clicked in an illogical order - maybe I clicked 'all mute' when my tracks were muted. Am now seeing the problem on a two track project. Started seeing this yesterday on a 20-track project. Only just getting into Cubase (after a break of 20+ years). Just in case more info will help someone (ideally the Cubase devs): But I'm prepared to go back to 11 just minutes after trying 12. So maybe I'll try setting it to high and see if it still happens. The issue does seem to be related to Asio Guard. The only thing that was different is that Asio Guard was set to normal in 12 rather than high in 11. Now they basically made it worse after fixing it! It's just madness because it worked fine in Cubase 11 after struggling with it in 10 and 10.5. Only disabling and enabling the tracks works and strangely enough - inserting a new plugin! Muting and unmuting doesn't fix it, the "constrain delay compensation" trick doesn't work. It shows the volume signal on the silent tracks but no sound is coming out.Īfter re-instating the audio driver and changing the asio guard to high some tracks started playing again but many others remained silent. It happening after soloing and midi editing on a track. I upgraded to Cubase 12 and after just a few minutes of working on a project, EVERY SINGLE TRACK except one went silent. Seriously, 10.5 seems to be even worse in terms of frequency. I mean, what are the odds that it's something about my setup when my setup has been completely replaced several times over now? It's a mystery, wrapped inside a shitshow. So while I have low confidence that anyone but Steinberg can solve this problem, I am very curious why no one else at VI-Control has reported it (I've searched and searched.) ![]() I've also done all the usual stuff to troubleshoot this -updating drivers, reinstalling Cubase (50x), deleting preference file, removing all plugins, etc. In fact, the only thing about my system that hasn't been completely replaced in the last 7 years is my mouse (I love this mouse.) ![]() I have, at this point, very low expectations.Īgain, in terms of troubleshooting, let me repeat: several different builds, different mobos, different Windows versions, different interfaces, different drivers, and seven plus different versions of Cubase. So I thought I would see what the wise and learned folks at VI-Control might suggest. (See here, here, and here.) I myself have raised the issue there multiple times over the years. This issue has been raised on the Steinberg forum many times, going way back. And sometimes, even that isn't enough for the corrupting element seems to survive the copy/paste process.Īs I've said, I've been living with this problem since version 7.5, which is what, 7 years now? I'm not the only one either. Sometimes not and the only remedy is to create a new track and copy the midi part over. I've discovered that sometimes, duplicating the track will (temporarily) fix it. Sometimes, soloing up the track makes it work again. I can even open the troubled part in the midi editor and trigger the VSTi with the piano roll or by clicking on notes.īut when I hit play, those same notes do nothing. I can still trigger it with my midi controller. Specifically, what appears to be happening is the midi part stops triggering the VSTi. Sometimes, a VST track will just stop playing. And it has happened ever since-through several different builds, different mobos, different Windows versions, different interfaces, different drivers, and different versions of Cubase. I first remember noticing this phenomena with Cubase 7.5. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |