David Baay

I have't seen that for a long time except for an issue that was fixed recently with the clip re-draw frequency during playback at high zoom levels causing the UI to become unresponsive. If it's just this one project, I would tend to suspect some plugin is causing the problem. Based on the track numbers in your screenshot, it looks like your synth count might be pretty high. If it's from a template with a lot of unused instruments, I would try 'Disconnecting' them in the Synth Rack until needed.

Let's make that @Matthaeus Ebonah, the OP.

Is it just the length issue, or you're also not getting all tracks? Sonar has Start and End Markers that earlier version didn't have, but they have to be set deliberately and can be over-ridden in the export dialog.

Is export working as expected in CbB? How about selecting nothing and exporting only the Maste bus?

With the Track Control Manager at the top of the Tracks pane set to show 'All' controls, set the C widget to force a specific output Channel for each MIDI track . Or hit "I" to show the Inspector and do it there. https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Playback.20.html

- Go to Preferences > Audio > Playback and Recording and set Driver Mode to WASAPI (Exclusive if you want best performance from Cakewalk or Shared if you want to be able to play audio from your browser or other apps at the same time). - On the Drivers page, uncheck the Magix driver if you see it there, and check the boxes for your onboard audio Headphone/Speaker output and Mic/Line input.

What does the dump .txt file way the crash is ocurring? Have you cranked up the Error Handling Severity at some point? I don't think you would normally see this error reported (bold part is my doing): Enhanced error detection is now integrated into the DAW. This feature is opt-in for now and may be enabled by adding the ExceptionHandlingSeverity value to the Cakewalk.ini initialization file. We appreciate users helping make Cakewalk better by reporting crashes to us as well as plug-in vendors when necessary. To control the error detection sensitivity, you can now add a new ExceptionHandlingSeverity value in Preferences > File - Initialization File. Valid values for this setting are: 1 - Unhandled errors are caught (default) 3 - All access violations are detected and unhandled exceptions are caught 5 - Unhandled errors and heap corruption is detected 7 - Unhandled errors, all access violations and heap corruption errors are caught (this is the strictest error detection mode)

No, MIDI clips allow automating only Velocity Offset with an envelope. I'm not exactly sure why this limitation is imposed, but suspect because MIDI controllers are channel messages affecting the sound of all notes sent on the same channel so it makes some sense to allow only one track-level controller envelope in a world where it's unusual to have events of different channels on the same track. But that does make it harder to keep automation and clips locked together when editing and using features like Groove Clip Looping. I can only suggest you just use actual controller events in the clip rather than envelopes.

Based on automation line crossing empty space before the clip, it’s a track envelope, not a clip envelope.

Possibly you created tracks by duplicating one that had the envelopes or inserting from track template…? Otherwise I don’t know; haven’t encountered anything like that. What do earlier versions show?

It's actually not possible to get a zoom level that shows 8ths in the timeline; the markers jump straight from quarters to 16ths at a certain point. Here's how to get timeline markers at any fixed interval at all zoom levels. - Set the Edit Filter in an audio track (can be empty) to Transients. - Right-click in the Clips Pane and choose Pool > Add MBT to Pool. - You'll get pool markers in the timeline at the specified snap resolution that will persist at all zoom levels (assuming you disable the Smart Grid snap option. - You don't need to keep the audio track that you used to get access to the Transient tool.

Not compact, but I just replaced my ancient Beyerdynamic DT-770 Pro with a B-stock pair direct from Beyerdynamic for $125 (normally $170). There is no evidence I can see of their being B-stock. The old ones were 600-ohm and the new ones are 250 and have redesigned drivers but sound pretty much identical. They also make lower-impedance versions if you need that. They isolate well with thick, plush muffs that are super-comfotable. Best sound for the money, I think, and I can vouch for their durability; my old ones must be 10+ years old and were still sounding great despite numerous drops over the years; they were just getting ratty.

If this means you're using a MIDI-DIN-to-USB cable with a keyboard that doesn't have a USB port, you should look into getting a 'real' MIDI (or audio+MIDI) interface. USB-MIDI cables are notorious for problems like stuck notes because they generally don't have any buffering built in to prevent dropped messages when there's a transmission error.

You should be able to set Now in the timeline without losing a selection so long as you don't inadvertently drag. But the value of Now=From/Thru is simply the ability to quickly set the Now time to a MIDI event, transient, clip, or other selection that you've made in order to see the exact time, set a marker, paste something or Split at Now in another track, etc.

The most common cause of dropped/stuck notes is having too low a MIDI Prepare using Buffer. The management of MIDI buffering has been improved over the years to adjust more automatically, but it can still be a problem in certain situations like adding a plugin that requires a lot of delay compensation. Try increasing the Prepare Using setting under Preferences > MIDI > Playback and Recording. The default is 50. Too high a buffer setting might also be an issue. Another possible cause is having the synth instantiated in the FX bin of the track rather than in the Synth Rack. This configuration is supprted for backward compatibility with older projects, but is not the preferred usage and can cause problems like this. If that doesn't get it, try shortening or lengthening the offending notes - just a few ticks will often resolve it.

