David Baay

Non-multi-timbral instruments generally don't care what channel is embedded in the MIDI events; they will typically respond to anything by default.

The Inputs you're looking at now are the MIDI Inputs to Instrument tracks. If you don't have a MIDI controller or MIDI interface (or it's not powered up), it's normal to have only the virtual controller available. But if you're just wanting to play back existng MIDI clips, the Input assignment to the Instrument track doesn't matter. What matters is that the Output of the MIDI side of the the combined MIDI-audio Instrument track is assigned to the correct instrument in the synth rack.

If you normally do have a MIDI controller or some other source of hardware MIDI input, it's possible that the Instument track assgnments have gotten fouled up by those ports going missing. I've never encountered this issue myself, but others have reported it can happen.

The easiest way to sort things is to right-click and Split the Instrument track so you can verify the MIDI track 's Output is assigned to the correct synth, and the Audio track's Input is assigned to the correct synth output. You can also see the MIDI Output assignment on the MIDI tab in the Inspector for an Instrument track without splitting it, but the Audio tab will show the MIDI Input assignment (same as the MIDI tab) not the synth's ouput so it's best to just go ahead and split them. This also lets you watch the MIDI and Audio track meters at the same timeduring playback to see where the disconnect might be.

46 minutes ago, sjoens said:

Are you alluding to the new beta?

Oops, forgot where I was. Pay no attention to that man behind the curtain!

1 hour ago, jono grant said:

- The Clip on track two, was copy special/paste special to the exact beginning of the top clip. You can see it pasted a bit late.

- The clip on the bottom track was special copy/pasted to the marker. It went to the same place as track 2 clip.

*I also tried this with regular copy/paste same result.

I can't repro that. For me, both Paste Specials went to the marker because that's the M:B:T time that comes up in the Paste Special dialog. I never thought  about it before, but apparently Paste Special can only go to the nearest tick because of that. I'm not sure why yours would end up exactly 10 ticks after the marker unless the time somehow got fat-fingered before the dialog was OK'd...?

But when I do a normal Ctrl+V with the Now time at the start of the clip, the new clip pastes to that exact time (i.e. 3 samples after the tick).

Bottom line: You might want to consider revising your workflow to keep everything starting on whole ticks. 125bpm is 2 ticks per millisecond so there really shouldn't be a need to place anything with any finer resolution than that.

39 minutes ago, jono grant said:

- The clip after it on the same track, was the same clip, drag copied to my cursor (properly) and then I placed a marker at the clip start. Which is late. 

When you say "drag-copied to my cursor" do you mean Snap to Landmarks with Now checked? The marker is on the tick, but the clip is 3 samples late. When you insert a marker, it will go to the tick that that clip is nominally 'on', so if the clip is between ticks, there will be a discrepancy. I generally snap everything to ticks so I hadn't considered that possibility.

I still need to look at the other steps, but I noted your snap is set to  By rather than To which can also cause unexpected results if not intended.

I've also seen Preferences intermittently open in the background for years, and/or with a bold font or other drawing issues. The slow access to Keyboard Shortcuts (and slow open of Preferences if the last page you accessed was Shortcuts), started just a couple/few years ago. There was discussion on the forum at the time that it seemed to have gotten suddenly worse, but the Bakers never seemed to acknowledge that something significant had changed. All I know is that accessing Keyboard Shortcuts in ye olde SONAR Platinum is basically instantaneous with the same .kbn file. The slowness in CbB is real pain.

16 minutes ago, Glenn Stanton said:

but he also asked about the SMPTE settings

Yeah the Format setting is relevant, but not the Source.

I often seen this issue with zooming from 0 instead of at the cursor, but I don't see it being consistently related to some number of mouse clicks. For me it seems completely random, and will continue zooming from 0 once it happens until I release Alt and try again.

22 hours ago, jono grant said:

There should be a way to work "wild" and not on any grid.

When snap is completely disabled, the finest placement you can make is to the sample, so things effectively snap to samples in that case. When snap to Landmarks is enabled with Clips and Markers checked and the musical resolution disabled, you can snap markers to clips and vice versa. But be aware that markers will snap to clip boundaries (both starts and ends) in any track or lane.  If you have a lot of tracks and clips with variable start/end times, markers could be snapping to some clip boundary that's not onscreen or that you're just not paying attention to.

1 hour ago, Glenn Stanton said:

in preferences -> project -> clock select the SMPTE/MTC

This clock setting is for synchronizing to SMPTE or MIDI timecode from an external clock source and has no bearing on editing/snap behavior.

I prefer using Set Measure/Beat At Now to manually sync the timeline to a varying tempo. By the time you do all the tweaks to get Audiosnap to "do it for you" you can generally do it manually with greater precision and more flexibility (i.e not snapping every single quarter note when the tempo is pretty stable for a couple bars.

I'd be glad to take a look at your sample, but I have an eye appointment first thing tommorow and my vision will be pretty trashed until the evening. PM a link and I'll get to  it when I can. Or you can hunt up one of the many posts I've made about the process over the years and have a go yourself.

If you know it's 92bpm, and it was recorded to a click, you're better off just setting that project tempo manually. But the reason it's off is that Audiosnap is incorrectly detecting the clip tempo. Open the Clip Tempo Map from the Audiosnap Palette, and select the correct tempo from the drop-down at the bottom left of the clip.

I had a quick look at the manual. The YPG-635 does have Local On/Off, but that shouldn't have any bearing on your current issue. The purpose of turning Local Control Off is so that the YPG's sound module doesn't respond directly to the keyboard (via internal 'Local' connection between the keyboard its sound module) when you just want to use the keyboard as a controller to play a soft synth in the DAW or another external sound module.. The usual way to use a keyboard synth in Cakewalk is to have a MIDI track receiving and echoing MIDI back to the keyboard and an audio track receiving and echoing the synth's audio output to monitors connected to the audio interface/soundcard of the PC. That way you have complete control over what you record and hear from within Cakewalk. Both tracks need to have the Input Echo button enabled. For the MIDI track, Cakewalk will auto-echo it by default (see Always Echo Current MIDI Track in Preferences > MIDI Playback and Recording) when it's in focus (track name highlighted).

Right offhand, I didn't see that any particular mode needs to be set to get the Yamaha's sound module to respond to external MIDI input, so if you're able to set the MIDI track's Input and Output to the Yamaha, and Input Echo is enabled, it should be working. But you should double-check the 'PC Mode' setting against the manual to make sure you've got it right.

Does the keyboard have a MIDI Activity indicator on it that lights with incoming MIDI?  How are you monitoring the Yamaha's ouput - echoing it back through an audio track in CbB or direct from the keyboard to headphones/monitors?

Yes, you should be able place markers and clips anywhere when snap is disabled or exactly on the snap grid if it is enabled. Can you share a minimal project that isn't working as expected?

My guess is you're enabling Lock to SMPTE.  A SMPTE frame (1/30 of a second) is 64 ticks at 120bpm.

4 hours ago, RICHARD HUTCHINS said:

using the master gain I lift the volume

Depending on the musical content, it may not be possible to get it to -14LUFS without applying some compression to raise the RMS level while keeping the peaks from clipping.

3 hours ago, tdehan said:

Faulting module path: d:\Program Files\Cakewalk\Shared DXi\TTS-1\TTS-1.dll

Time to move on from General MIDI. Check the Event list for RPN/NRPN messages that might be making TTS-1 unhappy.

I suggest you install the Early Access 24.02 release from here:

2 hours ago, jono grant said:

msmcleod's post above worked in 2 seconds. Set all clips to absolute time and then lock them. 

If it's all one fixed tempo I suppose it would. I was thinking you wanted to use SM/BAN because the tempo was varying which is my usual use case.

Select the whole track, right-click a clip and choose Bounce to Clip(s).

Thanks for sharing. I've had dual monitors for years but still don't make good use of them because I find it somehow mentally uncomfortable to mouse and type while looking at the secondary display on the right, expecially when doing something complex.

2 hours ago, Glenn Stanton said:

with regards to David's approach - pulling down gain on each track, you risk altering the level into any effects on those tracks - esp saturation, amp sims, etc and same for the master buss - any effects on that with reduced gain may behave differently than changing the overall input levels.

I'm only suggesting to pull down the Master bus gain, and since he's remixing, it's assumed he will adjust any Mastering plug-ins (probably not even in place, yet) accordingly. Nothing else in the project should be affected.

3 hours ago, Michael Fogarty said:

is it ok to just lower the input of the master bus

Yes, that will be fine. Gain-staging purists will undoubtedly object, but I've done null tests with a 50 duplicates of a track summing to massive virtual clipping and been able to get a perfect null against a single inverted track by pulling down the bus gain by the exact amount need to offset the summing.

On 2/12/2024 at 5:25 PM, mettelus said:

Also note, the selection behavior only occurs when using the - on the NumPad. When using the number row, the "selection" behavior does not occur, so you can type in -3 and it takes as -3.

Okay, I wasn't understanding what you were saying until I read this. The issue isn't really about whether anything is selected or not. It's just which minus key you use. The one in the Numkey pad will never enter a minus sign in this context; it only decrements whatever the current value is. Regardless of whether the value is selected or not, you have to use the top row of the QWERTY to get a minus sign. The Numkeys increment/decrement values in other contexts as well (e.g. MIDI Key+ and Time+ offsets)

On 2/14/2024 at 11:00 AM, 57Gregy said:

CbB doesn't seem to work the same way as SONAR

Yes, it does. but you need to use Paste Special (Ctrl+Alt+V) to get the Paste dialog box. Very old versions of SONAR (like S8 and earlier) opened the Paste  dialog automatically every time.

Like Go To, the paste dialog defaults to the start time of the selection so all you have to do is change the Measure. Ultimately it's the same number of keystrokes as using Go To, but it might feel more straightforward.

Not at my PC to do the calculation, but if the underlying MIDI value is in microseconds/quarter note, then Sibelius is likely showing more precision than is available and should be rounding to fewer places.