David Baay

You'll need to get WASAPI Exclusive driver mode working. That will let you get down to a 3ms buffer. But I don't have any pointers for making it work if it isn't doing so right out of the box. Unless possibly some VSTi you installed added its own driver for a standalone host that is interfering with WASAPI...?

The IK site shows SampleTron 2 is already included in TS3.5 though the JRR page does not. I got just about everything included with TSM 3.5 that I didn't already have with TSM 2 during the last Group Buy, but there's enough here to make me jump: Full MODO Drum 1.0, SampleTron 2, Hammond B-3X and MixBox. These were all $199 products during the Group Buy, and I only bought in at $149 (ARC System 3 with MEMS) with a double-dip at $49 to get all the cheaper instruments and FX.

I actually looked for a model with Nvidia graphics because I'll be running RC flight simulator software, but also because its been my experience that Cakewalk does not tend to have any issues with Nvidia drivers (with one exception involving a particular VST3's UI that was resolved relatively quickly with an update by Nvidia). Default scaling was 200%. I tried initially backing it off to 160%, but my eyes couldn't keep up. I'm now at 180%, and everything seems fine. I have not noticed any artifacts or other display weirdness, but obviously I have not been working with it for very long. At 200% the top of the Track Inspector in CbB was cut off which was the main reason for wanting to scale down a bit, and, of course just to have maximum room for track headers or PRV plus Tempo View, etc. I've never actually done a lot of audio work on a laptop, and don't expect to now. Other than just having CW as a reference when browsing and posting here and using it as a 'sandbox' for getting familiar with new software/plugins and trying out demos/freeware, the main thing I do on it is editing MIDI which doesn't require great audio quality and can be done while watching news or sports with half an eye on the TV or while having morning coffee and donuts in the recliner. ;^)

FWIW, I just picked up a Dell Inspiron 16 Plus, 16GB, 512GB SSD for under $1000 from their outlet store a couple weeks ago. It's immaculate, and you would not know it's not "A" stock. The chassis is all-aluminum and is a step up from previous generation Inspirons - comparable to XPS build quality, I think. My main DAW is an XPS8900 that was also a refurb and has worked flawlessly for 7 years with just the case fan replaced. Both are pretty quiet and stream smoothly at low latency with low and stable DPC latency, even with Wi-Fi left active though I do disable Bluetooth. The notebook is Win11, but I'm okay with moving on and have had no issues with it so far. IPS 3K 16:10 display is non-touch but has accurate color for photo editing and looks fantastic. It has a slot for a second SSD, and I will probably add one soon. My last desktop DAW was also a Dell and served me well for 7 years before the XPS. A lot of people seem be down on off-the-shelf machines for DAW use and Dell, especially, but I have had great luck with them.

The issue is with editing controllers: "...when I move a controller (not always) and move it up or down other controllers in separate tracks get grabbed and move at the same time."

I'm talking about the clip-linking feature documented below. If you right-click on one of the clips, and "Unlink" is grayed out, that's not the problem. http://gaga.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Arranging.44.html

FWIW, I don't recall ever seeing any of that.

This is the only think I know of that will cause Slide to be grayed out. Nudge options other than changing nudge settings will also be grayed out. Locking Data Only should not cause this to happen but does.

Are they unrelated clips or possibly copied as linked clips? As you probably know linked clips will be shown with dotted outlines in the track view. Otherwise have not seen that myself and don't know what could cause it other than a bug.

So I guess it's going to be another 16 months before the OP comes back to check for responses...? Not surprising, I suppose, given the features he's complaining about were implemented 10 years ago!

Strange, your selections are fine, and nothing there should really have a bearing unless you were to choose Instrument Track per Output - Mono or All Outputs - Mono. I did a quick sanity check with SI Electric Piano and it yielded a stereo clip as expected. Are you on the latest release of CbB? I would think this is just a clip-display issue if not for the distortion. What does the synth audio track meter show on playback? Try importing a recorded file from the project audio folder to an audio track. EDIT: I noticed the output from SI Piano is super hot and clips easily on chords at moderate velocity even at default MIDI volume 101. That might explain the distortion (clipping) unless it's only the recording and not the freeze. Lower the MIDI track volume or the Gain on the synth audio track.

MIDI meters are just showing the velocity of MIDI note events; there is no mono/stereo information in a MIDI event so the bar is always solid. That is pretty odd; I'll have to think about possible causes. What if you freeze the synth instead of recording? Recording is only really needed if you plan to tweak the synth patch from its UI in real time rather than using automation or controllers. Also, can you repro this with any bundled Cakewalk instrument?

The more intuitive way would be to go to the Now time at the end of beat 120, and tell Cakewalk that you want to be at the end of beat 142 at that same absolute time. Using measures avoids doing the beats/measure math (142 measures in the time of 120 is the same tempo as a 142 beats in the time of 120) and the +1 is needed because measures are counted from 1 not zero.

