David Baay

Sounds like the UIs have somehow gotten moved off-screen. They open as expected for me in your project, but I noticed the Multidock was undocked and minimized. I'm attaching a copy of the project in which I've re-docked the Multidock, and docked some of the synth UIs in it. If you undock them from there, possibly their screen coordinates will be corrected.

I had to re-direct where it was looking for audio files since it was apparently using the Global Audio folder on F: so you'll have to re-reference that folder when it prompts for missing files. I highly recommend you switch to using per-project audio.

Phil's project - Synth UIs in Multidock.cwp

2 hours ago, Emanu3le85 said:

I have tried many times to set the clock to internal but it automatically goes back to Audio,

If you have the metronome set to Audio, the clock will be forced to Audio. Likewise if the project has any soft synth or any audio track with input echo enabled. To use 'Internal', the project has to have only MIDI tracks and MIDI metronome. But that's not what you want anyway.

6 hours ago, Elijah K said:

So how do disable that ridiculous feature forever and ever?

On the contrary it's a highly useful feature in many contexts such as when editing drum parts in which case you are likely to want to select all the notes on a given note number to change their velocity/timing or drag them to a different note number to switch instruments/articulations. It's also useful for grabbing all the notes across a range of pitches (e.g. bass or melody notes) to cut/copy and paste them to different track to be played or coubled by a different instrument or transposed up or down an octave.

I don't draw my music to start with so I seldom have a need to preview a pitch by clicking in the keyboard, but I would recommend you just draw a new note to hear it. If it's not the right pitch, you can drag it where it needs to be or right-click to delete it. Or get in the habit of immediately clicking an empty area of the PRV after clicking a key to deselect everything. You can also Ctrl+click the same note to de-select.

9 minutes ago, User 905133 said:

USB?

Yes, USB. The PC version of the hardware actually shipped with a chip that you had to swap out to make the port compatible with Wintel USB.

But, you're right to question as I realize I was off by a decade. It must have been early 2000s when I got my first laptop that needed external MIDI.

It got tossed (actually just hidden initially) because it was only designed to offset the MIDI tempo and Pro Audio/SONAR did not initially have audio-stretching capabilities. You can now get the same effect using Tempo Offset by percent, but you have to enable Audiosnap Clip Follows Project in Autostretch mode on any audio in the project as Promidi mentioned in the first response. And it's not as easily done temporarily because it's destructive to the tempo map and percentages have to be whole numbers so it's not easy to get a perfectly reversible ratio other than 80% and 125%.

21 hours ago, minminmusic said:

So the next question I have...is it possible to repitch a track in Cakewalk similar to Live where in essence...it's just speeding up or down the whole track (with pitch) depending on how you set it?

No, you actually have to jump through some hoops to get CbB to change pitch corresponding to the change in playback speed, and it's unlikely to have fewer artifacts because it's two separate DSP operations. If Live is just re-sampling the audio at a lower rate with fewer total samples to make it play back more quickly at the interface clock rate, I believe that would tend to produce the cleanest result other than the slight alteration of pitch formants (chupmunk effect) that shouldn't be a probem with small changes in tempo.

