msmcleod

Double check your OneDrive settings... the enabled devices are stored in TTSSeq.ini, which is in %APPDATA%\Cakewalk\Cakewalk Core\ IIRC, %APPDATA% is one of the directories backed up by OneDrive by default. It can get itself in a bit of a muddle sometimes though, forcing a re-sync to older versions. If you've got more than one machine logged in using the same Microsoft account, this can also cause OneDrive to get confused as to which machine it's restoring to. Personally, I just disable OneDrive... but you can also change the OneDrive settings to leave this directory alone if you wish.

Just an observation, but you really shouldn't be using .wrk files in 2023 - these were deprecated over 20 years ago when Cakewalk Pro Audio 9 was replaced by Sonar 1.0. Sticking with .wrk files will mean you're potentially losing a lot of things added to your project, simply because they don't support all of the new features. A while back I went through a process of upgrading all my CWPA9 .wrk files to .cwp files in SONAR Platinum. It only took a couple of hours to do around 150 projects.

@Rok TheKasbah - the Arranger Track was specifically designed to be both as an edit tool as well as a traditional arranger. There's no need to create an arrangement to use it - quite often I'll create temporary sections to move or copy things around in a project. There's things it can do that normal selection/drag can't do, such as work on both your tracks & buses at the same time.

@Rok TheKasbah - I've just pushed a fix for this - it'll be available in the next release.

Wdf0100.sys is the Windows Driver Framework - which means some driver is taking up most of your CPU time. Try disabling your WiFi drivers. This makes a huge difference on one of my old Dell Laptops. Battery life in itself shouldn't affect performance, however a lot of laptops will default to slowing the machine down when running on batteries in order to preserve battery life. This will definitely lead to dropouts. You can change the profile used for on-battery/plugged-in in your Windows power options. The laptop should always be running in "High Performance" mode when you're using it for audio. Of course, this will mean a drastically reduced battery life - probably less than an hour on most laptops. If you really need the battery life, you might get away with it on a reduced power mode but with your ASIO buffer size set to maximum.

Personally, I never noticed it because I always have the dialog set to show. I almost always either use Simple Instrument Tracks, or more often Per Output Instrument tracks, but since I normally want to set the number of tracks for per-output instrument tracks, I have the dialog showing. The extra "click OK" step never bothers me.

Take a look at some of the suggestions in this thread:

I personally use CloneZilla which is completely free. I burn the ISO image to a CD, then boot off the CD to make the images. Because CloneZilla is Linux based, it doesn't get upset if you've got multiple drives with the same Windows partition on it. This animated gif is a bit old, but AFAIK the instructions are pretty much the same in the latest version: Drive Backup: Restore:

Just to add to @Lord Tim's solution... If you first save the tracks from the old project as a track template, insert the track template into the new project, then copy the tracks from the old project on to the tracks you created via the template, you'll preserve any automation/routing from the old project. The selection in the old project will be preserved during the process, so: In the old project: 1. Select the tracks you want to transfer over 2. Save as a track template In the new project: 3. Insert the track template you saved in step 2 In the old project: 4. Copy Special In the new project: 5. Click on the first track inserted by the track template to make it the active track, and make sure the Now Time is at time zero 6. Paste Special In some cases, you might get extra blank tracks created at the end of your tracks - you can just delete these.

If you enable "Snap Tempos To Whole Values", it'll always use integers regardless of the scale:

This has now been fixed and will be available in the next release.

The issue is now fixed and will be available in the next release.

@GreenLight - I can reproduce the issue. We'll look into it.

@pulsewalk - can you PM @Jonathan Sasor a link to your project, along with a video showing the repro? I can recommend ScreenToGif for screen captures.

There's no real automation in the PRV - what you're actually doing is adding MIDI Control Change events. As each control change is an individual event, the snap settings are applied to it. You can either continue to use CC events in the PRV with snap off (which by the way will potentially add hundreds of CC events), or use actual MIDI automation in an automation lane in the tracks view.

I tend to just use clip gain automation, normally after consolidating all my comps to a single clip.

@pulsewalk - I can't see any bug here. If you have "Select Track Envelopes with Clips" enabled, when you select a clip, any track envelopes are selected for the time range the selected clip occupies. So doing a CTRL + drag to copy the clip, will also copy the track envelopes. However, lanes are only created for parameters that actually exist for the envelopes in the destination track.

You can only use ports from one ASIO driver at a time. In order to change ASIO device, you need to uncheck all of your existing ASIO ports first. You'll then be able to choose another ASIO device.

Clip Automation belongs to the clip, not the track, which is why it's being copied along with the clip. If the other automation lanes are track automation, then this explains why they don't get copied too.

There are probably only a handful of plugins that don't support high speed bounce, but if the plugin is written properly, it should support bouncing at high speed. Unfortunately it's a matter of trial and error to find out which ones don't behave - some crash, some give unexpected results.

For Cakewalk to record in sync, it needs a reliable clock. The most reliable clock is the one from your audio interface, so make sure... 1. Before you start recording MIDI, make sure you have at least one audio track or instrument track in your project - it's fine if it's and empty track. As long as there is an audio track, the audio engine will be engaged and Cakewalk can get its timing from this. 2. Your record/playback timers are set to the correct audio device in preferences: 3. Your project clock is set to Audio:

Check that Pitch Wheel messages are enabled in preferences:

FWIW - I tried a MeLE Silent PC running at 2GHz + 8GB RAM with a 1st gen 18i8, recording 16 simultaneous tracks whilst playing back 32 tracks I'd previously recorded. The MeLE had zero problems with the recordings. Obviously this is nowhere near powerful to mix on (I didn't even bother trying to add plugins), but for straight multi-track recording, it did the job with no issues. Considering this thing is only slightly larger than an old cassette case and has literally no moving parts, I was impressed. I tried recording both to the internal SSD and an external SDD connected via USB3 - it was fine in both scenarios. This is the rig I used for recording:

There is no facility in the PRV to edit Poly Aftertouch. The only way to edit Poly Aftertouch is via the Events List View. I'm sure adding something to the PRV has been discussed in the past, but since the majority of keyboards don't even support channel aftertouch, let alone poly aftertouch, it was probably deemed too much effort vs the number of users who'd benefit.

This is possible, but not while Cakewalk is running. You'd need to: 1. Shutdown Cakewalk 2. Unplug your nanoKONTROL Studio, then plug it back in setting the new mode 3. Make a backup your ctrlsurface.dat, then delete the original 4. Start Cakewalk, and set up your nanoKONTROL Studio as a different control surface within Cakewalk again. Also, given how Windows does it's port indexing, there's a likelihood that any other hardware ports would now be renumbered, so you may have to go into MIDI devices in preferences and re-order the MIDI Output ports appropriately. The alternative is to reboot your PC after step 3. So while technically possible, it's really not practical.