PG Music Home Forums PG Music Product Forums Band-in-a-Box VST and Pro Tools/AAX DAW Plugin (Windows) If You Get Stuck with BBvst Not Working in your DAW

Everything is all go in the fixing and features being added to BBvst, you just need to hang in there as the end result will be well worth it ! A few things are being done at a time to keep it stable.

If you are stuck while creating your song in the DAW with something not working try this:

1. Save the SGU in BBvst
2. Open RealBand and Ctrl+T
3. Size it to just show the tracks window
4. Open > saved BBvst SGU
5. Generate > All BB Tracks

You can now drag the track number directly into the DAW track/s.
In Realband > Options > Preferences > Audio > Audio File Type (set to your DAW sample rate).
In Realband > Options > Preferences > General > Click and Drag Midi Tracks to other programs as Midi files..

Are you testing the plugin with Windows 10 (latest version) and FL Studio (latest version)?

This is what I'm using and:

1. If you copy very many measures FLS crashes. Do nothing else just copy a bunch of lines in the timeline.

2. Undo doesn't work.

I hope this can be fixed. But use the latest version of Windows 10 and FL Studio. Thanks.

If you're gonna do this why even bother with the VST?

I agree JohnJohnJohn. I use the real BIAB then just transfer to RB. Duh.
It is my opinion that the plugin isn't as broken as the forums are making it out to be. I think we have a lot of folks, just guessing here, That have never owned BIAB but because of the plugin have purchased it just for the plugin and don't really know how to use BIAB in the first place.I put up a survey. I hope people respond because it'll give us BETA Testers and PGM some insight.

I respectfully disagree. I am an experienced BiaB, DAW, VST and VSTi user. The BiaB has so many bugs that I can not get it to work in Studio One Pro 4 on my system. Studio One never crashed before BiaB VSTi and now it crashes each and every time I try it. I have to reboot to set my system back in working order. Plus it is random crashes so I can not pinpoint a cause. Hopefully Monday's update will correct these problems. But I am not going to hold my breath.

The BiaB VSTi may work for those using RTs but it is useless for those of us working in MIDI. YMMV

I’m not new either and have spent considerable time testing the plugin with three different DAW programs it is buggy.

I'm not new to BiaB either. How experienced do you have to be to do a simple 'copy and paste' and an 'undo?'

Couldn't you use the midi styles, Midi Super Tracks or RealDrumCharts from the VSTi ?

No disrespect but you are wrong. The VST is buggy and initially was broken. Ie. not working at all.

John (Silvertones) you and I have been on here together for a long time, and I both like you, and respect you and your knowledge and experience. I also appreciate where your coming from. You helped Beta test this release. I have to say my friend it is a little bit condescending to suggest that most of the people complaining are new users. It is also not fair to fire a shot across everyone bow then get mad and say you won't comment anymore (from the other thread) when other fire back or disagree with you. Like it or not your a valuable part of this conversation, we need and want your input. Please share what and how you feel, and don't take offense when others speak up. There is a level of frustration to this sort of thing, especially when we read the new release hype and pull out the old credit card.

To my observation most of the ones complaining are regular long time users or ones that are new but are not new to DAW work. one telling point is that we are all having the same problems. If this is user error why hasn't someone come forward to point out the error?

As far as specifics, I have tried Midi styles on my system they lock up and freeze. I have tried longer files, premade files, brand new files, shorter files. RT files, part RT and part midi files, 1 chorus, 2 chorus, and 3 chorus files. 2 instrument, 3 instrument, 4 instrument, and yes 5 Instrument files. I have tried 4, 6, and 8 bar Multiriffs. I have worked with the original download version 606 for me, versions 607, 608, 609, and 610. I have generated new files and regenerated old files.

A typical test for me is to open the DAW, insert a instrument track, or drag the instrument to the tracks view, pick a style, generate that style. Then drag the tracks to the DAW. Next pick (select) a multiriff, hit generate "all riffs", drag those to the DAW. Then pick an open channel/track in the plugin, select an RT, click generate for that channel/track,then drag that track to the DAW.

in the end results I have had the system work perfectly 2 times. Once in Studio one version 2.65, and once in Reaper . I have had it fail at the last track render, fail at the multiriff render and fail at the style render in each and every build. Is there some user error, I'm sure there is. One good example it the audio or missing audio issue in Studio one for auditioning styles and RT. That was due to a setting in the audio setup of the DAW. I did specifically asked for some help from Tech support, and did not get a call back. I assumed they were busy helping others. So I continued to test and experiment on my own. I hope this post supplies sufficient information regarding what I personally have tried.

Bottom line if I fiddle and tweak with it long enough I might get full results, but one should not have to do that with PUFRCHASED software. Still I am willing to put the effort in for two reasons.

1. I like the program and recognize what it can become for us all

2. I like PG music, the staff and owner as I feel they are a solid company that ultimately cares


Anyway thanks for listening, and John still love ya man, but you can't have my bud light.

