msmcleod

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. *** [coming soon] 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. 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.

This is the correct link without the https... it relates to the new Sonar only: http://legacy.cakewalk.com/Documentation?product=CakewalkSonar&language=3&help=Introduction.34.html

Sonar Premium and Sonar Free are the same program. Premium features are unlocked when you log in, and stay in as long as you're logged in. Note although you need to be connected to the internet to actually log in, you do not need to stay connected to the internet to remain logged in. If you remain disconnected from the internet, your log-in session will eventually expire, but AFAIK it lasts around a month. If connected to the internet, your log-in session will automatically refresh.

If your subscription ends, functionality will revert to the free version of Sonar, currently this means: Plugin oversampling will be disabled. Anything set to Elastiqué Pro will be rendered using Elastiqué Efficient. Dithering will fallback to using Triangular if it was previously set to POWR. If you had more than one arranger track, you will still be able to access them all, but you will only be able to view one at a time, and you can't delete, rename or add any new ones. This doesn't affect your existing arrangements, or your ability to create new ones using any of the sections from the existing arranger tracks. Jump to Track will become unavailable You will only be able to preview BandLab sounds from the BandLab Loop library - any that were already used in your project, will still be available. Track Manager will revert to showing the old "Show/Hide Tracks" dialog. The hidden tracks presets are 100% compatible between the old and new Track Manager. As long as you don't attempt to edit any of the oversampling/stretching/dithering settings, your existing settings should return to their previous settings if/when you renew your subscription.

^^^ essentially, this.

You should only get the message if you try to access a setting that is only available in the premium version... and this should be clearly indicated by the crown icon. If you're seeing it when doing other things, please provide us with the exact steps that led to the message appearing. Before releasing, we did see an issue when selecting an export preset (in this case the preset was set to use POWR dithering). We fixed this one, but it's possible there could be other loopholes. Please let us know all the detail if this is the case.

The search will filter the tracks list in the Track Manager (the filter button offers more options). It doesn't affect the main track view. The idea is that you can use the search/filter options to identify tracks you wish to perform a number of operations on. You can then select them (to perform a quick group operation from the TV), or mute/solo/archive/arm/hide etc directly from the Track Manager. If you want to hide the tracks, use the search/filter options to identify the tracks you want to hide, then swipe down the hide icon to hide them. You can then save this as a preset for that project.

The presets are "Hidden Tracks" presets - as they were in the old Track Manager. They are not search presets.

^^^ this

As far as I can tell PDC is taken into account, which is what it should do. I added a bunch of look-ahead plugins, and used the MIDI Sync display in MIDI-OX to show the time. Even with a 1.5 second delay due to PDC, the MIDI sync was showing the M:B:T time exactly in sync to what I was hearing. It doesn't matter what each individual track's PDC is as Sonar will automatically add a further delay to each track to ensure that each track is played in time with each other. In other words, each track is delayed as much as it needs to be to match the track with the largest plugin delay.

The only multi-client interface I'm aware of is the MOTU MIDI Express XT... but I think it's been discontinued. It's showing as out of stock pretty much everywhere. I've heard that the ESI M8U eX might be multi-client, but I'm not convinced as it's a class compliant only device. In saying that, it apparently has some clever routing capability, so it could be made to work. You can also run multiple interfaces by setting them to a different device id's using the dip switches at the back. FWIW I've not used this particular MIDI interface, but I had issues with ESI MIDI interfaces in the past with my Mackie surfaces. I wouldn't advise getting it unless you're certain you know you can return it. In the meantime, it might be worth trying loopBe rather than loopMIDI. LoopBe in my experience doesn't suffer the same latency issues as loopMIDI.

Not sure if this will cause more problems than it would solve, but have you tried switching from MME to UWP? I think UWP will support multi-client for MIDI inputs. Sonar certainly supports UWP, but not sure about MIDI-OX... although it might work if you use UWP in Sonar and MME in MIDI-OX.

The vast majority of MIDI drivers will only let you open a port once. It's very rare to find one that will allow more than one application open the same port. I've always had to use loopMIDI when I've needed to use MIDI-OX, but there's always latency issues. I've only ever used MIDI-OX for diagnostic purposes however, and not as part of a general setup. One way around this I guess would be to use a hardware MIDI thru on the output of your device, essentially splitting the signal so you can plugin it into two MIDI input ports. FWIW standard DIN MIDI input ports are optically isolated, so you could easily build a simple splitter cable connecting one MIDI out to two MIDI input ports - just don't make your cable too long. What you can't do is connect two MIDI outputs to one MIDI input - you'll need to go through a MIDI merge unit for that, otherwise the MIDI messages will be completely garbled. I must add though - are you definitely plugged into a USB-3 port? If you're plugged into a USB-2 port, or you're using a USB hub that has USB 2.0 devices also plugged into that, then you WILL see a reduction in performance.

