David Baay

The first step would be to determine if it's a MIDI problem or an audio problem. Since you already have separate MIDI and synth tracks, Check the MIDI track meter when the synth is not sounding to confirm MIDI is or is not being echoed (MIDI track meters are output meters, and are not affected by the arming state) If it's a MIDI echo problem, possibly the 'Always Echo Current MIDI Track function is failing somehow, in which case you might try forcing Echo On by clicking the button. If MIDI is being successfully echoed, and the synth is not sounding. I would check to see if disabling Zero Controllers When Playback Stops might have a bearing . Depending on the synth, this might be evident from watching for the mod wheel or faders in the synth's UI to change when the transport is stopped/started. It would be unusual for a channelization issue to depend on the state of playback, recording or arming, so I doubt that's relevant.

I actually reported as a defect a long time ago that automation editing should not create two nodes on the same timestamp. For consistency and ease of editing, it seems to me that an 'instantaneous' change should always be represented as a jump segment.

Maybe there shouldn't be, but based on the video, it seems there can be...? Jumps just seem a lot more logical and simpler to deal with - one node per change. Seems kind of weird to see two different tempos on the same timestamp in the tempo list too.

It's a bit hard to follow exactly what is happening, but the tool shown is for moving the split point not the slip-editing tool for moving a single clip boundary. Moving the split point will replace the waveform on the left side with the waveform on the right. While the behavior you captured does seem a bit buggy, I would say the root of the problem is that you have two tempo nodes on the same time to begin with rather than having a single node with a 'jump' transition from the previous tempo. Moving the single node at a jump point will behave as expected.

At a minimum, you should compare and/or swap AUD.INI files between the two installations. Assuming you're on Windows 10, whatever issue you're experiencing is highly likely to be a config problem. CbB started with the codebase of SONAR Platinum that was as stable or more stable than anything before it and has continued to be developed by many of the same people, including former Cakewalk CTO, Noel Borthwick, Given that, there would be no reason for "teething problems". Clearly your experience and the OP's are exceptions to the rule that that vast majority of users who didn't bail while CW/SONAR was temporarily orphaned have happily moved on to CbB and would never consider going back to any release of SONAR and losing the hundreds of new features and assorted improvements that have been implemented since. I took advantage of the Studio One crossgrade deal that was offered when Gibson abandoned Cakewalk, just in case the abandonment turned out to be permanent, but have never found a good reason to continuing using it. Bottom line: You should make every effort to figure out why CbB isn't working as well as X3 on your system. You have nothing to lose but a little time and everything to gain.

Good deal. I should have made it clear where the PRV-specific To/By setting is; it's a bit hidden. Cakewalk is so deep it's really easy to overlook things like this, but I try to trust the software and question myself first when something unexpected happens.

I do it regularly; a lot of my compositions lately are using it - sometimes including the second above the low note in which case I'm hitting both with my thumb which shortens the distance. But I can do the 9th by itself pretty easily with the same span.

Actually, no. I use it all the time and have not seen unexpected behavior for a long time except when settings were not right for what I wanted to do - i.e. user error. There were some issues within the first couple years of its introduction (back when major releases were only annual) but so far as I know everything has been ironed out at this point. I'd be really interested to see a copy of a project that isn't working as expected.

7.75" and can't reach more the an octave plus a second, either, but I've had no complaints.

I just picked up one of these to replace my ancient MIDI Express XT. My main goal was to reduce MIDI transmission delay, and the mio XL delivered in spades. The MOTU was one of the first Windows-compatible versions delivered, and was quite slow - about 5ms each way. The mioXL is barely over 1ms each way - gotta love it. Unfortunately I don't have much to offer the OP in the way of suggestions other than to leave everything connected as bdickens suggested and make sure it's all turned on before starting Cakewalk. And whatever you do, don't re-save a project that isn't routing correctly. That said, even when I would forget to turn on the MOTU, Cakewalk was picking it up just fine when it was turned on with a project already open running, and I've never had soft synth ports get mixed up when hardware ports were missing. But I don't have any control surfaces set up at the moment which may be a factor. And I don't run other USB MIDI devices either; everything went through the MOTU and will now go through the mioXL.

