![]() The first time I encountered this, I did actually restart my audio device, despite its only being one track that was affected, but it did not make a difference. If the track is selected, it becomes record enabled so it becomes processed in the real-time. After he restarted his Audio Device all was working. ![]() The user was able to hear all Instrument tracks but none Audio track. That makes me think there may be some uninitialized variable somewhere, and, instead of finding a “zero” (or whatever the initial value should be), it finds some other state that is still cached in memory after the Cubase restart but gets cleared by the reboot. It was feeling like something was corrupted in the project, though I don’t know what that would be, nor why it would come back to functioning correctly after a reboot but not after a Cubase restart. I didn’t mention it earlier, but I also even tried creating such a new track and, instead of copying the data from the track that was already in the project, copying the data in from the Pool, and it still had the same issue. And I did try that stuff, just in case, but no go.Īnd, in the past, when there’s been an issue of just one track not sounding, I’d been able to create a new track and copy the data from the old track across to that, and the new track would work, but that is not the case here. Perhaps I’m missing something, but if it were a device going to sleep (and, FWIW, my device is MOTU 828x running with Thunderbolt, not USB) wouldn’t that affect all the sound for the project, rather than just the one track?Īlso, when I have seen past issues where everything was showing up properly in the meters, including for the Stereo Out, but there was no sound (and this could happen instantaneously while running the project, with no time for a sleep-type timeout elapsed), I found I was able to bring things back to normal by either power cycling the interface or, less obtrusively, just changing the sample buffer size temporarily, both of which must have reset whatever was messed up in the communication between Cubase and the ASIO driver (or somewhere lower in the device driver’s logic). ![]() But this is a single track, not the whole project – the rest of the tracks play just fine. In the past, I’ve seen problems where sound from an entire project stops while meters are still showing output, but I’ve always been able to cure that by turning my audio interface off, then turning it back on. Has anyone seen this? Any clues? It is pretty annoying as often take a dinner break then resume work after dinner, and my system takes a very long time to reboot, so I don’t like to do that other than at the end of an evening. This feels to me like something is getting corrupted, and somehow doesn’t get back to normal despite trying various things. That is, until my dinner break, after which the same situation recurred. I even tried opening older versions of the project that had been known to be working, as well as closing the project, and even closing Cubase, in between, but still no go.Īfter giving up last night, I shut my system down for the night, and everything was back to normal today. I tried last night to find workarounds, such as changing the routing temporarily then changing it back, even creating a new track and moving the audio events from the Lead Vocal track to that new track, but no go. And it has now done so two nights in a row! ![]() No changes were made in the interim, but when I came back (after a dinner and practicing break), this situation arose. Here is a key, though: Things were working properly before I took a break of maybe an hour or two. This is particularly weird in that it shows StudioRack is getting the input of the track in order to process it, yet it isn’t passing the dry part of the signal. What’s more, if I enable one of the Waves Studio Rack plugins in the LdVoc Submix group track, I will hear only the wet portion of the signal, not the dry, original signal. (Note that, if this track is not soloed, then the rest of the tracks in the project are heard just fine, and they also route through the Stereo Out.) There is no actual sound coming from the Stereo Out, though, despite the seeming signal. (But the solo doesn’t matter in terms of whether this track is heard or not). ![]() To summarize, a mono lead vocal track, with a stereo output, is routed to a Lead Vocal Submix stereo group track (currently with all plugins disabled), which is then routed to the Stereo Out.Īs you can see, the meters are showing signal on all three tracks at various levels, and I have the tracks soloed so as to only hear what is coming from this track and its downstream buses. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |