Larioso

I have the same thing on a laptop I write this on, with the native soundcard not using asio. - same thing, you do some operation like save and suddenly audio is gone. - something is not compatible with audio drivers - I tried WASAPI, WDM and similar and same thing. It might work for a session, or not. - this is not my daw computer, so just having Sonar installed for reference and some quick fixes. For a good solution I would recommend getting some asio compatible audio device, or try install asio4all drivers to get asio on the interface you have. Search for asio4all on internet and install. With a proper asio interface I never had issues with Sonar, nor Cakewalk for that matter.

I use Sonar/Cakewalk to learn and play more in pocket with drums, this is midi then. You don't really need to listen at slow speed, stopped transport works, just zoom in and see if playing is on grid and line up with metronome or drums or something. If having drums, have that on another track, and zoom in timeline to see deviation from you playing. If you really listen to beat/metronome you will notice if so in how you playing end up but your ear is trained too and you will hear it better and better.

So you just got married a month ago and now on your honey moon with your new partner. - and think this happiness will last forever since you know your partner so well I was married to your current spouse a couple of years ago and really wish you two well. You used Cakewalk for 20 years successfully and now suddenly with the last project you run into some problems. - and your 25 years of programming make you conclude this is nothing to do with your last project - must be a programming error outside of your control I suggested early in this thread you try change threadscheduling model to "1" since you will use legacy WaitForSingleObject to sync threads, which would be known to you as programmer. - but you missed that completely as far as I can tell - because you already knew what the problem was, and it was not on you I had 6-7 feature requests on StudioOne Pro up to 4.7 and it became clear to me - all this already exist in Sonar - so went back to good old Sonar StudioOne has no sysex support, no surround mixing support, no real track templates with busses and stuff, and looks is simplistic compared to Sonar and not much you can do about it either since no theme editor - and I really hope you are not into realtime recording midi and CC, then you are in for a treat - the honey moon will end abruptly...

Great it was an easy fix. That's not easy to spot unless that module is visible. I ran Bandlab version 3 years ago, and had some initial problems getting toolbar and everything stay from project to project. Messed with workspaces and tried getting it permanent.

On toolbar button panel there is a "<S>" button for exclusive solo. If that is on it behaves like you describe. - check if that might be the case and just dim it

Multiband compressors are pretty good tool to get rid of ambient noises in post. - Waves C6 or something Also cancelling out some noise can be done with a tool like Waves S1 and panning a stereo signal and multiband EQ like H-EQ or similar. - sometimes multiple de-essers is good help too

Since it decides level hitting first plugin it may very well do so. - a compressor for one thing is affected a lot - many hardware emulating ones does not like 0 dBFs at all, and you have to turn gain down a bit

If not buying AAtranslator maybe you can learn what can be done in different formats https://www.aatranslator.com.au/ or if it might be worth it. As I recall they volonteer to convert one project for you so you can test. In general what I discovered is that all midi can be fixed if a daw can save project as midi. It will warn that some tracks will not be included. But you will have one thing to import or open and all midi is there. - then drag n drop wav-files from project maybe. Or do OMF as import after midi created project. Since no midi is included in OMF anyway.

Glad to be of service.

Could be the default setting of mute/solo does not mute sends. Configuration LinkPFSendMute=0 as default. " If this is set TRUE, pre fader sends on both tracks and buses are automatically muted when the track/bus is muted. Also if another track is soloed the pre fader sends on other tracks will be muted. This basically conforms to pre SONAR 4 behavior. " Set that to "1" probably fix this.

I am not sure all three pedals on piano are CC64, more likely different midi CC. - so if different lanes probably different CC and would say which one on the left Even list is a good tool to see exactly how the midi looks. - View menu, choose Event list

There is a value in configuration file, preferences, about setting the dropout time limit to watch out for. DropoutMsec=250 is default. Try increasing it....

