Hi ,

Do others have the same issue after generating a song on Reaper/ Windows 11 ?


The plugin is very convenient for Reaper , but it crashes randomly just after the generation


Loading it in a separate process as Reaper permits avoid crashing the daw (as the plugin is loaded inside the reaper_host64.exe wrapper , only reaper_host64.exe crashes) , but still it is annoying to have to reload the plugin after the crash of reaper_host64.exe


Btw , I am using the VST2 version as VST3 does not send midi program change to my synt vsti, but I have the same issue with the VST3 version.

Also , I have tried another daw (vsthost) with the same issue.

Hi ,

FWiW , I have noticed that the process bbw4_64.exe is launched during song generation

I have tried to change its setting to run it as an administrator (same for processes reaper.exe and reaper_host64.exe) with no success.

Sorry my DAW is not eligable for Win11 otherwise, the BIAB-VST has been stable with Win10.

Hi ,

Thanks for the info

Sometimes I am able to do several generations in a row , but eventually there is a crash

Gegu,

Welcome to the forum and to Band-in-a-Box. If you would like to help PG Music resolve the issue, there are several text file logs you can copy and post in the forum.

Use Notepad to create a blank text file. Save the blank file under the name "PreserveAllFiles.txt. Move the PreserveAllFiles.txt file to the BBPlugin directory at \bb\BBPlugin\PreserveAllFiles.txt.

The blank file instructs the plugin to keep all temporary input-output files. These files normally are generated on the fly then discarded. This allows you to look and copy them.

Some of the temporary files include:
BBoutput.txt
RBResults.txt
BBInput.txt
BBSong.txt

There are two locations where you may find useful information regarding crashes. They include:
\bb\Data\bbw4_PlugInLog.txt. Backend Errors messages can appear here. Backend is communication between the main Band-in-a-Box program and the plugin.
\bb\Data\bbw4_64exe_FlashMessageLog.txt
Flash messages are the yellow and green pop up messages that briefly appear. The Flash message file will show some error messages.

Hi ,

Thanks for your advice

Here are the files biab_plugin_crash_files ( I have not found files BBREsults.txt and BB Song.txt) , and the EventWiewer trace.


Before the error , I was able to generate about twenty generations of the same song in a row ( without playing it)


The WinDbg.txt file was made by attaching WinDbg to Reaper_Host64.exe process (but not in the same session as the files above)

When reaper locks up, in the Task Manager you can right click reaper.exe > Create Dump file
then zip it up and post in the reaper forum and they maybe able to tell you what's wrong.

You can try it in KV Element in Reaper
load element as a vst3 plugin then drag and drop the BBPlugin into it, hook the in/out up then click the EXT top left to sync it.

You can try Band In A Box Track Injector for Reaper

Hi ,


I can not create a dump file using the Task manager as the process does not lock but die

The Windows Event Viewer mentions several files but I can not find them
found errors are : 0xc0000374 , 0xc000041d , 0xc0000005 in modules "ntdll.dll" or "Band-in-a-Box DAW VST Plugin.dll"

This issue is very random , sometimes the crash happens at the first generation or after a few generations , but not always

BTW , I have the same issue with another daw (VstHost)


Thanks for your help anyway

Gegu,

Thanks for collecting all those files.

The plugins depend on the main Band-in-a-Box program to regenerate tracks. The bbw4_64.exe app you mentioned runs in the background as needed to provide a communication path between the plugin and the Band-in-a-Box program.

Again, thanks for your assistance.

Hi ,

FWIW , here is the procmon64 trace of reaper_host64.exe and bbw* processes from beginning of song generation to the crash : procmon64_logfile

using the build 4.5.33 of the VST2 plugin in Reaper 6.57 , driver asio RME Babyface Pro @ 44.1 Khz / 24 bits


No trace of a Band In A Box program , only the backend
but it seems that the size of bbw64.exe and bbw4_64.exe are similar ( 54946 kb vs 54981 kb) ?

There are several WerFault.exe process near the end

Also , I have tried to do a test with "dummy" audio driver in Reaper with the same issue.

Hi ,


It seems that unckecking "sync" during song generation does the trick (both in Reaper and VstHost)

If checked , error happens again

(Why ? ...)

Oh, the sync button. Why didn't you mention that earlier. I think you have reinvented the wheel.
I have not seen that problem in a long time. See my setup.

