Adam Posted February 17 Share Posted February 17 (edited) @Noel Borthwick Hi Noel, I thought I'd move this topic to the correct forum now that I'm using the latest version of Cakewalk Sonar. I've attached a short screen capture where you can see this problem occuring. Trying to record a guitar line and a mic'ed up amp, and, you can see the guitar line just disappears once I hit stop. Anyway, issue pasted below. Hi all, I've been experiencing a frustrating and increasingly frequent issue in Cakewalk Sonar where record-enabled tracks seem to be tracking during recording but disappear once I hit stop. The issue isn't consistent across all tracks—sometimes, I’ll record multiple tracks simultaneously, and while some tracks capture properly, others fail to record at all. A few key details: The issue occurs intermittently but has become more frequent over the last six months. There are no punch-in points set elsewhere in the project that could be interfering. The waveform appears while recording, as if the take is being captured, but as soon as I stop recording, the affected track(s) are empty. There is no record of the track in the recording folder when I checked afterwards. It happens across different projects and isn’t tied to a specific template or setup. I'm working in a professional studio environment, so this is becoming a serious problem for sessions. Has anyone else encountered this? Are there any known fixes or workarounds? I’d appreciate any insights or troubleshooting steps you can recommend. Thanks! Adam 2025-02-17 10-55-22.mkv Edited February 17 by Adam Link to comment Share on other sites More sharing options...
Guest Posted February 17 Share Posted February 17 (edited) oOK Edited February 22 by Sock Monkey Link to comment Share on other sites More sharing options...
Adam Posted February 17 Author Share Posted February 17 (edited) It's not equipment related: I use multiple DAWs and Cakewalk is the only DAW that behaves like this. I have an RME Madi FX PCIe interface which connects to three individual Orion32 interfaces via MADI. Edited February 17 by Adam Link to comment Share on other sites More sharing options...
Adam Posted February 17 Author Share Posted February 17 http://forum.cakewalk.com/Recording-Disappears-m3776475.aspx - Here's an older post where a lot of people were having the same problem. @Noel Borthwick Link to comment Share on other sites More sharing options...
Noel Borthwick Posted February 18 Share Posted February 18 On 2/16/2025 at 9:47 PM, Adam said: It's not equipment related: I use multiple DAWs and Cakewalk is the only DAW that behaves like this. I have an RME Madi FX PCIe interface which connects to three individual Orion32 interfaces via MADI. You can't assume that necessarily. Its not that abnormal to have an issue which is driver or system related that only shows up with one DAW. Not saying that that is the case here but there is some environmental issue that triggers this that obviously most users never see. So you stop recording, the recording appears and then spontaneously disappears shortly afterwards? If you watch the wave data folder in file explorer while recording, do you see the file get created and then removed shortly after? Another thing to check is your recording drive. Check for disk errors and also check if you have any software (such as one drive) monitoring the folder where audio is recorded. If a program locks the file it can fail recording. Most of the times where people have encountered such issues it has been related to problems like this. 2 Link to comment Share on other sites More sharing options...
David Baay Posted February 18 Share Posted February 18 (edited) On 2/16/2025 at 7:47 PM, Adam said: It's not equipment related: I use multiple DAWs and Cakewalk is the only DAW that behaves like this. I have an RME Madi FX PCIe interface which connects to three individual Orion32 interfaces via MADI. I notice the transport module in your video is showing the record bit depth is 32...? A quick Google confirms the RME is 24-bit. Any particular reason you have it set to 32? Whatever the reason, I would suggest changing it to 24 to eliminate that as a possible cause. Edited February 18 by David Baay 2 Link to comment Share on other sites More sharing options...
Guest Posted February 18 Share Posted February 18 (edited) ooK Edited February 22 by Sock Monkey Link to comment Share on other sites More sharing options...
Noel Borthwick Posted February 19 Share Posted February 19 Recording at a higher depth that the interfaces provides is just padding silence. 2 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now