David Baay

Wrong thread.

Sorry, but this is not consistent with telling people to read carefully which is insulting when delivered as an order with an exclamation point to someone who is clearly reading - and writing - more carefully than you are.

Not sure what you're getting at here. First, off, I never use Ctrl+Delete, and it did not work for me; I had to use the context menu. Redo is not available until I first Undo, so I did both, and both seemed to work fine...?

This is likely a big factor in this case - not enough reports to make it a priority. I had forgotten about it myself because I only stumbled on it the one time. It just sounded familiar enough that I looked back through my old bug reports to find it.

Please don't insult me. I did read carefully. You said nothing about preventing deletion of the bus in your first few posts. You just said you wanted limited controls to prevent you from inadvertently changing things. Peace. Out.

Select the clip, show clip properties in the inspector, and expand the Audiosnap section. Check the Enable box, set the Follow Option to Autostrech, and then enable Follow Project Tempo. Change the project tempo, and the clip will follow it. You'll want to experiment with the different online (realtime, non-destructive rendering on playback) and offline (used when exporting or bouncing) stretching algorithms to get the best result. It depends on what you're playing, of course, but I usually find that 70-80% of the target tempo is slow enough, and allows me to play more naturally than 50%. The less you stretch/compress the audio the better.

I did not say 'hide'. I said 'disable'. You could see the disabled controls if you chose, but would not be able to change their values or states, and there would be an indication of that, like having the control grayed out. Not everyone will share your particular idea of the perfect Master bus, so it would be better to generalize the capability of locking out controls so they can't be inadvertently changed.

Pretty weird symptoms. Maybe try Bounce to Clips before the first playback to render a new file. If it doesn't help, or breaks first-time playback, don't re-save the project.

I would alternatively propose just having the ability to selectively disable controls on any track/bus; this would give you this capability, and be more flexible and more broadly useful to more users.

Okay, after some head-scratching, I have figured out that SPFC/ASP is referring to Set Project From Clip/AudioSnaP. I'm not 100% clear on what the starting point was, but if you have tracks that were originally recorded to a click, and you just need to find the fixed tempo that matches, I would suggest using Set Measure/Beat At Now (SM/BAN) with the Now time snapped to a known measure and beat somewhere far out in the project (i,e, count out to the downbeat at 65:01, and 'Set' that). If the first downbeat isn't at time zero, and there are pick-up notes that prevent trimming and sliding everything back, you will first need to slide everything to put the first downbeat on 2:01, and 'Set' that beat as an anchor. If it's a live performance that was recorded without a click, you will likely need to set additional points to get the timeline synced up everywhere. Or you could try dragging a track to the timeline which uses Melodyne Essentials (installed from Bandlab Assistant) to create a tempo map. The results may be better than Audiosnap, but Melodyne has its own quirks that make me prefer doing it manually with SM/BAN. In any case, Cakewalk does have way of renumbering measures, so you'll just have to remember that the second 8 starts on 10:01 instead of 9:01, etc. if there's a pick-up measure.

Each MIDI track has a CH widget. That's the Output Channel assignment. If it's not showing in the track headers by default, you can use the Inspector. Everything in the track will get 'forced' to that channel on playback so it's non-destructive, and can quickly be changed to another channel.

Glad to help. Just setting the track Input to a specific port will avoid problems in most cases. Except in the case of multitimbral synths, you can have everything on channel 1, and just depend on every synth having it's own virtual MIDI port(s) to keep things isolated. Even with multitimbral instruments, most users still record/input all the actual MIDI events as channel 1 on every track, and just depend on the forced output 'CH' assignment in the track to re-channel the data on playback for the intended synth channel.

Fit Improv will do what you want, but you'll have to do it in a new project, or take the existing MIDI out of the project temporarily, and bring it back in because Fit Improv presupposes that everything already in the project will be in sync with your guide track, and is just going to change tempos to fit the guide track without affecting the absolute playback timing of any existing material. It will probably be easiest to just open a new project, tap out your guide track, execute Fit Improv, and then copy-paste the tempos from that project into the one with your existing MIDI.

If a MIDI track's input is set to Omni, which is the default when Input Echo is enabled for the first time (either manually or by Always Echo Current MIDI Track in preferences), that track can receive MIDI from anywhere, including virtual MIDI outputs of other synths, which is probably the issue in your case. The solution is to deliberately set a the Input of every track only to a specific port and channel (usually matching your controller keyboard) when you create it. You may also want to disable MIDI Out in the properties of virtual instruments that have one that you're not using. Personally, I keep Always Echo Current MIDI Track disabled because I like to be in control of which tracks are echoing even if it takes a little extra clicking.