I was searching for one of the longer threads about continuous track scrolling and found this post that actually complained about track-by-track scrolling before continuous (a.k.a. fractional) scrolling was introduced in X3b... to each his own. http://forum.cakewalk.com/Smooth-Scrolling-of-Tracks-m1615686.aspx And here's the big one complaining about it. Post #13 by Seth Kellogg explains why it was implemented: http://forum.cakewalk.com/Im-Disapointed-in-X3-m2918795.aspx#291886 This may not be the definitive thread, but here's one discussion about the loss of 'rebuild layers'. More than one poster pointed out that the result of rebuild layers was a little unpredictable and the last post points out the the Re-use Existing Lanes recording option largely made rebuilding unnecessary. I prefer to have control over what ends up where, and generally have it set to Create New Lane. http://forum.cakewalk.com/X2-Take-lanes-rebuild-layers-m2686731.aspx

All of this - especially lanes vs. layers - was discussed ad nauseum on the old forum as the changes were introduced. Editing a lot of audio takes is not part of my workflow so I can't say definitively that layers weren't better in some respects, but as with so many software evolutions it's likely you just need to embrace the new ways of doing things and ask specific questions about how best to accomplish tasks that seem to have gotten more difficult/awkward.

As a piano/keyboard player, I have the same envious thought every time I see a musician sitting under a tree in the park playing a stringed box full of air.

Goto measure 121, Shift+M, enter measure 143, beat 1, Enter. No fuss, no muss, no fixing the meter, tweaking mistaken detection results or removing superfluous tempo changes due to the piece 'breathing' a little within the context of a fixed tempo.

I should add that this thread may seem a little confusing because the first post is not not asking the same question as the title. The answer to the title is: MIDI already follows project tempo changes by default. What is really being asked is how to 'Set Project From MIDI Clip' which is what I posted. Once you've done that, the MIDI will follow any tempo changes you make from there.

First of all, don't have any tempo changes in the project before you start recording, and don't have CW syncing to tempo from some external MIDI clock. A MIDI clip won't really have a tempo of its own unless you take it out of the project as a MIDI file or turn it into a groove clip. It has 'inherent' musical tempo based on the absolute time that goes by between quarter-note events at the current project tempo, but that doesn't have to match the project tempo. If you change the project tempo by any direct method other than Shift+M mentioned above, the MIDI will follow that change proportionally because MIDI event timestamps are based on where they fall in the timeline at the time they're recorded, not on absolute time.

If you know the target tempo: - Snap the Now Time to measure = Current Tempo +1 - Shift+M to open Set Measure/Beat At Now - Enter measure = Target Tempo + 1, beat =1 and OK. If you don't know the target tempo: - Slide everything to align the first downbeat at 1:01:000, or 2:01:000 if you need a pick-up measure. - Snap the Now time to that measure, and Shift+M to set the matching measure and beat. - Listen to playback without the metronome running, and count out 8 or 16 measures. - Snap the Now time to the downbeat that should be 9:01 or 17:01, and 'Set' that. - if the original was recorded to a click, and the tempo that CW sets is close to a whole number, you can undo the Set, and do the first procedure for setting a known tempo. - Or you can just keep using SM/BAN to set additional point to lock the timeline to the project as needed.

Shift+M is Set Measure/Beat At Now. It allows you to tell Cakewalk where measures/beats are in your MIDI, and automatically calculates and inserts tempo changes to align the timeline to the MIDI, adjusting start times and durations of MIDI events to preserve the absolute playback timing of the performance. I live by it.

I'm not 100% sure of your routing since the screenshot of the inspector for track 13 is not showing I/O assignments. But I suspect the above is part of the problem. With Input Echo enabled on both tracks and inputs set to respond to the same channel from the controller, both instruments will respond to any input. If you want only the focused track to be heard, you should disable the forced Input Echo on both, and enable 'Always Echo Current MIDI Track' in Preferences > MIDI Playback and Recording.

The way I posted is still valid. Process > Length > 50%. Or drag-stretch to 50%.

Not sure I completely understand the setup. Are you crossfading two different synths/patches using MIDI volume or two audio tracks with volume controlled by MIDI? In the case of synths, the result is going to depend on the response of each synth to MIDI volume, and there's no standard/convention on this in the MIDI spec. And in the case of both audio and synth tracks, the result is going to depend on how you set the MIDI endpoints of the group, the volume of each track at the high endpoint, and how much correlation there is between the signals. With the right tweaks to the grouping end points and max track volumes, you should be able to get pretty close in either case, but it's going to take some fiddling; there's no simple recipe you can apply that's going to work for all sound sources.