I upgraded to BIAB 2019 Win UltraPak (rather expensive all-in-all), primarily for the features advertised in the VST DAW plugin. It does not work as is should, and really, dev should hold until this is actually ready and works as advertised. Further - as others have noted on this forum - the installation and operation on various DAW platforms should be fully documented beyond the rather dreadful, single video from a Presonus Studio fan ...

In my case here: a professional studio doing film and audio work, using various sample rates per project, and using various DAWs, RME UFX+ audio interface, RME ADI-8, ASIO, Thunderbolt, UAD PCIe, many VSTis and VSTs etc. Issues to date include:

ProTools Ultimate 2018.10: Cannot find the BiBA AAX plugin at all; does not recognise it (of course, is installed correctly, in the right location).

Nundeno 8.3: Exactly as per Pro Tools, cannot find the plug or show in plug list to instantiate on a VSTi track.

Cubase 9.5 or 10: This ne finally sees the BAIB plugin and loads, but the plug will not play sound or do anything of use; tracks have been generated

Ableton Live: cannot find plug.

I also suspect there may be issues with sample rates, eg: it would appear that BIAB standalone cannot run in any other sample rate than 44.1khz [?] In any case, many of my sessions run at other sample rates & in particular, at 48khz for film work. Surely in 2018, BIAB might be able to adjust its clock correctly [?]

Hopeless. Am expecting a working update and proper documentation, hopefully before BIAB 2020? In the future, will be far more careful before wasting money on PG Music products.

Hi,

