scoco

I'm having this problem using a MOTU 8Pre ES. Didn't used to happen. Like someone said, it happened after going to the paid version of Sonar. I haven't noticed it happening except when I'm recording inside a loop. Like someone else also mentioned, I make the loop wider than the record punch-in range. And I do NOT want anyone telling me I shouldn't be doing that. I need an audible cue in order to play in time as the punch starts. And I want to extend the loop past the punch-in range so I have time to hit Stop before the loop returns to the start and creates an unwanted new take and mutes the take I really wanted to keep. That's how I work. That's how I've always worked. @David Baay did you resolve this problem?

Mark, You mentioned the Korg nanoKontrol remote surface. After reading about it I decided to ditch TouchDAW and get a nanoKontrol. It took half a day to resolve a problem caused by the nanoKontrol being registered in Windows as MIDI device #11. Korg's driver apparently had to have it in the top 10 devices. Once I got it working with Sonar I realized how much easier it is to use. Almost everything about TouchDAW confused me. So I just wanted to say thanks for the tip.

msmcleod - thanks for the insights. Yes, if I had known about that and assigned the the TouchDAW Master fader to Sonar master faders, I would have seen the problem much sooner. I really would like to be able to use TouchDAW with Sonar because I record a lot of tracks alone (and it usually takes me a bunch of takes to get what I want). But since I posted about this problem I have had constant problems with Sonar locking up or stuttering or audio completely dropping out. After my initial discovery, I deleted and added a new Control Surface instance for TouchDAW. When I deleted that new one, Sonar started behaving again. Do you have any ideas about other settings that might be tripping up Sonar, even when the Android device is turned off?

Thanks to all for your replies. Here an update: It looks like I was able to resolve the problem. I got to thinking about what was different in my setup and remembered I recently had set up a Mackie ACT control surface and connected it through rptMIDI to my Android tablet. TouchDAW is installed on the tablet. When I deleted that entry from the list of control surfaces in Preferences, the problem stopped happening in all the projects I opened and tested. It might be worth looking into on Bandlab's end, but I'm good to go at this point (with this particular issue - there are many more).

Today, out of the blue, I noticed that Sonar's output level to my MOTU 8Pre ES was lower on left. In the MOTU's interface I could see the difference on the meter coming "from computer." But in Sonar the levels were equal on my master bus. I usually hide the hardware outputs in my console view. It wasn't until I looked at my hardware outputs that I saw that the left fader was set at -8.7. I right-clicked on the fader and saw a line that said "Revert to -8.7." But I can find no way to remove that setting. So, with any Sonar project loaded, I can set the fader to 0 before I hit play but it jumps back to -8.7 when I stop playback. How can I eliminate that "Revert to -8.7" setting or otherwise fix this problem? Hardware Fader Reverts on Stop Video.mp4

That's good news! Thanks msmcleod.

Thank you, Chaps. Sometimes I feel like the support people have me jump through hoops to fix a problem and never even try to reproduce it themselves. If the problem is in Sonar, none of that activity is going to do any good and it wastes time I'd rather spend on something else.

Sometimes I need to be able to select only non-zero track volume nodes in the automation panes and move them to change levels in a limited portion of a project. I used to be able to right-click and draw a selection area (lasso) around nodes that I want to move as a group. Up until the last few months that worked fine. Now if I select any node at all in the automation pane Sonar immediately selects ALL nodes within the time range of the associated =clip= in the audio track. I have to manually ctrl-click to select every node individually now. This problem doesn't happen in buses - I suppose because buses have no audio clips in them. I created a support request for this problem. I spent a lot of time troubleshooting the problem as I was directed, but nothing restored what used to be the default behavior. I believe that the problem is in Sonar, not in my installation or configuration. Having followed so many steps to fix the problem, I feel sure it would have been fixed if it were in my particular setup. My original request was marked resolved, but this problem persists and I created another support request and am waiting... Is anyone else having this problem? Right-Click-Drag Node Selection Not Right.mp4

I have had this exact issue at least since May, 2025. The number of Alt-Tab boxes varies. Most of them seem related to one plugin or another. I submitted a request about it. Jumped through the usual hoops - re-installing Sonar and taking screen shots, etc. Never got a resolution. And with other flakey stuff happening with my Sonar I can't help but wonder if it's related to this issue.