Personally, I think it's n urban myth that MOTU don't know how to write good drivers for Windows. They've been shipping Windows-compatible hardware and drivers since the early '90s. I have a MOTU MIDI Express XT interface from that era that still works fine under windows 10, and my MOTU PCIe-424/2408mkii interface runs great at 64 samples and even 32 if the project is light. Where interfaces mainly differ is in how much hardware/firmware/bus latency is added to the buffer latency, and that's where the MOTU shines because it's PCIe instead of USB. Pops/clicks/dropouts are all about whether the DAW application can get the buffer of audio processed before the interface driver requests it and Windows responding in a timely manner to the interrupt request to fill the buffer (that's where the Deferred Procedure Call latency - what LatencyMon measures - comes into the picture), and that's where you need start diagnosing problems with streaming performance . No doubt there are some dodgy ASIO drivers out there, but they're not coming from companies with the expertise and reputation of MOTU.

Most people would find the latency with that buffer size troubling. I generally run a 64-sample buffer while recording, and never more than 128, especially when input-monitoring  hardware synths. But you mentioned sync problems on the order of "a few seconds" which is a lot even for a PDC problem. The only thing I know of that has ever caused that much of a problem is some interface drivers not playing nice with Metronome Count-in enabled. Try recording without it. If it makes a difference and you have not had this issue before, a reboot might cure it. Also make sure to zero out any Timing Offset you might have tried in Sync and Caching (not to be confused with the Manual Offset for audio record latency compensation).

Since you have a number of posts not mentioning this problem, I take it's a new problem and/or project-specific...? Are you still using the MOTU M4 for both audio (presumablyin ASIO mode) and MIDI input or are you using a USB MIDI keyboard?  What buffer size and what reported input/output/round-trip latency in CbB? What plugins have been recently added to the project and where? If it's due to a PDC-inducing plugin, enabling the PDC Override button in the Mix module will only work if the offending plugin isn't on the track that you're monitoring or on a bus in its path to the output. Bypassing all FX  by the button in the Mix module should eliminate PDC but you might have to toggle playback to reset it.

2 hours ago, Jim Stamper said:

1 out of 5 times when I Save projects that are prone to it. 

You definitely need to submit such a project to the Bakers for investigation with details about how your machine is configured with regard to file storage and audio hardware/drivers, and what your workflow is like. I have only encountered this error a handful of times in decades with Cakewalk and never more than once with any given project that I can recall - literally years between occurrences.

Was it in the multidock or undocked? Shift+D to maximize the multidock. Second monitor?

Next Marker and Previous Marker in the Global context.

I have a Sonar 7 T-shirt that I wear sparingly to preserve it (and because it's tight and shows off my beer belly).

I could go for a coffee cup beer mug.

For me, the crash was happening with the VST3 until I got the missing instrument installed. I didn't think to try the VST2 before doing that, but if you have existing projects using the VST3 that are crashing, switching to the VST2 isn't easily done unless you know what instrument was being used and hadn't tweaked anything.

Sampletank is crashing CbB/Sonar when opening an existing project on my Win11 laptop but not on my Win10 desktop machine where the project originated. The big difference other than O/S and newer CPU is that the laptop is normally running onboard Intel graphics to save power, but switching to the Nvidia RTX did not help. The other difference is that the laptop does not have all the instruments installed that the desktop has, and I suspect is does not have the patches used in this project. Instantiating a new instance of Sampletank in a new project does not crash on the laptop so the crash might have to do with the missing patches.  I'll look into that.

EDIT:  Getting the missing instrument installed on the laptop eliminated the crash. This is something IK Multimedia need to look into.

This is because the controllers are being recorded into a second Take Lane, and when lanes are not showing the clips are 'layered' in the parent track such that the controller clip can be hiding the notes clip. Bounce to Clip(s) combines them into one clip which would normally be what you want. If you show lanes after that (Shift+T or click the Take Lanes button at the lower left corner of the track), you'll see there's now an empty lane that you can delete. It has been frequently requested that CbB have an option to merge new recordings into existing clips but this has not yet been implemented.

I can't repro a probem, and the LP-64 doesn't have a precision/quality setting that would affect the phase management and can't differentially process the stereo channels like the later LP MB, so I'm not sure how that would happen.

13 hours ago, AutoDoc Williams said:

I'm suspicious that maybe this happens when my PC goes to sleep and wakes back up as I normally just walk away from whatever I'm doing and don't shut Cakewalk down.  Right or wrong, I have always done this and have only recently seen this behavior.  Is it only me?

I reglarly do this as well, and have never seen anything like what you describe. As you probably know, flatline clips would usually indicate a problem with the picture cache, so I would start with clearing the cache (or just moving everything to another folder).

If that didn't do the trick, rather than re-importing audio files, I would just temporarily move them (e.g. to a subdirectory of the project audio folder named "temp") so they show up "missing" on opening the project, then move them back into the project audio folder and select the first reported missing one. After that, it should find them all without prompting further and automatically create new picture files.

Then you could bring the moved picture cache files back in to the cache, choosing "No" to replacing duplicate files, so CbB doesn't have to recompute every other picture file as well.

Interesting. What are the dates/sizes of the good and bad ones?

I found that it crashed when loaded normally, but when loading in Safe mode, I could choose 'Yes to All' and it would load fine. I have all the plugins except the Kilohearts stuff and the [QuikQuak?] Pitchwheel FX.

I added a Master bus and routed all the tracks to it. I don't have whatever SFZ files or Kontakt libraries were loaded in Sforzando and Kontakt so the only tracks that sound are Vital and BBC Symphony Orchestra, but those play fine.

Sforzando is 16-channel multitimbral so I was a little surprised to see so many individual instances being loaded, but I understand some people like to work that way for simplicity, and it didn't seem to be a problem.

Re-saved project attached.

SZJ's Crashing Project.zip

3 hours ago, SZJ said:

what is a safe mode

Browse to the project (from Existing Projects in CbB or via the Browse button in Sonar), and hold Shift while clicking to open the project. You will prompted to confirm/deny loading of each plugin used in the project. First try 'No to All' to verify it loads successfully with no plugins. Then close, re-open in Safe mode again, and try excluding only plugins that have been recently added or that you otherwise suspect might be causing the problem because they're new to you or maybe recently updated.

https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Automation.11.html

Yes, you can temporarily change tempo of all the audio, including frozen synths. It's non-destructive and completely reversible, but still best to use a copy of the project:

- Ctrl+A to Select All

- Go to the Audiosnap section of Clip Properties in the Inspector and check the Enable box.

- Select Autostretch in Follow Options

- Enable Follow Project and wait for CbB/Sonar to Autostretch-enable all the clips.

- Change the tempo.

If you like the feel, you can set the optimal offline stretching algorithm for each recorded audio clip and bounce to clip(s) to see if the quality is acceptable for your purposes (generally not for publishing/distribution purposes but okay for a demo). And, of course, the synths can just be unfrozen/refrozen at the new tempo.

EDIT:  I should add that the quick and dirty way that will be just as effective for the preview is to bounce the Master bus to a track that outputs directly Main Outs, solo it, Autostretch enable just that clip and change the tempo. You might actually find you get fewer artifacts from stretching the master than stretching individual clips and then mixing down.

Three options:

- Delete the section of AUD.INI starting with something like [Generic Low Latency ASIO Driver (1 in, 1 out)].

- Remove the Generic Low Latency Driver key from the registry under HKEY_LOCAL_MACHINE\SOFTWARE\ASIO

- Rename AUD.INI and let CbB build a default one.

I would start with both the 1st and 2nd options, and use the 3rd option as a last resort.

I think it has to be implemented as part of the main application to get direct access to hardware audio ports.