Snap 'By' instead of 'To' enabled for PRV snap? Or the Snap to MIDI Events button is enabled?

I recall running into this quite a while back. I believe I submitted a project to the Bakers but don't recall whether anything ever came of it. I'll have to look back and see if I have notes or a demo project.

Given that you just want to be able to pass a contiguous range of notes in the center and save it as a preset filter that can be applied to multiple files, I second musekamp's approach. The drum map solution was needed in my case because the passed notes weren't a contiguous range, and I didn't plan to delete anything. I just wanted be able to hear what was missing, and then transpose/re-orchestrate to preserve as much of a performance as possible.

It only seems global because the Cakewalk forum is a hotspot.

It might be, but there must be more to it than that Set Project is generally broken. Must be something project/content/configuration-specific. EDIT: Can you share the audio file?

Undupe.cal

Num Keys on the 10-key pad nudge by default if Numlock is off.

That's a little strange because the only way you get a duration that small by having Last Touched set in which case it would only stay that small until you drew a longer note. In any case, the draw duration shouldn't have any bearing on where the start times snap. I would have to go with Mark's suggestion that you inadvertently nudged the whole clip at some point.

I use a Drum Map to pass only notes that can be played by a physical music box when composing for that instrument using a VSTi.

FWIW I consider this to be somewhat of a myth. I start pretty much all my projects at 1:01:000 without issues unless: 1. There are pick-up notes before the downbeat. 2. An external hardware synth needs time to respond to a patch change or other controllers or SysX. But I don' t think this was the OP's concern in any case. He just wanted to include the "dead air" in the pre-roll he has already built into his project.

+1

Following on my previous post, I did a quick test: 1. Found and old project from 2016 that was deliberately set up to test Set Project (last Splat was 2017.10). 2. Opened it in CbB, and it got a 'toast' notification that it was detecting transients - apparently because there were no files for the audio in the Picture Cache. 3. Executed Set Project without doing anything else and it worked as expected, resetting a 100bpm project to the 125bpm fixed tempo of the clip. 4. Closed the project and CbB without saving and deleted the relevant files from the Picture Cache. 5. Opened the project in Splat 17.10, to have it write the picture files, and executed Set Project with the same successful result. 6. Closed the project and Splat without saving. 7. Re-opened it in CbB, and confirmed it did not re-detect transients because the Splat-generated picture files were still in place. 8. Executed Set Project, and it still worked as expected. I did not find anything in Aud,ini or Cakewalk,ini referencing the transient detection setting I mentioned so I think it must be the default.

CbB uses a different transient-detection algorithm by default. IIRC you can force it to use the old algorithm with an option in the Config File (AUD.INI). If AS was already enabled in a project saved from Platinum, you might need to set CbB to use the old algorithm if you don't first have it re-detect transients either by bouncing or by Re-compute Pictures. I haven't run into anything like this, but haven't had a need to Set Project in anything that dates to Splat era. I generally use Set Measure/Beat At Now anyway.

No, Step Sequencer is just a MIDI sequencer that drives a synth..

I'm not really clear on what the situation or goal is. Cakewalk does not yet provide any kind of 'pre-roll' capability. If you need to have anything happen before the first downbeat, you'll have to slide everything out to start at 2:01:000. But your post also suggests you're having to insert some dummy audio to get the transport to run in an empty project which you can avoided by disabling 'Stop at Project End' at the bottom of the Options menu in the Track View. EDIT: On re-reading I think I understand that you just want all the clips to start at 1:01:000 (i.e. 'Time Zero' = Bar 1). In that case you can just drag the start boundary of the first clip in every track back to 'zero', select everything, right-click and choose 'Bounce to Clip(s)'.