Ted Raven

Back to my issue: It really IS the Focusrite Scarlett, even with the latest drivers and firmware. I tried the Tascam US-16x08, which I usually only use for recording, not for playback and it sounded fine. The only question is, why it hasn't happened with CbB.

Yes, I totally understood this, except for being a new user (I use Cakewalk/Sonar since more than thirty years), ok, to this new Sonar, I am a new user, indeed. I just stated, that I then have to create threads for every issue, which I am completely fine with but which seems to have offended @Salvatore Sorice for reasons I don't understand.

I am only writing pure facts. It is a fact that I can never be sure if a problem already occured in previous versions. What is unfriendly in saying that?

Since I cannot be sure in any case, I have to open new threads for everything. No problem.

If THIS release is the first Sonar release I have installed, how should I know, if an issue occured in earlier versions?

Many thanks @msmcleod, with this information it seems that the source of the Problem is either one of my USB hubs or the USB controller of my mainboard. But I'm still wondering, why other DAWs, eg. Cubase, don't have the issue. Well, I'm going to try a different mainboard with a more powerful USB controller as soon as I can.

Ha, good point. I actually haven't tried yet if it happens when I start the playback anywhere later than 1:01:000. Audio interface: Focusrite Scarlett 2i2 3rd Gen. Driver mode: ASIO. No Fade, no CCs in the track at all (only one track). I will disable the 64-bit mixing engine and try. I will also do the reset (though I have not changed much in the preferences yet). So I won't need a config backup. Thanks for your help.

But I don't have a 16-device limit in Windows, I have a twelve device limit in Cakewalk/Sonar. In Windows, all my USB devices are being recognised, which are many more than 16, and work perfectly well. Only in Cakewalk, there seems to be a limit of up to twelve MIDI devices.

It's old, I know. @scook, I always run MME. The problem still exists. It's not, that particular devices won't be recognised. When I attach, say, sixteen MIDI capable USB devices twelve of them are being recognised. I disconnect any of these twelve, restart Cakewalk/Sonar, one of the missing four will be displayed in the list instead. So all the devices work with Cakewalk, just not at the same time. I want to connect my USB MIDI capable synths, MIDI interfaces, and controllers via USB. Quoting Rincewind: "That doesn't work!"

I don't have this issue in CbB nor did I have it in any old Sonar version. So it cannot be a hardware/driver issue nor an old issue. Also, it happens with or without the use of plug ins. And even with only MIDI tracks. 2025/08 is my first version of the new Sonar, so I cannot tell if it happened in previous versions as well.

When starting to play an audio track, the audio engine starts along with the audio playback at mesure 1:01:000 resulting in an audible click noise. Suggestion: Delay the playback for about a quarter second after the audio engine has been started (which is the solution, other manufacturers use and also solves potential MIDI timing glitches in the beginning of a track). Of course, I could place my audio from mesure 2 instead of 1 but that would interfere with the time an measure numbers, unless there was an optional delay, that lets the track begin with measure 0 instead of 1 and still starts the time with measure 1.

Many thanks, @Wookiee, it worked. I wasn't able to find this in the manual or a tutorial. Thanks again, you're my hero of the day.

1. I create a virtual instrument track with IK Multimedia Modo Drum, actually an instrument track and a related MIDI track. When I play or use the piano roll, I can hear the drums. -> Fine 2. Since there is only the piano roll, I change to a drum map (on the MIDI track output I select New Drum Map and select the desired drum map from the list. When I open the piano roll, the drum map is shown but I cannot hear the drums anymore. The instrument track seems to got disconnected from the MIDI track. I tried several thing like renaming, deletion and re-creation of the tracks and so on, without success. Is this a bug or am I doing something wrong? Btw., nice move showing the note names in the piano roll.

So I take it, that you are not going to implement DAWproject into Cakewalk to get in touch with the outer World?

Hi How great are chances that Cakewalk Sonar will support DAWproject import and export soon?

I completely forgot that I opened this thread. So, I e-mailed the support. after a bit of e-mail correspondence ich which I explicitly stated that I am using Cakewalk by Bandlab, I got the answer that I should be aware that Sonar X2 is not being supported anymore. WTH? My reply, that I am not using X2 but CbB has been ignored since. So no help from the support. If Cakewalk wasn't the DAW with by far the best MIDI implementation I would switch to another one.

Thanks!

Where can I post bug reports? Is this the place? Will questions be read by (or forwarded to ) Cakewalk developers? The USB issue is a serious problem and will make it impossible for me to use Cakewalk anymore. Actually I am currently pausing my work in hope for a bug fix. If needed, I will not hesitate to provide whatever information I can.

My info box displayed the text "2020.10 #1", nothing more, nothing less. There was no information about early access.

2020.10 is an early access version? Thanks for this information, which I did not receive prior to or while updating. Do you know how to prevent Cakewalk/Bandlab Assistant from installing early access versions?

Thanks but nope, there is no hidden dialogue box. And I won't reinstall CW. If I do so, I will have 2020.10 on both PCs, and if it indeed is an issue with 2020.10, I would have the problem on both PCs. I always update CW on one PC, test it, and then - if it works well - update the other PC.

Thanks for your reply. I tried this but it did not solve the problem. Actually I did not really expect it to, since it does not happen to a certain device.

Some of my USB devices are not being recognised by Cakewalk, though they are present and active in the device manager (Win10 Pro 64, CW 2020.10). When I disconnect one of these unrecognised devices from its USB port, Cakewalk does actually recognise that it has been disconnected and suggests to reroute the MIDI ports (which obviously have not been routed before I disconnected the device). After reconnecting the device, it is being recognised by Cakewalk but therefore another USB MIDI device won't be recognised anymore. When I disconnect and reconnect the latter, the first device is not listed as active anymore. A vicious circle. It clearly is not a certain device that won't be recognised by CW. I have to admit that I have quite a few USB devices, as there are a sixteen port MIDI interface (with six ports deactivated in CW), four synths connected directly to the computer's USB, and two controllers with direct USB connection. All the ten synths connected via the sixteen port interface work fine, while at least three of the directly connected devices are inactive or not even listed at all. So I have a maximum of thirteen devices connected to four USB ports I can use at the same time instead of sixteen devices connected to seven USB ports. I do use a USB hub (active) but there does not seem to be any rule if the devices are connected to the hub or directly to the PC.

This is a strange issue, since on both of my PCs (CW 2020.09 and 2020.10) I can open WRK files and play them, just as any CWP file. Have you tried to uninstall Cakewalk and reinstall it?

When I choose a MIDI track and right click on the patch selector at the left of the screen, an error window appears that claims that I tried to execute an unsupported action. Furthermore, this dialogue cannot be closed. Also this happens, no matter whether a channel, bank, and programme have already been selected or not. Please have a look at the attached video. My CW version is 2020.10. Cheers Ted Edit I just did some research. Running Cakewalk on another PC with CW 2020.09 installed, the patch selector (or path browser) works perfectly well. So it seems to be an issue with the latest update. Both machines are Win10 Pro 64. 2020-10-25 11-41-00.mp4