Story short: - consider getting a pci usb 3 card to use for audio, cost about $25 - mine is based on a NEC chip and had that for many years to get usb 3 for backups on former daw computer - what that does is creating a new usb root hub beside I assume the only Intel 3 controller now in your device manager How did I end up doing this? Intel i7-12700F cpu base frequency 2.1 GHz, but runs constantly at 4.5 GHz, since I turned off half speed E-cores - C-states in bios off Usb controller Intel 3.x something, only usb root hub in system - 3 x midi interfaces on usb, 12 ports Interface RME Digiface USB 64 samples buffer For three months I dug into everything bios settings, shifted mb from Asus to Gigabyte and nothing solved it. - talking to support for Asus, Gigabyte and Intel, nobody had anything but just "check cables", "try another port" and similar - I tried and Presonus Studio 1824c interface too, but sent back as no difference Usb controller know what is audio devices through initial handshake, and I think something prioritize down audio and less vital. - even as I checked that MMCSS give audio high priority threads., Pro Audio used by Sonar - if on Intel controller driver or on windows, I am not all sure, and now I don't care since solved So now running no issues 64 samples asio buffer. Really weird stuff with these super computers as delivered how they mess with us.

"Thread syncronization", I am thinking different thread scheduling models in settings Configuration File. - 1=wait for single object type, which is legacy as stated - 2= I believe is default since long You did not mention as I read, so just an idea to troubleshoot for devs to get more info...and maybe solution not to handle rendering different than mixing and the rest.... I got a new 16+4 core i7-12700F beginning year, and had some crackling issues and also tried running different number of threads/cores in Sonar, also in that config at top. - I would try 2 cores, 4 cores and something like that to narrow down when issues appear - setting is MixThreadCount but really is number of cores to use - it works directly as audio engine starts exiting preferences, so no need to restart Sonar/Cakewalk My solution was to get another usb 3 interface as pci card, so computer had two usb root hubs. So no problem with Sonar at all. - newer computer mb seems to use Intel usb 3 controller, which makes a single usb root hub only - just stating for clarity, nothing to do with current OP

In plugin manager go to Options and press Reset All button. That will clear everything and next rescan will not have your plugin on list.

I had that with RME Digiface USB on windows 11. For me it was enough to forget opening a project in a different sample rate. - you have no audio device in system My setup - syncing interface through ADAT input from a rack unit - temporarily I changed to 44k for a project I ran so that worked - and forgot to change back to 48k on that ADAT unit - then trying to play back that 48k project I got the message "no audio device" Check out these simple things.

postrf in wrong thread after login

I've had that, doing double click to open a midi clip, just moved it a bit, since snap was off.

Cakewalk support fixed that for me, as Lord Tim said, just contact them to get out of that misery. - they made email same as bandlab account

Relax, in my book Cakewalk "soon" means 6 months, so christmas time is to be expected. I hope there will be as before, versions with less content which I don't need anyway and those with everything included. - I would not mind even without ProChannel as I have on my Sonar Artist 2015 - I just find it annoying to ensure that is disabled in templates used - and that you can have Sonar offline forever if so, no regular activate of any sort

I would not worry about enable/disable plugin causing pops. Pretty standard in all daws IMO. In Preferences there are settings for fade in/out when transport start/stop. - set to 10ms or so usually fix this

no clue why it did not work the other day.

I just come to think of the old Optimize for appearance or performance dialog. - I would test turning for performance so all visuals stuff are gone - as a test Redrawing stuff make me think it might be relevant. - had long ago that shadows under mouse or popup menus etc could even create crackles in audio - so a windows visuals thing

Use some digital out from interface, M900 support both coaxial and optical inputs. - no need to use USB

But difference is rather major between suddenly running a project at 44k instead of 48k. - it happend to me in Sonar 4.x or something with an interface I had - if there were a windows sound beeping at 44k interface changed to 44k suddenly So turn off windows sounds completely not to have that happend.