Billy86

Sending up a flare to the MIDI gurus... Playing a song with an audio track and with Midi triggering a Kontakt piano. When I stop the transport, the last notes ring on and on, slowly fading, but never completely stopping. I have to hit the reset MIDI and Audio button in the control bar to stop it. Doesn't happen every time, but it's the rule more the exception. I've tried checking/unchecking a few boxes in the Preferences/Project Midi... [including "Zero Controllers When Play Stops" and "MIDI Event Chase on Play" ] but nothing seems to help. Any ideas? Thank you!

Here is another site with a ton of free Midi files. https://www.midiworld.com

Make sure the new file path is in the paths the VST scanner scans to load it in.

Glad it worked out. Will run through this later as well. Maybe mark your posting as Solved? Might help someone else who hits this issue?

I emailed Waves Support as well, and was pleasantly surprised by the quick response of a couple of hours. Here's the reply. <<Let's first try refreshing the Windows redistributables. Redistributables are components of code which among other things, are also responsible for many functions of Waves plugins. Please follow these next steps: Quit all applications. Make sure all the latest windows updates are installed. Go to C:\Program Files\Waves Central\resources\res\external\Redistributables. Now, go through each folder and run all the Application files, one by one ( Let me know if you're getting any errors). Select the 'Repair' option to repair all of them. If prompted to restart, you can skip that until you finish all the files. See if you can load the plugins.>> I haven't had time to try this, so can't say if it fixes it or not.

Just hit the same issue. I installed and activated some V12 plugins on a second computer (got a second license with some recent updates of owned plugs). Latest install of CbB. During the scan for the new plugs, I got: The following plug-in caused an error during load: WaveShetll1-VST3 12.7_x64 and WaveShetll1-VST 12.7_x64. Pop up suggested I disable them so the system doesn't become unstable. Did that. Also got a separate toast error notification during the attempted install... Error: [WaveShell7-VST 10.0_x64] Main Call. Looking for some help as well. Thanks!

Was back at my computer, and I couldn't replicate this behavior. Everything seems to be fine now. Not sure why, but if it acts up again like this, I'll capture it on screen to show what it's doing.

Will check this out when back at my computer. Thanks.

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!