Yes I can. But all of my other VSTis allow me to assign a sound source in one of my DAW tracks and the VSTi will use that as its sound source. You can not, as yet, to that with the BiaB VSTi. There is also no way to move all of the MIDI tracks simultaneously to a DAW. Also if you use MIDI in the BiaB VSTi it will automatically generate a wav which for my purposes is just a waste of time and space. Thus my statement that "it is useless for those of us working in MIDI". One might as well as use BiaB like we have in the past.

Ok I'm with ya, I just tried it and yes it's useless rendering the midi to wav, but that should all change now and won't do that.
And yes in Biab VSTi you need to be able to send the selected track generated midi to a virtual instrument while it plays back in sync. All the midi tracks would be on a different channel but maybe right clicking the midi track in the Biab VSTi you could rechannel it ?
Same as in the Biab VSTfx you need to be able to send the selected track generated audio like "Direct Input" MultiRiffs to say Amplitube/Guitar Rig while it plays back in sync with the other tracks in the DAW, this way you get to see what riff fits best playing back with the effects added live.

We are currently working on developing these features so that synced playback with the DAW and sending midi to virtual instruments will work as expected. An undo feature is not currently implemented but has also been added to our backlog. Right now we are looking into features that may be broken or causing crashes such as the copy feature in FL Studio but I assure you that these things will all be added/fixed. We appreciate your patience and feedback!

Thanks Adar, we appreciate what you do, hope you get through that backlog !

Thank you Adar! We appreciate your hard work and keeping us in the loop!!

Very well stated, especially as you say when you have to pull out the old credit card to pay for something that doesn't work as its supposed to do.

I honestly don't know why some people keep shouting that it could very well be users fault when its as plain as day that it's simply buggy software, that should never have been released in the state that its in.

Please ask yourself why some users shout to the roof rafters its mainly users fault.

I have my own reasoning about that one, some people don't have to reach for the old credit card!

Aey

It wasn't user error in my case.

I really haven't done anything with MIDI in the past. I just wanted to us my BIAB files to working on my timing.

What I had, but it is now fixed, was a lot of static and distortion when playing my files. I had not even attempted MIDI because it wasn't what I was using in the past. User error - no. Buggy software - yes.

Again it is all fixed for what I need and I am happy.

...Deb

Let me be clear I’m not coming down on John, he’s a great dude that I like around here, but we need to point out the issues clearly so they get handled promptly. There may be some user error, but if so let’s have some input into what that might be. We get videos regarding all the wonderful things it can do in a particular DAW. I would rather have instructions on how to set it up and troubleshoot problems. I have been using BiaB for over a decade now. I love it and tell everyone about it. I want PG music to flourish. I was a regular user of RB as my main DAW. It is awesome when you really dig in, but it can be slightly shaky as well. The plugin to me has the potential to turn more feature rich DAWs into powerful upgraded RBs.

The way I know that this not largely user error is that PG is saying that certain issues are being worked on and patches and enhancements are coming. That wouldn’t happen if they thought it was all user error cause how do you fix something that’s not broken.

I think you nailed it. What they don't understand is the blind support and denial of problems only makes things worse as it pisses people off who are dealing with the problems (and who paid for the upgrade!)

Thank you for responding Adar. This is great news but also what I have come to expect about PGMusic. I figured that you were working on the current problems now and would implement added features later. That is why I didn't make any requests in the wish forum.

I have 2 PC with BIAB plugin VST3 and Studio one 3 pro and 4 pro.The 610 Plugin works perfectly. Real and MIDI. The only difference4 is in the generation time that's very fast on the main PC (see below) and very slow on the other.

Yes some people using Studio One Pro 4 have no problems while others do have problems. Unfortunately I'm in the latter group. Weird isn't it!

Ok. So sometimes, especially the written word, doesn't come out right. Apologize for that. I'm going to attempt to explain my thinking.
If you have been a BIAB user for awhile I guess I made the assumption that you would know that it takes time after the release before Christmas to iron out the bugs.its been this way for ever.Report the issues so they can get fixed. I'm sorry but I love PGM and their products. I f it's felt I'm blindly supporting them you are correct especially when comments are counter productive. I was just trying to gather another piece of data.

John I understand completely, thanks for the clarity we all love PG products. If I sounded hard I apologize as well. We are all appreciative regarding the efforts made, both by the PG team and those that help beta test. Your are dead on about the time it takes to iron out the problems. I clearly remember the tussle to get RD right, and then a year later RTs. I also appreciate your efforts to get data to share with PGM.


However lets be totally honest here, as difficult as it is to create software for the multitude of computers that will use it, these things should be ironed out before it hits the market. 1 patch, maybe 2 but were in 9 patches and its still pretty buggy.


Anyway we are all patiently waiting for the next fix then, continued development of this awesome and enjoyable programs.


John thanks again and I hope you keep on "blindly" supporting and asking question.

I will.

But that doesn't make it right! And that is NOT a success strategy for adding new, younger, customers.