It depends. System common / system realtime messages don't have a MIDI channel. One of the system realtime messages that can be sent by devices is "Active Sensing" - this is usually sent every 300ms or so, and is used to indicate that there is still and active MIDI connection. Not all devices send this, but some definitely do. Without seeing the message though, I can only speculate.... I doubt it's the MIDI interface itself though.

As a rule, it's normally best to automate the audio track volume of a VSTi rather than the MIDI track volume. Apart from the fact a lot of VSTi's don't respond to CC7, when they do, what you're actually doing by automating MIDI volume is changing the volume pre-fx which isn't usually what you want. The audio volume fader is always post fx. If you do need pre-fx, consider automating the audio track gain.

Uncheck "Allow Only One Open Project at a Time" within Preferences->File->Advanced

@Canopus meant you can't activate such an old version of Cakewalk... not the version of the operating system. The latest version of Cakewalk is 2024.12. Later versions of Cakewalk may complain that you're not on Windows 10, but it will still install. I've had it running on a Windows 7 machine without issues.

You don't do this within Sonar, you set this in your audio interface control panel.

IIRC, I don't think the timecode contains ANY tempo information at all. The timecode on tape contains only the hours/minutes/seconds/frames. You'd stripe the tape first, then set the zero offset for measure 1, then enter the tempo map into the tape-sync device. The device would then read the timecode from tape and send out MTC via MIDI using the tempo map you'd entered. I used to use a JLCooper PPS-100 with my MT-8X. Typically, I'd do the following: 1. Strip track 8 with the time-code. 2. Let it play from the beginning for around 10 - 15 seconds, then stop. 3. Set measure 1 to the current position, and enter in my tempo map into the PPS-100. 4. Set Cakewalk to sync to MTC and arm my tracks 5. Rewind the tape, press record in Cakewalk and play (or rec if I was recording on tape as well) on the tape machine. 6. Record my MIDI within Cakewalk, and audio on tape. You can be as accurate or inaccurate as you want to be in step 3, depending on whether you need things aligned to a grid within Cakewalk. For some projects, I just set the tempo arbitrarily to 120bpm, and forgot about it - especially if I was recording a keyboard part to an existing recording on tape. The song wasn't actually in 120bpm, but it didn't matter as I wasn't using the metronome, and I wasn't interested in editing the MIDI; all I wanted was to record a MIDI performance and have it play it back exactly as played. My usual workflow in this case was: 1. On a blank tape, record the whole band on to one mono track (usually track 8 ) 2. Record the drums on tracks 1 to 4, with the drummer playing along with the guide track on track 8. 3. Record the bass on track 5. 4. Bounce the bass/drum tracks to a stereo pair on tracks 6/7. 5. Use tracks 1 thru 5 to record the guitars, then finally the vocals. 6. Stripe the tape on track 8 (overwriting the guide track), then record the keyboards in Cakewalk. Obviously every session was different, so I could end up with a bass on it's own and drums in a stereo pair, or bass/kick on one track, snare on another, and overheads on a pair etc.. all depended on how many tracks I had spare. Really, the only reason I used time-code was to get one or two stereo keyboard tracks for the price of one mono audio track. I could also add a quiet drum machine kick or snare if needed, should the bounced drums balance not be quite right. Once everything was good, I'd typically take Cakewalk out of the equation by recording the MIDI from Cakewalk on to my Alesis DataDisk. That way, all I needed was the tape deck, the PPS-100, DataDisk and one or more MIDI sound modules. I could play from any position on the tape, and the DataDisk would pick up almost immediately. I'd also do a sysex dump from the PPS-100 to the same floppy on the DataDisk, so that the tempo map / start time etc was there ready to be restored for that song.

AFAIK there's no plugin to do this, you need a hardware converter to convert the SMPTE timecode to MTC. In saying that, if you've alread recorded all 8 tracks at once into your DAW, there's no need to use the timecode track. All you need is to create a tempo map from the existing audio, and there are several ways of doing that, i.e.: 1. Drag an audio track to the time-line and let Melodyne extract the tempo; OR 2. Insert a MIDI track, arm it, then record the same single note played every beat. Then select the clip, then Process->Fit Improvisation from the main menu; OR 3. Set the now time to various points in the track, and "Set Beat as Now" giving the relevant measure/beat at the now time. The tempo will be calculated based on all previous "Set Beat as Now" operations.

You can do this... however, if you've already marked all of your sections out, you can just as easily create an arrangement:

It's probably on Lane 2 (or layer 2).