Hi ,

The sync button I am talking about is on the GUI biab_vst_sync

It is not evident why it has an influence during song generation , but I am affirmative on this.

My point gegu was this is unforturnately old news to many of us. I set my configuration to avoid this trap. You ask why? Because even well into its 3rd year this application is a bit of a work in progress. It can work fine and do what nothing else can do, but you have to know what not to do.

Hi ,

The workaround (I think I have found) is not too restrictive, I hope it can be useful for others.

But of course it would be better if the cause is solved


Thanks for your help and advice

Gegu

The somewhat glib response points to a glaring issue with BIAB..."old hands" find & share solutions and the program isn't modified to resolve them as there's insufficient "call" to do so.

Newer users are left with the task of problem identification & solution finding or asking for help in the forum as the search engine for such issues is, at best, hopeless.

If the wheel isn't known it will, eventually, be (re)invented.

Hey don't blame the messenger.

Hi ,


The plugin does not crash during song generation if I don't check "sync" ,

but still there have been a few crash while the daw is doing nothing


Some error dumps that occured during song generation : vst_plugin_crash_dump_files

Thank you for the feedback gegu! As far as I am aware, there has never been an issue regarding the sync button causing a crash while generating, so this is not old news to me.

In order to help determine the cause of the crash, I will need you to provide me with the following files:
1. C:\Users\Public\Ticket\BBPluginDebug.txt
2. bb\BBPlugin\SavedTracks\BBInput.txt
3. bb\BBPlugin\SavedTracks\BBOutput.txt
4. bb\BBPlugin\SavedTracks\BBSong.txt

*Note that files 2, 3, and 4 require the presence of this text file: "bb\BBPlugin\PreserveAllFiles.txt". All of the files should be acquired immediately after the crash.

Could you also provide me with a saved song file (.sgu) as well as the exact steps you took to reproduce this crash? This should include details like which style/other tracks are loaded and any other information that may affect the way the song is generated.

If you have a screen recording program (like OBS which is free), it would be great if you could share a video of your screen leading up to a crash. This is often the easiest way for me to determine what the cause of the crash is.

You can upload all this information here or email me directly at aguy@pgmusic.com. I will do everything I can to help you resolve this issue!

Hi ,

Here is the video recording of "follow that cab" generation with "sync" checked, using vsthost64 daw and the VST2 plugin (VST3 plugin , reaper daw crash too) :

vsthost64_biab_vst2.mp4

Sometimes the crash happens at first or after a few generations , whatever the song is


As I said , having "sync" unckecked during the generation helps a lot , but I have had a few crash even when doing nothing

As for the files you asked for , I have already given links in my former posts

Well here I am being all glib again. There was so much wrong with that video it is hard to discribe. That is not the way the program is supposed to behave. Five minutes I will never get back again. But if Adar puts his eyes on it that is your best bet for getting it straightened out.

By the way, did you try my configurations for Reaper? Cause I see you have the Audio outs all messed up (IMO) which can be fixed in the configuration settings. I really do hope Adar can point you in the right direction.

Hi ,

For Reaper , I have tried the "dummy" audio driver with same results

hi ,

same conditions , crash occured after only three generations :

A video with reaper ( crashed at second generation) :

reaper_biab_vst2


Window Event Wiever :

Rendering : Separate ...(Try to) Disabled (Default)

Hi ,

Crashed almost immediatly unfortunately ... (both in Reaper and Vsthost64)

For Reaper , I prefer using separate outputs to equalize each track live (sent to jamtaba plugin)

Those download vudios are freaking out my computer.... are you in eastern Europe?

I am from Paris , France , and I have been living here for 60 years

Gegu,
what version of Reaper? I don't have to go through much effort to load PG Music BIAB onto a track.
It won't have any impact but you should synch the tempos.
Have you checked the folder generated files are saved to? It may be going beyond it's nominated size...probably won't help either but worth checking.
That was a lot of regenerating...I don't do any changes or regenerations within Reaper as I feel much more comfortable doing the grunt work in the main BIAb prog...but I understand it was to get you to the crash point.
Don't worry about negativity - it's the change to Lake Michigan water that has seen the rise & rise of the curmudgeon estate.

Hi ,

Reaper version is 6.57 , but the problem exists also with another daw (Vsthost) , on two computers running Windows 11
(maybe this OS is more tricky about certain errors ?) ,and it can happen at the FIRST generation too.

