Billy86

Thanks for the response. I have a Gen 1 Presonus FaderPort attached. I’ll see what I can do when back at my computer.

I must've set something somewhere to make whatever is happening happen. Here's what's happening... No matter what volume I have a track set to (either manually or with volume automation in read mode), when I bring that track into focus (let's call it track A), the volume fader of track A snaps to -4.2 db and won't move off that mark, even if the track's volume automation in read mode says otherwise. If I put track B in focus, track B's volume fader snaps to -4.2 and won't budge; meanwhile, track A returns to its proper volume level and obeys volume automation. This happens with volume automation on or off. In fact, the in-focus track completely ignores volumes I have in the Volume automation lane, with the project set to Read automation, and locks at -4.2 dB. Even if I open a brand new project, with just empty audio tracks, they're ALL set to -4.2 db and won't budge, whether automation is on or off. If I insert a new audio track in a completely new project, its volume fader is also set to -4.2. Don't know if this has anything to do with it, but right before this behavior started, I had used the loopback function in my Scarlett 4i4 to record into CbB from another stand-alone software product, Izotope RX8. I can see in Focusrite control that everything looks normal. I've tried to shut down/relaunch CbB, and completely reboot my computer, but it had no effect. Should I uninstall/reinstall CbB. Something get corrupted? Any ideas what might be causing this?

😄

👍

If you don’t mute a frozen track, does it still produce audio? I thought it did, that’s why I freeze/mute if I record to aux track and it produces the audio.

One major difference is that you could record what you’re blending on an aux track, but not a bus. You could then mute/freeze/hide the individual tracks to reduce CPU load and capture some screen real estate and you still have the original source tracks If you need them later to make changes. You can also position an aux track amid the tracks you’re sending to it in the console view, in effect having the convenience of a group bus amid the tracks it controls. Drums, guitars, vocals, etc. Think VCAs. Personally, I find this a lot more convenient than having to hassle with the bus view section, which can consume a bunch of screen space if you have a good number of busses, or you have to keep opening and closing.

Not a developer here, so thanks for the nuance on the language... So... OUR "ie: the users" expected behavior is as you describe and what I would like, which is not the reality of the way it works... but the way it currently works disappearing behind the GUI on the second monitor is IS the developers "expected behavior" and would need altering to meet user expectations? This falls under the "requested feature" umbrella? Not a problem starting (or following up on that effort, if it's already been requested). It really is a PITA.

@Starship Krupa @User 905133 This is it! The discussion/sleuthing you did a year ago boiled down to the EXACT issue I’m having: pinned plugins are not being closed, they are being hidden behind the CbB GUI on the second monitor on any mouse-click on that monitor screen. @Noel Borthwick @msmcleod was this determined to be a bug? Thank you!

Thank you very much. Will give it a read. Hopefully, there’s a solution to be had.

Argh. This is driving me crazy. On the left monitor where the Console View is, any click on anything (say, for example, a solo button) will send any open plug-in GUI behind the Console GUI. This behavior doesn’t happen on the right side monitor. Anyone dealing with this?

Ah, yes. That did it! Thanks!

Since the latest update, I don't seem to be able to right-click a plugin in the browser and add it to a category-type folder. For ex., transient shaping plugs. Anyone else seeing this? I know I can choose manage layouts from the Plugins drop-down in the browser, but that's a much more time-consuming process.

I don't know if there's a fix for this or not, but... I'm using two monitors. Console view on the left, track view on the right. Nothing special. I like to have multiple Plugins open at once. In Preferences/File/VST Settings, I've unclicked the "Recycle Plugin Windows," so the check box is empty. I am able to have multiple plugins open. All good. BUT... I drag a plugin or two from the right monitor to the left monitor to spread things out. When I do, and then launch another plugin from the left monitor/Console View, any plugins that are already open on that monitor disappear behind the Console View GUI, and I have to minimize the Console View, drag the plugins to the right monitor, maximize the Console View on the left monitor, drag them back, and carry on. Is there any kind of "Plugin GUI always on top" setting I'm missing? Thanks!

Hmm. Interesting. Hadn't thought of that. In my current project, I get a message that 5 tracks are routed to silent buses. Four are active (not hidden) and working fine, and one is hidden and archived.

Thanks for this tip. I consistently get “Silent Buses Detected” at startup even though, in every instance, they’re all routed and outputting.

Just found this gold mine of information and want to add my kudos and thanks. This doc is incredible! Wow.

Great, yep!

Hi, EZ Tutor. Please consider editing your header to mark this as Solved. Others may be trying to figure this out as well! I know I always read Solved issues. I might not be dealing with a particular issue today, but I just might tomorrow. Cheers.

This is cool. Say you have three views in a floating multi dock (console, PRV, and a virtual instrument GUI), is there a way to set a key binding that would cycle through whatever you have in the multi dock, alternating each into focus as you “toggle “ through?

I'd say I'm an intermediate MIDI user. Have and am using MIDI-controlled VSTi's. I understand the signal I/O signal routing from Controller to MIDI channel to VST channel. Can't figure this out: Just bought LX25+. Registered, downloaded and installed the software for CbB (adds some deeper integration/control beyond generic MIDI Controller). Plugged in and turned on. No driver is required for LX 25+, as it's class compliant. Cakewalk recognized LX25+. Added MIDI input/output for LX25+ in Preferences/MIDI/Devices. Added LX25+ as a Control Surface in Preferences/MIDI/Control Surfaces. In Port and Out Port set. Added MIDI track and set input to LX25+ OMNI... Input Echo is on. Midi track is in focus. Always Echo current MIDI track checked in Preferences/MIDI/Playback and Recording. No MIDI signal from the controller registering in the meter. No sound from VSTi. (Addictive Keys). Tried as both a Simple Instrument Track and as a separate Midi channel paired with the AddKeys' channel. No joy. Also, interestingly(?), the WAI color (red) assigned to LX25+ is not showing up in the MIDI track I've set the input to LX25 on; the color (aqua) reflects another control surface I have connected, Presonus Faderport. Closed Cakewalk. Opened MIDI-OX to test. LX25+ is recognized and working. Keys/pads, encoders all sending signal. What am I doing wrong ? Thanks. EDIT: Operator error. When I added it as a Control Surface I selected the actual name of the controller (Nektar LX25+) that showed up in the dropdown menu Controller/Surface instead of choosing "ACT/MIDI Controller." Back in business.

😁👍

Thanks yes. Asked you a question there as Billy S and you answered. I have the Gen 1 of the single channel FP and cant think of a reason to upgrade to the Gen 2 version if it’s not anymore integrated with CbB.

😂

Hey, whatever works! 😀

I’m not a very technical person, so I’m curious what this means for performance. I use ParkControl and have often wondered about lasso. Also, would this create additional heat that needs additional cooling? It sounds like lasso is sort of ParkControl on steroids and kicks the CPU in the butt performance-wise and keeps it at higher rate?