msmcleod

Just pushed a fix this morning. It should be available in the next update.

The other thing to bear in mind, is that you can’t negatively delay before 1:01:000. Any articulations that are delayed such that they would be delayed before 1:01:000, will be clamped to 1:01:000. The way around this is to insert a blank measure at the beginning of the project.

There were no themes in SONAR X3 - they were first introduced in SONAR Platinum.

@Nigel Simmons - One thing that could be the problems is your MIDI prepare buffer size. If this is less than the negative delay, this could be the problem - e.g. a MIDI Prepare Buffer of 50ms, and a negative delay of 100ms will almost certainly result in the articulations not being sent out. Try setting your prepare buffer to at least 25ms to 50ms larger than your largest negative delay - i.e. a negative delay of 100ms should have a MIDI prepare buffer of somewhere between 125ms and 150ms. Note that this requirement only affects negative delays, not positive delays. Also note that an excessively large MIDI prepare buffer will add a noticeable delay to the project starting after pressing play (i.e. setting it to 1000ms, which is a second, will add an extra second to the delay between pressing play and your project starting). The MIDI prepare buffer is set ion Preferences->MIDI->Playback and Recording: If this doesn't solve your problem, please send your problem project to @Jonathan Sasor. Issues with negatively delayed articulations are incredibly difficult to reproduce, and even once we reproduce it can take hours of debugging to determine the root cause - so please try to delete as many tracks as you can to keep the project as simple as possible, whilst still reproducing the problem. If you could also let us know what your MIDI prepare buffer size is, this will help to reproduce our end.

I always set Windows to use my on-board Realtek sound device, and use my audio interface solely for DAW use in ASIO mode. That way Windows can do what it wants with regard to sample rates without affecting my audio interface. If your audio interface is set to the default Windows device, Windows will try to override it. In my studio, both outputs go into my Mackie Big Knob Passive - this has two inputs which I can switch between. In my office, I use one of these, which mixes my Realtek, Focusrite 6i6 and Alexa together all going into my ARC Studio before going on to my speakers.

I use a Silent PC for tracking on occasion. It's an Intel J4215 @ 2Ghz with 8GB of RAM. I've also got an Intel N100 @ 2.6GHz with 16GB of RAM. Both of them run Sonar fine, but you need to realistically set expectations. The reason I chose these over a laptop is because they're completely silent - they just get really hot (they're designed to). Decently powered laptops sound like a jet engine when the fan kicks in. The J4215 is fine for tracking - I've recorded 16 simultaneous audio tracks while 32 audio tracks are playing, with an ASIO buffer size of 128. No FX were used at all, and the Pro Channel / Spectrum Analyser was disabled on all tracks. The audio was being tracked to an external SSD via USB3, which it coped with fine. The N100 does a fair bit more, but again, I can't expect too much. It'll happily run a fairly standard 32 track project with 2 or 3 VSTi's and a standard set of VST effects. Any reverbs are normally put on a bus for sharing, and if doing any mixing, I'll up the ASIO buffer size. I also commit changes regularly, bouncing to track(s) after edits and freezing when I can. The N100 is eventually going to serve as a virtual synth. TDLR: A mini PC will work, but I wouldn't recommend it for general DAW use. It's certainly adequate for tracking on location though.

Does it show up as a separate download in the Cakewalk Product Center?

1. For Track Colors, go to Preferences and check "Show Strip Colors". You can adjust the Saturation to suit: 2. There's currently no way to change the marker colors other than changing Color Scheme, however we're currently having discussions about ways to provide color schemes in the future.

This means that Library.db (the file that stores your plugin categories) has been corrupted somehow. While Sonar isn't running, 1. Go to: %APPDATA%\Cakewalk\Library within Windows Explorer. 2. Rename Library.db to Library.db.old 3. Start Sonar Library.db should be re-created. You'll then have to re-categories any plugins that don't categorise themselves automatically.

FWIW - if you use Articulation Maps, Articulation MIDI events are always sent prior to any notes / CC events on the track.

Just to confirm, are you running the ARM version of Sonar, or the Intel (x64) version?

Can you let us know: - The resolution / scaling of your screen(s) in Windows - Your display scaling within Sonar

