David Baay

I figured... just had to throw that in. ;^) Glad to hear you got it worked out.

It's a bit surprising that your I/O latencies are more than twice the buffer size each way (i.e. lots of hardware/firmware/bus latency), but if audio file playback sounds okay I wouldn't be too concerned about that just now. I suggest you start by clicking the Reset Config button in Preferences > Audio > Config File. Cakewalk will build a default AUD.INI, and back up the existing one. If that doesn't get it, try disabling '64-bit Double Precision Engine' and 'Use Multiprocessing Engine' one at a time to see if there's an issue with either of those in your system, or maybe with the related 'Plugin Load Balancing' if you have that enabled.

There is no simple, built-in function for doing this, but it can be done. I've posted this workaround a few times over the years. Awkward, I know, but it works. It would be a lot easier if Cakewalk let you enter times in samples - or even minutes and seconds - but it doesn't so you have to do some SMPTE conversions: 1. Enable Auto-stretch (a.k.a. Clip Follows Project in Auto-stretch mode) on all audio clips. 2. Select a MIDI or audio clip that runs the length of the project (or select in the timeline). 3. Go to Process > Fit to Time. 4. Convert the current Thru time to total frames (usually 30 frames/sec). 5. Divide that by the desired tempo change factor (e.g. 1.10 to get a 10% increase, 0.90 for a 10% decease). 6. Round and convert that new value to minutes:seconds:frames. 7. Enter that as the new Thru, and select Modify by Changing: Tempo Map. 8. Click OK. P.S. Since you're clearly a stickler for correct musical terminology (tempi vs. tempos), note that it's 'ritard' with an 'i'. The old forum would not have let you write '*****'... or even 'ritard' IIRC. ;^) P.P.S. Hmmm. ... I guess using derogitory terms is okay for groups, but not individuals.

How tight does it need to be? Your observation that Fit Improv honors the beat value in the meter gave me the idea that it would be possible to align the timeline only at measures by temporarily setting the meter to 1/1. This is often all I need to do for my purposes, and possibly would be adequate in your case - or at least give you a starting poiint for using Set Measure/Beat At Now to dial it in more precisely.

Hmmm... that's interesting. In most contexts, a beat is always quarter (actual tempo values are always 'quarters/minute', for example). That could actually be useful... But to answer your question, I don't think it will be possible to get tempos on dotted quarters with Fit Improv. SM/BAN is the way to go. What's the actual musical situation you're trying to address?

A 'beat' is always a quarter note in Cakewalk, regardless of the meter, and that's 'non-negotiable' with Fit Improv. Set Measure/Beat At Now allows more freedom in specifying where you align the timeline to MIDI, and treats notes that cross tempo changes properly where Fit Improv has a bit of an issue as discussed in a recent thread.

Yes I understood that. I was just pointing out that it's not documented. Ref. Guide says the Select tool will move a group of notes just by clicking and dragging one of them.

Release the click when the selection is complete, and then click again to move. Works as advertised, and is documented in the Ref. Guide, except that it isn't mentioned that you need to hold Shift to move a selection.

Note that I said you have to release Ctrl while continuing to hold the click before you start dragging. This is what makes it awkward. If you don' release Ctrl, you get a copy.

Yes, I noticed that. I found that the following rather awkward gesture allows moving a selection: - Ctrl+Left-click a note in the selection, then release Ctrl while continuing to hold the click, and drag. - Only the clicked note will appear to move while dragging, but when you release the click, the whole selection will move.

Right-click the Smart Tool button in the Tools module, and make sure the 'Move' option is checked.

Confirmed the Move tool seems completely broken in Staff View; I don't get the Move cursor at all. And it goes back at least to the final release of Platinum. But Smart Tool works fine for moving notes in the SV so there should be no need to switch to the PRV.

I don't know Battery, but would check directories it uses in Program Files and/or AppData for files that have been modified after a session with a certain project. Not sure if this is technically possible, but it sounds like Battery is saving a preset/config somewhere and restoring it independently of the plugin state saved in the project file.

Cannot repro a problem with either of those, but have no bright ideas for what would be causing that in your installation. Is it all projects, and have you restarted Cakewalk or rebooted lately?

In CbB they are 'Take Lanes', and Shift+T will toggle them open and closed, or you can click the button that shows at the far left side of the track header when the track height is a little bigger than minimized.