This information from another user might be useful. He found that the lack of sound does seem to relate to a mismatch in audio settings between software and Windows. (I've passed this information on to the developers.)

https://www.pgmusic.com/forums/ubbthreads.php?ubb=showflat&Number=507674#Pos507737

I also find myself wondering if maybe using the WAS driver in BIAB could be part of the problem. I'm only guessing here. I always use MME as my audio driver and not the WAS that BIAB defaults to.

Regards,
Noel

It is high on our priority list to address this issue of the plugin apparently not showing up on some systems. Presumably you have copied / installed the dll to the folder that the program expects, and have scanned for plugins etc. Some programs have a blacklist of plugins, and perhaps it has been added to that list.

I will mention, on many systems including the ones we tested, it does just show up and work.

Yes - we are planning to have dedicated documentation/videos for each program.

I get a little red square, what would be the close button on a Windows app, and nothing else when loading the BIAB VST into Ableton 10.1.5.

I agree wholeheartedly. I have Reason 10.2 and Reaper (latest version) and neither can load the VST. Somebody screwed up and yet there seems to be no sense of urgency in fixing this mess. I might create one by asking for a refund.

I find that a little hard to believe that it works on some systems. It does not work on Reason 10.2. The message Reason gives is "could not load". Reaper can't even find it. Cubase can't either. What do you think the chances are of three programs not being able to load the plugin. You need to start with the assumption that there is something wrong instead of assuming that the VST plugin is OK.

I will give my upgrade one more week and then I will ask for a refund.

My BIAB vst plugin loads fine in REAPER. You just have to make sure it is placed in the correct place that REAPER looks for vsts. Any new vst should immediately be scanned by REAPER and then become available to load.

I have no issues with the vst loading in ableton. However, it does take forever to render parts compared to BIAB or realband. The multi riff is even worse. Takes 7 to 10 minutes to generate 8 bar multi riff. I have moved back to real band for this function and then just drag into ableton for arrangement.

I agree with the OP. Not only the VST, the main program is, obviously, not ready for release, it's still work in progress, not a polished and finished product. I will wait a couple of weeks, and after that, I will consider asking for a refund.

guichard,

Are you running Reaper 64-bit?

Regards,
Noel

Spending an hour or so trying to get this to even be seen by Pro Tools is a Pita. Pain in ...
I reset preferences, removed aaxplugins file, so that PT2018 could re-scan the plug-ins. Still no sign of Band in a box plugin.
It is in the correct location, and visible through File Explorer. (Win 10)

I can see, and use the VST in Studio One 4, and also in Sonar. But, most of my work is done using Pro Tools.
Has 'anybody' been able to have Pro Tools see this dang thing? (I am using PT 2018.7)
Thanks,
Bob

First of all I have to admit, that I´m very happy seeing PG working on a long, long ago asked feature "The VST plug-in". And knowing the agility in PG I´m pretty sure this long cherished wish will come true sooner or later!
Secondly I have to state that it shows up and "works" (at least with the minimalistic features PG thinks to be enough to release it)in Cubase 10 here.

By far not good enough to satisfy the high expectation on such a plug-in, but a first step into the right direction.

Here are some features I´d like to see:

1. Synchronization with the DAW´s transport and tempo (tempo changes) (btw: Toontrack is able to do this)
2. Allow multiple instances to be loaded in a DAW
3. Audio output through the Channel where the plug-in is inserted (incl. use of FX plug-ins in that specific channel (e.g.Amplitube))
4. Multiple instances of BiaB plug-in allowed in DAW
5. All features (hold, shot, push....) chord input,...
6. Fast regeneration


looking forward to see this wonderful plug-in improved!

KR
SC

These are not features - these are what is expected as a minimum.

THANK YOU! I get so dang tired of hearing bug fixes and bare minimum functionality described as exciting new features around here!!!

Completely agree... I am so disappointed!

An update is in the works (very soon-to-be-released according to the chat line), but these are major hurdles they have to overcome.

There is no way this was properly beta'd. Another example of the Marketing out-running the Engineering dept.

unfortunately have to agree with OP, after buying the software I was extremely impressed with fast shipping of the external HD, however installing from HD was a nightmare kept getting the error that not able to copy from source drive, when I relay this to the developers I did not get a proper response, decided to download everything from website (I actually paid for the drive so I wouldn't have to)bought the ultrapak, the latest VST which is supposedly VST 3 is actually not working properly I am using Studio one 4 Pro, for some reason in the latest update I am not able to load individual real-tracks, nothing showing up in plugin? I am not very happy with the product or customer service so far, my excitement has rather faded...VST was one of the major reason I bought the software.

Navid Syed, welcome to the forum and to BIAB.

As you have read, there are issues with the VST Plugin. This is a new feature this year and improvements have already been made, and are still being worked on. It is also fairly soon after the new release and that may explain why you haven't received a response. How did you contact them? If you call or live chat (when they are open), you should get right through.

You could also post your questions here. We are only fellow users but we may be able to answer them, or relay to the developers if there's something we think they aren't aware of.

Most of those here would, I think, agree that PG Music is among the best companies for customer service. I hope you will continue to give them a chance to help you. And give us a try, too.

IMO the fault lies more or less with PG's marketing advertisements ... if an inexperienced PG newbie is not familiar with the way the PG system works, they must have believed they bought a full blooded BIAB VST work horse with version 2019 .... alas, not yet.

PG could reconsider their advertising, sounding more like: hey buyers, stop moaning; you get 40% off in december; see it as a beta tester discount. Thereby allowing us to get your opinions and bug finds to improve coming updates during the coming 6 months.

I must say the essential fixes up to 607 came rather fast. Before Xmas even. I've been working with the 64bit version a while now, and cannot find problems regarding my ways of using of BIAB other than that the VST still sucks, and the stylepicker has some built in search faults. 607 seems very stable, no serious crashes, just found only one i can deliberately force happening. And the amount of RTs, you can spend weeks checking them out. Some amazing stuff in there, and i still find good things among the older RTs .... It's been a while since i really needed to hire a musician for some demo recordings ... An i just downloaded 608 -F

This is an old thread. The main problems that the OP brought up (plugin not showing up on some systems) have since been resolved. Problems with installing Band-in-a-Box from the hard drive and other problems would be much better in their own threads...