@Tommy Byrnes - what is your display scaling set to within Windows? If you're using a custom scaling (i.e. not the standard 125% / 150% / 175% / 200%), it's known to be problematic - in fact, Windows warns you it might cause problems if you try to set a custom display scale other than the standard ones. Another thing worth trying is running dxdiag.exe - this is a built-in Windows diagnostic tool that will check the integrity of your DirectX configuration.

The issues for both the Play List View and the Color Preferences page have been fixed for the next update.

TH-U is a separate installer in the Cakewalk Product Center

FWIW - I'm running a i7-3770 @ 3.4GHz... I've now got 32GB ram, but was running on 16GB for years. I'm typically use an ASIO buffer size of 64 on my Focusrite interface ( I can use 128 on my RME, as its round-trip latency is better). 8GB will work up to a point, but performance will drop considerably once Windows decides to swap memory to/from disk. To avoid this happening, try to make sure Sonar is the only application running (a web browser with lots of tabs open is a killer!); avoid multiple VSTi's that use larger sample libraries (things like TTS-1, the SI Instruments, AIR XPand! 2, Synthmaster - even Omnisphere are probably ok, Kontakt probably isn't). Also stick to 1080P for your diplay resolution, as 4K will use 4 x the memory for graphics rendering. FWIW, I've run Sonar on an Intel J4125 @ 2.0Ghz with 8GB RAM, recording 16 simultaneous audio tracks whilst playing back 32 audio tracks without issue. No VST's were involved however, as it was just a tracking session. If you do start to see performance drop and upgrading your machine is not an option, consider upgrading your RAM to 16GB while they're still available - it's relatively cheap nowadays. Other techniques such as freezing tracks when they're "complete" can help considerably too. For tracks using sample library based VSTi's, make a copy of the frozen track (so the copy is a pure audio track) and archive the original synth track / disable the synth in the synth rack. It's worth mentioning that Sonar will not run on Windows 7, as it relies on Windows API's that are only available in Windows 10 and above.

Are you using any clip gain envelopes - also what is your screen resolution / scaling?

@John T - I'd advise unchecking "Show Waveform Outlines" within the Track View's View->Display menu. @Jorge Tata Arias - AFAIK, GPU acceleration only affects the PRV for the time being. It shouldn't affect Track View audio waveform display performance.

Joking aside... have you priced up the cost of a compatible Data MiniDiscs for that? A pack of 3 is around the same cost as the discounted Sonar subscription, if not more. I have a Yamaha MT8X and the cost of decent type II cassettes is just as crazy - around $20 - $25 for a new/old stock Maxell XL-IIS 60 or 90. The surprising thing is that when you account for inflation, they're actually more or less comparable to what they cost back in the day.

SONAR/CbB/Sonar have always been both forward and backwards compatible. If you try to open a newer project in an older version of Sonar/CbB, it'll just ignore the new stuff. Some newer features aren't compatible in older versions, such as the new Audio Snap transient detection algorithms introduced in CbB (if you try to open in SONAR Platinum). In cases like this, the transients will be thrown away and you'll need to re-detect them using the older algorithm. You'll get a warning dialog when opening the project if this is the case.

It has definitely been discussed, but nothing scheduled yet. Part of the reason for delaying is Microsoft's impending release of MIDI 2.0 support.

Press "P" for preferences, select the following (English is always the top option on the language dropdown), click OK, then restart Sonar:

What you say is only true for "Track Manager" in the View menu. The old Track Manager is not a view - it's a dialog - so we show the crown in this menu only. There was previously no Track Manager entry in the View menu. The following will show the old Track Manager dialog: Pressing "H" when the Track View (TV) or Console View (CV) is in focus. Selecting "Track Manager" from the TV or CV Track Manager button context menu. Selecting "Track Manager" from the TV "Tracks" menu. Selecting "Track Manager" from the CV "Strips" menu I've updated the original post to make this clearer.

Track Manager Within Sonar Premium, the old Track Manager dialog has now been replaced by a new Track Manager panel which can be docked along with the Browser/Synth Rack, or reside on the desktop as a floating window. It is no longer modal. To view the new Track Manager, either press the "H" shortcut key, or select "Track Manager" from the main View menu. The Free edition of Sonar will continue to show the old Track Manager dialog when using the "H" shortcut key, the Track View button context menu, or "Track Manager" from the Tracks View "Tracks" / Console View "Strips" menus. The Track Manager not only allows you to show/hide tracks, but also allows you to select tracks, change the MSR, echo, frozen and archive states, as well as rename / move / delete tracks. Swipe behaviour is supported for quickly changing the states for multiple tracks and buses. A : When highlighted, you're seeing the tracks/buses in the Track View B : Enables/Disables "Synchronize Track and Console views" setting C : When highlighted, you're seeing the tracks/buses in the Console View D : Hidden Track Presets - works the same as it did within the old Track Manager E : Filter track/buses list by name or number F : Additional filter options by Track State / Track Type / Plugins. When highlighted, a filter is being applied. G : Menu for Sort options / Delete Tracks H: Shows the current Track Color. Clicking this will show the Track Color picker. I : Show/Hide Track - when enabled, the track is hidden. Click or swipe to apply to multiple tracks*** J : Track Number / Selection status. Click or swipe to apply to multiple tracks. K : Track Type Icon - clicking will jump to this track. Dragging will move the track / highlighted tracks* Double click to open synth UI ( Instrument tracks), or open editor (Audio/MIDI tracks). L : Track Name - clicking / swiping will highlight the track rows** Double click to rename track. M : Track State buttons - Mute/Solo/Arm/Input Echo/Freeze/Archived - click or swipe to set for multiple tracks * Drag to move tracks will only work when ordered by Track Number and no filter is applied. ** Row highlighting is separate from track selection. Unlike the Track View, grouping operations (including Delete Tracks) are always performed on the highlighted tracks within the Track Manager. *** ALT + Clicking the hide button will hide all tracks within the Track View and/or Console view other than the ones in the current search results. When you ALT click the hide button of a track, only the tracks are affected; when you ALT click the hide button of a bus, only the buses are affected. This way you can match your filtered track results in the Track View/Console View without hiding your buses and vice-versa. [2025.07] ALT + Clicking the hide button of a Folder Track will unhide the Folder and all its content tracks. Filter Flyout: The Filter options allow you to show only the tracks of the state / type you're looking for. Each checkbox has three states, e.g. for the mute button: Off: - don't care if it's muted or not On: - only list tracks that are muted Tri: - only list tracks that are NOT muted The states/types are "ANDed" together, so the following means only show audio tracks that are muted and not hidden: The Contains Plugin(s) section allows you to further filter tracks/buses, so the only the tracks that contain any of the specified plugin FX or Synths are shown. For example, the following will only show muted tracks that have CA2A or Core Compressor within them: The Reset button will clear all of the checkboxes, so that the track list is no longer filtered.

Depending on the options you've checked within the Backup/Restore Settings page, the config profile file can contain a compressed copy of: Various Sonar settings contained in the registry (it does not include your plugin inventory or anything related to your user account) Cakewalk.ini (general Sonar settings) TTSSeq.ini (MIDI settings) Aud.ini (Audio device settings) ctrlsurface.dat / ctrlsurface_UWP.dat (Control surface settings & control surface user presets) INSTRMAP.ini / Master.ins (instrument mappings) userArrangerSectionTypes.json (user arranger section types) When applying a config profile, the existing files above are replaced with those in the config profile. Obviously it can only replace what was stored within the file when you created it. If you do this via the short-cut/command-line method, these files are replaced before Sonar properly starts up. If you do it while Sonar is already running, it replaces them then re-applies all the settings from the new files. Either of these methods should take no more than a few seconds - normally around 3-5 seconds, but certainly less than 10. I suspect the difference in time is due to Windows reacting to your hardware being connected/re-connected rather than anything the config profiles are doing - especially since, as you say, subsequent loading of the same profile is much quicker. Windows knows what hardware was connected the last time it was switched on, so if anything has changed, it has to deal with that. The only other thing that could affect things would be an anti-virus/anti-malware program, but if it these were the culprit I'd expect it to be slow every time.