David Baay

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.

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.

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

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.

What does "won't load" mean? Is there an error? Possibly VB-Audio overwrote the MS VC++ Redistributable with something that's incompatible with CbB.

In DAW world there is no meaningful difference between a Strip FX and an Insert FX they are both "in line" such that everything at the track input is forced to go through them (notwithstanding that some module might have a parallel path built into it). The Prochannel is effectively just a second FX bin that can be placed before or after the track FX bin, just as a 3rd-party channel strip plugin can be placed before or after other plugins in the FX bin. And then there's the Clip FX rack which gives you a place to put a plugin ahead of everything once the live input's been recorded. In some sense it's a moot question because by the time any plugin anywhere in the DAW sees the signal it's already been amplified to line level before it was digitized whether by the mic pre built in to the interface or by an external mic pre into the interface's line in or by the amp in a hardware instrument that outputs line level.

That's totally uncalled for, and the exact opposite of "please don’t read too much into this". I trust you'll be back here with your half-eaten hat in hand if and when it turns out there is in fact a perpetual license option...?

You haven't seen any of my 3000 posts about using Set Measure/Beat At Now to match MIDI/Audio tempos? ;^) It's way more precise.

As noted in the older thread you bumped, if you want to change the project tempo and have the audio follow the change, you can enable Follow Project in the Audiosnap section of the Clip Properties tab in the Track Inspector. You'll probably want to set the Follow Option to Autostretch first to have it stretch uniformly without regard to where transients are. Or you can Slip-stretch the clip by holding Ctrl+Shift and dragging the clip start/end to have it play slower/faster without changing the project tempo. This will also enable Audiosnap and you can see and adjust the Stretch Amount (percentage) in Clip Properties and change the algorithm that's used to render the stretching.

Hold Ctrl+Shift and hover over the clip start/end to get the Slip-Stretching tool.

You can lasso clips in lanes (or select an entire track)and execute Bounce to Clip(s) (from the Clips menu in the Track View or the clip context menu to combine them, and then delete the empty take lane. CbB keeps recorded takes separate by default and does not have the oft-requested option to automatically merge new input into an existing clip while recording. You can always split clips within a lane or selectively cut/paste/drag some notes to a different lane after the fact to facilitate arranging.