David Baay

Microsoft Support thread on multiple mouse driver instances causing problems. https://learn.microsoft.com/en-us/answers/questions/4083226/i-have-multiple-hid-compliant-mouse-drivers-showin Easiest solution might be too leave them both in place but disable one.

I'm not seeing a problem with dragging either the velocity hotspot on the upper edge of the note in the notes pane or the velocity 'tail' in the controllers pane or Shift+dragging notes around to constrain pitch or time. I have to think something is going on with your mouse/driver. If you're using a wireless mouse maybe change/charge the battery. Do you still have CbB installed and it's working normally?

Working as expected here, and I'm not aware of any setting that would affect this. But the dimming might be a little more subtle than in CbB, depeding on the your color scheme, the track color and the size of the waveform. I do recall it being a little more obvious in CbB with the Mercury scheme.

I don't see why that would be an issue; just leave Volume at 0dB. If you want higher level into the Maximizer use Gain. If it's after some other FX in the bin and you need to control Input level to it put an empty FX Chain ahead of it as msmcleod suggested. Anotherr option not mentioned is to put it in a Prochannel FX Chain, and set the Prochannel to Post FX Rack. Lots of ways to skin this cat without having another routing option that 99% of users will never need.

Choosing left or right gives you one side of the stereo pair. It's just Sonar's default labeling. In Preferences > Audio > Drivers You can enable to show friendly names like Mic1|Mic2 (double-click to edit and use the pipe symbol between the two input names).

Sonar now has Cakewalk ZIP format which can save Audiosnap transient markers and editing. Historically I just used normal zip files. For your legacy bundle files, if you weren't aware of having done anything with Audiosnap, you probably didn't lose anything except Audiosnap being enabled on some clip(s) which initially just performs transient detection without altering anything.

https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Playback.19.html See especially the section titled Mono audio clips may be increased by 3 dB in certain scenarios

Try setting Disk I/O buffers back to default (256kB I believe) or even down to 128. I've never had to go over 256 even when using an HDD for audio instead of SSD.

I was just going to ask what's controlling the tape sync when you posted. It seemed likely that was the culprit rather than the EI latency being variable.

This would bring a lot of pc's to their knees. What sort of preset are we talking about here? I have the same question as Jonesey. Are we talking about Track Templates? I guess the first save might be slower because Sonar has to initially save all the parameters of all the synths whereas subsequent saves only have to save changes. That said, I can't really reproduce an issue saving a project with many new synth tracks added, but I don't have some of the particular synths mentioned - notably Spitfire and Neural DSP. Seems to me this issue is still not fully explained.

Is it equally as active on a re-save as on the initial save? This may be a red herring but the Interwebz say: "The wmiprvse.exe process is the WMI Provider host. It's a part of what's known as the Windows Management Instrumentation (WMI) component within Microsoft Windows. It's normally used on desktop systems connected to a corporate network so the IT department can pull information about that desktop, or create monitoring tools that alerts IT when there's something wrong with that computer." Is this a personal machine? EDIT: On further reading I gather it can also be used for some other legitimate purposes on a non-enterprise machine, but high CPU usage can indicate a problem, including the process being exploited by malware. Given that it's only manifesting in this one particular use case, I would think that's unlikely but might be worth doing a malware scan and stopping to think what else you've deliberately installed recently.

If a reboot fixes it and just re-launching Sonar doesn't, it sounds like the Presonus driver is getting into a bad state. In that case, you may find that just power-cycling the interface also fixes the problem. I would try running it with some other DAW software and if it continues to misbehave, talk to Presonus. If it seem okay with another DAW you might need to look harder at the Sonar project content or try 'Reset Config to Defaults' in Preferences > Config File. This will back up your existing AUD.INI and replace it with a default one. If this solves the problem, you can compare the two files to see what's different.

Grooveplayer is used by the metronome; is it working? TTS-1 was indeed removed from CbB, but if you had any older licensed version of Cakewalk/SONAR installed, it would have kept working. If the uninstall broke something, you can use the custom installtion option to re-install plugins from the licensed version.

