brundlefly

So far as I know, the mouse wheel is the only way to scroll the Inspector. In addition to using Full Screen mode as suggested, you can quickly toggle the Control Bar closed/open by the default shortcut 'C'. You might also consider removing less frequently used modules from the Inspector by the Display dropdown at the bottom. But ultimately, CbB/Sonar really need a little more vertical resolution; 1200 is sufficient.

Dragging out a selection of multiple clips will get you one file per clip, whether separated by time, tracks or lanes of a track.

And just FYI for posterity, Sonar has since added an Absolute Time offset (milliseconds) option to the Time+ setting in the Inspector which is easier to use than the articulation-based offset if you just need one fixed value for a whole track.

+1 And do it in a second lane of the track and then bounce to clips if you want to combine notes and controllers. FWIW, I'll add that I find my pedaling in actual performance has the pedal being released just after the barline (or any chord change), producing a little overlap on chord changes. Here's a pair of up/down pedal controllers quantized to the 1st and 3rd 32nd (120 and 360 ticks) after the bar and configured as a MIDI Groove Clip. Groove Clip - Sustain Down 120, Up 360.mid

If the project timeline isn't synced to the Karaoke track, the simplest solution may be to apply Drum Replacer to the Karaoke click and replace it with whatever drum sample you want to use. If the timeline is already in sync, you can simply change the Metronome to MIDI mode, and ouput it to Juno. You'll have a little latency due to the MIDI OUT and monitoring the Juno through CbB, but it should be tolerable if your ASIO latency is low.

I see where you're coming from but I think track-to-track routing with a patch point model makes more sense for consistency with the way audio distribution works, and because it means each synth would have a MIDI track (or MIDI half of an Instrument track) in between it and the source that can be used for synth-specific Velocity and Time Offsets, MIDI volume and pan contro/automationl, MFX inserts, additional MIDI events, etc. And regarding Input Echo, this gives you the option of interrupting MIDI to one of the synths without disconnecting it.

I have a first-generation MOTU MIDI Express XT that still works fine, but I replaced it with a MioXL because it was slow (MIDI RTL ~11ms). The MOTU had fairly basic routing capability and was not hard to master. The mioXL can host USB and LAN connections as well as MIDI DIN, configured by an app, and I had to write an extensive 'usage' doc for myself to translate the manual into terminology and that made sense to me and keep track of the configuration. The problem with hardware solutions is that the project then becomes dependent on the hardware being available and configured correctly and that can fall apart when you migrate to a new machine or add some other hardware to your system, but they are a necessary evil if you use old hardware synths and controllers with only DIN connectors.

Though you may not be using it, the Yamaha-Steinberg installer likely installed the Generic Low Latency driver. Check is there's a key for it under HKEY_LOCAL_MACHINE\SOFTWARE\ASIO in the registry and remove it if found.

All that's needed initially is a one-to-many patch point solution, like audio patch points, where you would output a MIDI track to the patch point and it would appear as an Input for other MIDI and Instrument tracks. Eventually MIDI 'Sends' could be implemented for additional flexibility but that's not essential. CodFN42's MIDIChFilter fits the bill but forces you to have a dummy synth track assigned to its output which partially defeats the purpose of having fewer tracks to deal with (though it can be hidden). It also adds another plugin to your synth rack that could otherwise be invisible if the feature were built-in. And I've recently discovered an issue with using MIDIChFilter in Project Templates that makes it not an ideal workaround. I've asked the Bakers to look into this as it could cause problems with other MIDI OUT-capable VSTs.

I understand why you might think that, but unless your entire display is failing to update smoothly, I would wager this is actually not a graphical issue but an issue with the driver reporting the sample position consistently to CbB. It's a little unusual to have the Now Cursor position move erratically without also having audible glitches, but not unheard of. The Steinberg "Generic Low Latency ASIO" driver is actually known to cause exactly this kind of issue. There should be a Yamaha-provided driver for your mixer that will work much better, and you will want to remove the Steinberg driver from you system, not just disable it in Preferences.

Exactly. The selected tracks in the OP's screenshot are Synth audio tracks, not Simple Instruments. In order to freeze separate Synth audio and MIDI tracks, you need to select the relevant MIDI track(s) as well. I just checked and CbB successfully group-froze three split Instrument tracks with no problem when I selected all six MIDI and Synth tracks.

What are you using for an audio interface? Using WASAPI with onboard audio is more prone to this kind of thing and more prone to vary from one system to another, especially if it's WASAPI Shared rather than Exclusive. In any case make sure your Playback and Record Timing Masters are set correctly under Preferences > Audio Driver Settings.

Looks like I was mistaken that you can get the full installer directly. It looks like you first get an installation manager and will have to run that on the online machine to get the actual application intaller which I would expect will be saved to your Downloads folder at some point, but I could be wrong. Been a while since I started from scratch.

Just download the latest full installer to a PC that's online, and transfer the executable via USB. https://www.bandlab.com/products/cakewalk

This suggests that you're looking at the UI for a second instance of EZ that's not receiving MIDI, and that you made the kit change in that instance. Check your synth rack and routing of MIDI/Instrument tracks, drum maps etc. And possibly you have hidden tracks that are obscuring what's going on. EDIT: Oops. I see I missed some posts and you've already checked the synth rack. I would still suspect this is some sort of routing issue as opposed to graphics (which would not explain the kit change failure). It would be helpful to get hands-on with the project to understand, but I don't have EZ Drummer.

Looks like you have made the Multidock full screen with the docked Navigator showing. Shift-D to restore the multidock to partial height and drag it to the desired height. P.S. I never noticed this before, but Views > Navigator in the main menu gets you a docked navigtor. If you want the "regular" Navigator strip at the top, open it from the View menu in the Track View (Alt+N default) or drag it open from just above the timeline.

I don't know about opt-out, but it should be easy remove the limit on how tall the FX section can be. Volume and Sends are unlimited.

PM me a link to a zipped copy of the project folder and I'll give it a whirl.

Here's one with some interesting info about where things are stored, but the OP ended up reinstalling everything to get icons back:

I don't have Analog Lab V, but have seen other analog-modeling Arturia synths make quiescent noise at a low level - not audible, but visible in meters and analyzers as your screenshot shows.

I'm going to suggest running the VC Redist repair tool linked in the post below. If the problem persists, it may be due some plugin-related race condition that has a different outcome on the two machines.

Cool. Glad to help.

Izotope/NI stuff is mostly scalable which will help with the overall size of controls and displays but may still leave text too small. I always try scaling the plugin first if possible and only disable DPI Awareness if that's not sufficient.

True, but giving step-by-step instructions for anything always comes off as more complicated than it is. ;^) I always advocate finding a used/open box deal for those on a budget. That's a good example. I think an M5 is in my future when ye olde MOTU 424 PCIe system becomes unusable due to hardware or O/S evolution.

I was just going to add that the UID of plugin should not have changed with the update to v2.5. My guess is that your old projects were using the VST2 and you only installed the VST3 version of the plugin when you updated. If that's the case, Installing the VST2 will save you time having to correct the drum maps in multiple projects.