The symptoms are a little weird, but basically it sounds like you need to make sure each MIDI track is using a different channel, and different from whatever channel your controller is sending when you're playing along. And you'll need to change the patch on the channel you're playing to match whatever part you're trying to learn. I'm a little surprised to hear it's affecting both the Roland and the Motif. I would have expected this problem to be synth-specific. Would need to see the MIDI file to understand how the file itself might be causing the problem.

I haven't checked your 'Before' project, but I suspect you deleted the wrong guide track notes when cleaning up the dupes. IIRC, the earlier ones were the correct ones When I use Fit Improv in my cleaned up project, it comes out essentially the same as with SM/BAN, and does not have the 'out of whack proportions' in that region that yours does. I also tightened up the timing of my cleaned up project to snap the guide notes exactly to the corresponding notes in the original track where possible. That could also have made the difference. I'm attaching that cleaned up project. I changed the duration, velocity and pitch (to C4) of the guide track notes so they could be easily seen and distinguished from the musical track when looking at both in the PRV. The clip is muted so it's not heard on playback through TruePianos. EDIT: Looked at this some more, and can see Fit Improv miscalculating the duration of long notes crossing tempo changes vs. SM/BAN getting it right. SM/BAN re-calculates durations to maintain the absolute timing of Note Offs while Fit Improv does not. Having the guide track perfectly aligned did help avoid the issue for some shorter notes crossing a single tempo change, but not for the whole notes crossing several changes. FitImprovTest - Dupes Removed and Guide Timing Optimized.cwp

Yes, but the point of the forumula was simplify it to: -120/1,25 = -96 ticks

Set Measure/Beat At Now aligns the timeline to existing MIDI and Audio tracks without affecting the absolute timing of either. So it won't bring them in sync if they aren't already. And when you delete the tempo changes that brought the audio in sync with the timeline, the MIDI will follow, but the audio won't, so that's not going to get you what you want, either. What you want to do is align the timeline to the audio first using SM/BAN, and then import the MIDI, and it take on the project tempo(s).

The goal is just to create a 'Master' track within the project that renders the Master bus output to a WAV file, just to make sure you don't have a routing issue within the project or some problem with your export options that's causing the vocal to be dropped. Assuming everything is currently routed to your interface hardware output via a Master bus: - Insert > Audio Track - Double-click the track name and rename it 'Master Bounce'. - Expand the track header, and change the Output assignment to go directly to your audio interface/soundcard output. - Ctrl+Shift+A to de-select everything. - Tracks > Bounce to Track(s)... - In the bounce dialog, select Master Bounce as the Destination, change the Source Category to Buses, highlight only the Master bus, and OK. - Mute the Master bus (grouping in opposition with Master Bounce is not immediately necessary - just a convenience for toggling between the bounce and the 'live' mix later). - Start playback, and verify the vocal is present in the Master Bounce. - If so, stop playback, select that track's number, and File > Export > Audio > Files of type: MP3

Indirectly, yes. It just happens that I like to use 125bpm as a baseline for relating ticks to milliseconds at a given tempo because it's exactly 2 ticks/ms, making the math easy. Here's the full derivation; you would substitute a different 'delay' value in ms to get the simplified formula for a different delay: ticks = beats/minute x 960 ticks/beat / 60000 ms/minute x 50 ms --> beats/minute x 0.8 --> Tempo / 1.25 EDIT: And, of course, you need to enter a negative value in time+ to advance the AmpleGuitars track, effectively delaying the rest of the project relative to it; so the formula gets a minus sign: - Tempo / 1.25

Try going to Properties of non-workiing VSTis in Plugin Manager, and setting "Do not intercept NRPNs".

When you say "I can play the notes which are showing on the piano roll and they make a sound", do you mean on a hardware controller, on the PRV keyboard, or by clicking the notes in the PRV? Other possibilities: - Clips muted - Notes muted - MIDI channel mismatch - Instrument attack too slow for duration of MIDI notes. - Instrument's velocity response curve requires a high minimum velocity to be heard. - Wayward controllers silencing the synth. - MIDI Prepare Using buffer too low.

Oops. Make that Offset = - Tempo / 1.25 Glad to help.

Positive values delay playback of the offset track against the rest of the project, and negative values advance it. But it's fixed value in MIDI ticks, so you'll have to calculate the offset for a given, fixed project tempo. To advance the Ampleguitars track by 50ms: Offset = - Tempo / 2.5