And check for the age-old culprit of many crackles: Steinberg Generic Low Latency ASIO Driver. Even when not in use, it seems to wreak havoc with Sonar and should be uninstalled.

Kind of out of ideas. Next step might be to install Microsoft's Process Explorer to see what all is going on. But I would also just check disk activity in Windows Resource Monitor to see what files are being written/accessed during a slow save. https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

Is this affecting all/most projects of comparable complexity? Are they mostly/all audio or mostly/all soft synths? Are you still using the Presonus Studio 24 or the V-Studio 100 mentioned earlier? If you're running 192 or 96kHz and the project has no recorded/rendered audio yet, try 48kHz. Is your PC optimzed for streaming audio? Ensure the following at a minimum: - If it's a laptop, plug it in. - Set Windows power management to Best Performance. - Set onboard audio (e.g. Realtek) as the default device for Windows and generic multimedia apps to play audio. - In BIOS, disable Speedstep and C-States (CPU-throttling). - If problems persist, adidtionally disable Bluetooth and WiFi (at least temporarily to determine if either is a factor). - If problems still persist, run LatencyMon to see what might be causing high/spiking Defered Procedure Call Latency - a measure of the PC's readiness to respond to interrupts from the audio interface requesting a buffer refill (not to be confused with audio buffering latency). https://www.resplendence.com/latencymon

Ah, OK. I misread "used to" as referring to some time in the past. 🤪 So far as I know it's always been up to the user to be aware and manually change modes. Or possibly the plugin itself could detect when it's being asked to process samples faster than real time and do whatever it needs to do.

I played around with your scenario, and others, but I cannot get the drum map to persist when focus is on a non-mapped track in any circumstance. I think the best it's going to get is for the Bakers to program the Drum Pane to persist the map assigned to the most recently focused drum track when PRV focus moves to a non-mapped track. If you have more than one drum map in the project, this could potentially lead to a situation where drum hits on a track assigned to another map are displayed in the wrong map but that could probably be suppressed by some additional logic. If projects only allowed a single drum map to be used none of this would be an issue. It seems to me the only way you support that is to have the drum map display based on track focus. I'd be curious to see how other DAWs handle this.

I think your best bet would be a late '80s or '90s vintage programmable multitimbral hardware synth that has a GM soundset like the various Roland, E-MU and Korg keyboards and rack modules. The basic soundset is there, but with the programmability to allow changing the sounds in all kinds of ways (including adding portamento) that most GM-only modules were not designed to support. I think GM was so passé by the time virtual instrument plugins came along that there was never a lot of developer interest in going above and beyond emulating a non- or minimally-programmable rompler.

Leaving "Render in Real-time" unchecked is Fast Bounce a.k.a. Offline. OP confirmed earlier that Realtime render succeeded but said the ouput had some pops/glitches. This is iinteresting in hindsight because that can also be a symptom of plugin compatibility issues with the 64-bit mix engine.

Thanks for the heads up. I should have thought to suggest toggling it one way or the other as a troubleshooting step.

I'm not sure what all is going on with your project - I'd have to get hands on with it to really understand and troubleshoot - but It's highly unlikely the update alone preciptated any of this.

Exclude all Sonar-related app and document folders from scanning by Windows Defender or other antivirus.

Sorry for the confusion. I guess I expected to be getting a reply from the OP and totally overlooked who was posting. There hase been some evolution of the behavior of the Tracks Pane over time and I forget which version you're using, but the behavior in Sonar is pretty much unchanged from SONAR Platinum: If the track number is lit, the expectation is that the notes of the track will be visible, and if it's not they won't. His screenshots are showing the opposite with regard to the visibility and selection status of the Drums track.

As noted, that will stop if you disable Always Echo Current MIDI Track in preferences; at least it will stay None until you deliberately arm or echo it. I had forgotten that the default to All External hadn't been implemented in CbB... another reason to move on to Sonar. You still can't assign a default input, but at least you won't have virtual ports echoed/recorded when you neglect to proactively assign one. Promidi's suggestion to use Track Templates is a good one.