Syncing the tempo before generating song does not help

I have checked disk space on both computers , it is OK

I have taken care to restart the computer before testing (but not always)

I am using the BIAB plugin as it permits to generate songs then play them without putting them on tracks (by just hiting the "play" button") , and I am using Reaperfor the jamtaba plugin (playing guitar on the internet live with an backing track fed directly by the BIAB plugin)

Anyway , let the developers investigate.

You can try it with Rewire, you don't have to use the Reaper script with it. Just load the RewireVST into Biab then select Reaper.

https://forum.cockos.com/showthread.php?t=251311

The Biab rewire control GUI crashes too

Anyway , it is not as practical as using the plugin inside Reaper

An error that occured while the DAW was idle :

after a while I upgraded my BIAB 2022 with latest VST only to realize it is crashing my cubase 12 pro not loading songs which are saved in standalone BIAB??

Is it the actual Rewire64Vst that crashes if so it's maybe Win11 issue:

Watch: https://www.dropbox.com/s/zu9hnipkjseu5n3/Reaper-Biab-RewireVST.mp4?dl=0

It's best to start a new post detailing your specific issue. Piling one report on top of another means your report may not get the attention it deserves.

Check out +++ THIS +++ post and +++ THIS +++ post for suggestions about log files you can attach to your post that will help Adar, the main plugin developer, identify and fix the issue.

Hi ,


I got this error while loading the BIAB plugin in VstHost :

Created VSTSynthFont64 instance 1 host=band-in-a-box
getOutputProperties 0
getOutputProperties 2
getOutputProperties 4
getOutputProperties 6
getOutputProperties 8
getOutputProperties 10
getOutputProperties 12
getOutputProperties 14
getOutputProperties 16
getOutputProperties 18
getOutputProperties 20
getOutputProperties 22
getOutputProperties 24
getOutputProperties 26
getOutputProperties 28
getOutputProperties 30
getOutputProperties 0
getOutputProperties 2
getOutputProperties 4
getOutputProperties 6
getOutputProperties 8
getOutputProperties 10
getOutputProperties 12
getOutputProperties 14
getOutputProperties 16
getOutputProperties 18
getOutputProperties 20
getOutputProperties 22
getOutputProperties 24
getOutputProperties 26
getOutputProperties 28
getOutputProperties 30
Initialising VST: VSTSynthFont64 (2.0.0.0)
(2778.4c54): Invalid handle - code c0000008 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
ntdll!KiRaiseUserExceptionDispatcher+0x3a:
00007ff8`c8167eda 8b8424c0000000 mov eax,dword ptr [rsp+0C0h] ss:00000000`0013ef70=c0000008


the rendering plugin loaded by bbw4_64.exe was : E:\vstplugins\64 bits\PG Music\Band In A Box\VSTSynthFont64.dll

(version 3.4.3.1)

I still don't understand why you need to use VSTHost in Reaper.
It seems unnecessary and the potential problem.

VSTHost is old that's why I suggested trying in Element as this fixed all the crash problems I was having in Reaper, so I think it is worth a try.
You can also try https://jstuff.wordpress.com/pluginflipflop/


KV Element with BBPlugin in Reaper:

Sorry, maybe I was not clear :

Vsthost is a standalone like Reaper , I tried it to see if the issue is only with Reaper


Btw , with Reaper , I have tried a minimal project with only one track containing the BIAB plugin , same issue
Another test was with Coyote VST (1.0.0.1) instead of VstSyntFont64 , same issue

Fwiw, the most common error encountered is heap corruption in the BIAB plugin


Would it be worth generating a song with only audio tracks (assuming that the synth vsti would be loaded but not used in this case ...) ?

Hi ,

Issue too using CWITECH TX16Wx VST2 plugin as the renderer in a minimal Reaper project containing only one track with BIAB VST2 plugin

The easy solution obviously would be to reinstall Windows... It seems that your problems mainly concern your own configuration. Otherwise we can continue to write pages for years with everything that does not wor

I agree, but the fact is that this issue happens on two computers both running Windows 11


Will try to reinstall Windows 10 on one of the computers ...

FYI I'm on Win11 and I use Biab Plugin in Reaper, and really no problem, even after 10 generations. If it does under your 2 WIN11s, actually very weird. Look at disk access rights or driver updates?