Rollback is a handy way to confirm that an issue is in fact related to an update. IMHO it should always be available for that purpose and in case it confirms an issue that's a showstopper for a certain workflow that may not be affecting eveyrone.

First things first: - New project from Basic template. - Verify Metronome is set to Audio, not MIDI, and high/low click levels are reasonable. - Assign the metronome output directly to hardware "Main Outs" to which your monitoring system is connected. - Enable playback metronome and disable Stop at Project End in Track View Options. - Start the transport; do you get a click?

IIRC correctly using a unbalanced TS cable between balanced inputs and ouputs results in a 6dB attenuation. If one end is not balanced, I'm guessing there will be no difference.

Had to Google that one. Sounds distinctly like not a good thing to have enabled on a DAW in General. In case you haven't already, and just to be sure, you should check the security setting mentioned in this decription (probably a bunch of AI misinformation, but FWIW): How it works Core isolation runs core processes in a virtualized environment that's isolated from the rest of the system It protects against malware and other attacks by isolating computer processes from the operating system and device It prevents malware from hijacking high-security processes How to enable or disable Open the Windows Security app Select Device security Click Core isolation details Click the toggle under Memory integrity to turn core isolation on or off Restart your device for the changes to take effect Known issues Some devices or software may have trouble running with Core Isolation enabled

Not sure what you mean by that...? Regarding audio ouput, be sure also to check the 'Show Mono Outputs' box at the bottom of the Audio Devices page in order to be able select individual mono outs for tracks.

I just picked up a UMC404HD last week. I've not seen anything like what the OP describes with my unit, but thought I would share some other info: When I went to download the driver on the Feb 17, the newest available was 5.30.0. I was having some issues with variable RTL (+/- 6 samples at 48kHz) preventing dialing in the Manual Offset to get sample-accurate record latency compensation, and in the process of troubleshooting discovered that a v5.76.0 driver was just released two days later. So far as I can tell, the only thing it changes is the way inputs are presented to Windows via the WASAPI driver. And it seems a step backward from the 5.57 driver (which I'm running currently) as the 1/2 inputs are not presented as independent mono inputs, only as a stereo pair. There's no changelog so it's impossible to know what else was changed, but it had no effect on the variable RTL at 48kHz (observed in both Sonar and another DAW and in the CEntrance Latency Tester). AT 96kHz, the variability is only +/- 1 sample, but I'm not going to start working at 96kHz at this late date just for that. One other observation: The 5.30 driver I originally downloaded had 48 samples = 1ms lower RTL across all buffer sizes at 48kHz with Safe Mode enabled than either the 5.57 or 5.76 driver so I'll probably roll back to that version given there don't seem to be any other improvements to the ASIO driver. All three versions support Win11.

Crackle-inducing plugins will often be those that use lookahead buffers and require delay compensation. In Sonar you can identify these by hovering over each plugin in an FX bin to see how much PDC it's inducing, if any. Mastering plugins from Izotope, linear phase EQs and Compressors and transient shapers are common offenders. Also if you've added any soft synths in the mean time, you might try freezing those. Synths that use physical modeling like those from AAS and Arturia, Izotope's Iris 2, Pianoteq, etc. can add a lot of processing load.

My beef with Set Project from Clip is that a regression occured between S8.5.3 and X1 whereby the tempo change it creates are not exactly on timeline beats now. They tend to be a little after the beat where the tempo is increasing, and a little before it where the tempo is decreasing. Aside from simply looking and "feeling" messy when you view the tempo list or zoom in the timeline, this can make arranging by copy/cut/paste with tempo changes problematic when selecting with snap to measures misses a tempo change or includes one it shouldn't. I tried for years to get traction on fixing this regression to no avail. I ultimately wrote off using the function because of this, but also because I found that the time it takes to massage the beat markers into position for Set Project to work correctly was better spent spent on SM/BAN which is a lot more flexible anyway, allowing you set only as many points as necessary, not always evey beat or even every measure. Aand it works the same for freely recorded MIDI!

The keystroke you're looking for is Shift+M - Set Measure/Beat At Now - but it's not a real-time operation. You set the Now Marker at an absolute musical time, and use SM/BAN to tell Sonar what measure and beat that is. Sonar will insert the necessary tempo changes to make the specified timeline beat align with the muscal beat at each point. Depending on how variable the tempo is, you can start by setting downbeats every 8-16 bars, and then set additional points in between to tighten it up as needed. If the music doesn't start with a downbeat at 1:01:000, additional steps are needed to do it properly. If you Google "SM/BAN site:discuss.cakewalk.com", you'll find previous posts of mine on the subject with detailed procedures. No doubt someone will suggest dragging the audio to the timeline to have Melodyne Essential create a tempo map for you, but I personally find the results are often marginal at best compared to SM/BAN. It;s also possible to record a guide track of MIDI notes in real time, hitting a key on your keyboard at every beat (no more, no less) and using Fit Improvisation against that guide track to create the tempo map, but you'll tend to get a rushing/dragging timleine from that as well.

Did you download the latest ASIO driver from Line6? I Googled and saw some posts saying the ASIO driver didn't load properly in Win11 until updated last March. My guess is Windows is using it as a WASAPI device so it doesn't matter that the ASIO driver is not loading. If all else fails, try changing CbB to WASAPI mode.