There’s a 610 build of BIAB 2019 available. There are changes for the desktop version and the DAW plugin.

You can get 610 here https://www.pgmusic.com/forums/ubbthreads.php?ubb=showflat&Number=513436#Post513436

Note the version number of the plugin is not changed, as the fixes were in accessory Files.

Here are the changes for the plugin:

[*]Fixed: (for the VST DAW Plugin) Generating multi-riffs would sometimes generate an error. (tips: make sure to first select a multi-riff before generating. Also, highlight a region of the chordsheet first to generate just that section as a multi-riff)

[*]Added: (for the VST DAW Plugin) Shots, holds, rests, push chords now read in from BB files.
[/list]

Note that a frequent cause for people saying the multi riffs didn’t generate is that you need to select a multi riff first. (Via the select button) and the. Press generate. (There was also a sometimes error message that has been fixed too’)

Also for multiriffs the typical use is to highlight a section, for example 4 bars, and then select generate and you will get 7 variations of riffs for those 4 bars. If you don’t highlight a section, you will get 7 variations of the whole song (at least the first chorus). Nothing wrong with doing that, it just isn’t the typical use.
Also remember that multi riffs will generate with a single leadin bar because there are often pickup notes in the riff. And there may be an extra bar if there are trailing or decaying notes too.
_________________________
Have Fun!
Peter Gannon
PG Music Inc.

i'm sorry to report that the plugin build 610 does not work any better than build 609
in fact 609 was working even if it was shaky. it did work on new shorter files. I built a new file of 32 bars 1 chorus and while it generated fast, the multiriff (8 bars)locked up on riff 2. it still generated the range check error

Rob,
That's an install issue, where it wasn't installing one file. We've fixed the 610 installer, so you can just download it again and install it. After the install, you can verify that c:\bb\bbw4.exe (assuming BB is installed to c:\bb) is dated 12/28/2018. That's a sign the installation was correct.

BINGO.... Did not get a chance to do more than a 12 bar song with a 4 bar multi riff but worked like a charm in Ableton. Will put it to a work load tomorrow. Great progress and thanks for the hard work

Thanks rap,
Note that this update just addresses two things (multi-riff and shots). There will be a release on Monday that adds more plugin related fixes and features, as well as a 20 minute video on using it with Ableton. we shot that video today, and it worked well in Ableton.

Aawesome Peter I give it a run today I appreciate the effort as we say down here Y’all put into it

Hi Peter--

Could you please answer 2 questions below and
check directly and confirm with your IT dept/ programmer and let us know. I really appreciate your great customer service.

There are some long threads on another BIAB user list where people are asking these 2 questions below--

1. Has BIAB 2019 program really been totally rewritten as a 64-bit program
or did PGM figure out a kludge to wrap the old 32-bit code (or
is much of it still 16-bit?) is it some sort of a wrapper so that it
interacts with other software as a 64-bit program but internally still
32 bit? Sort of like j-bridge serves as a 64-bit "wrapper" for 32-bit
plug-ins so they can be used with 64-bit DAWs.....or has the BIAB 2019 been completely rewritten in native 64 bit code without shortcut wrappers.....question 2 below is associated

2. With the new 2019 BIAB VST feature-- the rendering takes a lot longer in DAW's in both Ableton and Presonus Pro in multiriff mode and in general with the generating. Why does the rendering take a lot longer in the DAW's and why is it faster in the BIAB standalone. Some are saying because BIAB 2019 is not true native 64 bit. I for one as many do-- appreciate fast render times and being able to quickly stay in the creative zone and not have excessive render times.

Thank you for getting the correct answers to us so people will stop speculating and complaining. Your software is awesome but we sure hope the rendering can be faster and need to know the answers from your IT Dept.

It stops a 3rd of the way across when I Generate tracks in both Studio One or Ableton Live. I have tried changing the mapping of directory. still the same. Please Help!!

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..

I was having ~ 30% success rate under Build 609 conditions to get the DAW VST to generate correctly in Cakewalk,sadly no success now under Build 610,with generation hanging at about 75-80% complete and requiring Cakewalk to be crashed out in Task Manager.

...stop press...additionally,the four failed attempts I had this morning to generate a song have also left behind four folders in >C/bb/BBPlugIn/SavedTracks,the combined total filespace used for these is 175Gb! I only noticed this when doing a routine defrag.Currently,the four folders are defying any attempts to change permissions to allow me to delete them.So quite a hit on disc space so far...

I'm sure we'll get there,and when it does work,the results are really pleasing.

Cheers

Neil Cummins
Warrington
UK

I had a similar experience with the VST in Reaper. Seems like 610 is worse than 609...a big step backwards. Isn't there any kind of QA testing platform that would enable the developers to simulate the various environments?

Thanks for the feedback Guichard! Can you please provide a bit more detail on what issues you are experiencing with the plugin? Which tracks are causing errors? Are you able to reproduce the problem every time? As Peter mentioned, build 610 only addressed issues with Multi-Riffs and opening saved shots but there will be another build released this week which may address some of these issues.