Ok...

I open Reaper 64bit and add an instrument track with the Band in a Box VST plugin (tried both VSTi and VST3).
Add chords and pick a style and press generate.

The little blue bar only goes about a 1/4 inch then returns to the beginning and does not generate anything.

I've changed audio from my Presonus 192 to the WAS and that didn't help either.

I know the original plugin from the first release worked just fine but was limited in functionality which has been well documented on the forum.

I even tried the Stand alone version in the BBPlugin/Files folder which is an EXE file and do the above and get the same results.

In the BBPlugin/SavedTracks folder there is an output text file and shows this error:

Error=-14
BBHandle=593194
;Error #-14, WindowHandleForMessages is not defined
StyleTimeSig=4
CompileTimeSeconds=0


I have a high end Rizen 7, Radeon RX580 Video, Republic of Gaming 8350-F Motherboard, 16Gbs of ram and both "C" and "D" drive are SSD drives. I have my BB on the "D" drive.

Any ideas gang?!?!

2019 is destined to be the year of these kinds of posts! The upside? We are seeing a ton of new forum users as they try to get BIAB VST to work and when it doesn't they come here! Hopefully they'll stay and PGM will fix the issues and the BIAB family will grow with some fresh blood!

So far it’s a bust while the plugin did begin to generate the multiriffs it locked up Studio one 4 and I had to crash the program. I’m trying it in standalone mode

Well so far both the VSTI3 and the standalone version do not work properly here.

Both allow me to generate from a style, then when I try multi riff it locks up and won’t finish the blue progress bar locks at about what looks like 90% then I get error messages. I am going to try tech support and see maybe it’s me but kinda doubt it.

RobH, Marcus.
When I wake tomorrow morning I hope we don't have one other person reporting these negative results.

My Christmas wish is that you are the only two out of dozens and dozens (if not 1000s ) of folks who are having these issues with V609. And that everyone else is busily working on creating new music with the Reaper-BBVSTi.

But don't worry, when this Christmas miracle occurs, PGM will be able to put all their attention to helping both of you.

Dan

Tried it in Studio one 2,65, Studio one 4, Reaper, and as a standalone. No joy I get a message in all three DAWs “Range Check Error at: 00407C4A”

Trying to reinstall the update now to see if something went south

Hopeful but not expecting much.

Talked to Kent by live chat. He tried to help, but for him it works fine there. I am beginning to think that this is going to be a long journey to get the thing working properly.

Same problem in Studio One 4 for me too. Error Message: Range Check Error. However this update at least allows me to do multi riffs sometimes. I wasn't able to generate multi riffs at all before this update.

I just opened up a new file and it actually worked. Yet not as the video said I didn’t click all riffs I just click one of the riffs and clicked generate and it did them all. I just tried again and it started to generate without hitting the command

I installed the latest release and I get the "Range check error at: 00407C4A." every time. But if I click OK and then click through the warning that it has crashed it seems to work. With that serious of a crash I wouldn't use it for anything but beta testing right now.

JJJ doesn’t the blue progress bar freeze on your system?

Ok, I just downloaded the latest build (even though it already was 609!) and now it will never complete the multiriff generation! The blue bar stops at about 4/5 of the way through and I get the error. If I try again, same result. Every time I try, same result. This is behaving worse than the last build. Now it is unusable.

Daaaaaaamn this thing actually worked once more testing to follow.

Faaaaaaaaaaaaaiiiiil

22 minutes and still says 4 sec to render

Yes I get the out of range error as well. However if I make the song fairly short like 12 bars the multi riff seems to work. Another problem I experienced was I loaded one of the demo songs called Mmm River Gospel 12-8 with Vocal Mmms.SGU. This song has a multi RT with the vocal mmms and would not generate that track at all but generated the rest of them. So it looks like it will not generate a multi RT.

So Brian I guess that means we should make a bunch of short jingles!

I got it to work one time then it stopped. I called PGM and was told that, and I quote “ it works here on our computers”, great maybe PGM can have someone swing by my house and let me use their computer when I want to create a new project, since mine won’t work three update patches in.

I have every confidence that it’s going to be fixed and will be working properly soon. Just it’s very frustrating to buy something that needs fixing. Kind of like recalls on your car.

Oh well maybe the next patch will get it right, or the next, or .............

I was able to render short 12 bar song in ableton. render time was long but it worked. i was able to regenerate a single, separate track with no issue. multi riff caused range error but I was able to click through that and render completely although render time for 8 bars was over 12 minutes. ( Now i know why they skip ahead in video). tried to re gen one of the multis and it tried to do them all and crashed ableton completely causing need for full reboot of computer.

Maybe 610 will be the one?

I'm giving up on the VST! The main BIAB generates and I can drag over just as fast if not faster than the plugin ever did. I'm waisting more time just trouble shooting rather than making music. In all fairness....my music isn't that great!

I've had BIAB for many years and have faith that they will sort this out. When you think that the various combinations of hardware and drivers in all the computers running this...there are bound to be issues.

G'nite and Merry Christmas to the BIAB forums clan!

Marcus
JJJ
RobH
Brian
Rap429

