David Baay

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.

I installed the trial and did a quick test using a project I developed to measure PDC. The test is sample-accurate and measured 9,984 samples (208 milliseconds at 48kHz) of delay. I didn't see any option to lower it by reducing the quality/precision of the processing, and no mention in the documentation of a delay. For good measure, I tried playing my RD-700NX through an input-monitored track with PDC Bypass disabled and the delay was horrendous and unplayable as expected. Notwithstanding that the web page claims "Real-time Processing", this plugin is only suited for post-processing of previously recorded audio at the mixing stage.

I was incidentally comparing Youlean and Sonar's numeric peaks recently and was actually surprised to see them reading identically because I'm pretty sure CW meters are not "true peak" (i.e. processing the samples as though converting to analog to find intersample peaks rather than just reporting the raw sample level). It's more likely the material I was metering just didn't have significant intersample peaks. I suspect calculating true peak on every track in a big project might add significant CPU load and would not be worth the overhead - maybe useful if it could just be selectively enabled on the Master bus which would usually be the only place it matters. In any case, I agree 1dB is a lot, and would make me suspect there might be some additional gain somewhere. Youlean is in the FX bin so any make-up gain, volume automation or post-FX Prochannel plugins could alter the track peak after Youlean sees it.

If the input to the external mixer is to separate mono channels, make sure they're panned hard left and right.

Did you change file Type to MIDI in the Save As dialog? Type 'Normal' is a Cakewalk project file with a CWP extension that other apps won't recognize.

In my view you can't go wrong using the free CbB until it will no longer activate because it's been fully superceded by Sonar. There should be plenty of warning about that to give you time to decide whether to subscribe to Bandlab, buy Sonar outright (if that ends up being an option) or port the (presumably few) projects you will have created in the mean time over to a different DAW. I'll also wager that even when activation is discontinued, you'll still be able to launch CbB and open projects to extract/export audio and MIDI, save plugin presets, etc. for some time to come; you just won't be able to save changes to the project file as is currently the case when not activated. CbB and Sonar have a good complement of VST FX already included, and I'm sure the bundled synth content will grow over time as the product is re-monitized. But, as has been suggested, few users restrict themselves to bundled VSTs for long, and that shouldn't be a major consideration in my view, given the vast number of free and inexpensive options available. The most important thing is that the DAW has a workflow that fits your compositional style and feels intuitive and inspiring.

Now there's a blast from the past... I had totally forgotten about that interlude.

A quick Google says EastWest instruments do not respond to CC7 by default (although I'm guessing it can be MIDI Learned). It uses CC11 Expression or possibly CC1 in some cases.

In case you're not aware, you can use drum maps with any MIDI OUT port whether physical or virtual; you just need to assign the Out Port in the Drum Map Manager. To assign all note numbers to the same port, hold Ctrl+Shift while assigning one. Newly added drum maps will default to the first available port, usually a physical one on your interface.

C:\Program Files\Cakewalk\Shared Utilities\Internal\ProChannelConcreteLimiter I bought it back in SONAR days so can't comment on it's availability in the new release.

This kind of stuff is very difficult to advise on without fully understanding the layout of the project, what you're trying to accomplish and the exact steps and moves you're trying to make to get there. I'm confident it's all explainable, but I would have to see the project. While starting over may still be the easiest course, depending on how out-of-whack (the technical term) things have become, I'm pretty sure I could fix the existing one if you care to share it.

The Bakers recently removed support for GS wavetable synths and also removed the TTS-1 multi-timbral soft synth at Roland's request. I can see that the ouput of the highlighted track is assigned to the UR22's out so, yes, I think you were listening to the Juno's output. Possibly it is no longer in the correct mode to act as a General MIDI synth. Also, ideally, you would want to add an audio track to the project to receive audio input from the Juno and echo it out to your monitors so you can record the Juno and monitor with plugin FX if desired. Then save the project as Type 'Normal' instead of MIDI so that it becomes a full-fledged Cakewalk project file. Re-saving as MIDI will lose all the CbB features and audio routing.

The pedal will cause the Juno to generate the CC64 sustain events that can be recorded in sound-on-sound mode in real time into the track with the MIDI notes. You'll hear the effect of the sustain messages acting on those notes as they play back so you can get the pedal timing right with a little practice. If some of them end up a little but to early or late, you can drag them around after the fact as needed in the Controller pane of the Piano Roll View. it's just a faster way to get the events into the track.

There is an option at the bottom of the Options tab of the Track View submenu called 'Stop at Project End' that will cause the behavior described in a new, empty project where the 'End' is effectively at 1:01:000. If you disabled it, the transport will run in an empty project. I always leave it disabled.

Try using the Channel, Bank and Patch controls in the MIDI track header (you might need to set the Track Control Manager to 'All' at the top of the Track View to see them or use the Track Inspector. The values you set there will be sent when the project is opened and every time Playback is started, and they'll written as events in the MIDI track when you Save As MIDI. https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Inspectors.2.html