This is an old issue that I reported way back in 2016. Last worked as expected in X3e.

Looks like a bug to me. Arming a Simple Instrument track by the shortcut should only enable MIDI recording as you expected - same as clicking the record arming button.

As Mark noted, the Absolute (SMPTE) runtime of audio clips will not be affected, but they will appear to change length because the Musical (M:B:T) time scale is the fixed, visual reference in Cakewalk. Importantly, however, the start time of audio clips is set to follow 'Musical Time' (M:B:T) by default, so any clip not starting at time zero will maintain its position in the M:B:T time and get audibly out of sync with clips starting at other times. In order to prevent this, you can either change the Timebase property of all audio clips to Absolute from Musical time before making any tempo changes, or (a better option in my view), use Set Measure/Beat At Now to change the tempo, which automatically preserves the Absolute playback timing of all clips (both audio and MIDI) in a project. To do this: - Set the the Now time cursor at measure Current Tempo + 1 with snap enabled. - Hit Ctrl+M to open the Set Measure/Beat At Now dialog. - Enter the Measure as Target Tempo + 1, Beat 1, and OK.

+1 for for all of your suggestions, especially an option to turn off auto-scaling (with a context menu option to 'fit' the scale one time), and an option to use only jump-type tempo changes.

Sounds a bit like what I've seen when attempting render direct to MP3 in real time. If rendering to MP3, definitely use Fast bounce. If rendering to .WAV either use Fast Bounce or try a more 'middling' buffer size like 1024 if the system can handle it. But could still be a plug-in; try disabling anything in the project that you don't use regularly.

So when do we get a to hear this piece? I'm a big fan of unusual time signatures, syncopation, counterproint, etc

You mentioned 'recording' tracks. If that means you're using synth recording and/or exporting with Fast Bounce disabled, you should try enabling it. Fast Bounce is an offline process that is largely immune to resource limitations, and frees the rendering process of the need to manage streaming output to the interface in real time. But it does use the realtime buffer size as a 'chunk' size for processing by default which can be problematic if it's small. You can override this by setting a non-zero value for BounceBufSizeMsec in the config file (AUD.INI). I've had mine at 20 (milliseconds) for a long time to avoid problems with certain synths that behave badly when rendered offline with small buffer size I usually run. Values up to 200 or even 300 are not unreasonable to try, and may improve render speed, but will use more RAM which might be an issue in your case with the high track/instrument count. One way or another, unless there's some interoperability bug between Cakewalk and EastWest, you should be able to resolve this with configuration or procedural changes that don't require disabling synth instances. FWIW, I also found this which might be applicable if one instance alone drops notes: "[The polyphony option is] in the main PLAY window (not the browser) at the bottom of paramaters on the left (starts with MIDI device, then MIDI port etc). It's set to 32 voices as standard which often isn't enough at all (for me) if you have many notes playing at same time (with release trails). I have mine set to 64 which mostly covers it."

Do you have a -6dB Center Pan Law set? It's under Preferences > Driver Settings > Pan law, but is actually a per-project setting..

Hmmm... yeah. that may help in some cases. I leave it disabled because it has other side-effects I don't like, and some actual bugs, so I kind of forgot about it. It's been so long since I thought about it, I'd have to go hunt up some threads on the old forum to remember all the issues. With all the work the Bakers have done in the last few years, some may have been fixed in the mean time.

Actually, this has always been a thing. Cakewalk came late to the concept of MIDI 'clips, and their boundaries have always been defined by the starting and ending event times. The exception is a MIDI Groove clip which has a defined number of Beats in Clip that allows it to have empty space at the end. So one way of dealing with this is to convert the clip to a Groove Clip. Their are ways of preserving empty space in a MIDI clip when doing certain operations, but the only surefire way is to preserve space no matter what you do is to insert dummy controller events ( I usually recommend Pedal Up, CC64=0) or silent, zero-velocity note events in the clip at the desired start and end times.

Muting clips and enabling 'hide muted clips' is only necessary when you want to hide notes in different lanes of the same track. To show only the notes of one track, you just need to open the Track Pane at the right side of the PRV (View Show/Hide Track Pane. This gives multiple options for filtering what you can see and edit. Normally it will default to just showing the track you double-clicked as you expect: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingMIDI.10.html