brundlefly

I had originally mentioned smart mute in connection with my comment about 'behind the scenes' linkage, but deleted it because I didn't think it was likely you had it enabled since it's disabled by default, and you indicated it was possible to unmute the Synth track and independently mute the MIDI track.

Tempos persist until a different one is encountered. Go to Views > Tempo, and you will find other tempo entries that need to be deleted. Superfluous tempo entries often result from copy-pasting clips with tempo changes included in paste options.

Same as the physical world - If you have cables coming from the outputs of several different sound sources, you 'select' the one you want, and plug it into the input on the mixer.

I can repro that behavior (using Lounge Lizard Full) with the exception that in my environment, the synth track mute does not follow the MIDI track mute in a split instrument. A few relvant behaviors I noted: - When input echo is enabled on the "unrelated" audio track, the MIDI activity indicator in the Lounge Lizard flashes, but only the first time. - If the Lounge Lizard MIDI track mute is cycled off and on, enabling input echo on the audio track no longer has an effect (the Lounge Lizard activity indicator does not flash, and live MIDI input remains muted). - Cycling the audio engine always causes the Loung eLizard activity indicator to flash, and restores input echo through the muted MIDI track. There has always been some 'behind the scenes' linkage of MIDI and Synth tracks that's possible because of the internal control of both MIDI transmisison and synth audio ouput that does not affect hardware synths. An example of this is that muting the MIDI track while holding a note will stop the sound from Lounge Lizard though no MIDI activity is registered i.e. the output of the synth is being stopped by some means other than sending a Note Off or All Notes Off or other MIDI message. Bottom line: Your scenario demonstrates an inconsistency that should be resolved one way or the other: Either a MIDI track mute should always stop live input echo to both soft and hardware MIDI ports or it should never affect either of them. Personally, I agree that the it would be more intuitive if live input were muted along with existing MIDI in all cases.

For the record, I ran SONAR from a secondary drive for nearly a decade on my previous machine. Not a problem.

Check Event Viewer for error details, and maybe run a memory test: https://www.memtest86.com/download.htm

I use Mercury, and can't replicate that behavior. For me the fade line remains white against a dark, unselected clip and black against a light, selected clip at all zoom levels. I'm guessing that what you're seeing is a characteristic of your particular combination of video monitor and display resolution/scaling.

I suspect that something wasn't set right when you first tried live input with the separate MIDI track muted. For me it's very consistent that the muted MIDI track continues to echo live input, and sound is heard whether driving an unmuted soft synth or an input echoed audio track hosting a hardware synth.

I havne't used this gesture enough to know if it was any different before 19.07, but here's what I'm seeing in 19.11, and it mostly agrees with the documentation. - With the Smart tool in lanes, I can get the crop tool but the hotspot is extremely small and hard to hit - just in from the clip border in a narrow band in the upper half. - The Ref. Guide shows the whole zone along the boundary between the clips is devoted to moving the split point except at the top where you get the fade tool and in the bottom half where you get the Comp tool (if enabled). - It's not documented AFAIK, but I found that disabling the Comp tool function of the Smart tool gives you the crop tool near the boundary in the lower half of the clip (same as what you get in the parent track with lanes collapsed). - Switching to the Edit tool gives a much bigger hit zone for cropping and works fine. https://www.cakewalk.com/Documentation?product=Cakewalk&language=4&help=Tools.04.html

For amp sims, you might want to check out Nembrini Audio's 70% off sale: https://www.nembriniaudio.com/ I'll let someone else recommend a decent cheap/free guitar synth.

I think I must have overlooked or misread this the first time. You're talking about existing MIDI on the muted track, right? If so, that sounds distinctly weird, and I'm pretty confident I won't be able to reproduce it. Can you detail a little more what synths and MIDI/Audio I/O routing are involved? If anything, I'm thinking it might have to do with recent changes to MIDI 'Prepare Using' buffer. Are you running the new default 20ms buffer size now?

Yes, everything you describe has pretty much always worked that way. The only thing I was't sure about was the MIDI meter not registering live-echoed input. That certainly isn't expected, but I verified it goes back at least to X2, the oldest version I still have installed. Don't think I've ever noticed this - probably because I don't pay much attention to MIDI meters in general except when troubleshooting. I could go either way on whether muting should affect live MIDI input. It might be the more intuitive behavior, but it's been the way it is now for so long that I'm sure there are some long-time users that have subconsciously come to depend on it working that way. But regardless of the source, if a track is outputting anything, the meter should show it.

