David Baay

I still fire up the old hardware regularly, especially the Roland D-110 that was my first MIDI synth module and on which many pre-VST projects were based. I always thought I should learn to play a breath controller but never got to it, and would struggle to learn breath control at this late date I'm afraid. A lot of my projects have wind/brass accompaniment, and a lot of solo piano works could use some. Maybe we can do a little collaboration to help you re-acquaint yourself with Sonar. Here's an example (I've been told I need to give time for my soloist to breath 😜) : https://www.bandlab.com/post/89b09300-f6f9-e811-9f2a-00155d77cb96

Click the 'Advanced' radio button at the bottom of Preferences.

Go to Preferences > Project > Clock, and change Ticks per Quarter Note from 192 to 960.

You'll be back after you run into the first 20 things that DAW can't do - or does awkwardly - that you used every day in SONAR/Sonar. 😜

Couple quick thoughts on this: - After re-saving as a "Normal" .CWP (Cakewalk Project) file, go to Preferences > Project > Clock and change Ticks per Quarter to 960. - To fix the drum track, click the clip to select the whole thing, go to the Event Inspector module in the Control Bar and enter 120 (ticks) in the Duration field. This will change all the drum notes to be a 32nd duration (at 960 ppq which is a convenient length to be able to see them and differentiate them at all zoom levels and will take care of the one hyper-long event at the same time. As I'm sure you know, changing drum note durations has no audible effect because the entire sample is played as a 'one-shot' with no regard to the Note Off timing. - In addition to setting a fixed the drum note length, you might want to apply a drum map to the track by choosing New Drum Map from the Output pick list and selecting GM Drums (Complete Kit) so that the track displays in the drum pane of the PRV with kit piece names and individual mute/solo controls per drum.

This is absolutely impossible More commonly, if you have the shorter clip selected when you initiate the export, that selection becomes the default export length. For that and other reasons, it's best to hit Ctrl+Shift+A to de-select all before starting an export of an entire project. Before Start and End Markers were introduced, I generally used a punch or loop region to define the export range.

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?

Not sure what you have going on, but everything's good here on both my Win 11 laptop with onboard Intel graphics and my Win10 desktop with Nvidia. Are you sure it's not project-specific and maybe plugin-related?

Prochannel buttons show up enabled in the Console View as expected here.

@p-w-m, @Neil Scott, @Aaron Doss and others experiencing UI reponse/lagging issues. I'm wondering if this might be fallout from the experimental 'Enabe GPU Acceleration' option in Preference s> Customization Display. I suggest you try disabling it.

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.