brundlefly

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.

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.

The Project menu was introduced with Skylight in X1. Not sure why exactly except possibly just to keep the Insert menu from getting overloaded. All the "Insert items" in the Project menu are related to the timeline where the Insert menu is more about adding content. Works for me.

Thanks, Mark. With that in mind I'm giving it a whirl on my I7 11800H laptop with Win11. It certainly didn't bring Sonar to its knees like it did on the older machine, but I did get one late buffer (heard the pop) about 30 seconds into a very light project that was hardly moving the performance meter. Will run with it for a while and see how it goes with different projects.

I realize this comment is a year old, but for the benefit of anyone stumbling on this now that it's been bumped, ThreadSchedulingModel = 3 is an experimental "aggressive" thread- scheduling model that I think has been proven to be statistically more likely to cause glitches than to resolve them for most users. SONAR became severely disfunctional on my i7 6700k desktop machine when I tried this non-default setting when it was first introduced. Others reported similar problems, and I know of few who have benefitted long-term. Feel free to try it, but keep an eye out for issues that may not manifest immediately or in all projects, and don't forget that you did it as many did at the time, claiming they hadn't changed anything and that problems were due to the update itself. The default ThreadSchedulingModel = 2 is best for the majority of machines.

You can use the Arranger (see the Ref. Guide), but if it's going to be the primary version of the song, I would do it the old-fashioned way: 0. Save the project as it is now. 1. Enable Ripple All in the upper right corner of the Track View next to the Auto-Crossfade setting. Ripple All ensures everything in the project (all tracks, tempos, track/bus automation, etc) are moved/copied/pasted/deleted when you move/copy/paste/insert/delete even a small part of one track. 2. Set the Now time to the place where the repeats will start, and Project > Insert Time/Measures. 3. Insert the number of Measure needed to acommodate the three repeats. 4. Select in the timeline or a maybe a clip in some track that conveniently emcompasses the full length of the chorus. 5. Ctrl+C to copy, and then Ctrl+Alt+V to Paste Special with 3 repeats. 6. Add volume automation to the Master bus, with a nodes at 0dB where the fade starts and -Inf where it will end, and choose an the desired curve. I usually like Fast Out over about the last 8-16 measures, depending on the tempo and song structure. 6. Save As the new version with a suffix added to the name like " - Added Chorus Repeats and Fade Out".

No, MIDI content is saved directly in the project and can be lost if too many levels of Undo are accumulated between saves, or if you save after it's deleted without changing the project name. This is one of many reasons to use Save As with a suffix added to the name after major edits (like deleting a track that's not empty) so you have backups of earlier versions. You might also consider increasing the number of levels of Undo.

I'm guessing you need to right-click the resolution and uncheck Smart Grid. Smart Grid auto-adjusts the resolution based on the timeline zoom level.

You can swipe in the Controller Pane with the Erase Tool or right-click and drag to lasso and hit the Delete key. The Erase tool doesn't care where you drag in the controller pane vertically, but Lasso requires 'capturing' the top of the controller 'tail'. For controllers with values of 0 or 127 (e.g. Pedal Up/Down), this is most easily accomplished by dragging outward from the center of the lane up to the top or down to the bottom. To get both, drag one way first, then hold Ctrl and drag the other way to add the selection. Like Promidi, I'm a big fan of Select By Filter, but some people really prefer doing everything graphically with the mouse.

To get a project to open in Safe mode you should have CbB already open. and then hold Shift while double-clicking the project file in Windows Explorer. If CbB isn't already open, the Shift is intercepted by the application launch process and causes it to 're-personalize'. The Bitbridge error is going to be due to some 32-bit plugin in the project that needs to be stopped from loading in Safe mode.

The crash dialog and/or dump text identified Session Drummer as the faulting module, explicitly? I have never seen that, and I've run quite a few old projects in Sonar that used it. I agree Bandab should provide a method to upload large dump files directly, but I don't get too aggro about having to use my own share (OneDrive).

The motion of the Now cursor in the Track View has been recently improved in Sonar. The PRV Now cursor does not seem to have benefitted, but I don't think it's any worse than either of them were in CbB, just more noticeable compared to the new Track View cursor.

Not sure why this isn't working or what the error is, but why don't you just open the X1 project in CbB and finish it there? Even if you really want to stay in X1 for some reason, you can transfer it back after freezing the track in CbB. X1 will warn that the project is from a newer release, but shouldn't have any problem opening and re-saving it.