Whether using a multi-timbral synth or multiple single-instrument synths, to layer two soft synth sounds you just need to enable Input Echo on the two MIDI or Simple Instrument tracks outputting to the two synths or channels of a multi-timbral synth. By default, Cakewalk auto-echos the focused track, but you can force echo to stay on when a track is not in focus simply by clicking the input echo button - looks like ))).

I think you understand now, but just to explain it another way: Note that the feature is called snap-to-grid, not snap-to-cell. Grid lines define the center of the interval to which you're snapping, and the snap zone for that line extends half the resolution to either side of it. As soon as you get more than half way to the next grid line (assuming lines at the same resolution as snap) , the start of the note will snap to that nearest grid line, whether it's earlier or later. Aim for the line, not the space.

No sure what you mean by 'cells'; that term applies to the Matrix and Step Sequencer views, but not the PRV. Depending on settings, you can have gridlines displayed at a higher resolution that you're current snap setting. A full-size screenshot showing the whole UI linked from a photo-sharing site would help. Edit: One thing I would recommend to help make sense of the nap behavior is to enable PRV-specific snap at the desired interval, and enable Grid Resolution > Follow snap settings from the View dropdown in the PRV menu bar. As it stands, I suspect you have the grid set to 8ths, and snap set to a 1/4 or higher.

Did you uninstall Platinum? If not, does it still behave as expected? Here's a quick description of the behavior that I consider typical and longstanding at tempos around 120bpm: At low zoom levels (i.e. approx. 16 or more measures showing across the clips pane), the Now cursor travels pretty smoothly, but looking closely, I can see the cursor line wobbling back and forth against the marker above it by a pixel or two. With about 8 or fewer measures showing, it becomes noticeably jittery. And at still higher zoom levels like 2 measures or less it starts to show a distinct 'ghost' that trails the leading cursor by progressively more distance the higher I zoom - maybe a half inch with half a measure showing. Are you seeing something worse than that?

This will also happen when Punch recording with Mute Previous Takes enabled. In either case, swipe through the upper half of the clip with the Mute tool as Mark mentioned to unmute them.

Altering audio hardware should not have any effect on MIDI or audio routing of simple instrument tracks. Split the instrument track and make sure the MIDI track ouput and audio track input assignments are still correct. Also make sure all MIDI track inputs are assigned the specific port and channel your controller is sending on, and not All Inputs-Omni. This will ensure that tracks don't unintentionally echo MIDI being generated by - or passed thru - other soft synths.

Hard to say exactly since your screenshot is showing the timeline or the snap setting. In general, Cakewalk does work like every other DAW on the planet in this respect.

Wow. I don't recall anything quite like that ever being reported previously. Is it repeatable or just happens at random/intermittently? Really sounds like some kind of memory corruption happening. What O/S? If you have a project that demos this with a repeatble recipe, I'd be interested in giving it a whirl on my system.

How old is your interface? Sounds a bit like symptoms of failing capacitors in the output section.

To see the 'Inline PRV' in tracks, set the Edit Filter that defaults to 'Clips' in the track header to 'Notes'. You can then adjust what is whon by the MIDI dropdown in the track view menu bar. Cakewalk can do partial quantizing of real-time recordings by percentage or groove quantizing to a selected or copied reference clip. There are also options to randomize hard-quantized notes using MIDI FX, but there is no really intelligent 'humanizing' funciton built-in. It's not clear what's happening that's requiring you to restart Cakewalk or your PC. What are the symptoms, what audio interface and driver mode (ASIO, WDM, WASAPI) are you using?

As I said, I assume that by 'current channel' you mean the output channel assigned to the track. If you have a separate ouput channel assigned to each track and only put parts for one instrument on each track, that output channel assignment will take care of re-channelizing everything as a needed. If you're not using forced output channels, you should. In the case of non-multi-timbral instruments, channel doesn't matter at all; the dedicated virtual MIDI port presented by that instrument ensures that no other synths see that data, and most single-instrument soft synths will respond to MIDI on any channel.

Someone else mentioned this in another thread, but I checked the current release against the last release of SONAR Platinum, and also X2, and did not see any difference on two different machines (one ASIO, and one WASAPI). As I mentioned in that thread, the Now cursor has always been a bit jittery at higher tempos and zoom levels for me. It could certainly prettier at higher zooem levels. That said, I suppose it's possible they're all using some shared code, and all are more jittery than before, but I haven't noticed a change. At what tempo and zoom level (measures in view) are you noticing it's worse.

I think Mark will confirm that Cakewalk has no mechanism to force a buffer size change. Though it might not be the whole story behind the issues you've encountered, any change in the buffer size wasn't directly due to the update.