David Baay

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.

Hold Ctrl+Shift while changing one port assignment, and they'll all change.

Dis-Arm the track. When armed for recording, the meter shows the Input level.

Like other clip-level FX and edits, Region FX can also be rendered by Bounce to Clip(s). Not sure why the OP is reporting it doesn't work.

Just to be clear, since the microphone has an analog connection to the Neo 'interface', it is not going to show up directly as an input device in CbB. What you should see is the driver for the port on the Neo to which the Mic is connected. It looks to me like the Neo is strictly a class-compliant Windows device so you should see its inputs and outputs in WASAPI mode. Ideally you should connect headphones or motniros to the Neo's analog outputs. If you want to use the USB speakers, you;ll want to set that as the Playback Timing Master while the Neo is the Record Timing Master, but using two different devices for input ant ouput is not ideal. Here's how you would normally go about using a class-compliant device like the Neo: - In Preferences > Audio > Playback and Recording, set the Driver Mode to WASAPI - In Audio > Devices, Check all input/output ports associated with that device. - In Audio > Driver Settings, ensure that the Playback and Record Timing Masters are set to Output/Input ports associated with that device. - Connect headphones (preferable when recording from a mic) or powered monitors or an amp with passive speaker/monitors to the L/R Outputs of the interface. - Add an audio track to a project, assign the relevant Input via the "I" control (a.k.a "widget") in the track. The Ouput should already have defaulted to the Master bus (or direct the interface outputs if you started from a completely empty template with no buses). - If using headphones, enable the Input Echo button (icon looks like headphones) on the track. Do not enable this if using monitors or you will get feedback between the mic and monitors. - Click the record (arming) button on the track to arm it for recording. - Make some noise into the mic and verify you see the track meter responding; if it's peaking in the red (above -6dB), turn down the input level on the interface. - Hit R on the PC keyboard to start recording, and make some more noise into the mic. - Hit Spacebar to stop recording. - Hit W to reWind, and hit Spacebar again to play back the recording.