Well only 5? ... doesn't look like a total bust for V209 but not exactly the Christmas Miracle I was hoping for.

I’m sure that us 5 are just the tip of the iceberg as most folks haven’t posted. Their just waiting to see. The fact that it is the exact same problem for each of us tells me that it is not user error but a reproducible bug. Now it might be a setup or configuration issue common to our computers. Only time will tell.

I would love to hear from folks that the plugin is working flawlessly for, and doing everything that it’s supposed to do.

Robh, what version of Reaper are you running - don't think anyone has mentioned?
Are you disabling your antivirus or white listing the BIAB executable?

It may just be something simple in your configurations.

PGM needs to provide a diagnostic file which records errors which we can send to them to troubleshoot!

Me Too .

Sample tank no sound at all now .

Great questions MS. I am using the latest Reaper, however I don’t really use reaper much just for testing to see if it is the same one two DAWs. I don’t know what “white listing” means. The only Antivirus I use is windows defender since I use my iPad to search the internet 95% of the time and only hit the internet on laptop to install or download stuff for music

Me too was for the bb-vsti !

I just made a small 24 bar song and had different instruments muted on certain bars and included shots on some bars and saved the file in BIAB. When I opened the song in the VST and generated and the muted parts played and the shots did not work at all. I guess none of that has been incorporated as of yet.

Brian

Muted parts have never been saved in the BIAB file. And PGM has not as yet commented on weather or not shots and holds will be included in the BB-VSTi.

Ok perhaps in the future.

By the way which version of BIAB are you using? Mine saves mutes I just saved a song and loaded it back up and it was just like I saved it with the Mutes.

My BiaB saves with mutes too.

So I did a detailed testing this morning of the VSTi plug. If I keep the number of bars at 12, and the multiriff bars at 4 to 6 max I get a render of around 1:30 I can add a second drum track below the melody and solo tracks, but it changes the name of the track to one of the tracks above but does generate a drum track.

If I go above around 18 bars or more than 6 bars of multiriff I get a slow down and a Range check error and I lose the yellow note banner.

I hope this has the techs to locate the problem.

Say what?

I am still on 2018, but I just read somewhere in forum that this old issue continued. Heck, it is hard to keep up all the things going on. Thanks for the info. Maybe time for me to get off the fence.

Greetings, new here

Just got BB to run the vst in Studio One 4.
The first version of the plugin seemed to work work OK, but the two upgrades have both been buggy.

I can still load a .sgu file into the vst (no option to load .mgx?), and generate the parts.
It takes about a minute per track to generate (16 bars).

But the only way I can then get the generated .waw into the DAW is to manually drag them from the location they were saved on the disk (c:\bb\BBPlugin\SavedTracks\) The drag-and-drop as demonstrated in PG's demos don't work.

Entering cords manually in the vst, then generating does not work. The computer will freeze up for several minutes.

Still, this plugin could be a lot of fun, so I am crossing my fingers for a fix!

See if you can follow this convoluted message.

below is a tread going on right now with two of the top forum gurus who also acknowledge that BIAB does not save muted tracks. How can everyone be so confused on this?

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

I now see what the confusion is. I am adding mutes at the bar level not the mixer level. This would explain what is going on. It does save mutes at the bar level just not the mixer setting.
Brian

Am I misunderstanding this? I have many BIAB songs where I have muted the melody in the mixer so I can play the melody myself. If I save the song with the melody muted, when I open the song again, the melody is still muted.

I'm I misunderstanding the issue here or do I have a freak, albeit very welcome, "feature"?

Maybe this is because I'm using BIAB 2018 and not the new version or the VSTI plugin.

Jeff

Will the Plugin ever have Mute, Solo and Volume on each track / Master?

FWIW, I just installed BIAB 2019 last night and stated playing with the VST3 plug in today. For giggles I ran 3 instances of the plug in with different styles and 5 real instruments each. Ran just fine. Sound was terrible with different styles, but I just wanted to see if it would work. Each track in Studio One 4 has it's own Mute, Solo, and Fader for all 15 rendered audio tracks and the shot, rests and holds work fine.

Need to putts some more but "having fun"

Walt

BiaB doesn't save the mute status of tracks - it has been that way for the last 30 years.

One day you may practise all your songs with the melody muted, and the next day you might want them with the melody playing.

If you want to silence a part for a song, you can disable it (track settings - disable), or turn its volume to zero.

>Need to putts some more but "having fun"

Thanks for the report WallyG.

>And PGM has not as yet commented on weather or not shots and holds will be included in the BB-VSTi.

Currently the only thing not implemented is the plugin loading shots from previously saved BB songs. That will be implemented.

Already implemented is everything else about rests, shots, holds,
- you can type them in and it saves with your DAW project
- if you save as a BB file the shots are saved in it
- the shots etc. generate with the arrangements

Just wanted to say a big thank you to the hard working gang at PG Music. Currently, 611 is working using the latest 64bit Reaper and the VST3. Rendered the main style and did a 16 bar multi riff. All worked great!

Cheers....job well done......forgot to mention...rendering speed is much, much faster!