Trying to render a saved song in Cubase/Studio One 5. Both DAW's crash. Not had this happen before. I thought it might be that I always use 96kh 64bit in my DAW but having tried alternatives like 44kh the problem persists.

Is anyone else having issues with the plugin?

I really wanted to try my own style to an old Beatles Song by changing tempo and instruments. I saved the song in BB and opened the song in my DAW in cubase via the plugin, tried to render and CRASH everytime.

Any help would be greatly appreciated.

Greetings Mal from Spain!

You may want to post your question in either the +++ Band-in-a-Box for Windows +++ or +++ Band-in-a-Box for Macintosh +++ forum section so it will receive more views and responses.

It is helpful to provide the year and build number of your program. That information is available in the Help > About window.

This forum section is primarily used by PG Music Sales and Support to answer common questions they receive by phone, chat or e-mail.

In addition to Jim's advice above, try setting your DAW to 44.1k Hz sampling rate. Band-in-a-Box and its RealTracks uses 44.1K, so making sure that everything is using the same sampling rate could help.

Thank you.

Yes I am having the same problem with cubase pro 11, i can't seem to close a project or remove a track with band in a box plugin on/in without it crashing( Freezing ) Cubase, very frustrating.

[quote=Darren Ross]Yes I am having the same problem with cubase pro 11, i can't seem to close a project or remove a track with band in a box plugin on/in without it crashing( Freezing ) Cubase, very frustrating.
[/quote
I have the same problem (Cubase). I have had a long dialogue with support without getting a solution. It ended up that the support recommended me to reinstall Windows 10. Did this to test, but the exact same problem persists. I have the same problem in both my laptop and my desktop. I have no problem with any other VST, neither VST (2) nor VST3. Same problem after upgrading to 2022 and VST 4.0!

Hi,

Just purchased the 2022 BIAB Mega Pak to run as a Cubase 11 Pro plugin and it crashes Cubase the instant I try and do anything with it. It works in standalone mode running alongside an open Cubase 11 project but as a work flow it becomes cumbersome. The fact that others are reporting the same problem from C 10.5 upwards without a solution is worrying and disappointing. I wish to record at 24/48 in the future, so the suggestion that Cubase must be set to 44.1 isn't solving anything. My current project used to test BIAB is already at 44.1 and the plugin is as unstable as it gets. As I said earlier, dragging MIDI and audio from BIAB into an existing project works ok but is a long winded way of auditioning suitable BIAB performances alongside my own recordings. No other plugins are causing issues and Cubase 11 is very solid and stable.

My Windows version is up to date as is Cubase 11 and few apps are running in the background. The PC is only ever manually connected to the Internet and therefore virus protection software is by default disabled while off-line and only manually enabled when I actually connect.

What is the solution to this seemingly long running issue?

Hi, I've had this problem for as long as the DAW plugin has been around. And that probably for at least 2 years, if I remember correctly.

It's exactly as you described it. Biab in stand alone mode works great, I always used the newest version of Biab, but running the Biab plugin simultaneously with Cubase Pro 10 or 11 or 12 doesn't work at all. Cubase freezes. It doesn't matter which function you used before.
So task manager, exit Cubase, restart computer, work with Biab in standalone mode, exit Biab, restart Cubase, then import the rendered files from a folder into Cubase.
Simultaneously working with Cubase is well thought out, but it doesn't work at all. I now have about 80 different plugins from various manufacturers. It all works. Never had any problems with it. But at least it works "in a roundabout way" with Biab, so - what the heck ;-)
I am very happy that Biab exists at all. So I can personally live with the "disorders".

If you are having crashing issues you can try it in KV Element
load element as a vst3 plugin then drag and drop the BBPlugin into it or select from the list, hook the in/out up then click the EXT top left to sync it.
This fixed all the crash problems I was having in Reaper, so I think it is worth a try.


KV Element with BBPlugin:

Thank you for the feedback. I've just tested the latest version of the Windows plugin in both Cubase 11 and Studio One 5 and can confirm that the plugin is working as expected in both DAWs. If you are still having issues with plugin in either of these DAWs (or any others), please create a separate post in the Band-in-a-Box Windows VST Plugin forum with details (VST version, DAW version, etc.) and steps to reproduce the problem.