Ya, I have been around a long time and I can tell you this was a particularly difficult launch. A month in and at the deadline for the sale and still struggling with making things fully functional. Oh well...., it is what it is.

I could see in the Beta it was short of being ready, but what can you do wait another year ? I don't think I could of done that.
The fixes are coming fast and regular, Adar is doing a great job as we type ! All the things we need to get it working great are planned. When it's all done it's gonna be Magic ! just hope they keep this momentum up !!!

However go to the support page and look at the history of the builds throughout the years. Can you honestly say you expected such a MASSIVE update to be perfect right out of the box? This used to bug a friend of mine. No pun intended. He would just wait a month or so to avoid being frustrated. PGM business plan is none of any of our business.
Happy New Year

John ya gotta point there old friend. This is a biggie, major upgrade that is a game changer to me.

While I do agree with that I also think it should have been more stable for release, and past history of builds and patches should not dictate future plans, in fact it should teach us valuable lessons. Those who not learn from history are destined to repeat it.


That been said, hey I love this company and what they are creating, and I do believe their core principles are true. You said PGM's business plan is none of any of our business. On that while I partly agree, no business will survive without satisfied and engaged customers. The Motto of "the customer is always right". is timeless, and speaks volumes about how commerce is and should be done, if it is to be done properly.

There is a core if followers here, yourself, myself, and many before and after our entry that will do business with PGM no matter what cause this is something we have done and will do. But there is always a need for new customers due to attrition. for a newbie coming in this is hard enough to learn without the problem of it don't work.

Me personally I would rather have the release now and fight through the builds and patches, but some of the newer folks do not have the long term history, and may get frustrated and not come back. To me that would be tragic in the long run. So if we stifle their voice it could at some date get kinda quiet around here.


Anyway I am going to shut the heck up, and bet the next build is going to be a really good one, and I wanna see what Pipeline said happen, keep the momentum right on into the Mac release later this year. Once the buggies are squashed this thing is going to be really useful.

Go Adar, we are rooting for you, ride um cowboy!!!

I mentioned this once before (i think), and if it's a fair kind of marketing policy i dunno: ... PG releases new stuff usually in December, at a 40% offering. Then it takes about 2-5 months of aftermath ironing serious bugs and issues out once the going gets tough on all those differing types of windows OS computers, used by both beginners and nerds. Well, compliments to PG as they work hard satisfying every one. In fact buyers are rewarded, and at the 40% it's OK with me; especially with this years upgrade ít all worked quite smoothly after the latest updates/fixes .... Compliments to all those hardworking programmers ...

Maybe because of this Decemberly marketing policy i sometimes get a little annoyed that nothing happens for quite a while f.i. regarding persistent BIAB 2018 minor bugs and fixes, last year after July/August i think. But as always Kent and the rest of the staff were quite helpful and quick on the draw providing assistance.

I have bought expensive software (and hardware) which was all of a sudden abandoned without even being fixed properly. IMO f*ck Digidesign and Logic; they're pure ripoff companies, never no mo. -F

Now who needs a snickers!!


your channeling your inner Joe Pesci

Not being disrespectful to PGmusic, I have been using BIAB since 1992, however, the VST is poorly coded and I am not going to even attempt to use it again until this forum is happy with it. It has caused a lot of havoc and has crashed my brand new machine several times and I mean really crashed the system.

If I was PGmusic, I would feel very uneasy about suggesting that the software is good to go. Anyone who uses their system to make money should avoid the vst. I am using BIAB for creating styles nothing else. If the vst would work then it would save me about 10 minutes each time I create a style. Right now, I have just gone back to using BIAB as a stand-alone. The vst is a waste of time and needs fixing before I ever try it again. BTW, I use Ableton 10 Suite and Komplete Ultimate. Nothing ever crashes, only the BIAB vst. BIAB itself is really stable. The vst is at best a beta test which is damaging PGmusicˋs reputation.

Greetings all. My two cents. I have Mixcraft Pro Studio 8 running on a Windows 10 PC. It's been running great with no issues. I select VST Plugins left and right with no issues. Everything works perfectly.

I just installed BB 2019 with the DAW Plugin. Opened Mixcraft and saw the BB Plugin listed under my VST Plugins. Perfect. I clicked on it and *BANG* Mixcraft froze irrecoverably. Tried it a few times with the same result. Tried rebooting my computer. Same result. Everything else in Mixcraft works just as it should until I try selecting the BB Plugin. Then I am hopelessly frozen until I force close with Task Manager.

The Plugin feature of BB is what prompted my to blow $250 on BB. Should I be considering a return or is there hope on the horizon?

Thanks,

Dave

Have you installed the latest and greatest update?

https://www.pgmusic.com/support_windowsupdates.htm

Yeah. Just tried it. No love.

I downloaded Mixcraft 8 it crashed a lot of times as it scanned the plugins 32/64.
It won't load the VST3 but it loaded the BB VSTi and the BB VSTfx

There are lots of fixes and improvements currently happening with the VST, I would hang in there if I were you.