Welcome to the forums, JVLaine! Is there anything in particular that you click on in the plugin that makes it crash? You could also try Running FL Studio as an Administrator and see if that helps.
Welcome to the forums, JVLaine! Is there anything in particular that you click on in the plugin that makes it crash? You could also try Running FL Studio as an Administrator and see if that helps.
This issue does not happen as often when in the "preferences/Daw Settings" tab, "Highlight Bar from Daw is set to 'none' Anything else FL Studio will crash almost immediately. I have tried all the various suggested recommendations with no real effects. I have downloaded the latest update (Build 920). now Fl Studio just shuts down when you try to use it!.....
Welcome to the forums, JVLaine! Is there anything in particular that you click on in the plugin that makes it crash? You could also try Running FL Studio as an Administrator and see if that helps.
This issue does not happen as often when in the "preferences/Daw Settings" tab, "Highlight Bar from Daw is set to 'none' Anything else FL Studio will crash almost immediately. I have tried all the various suggested recommendations with no real effects. I have downloaded the latest update (Build 920). now Fl Studio just shuts down when you try to use it!.....
Still after the latest updates both BIAB(920) and FL Studio (20.9.1) this problem persists. Running as an Administrator does not help. My workaround for the time being is to run the DAW Plugin standalone and not inside FL Studio. Rather annoying.
BTW I am not a "Newbie". Been using Biab for over 15 years, and registered to this forum 2005.
Thank you for the feedback JVLaine! This will be fixed for the next build. Please let me know if you are still having issues after testing the next build.
These patches included fixes for the plugin as well, so if you're ever experiencing crashes it's a good idea to make sure you're on the latest build first. The patch updates are cumulative, so you can go ahead and simply install the latest one for your specific version year.
Is this available only to J.V Laine. Or all of us having this problem. because when I try to access this, I get an access denied and I cannot return back to where I left off. please!.... I really need this.
Is this available only to J.V Laine. Or all of us having this problem. because when I try to access this, I get an access denied and I cannot return back to where I left off. please!.... I really need this.
That link goes to DAW Plugin update to build 4.5.33 which is still in beta testing. If you can't follow the link than you will need one of the PGTeam to get you in. Will have to wait for them to come along.
That link goes to DAW Plugin update to build 4.5.33 which is still in beta testing. If you can't follow the link than you will need one of the PGTeam to get you in. Will have to wait for them to come along. _________________________ Dan, BIAB2022, Dell XPS 8920 Intel Core I7-7700 @ 3.60GHz 16GB RAM, REAPER, nanoKontrol2, SL88-Studio, M-Audio61
Is this available only to J.V Laine. Or all of us having this problem. because when I try to access this, I get an access denied and I cannot return back to where I left off. please!.... I really need this.
Not even JV Laine couldn't access this ;-) ...and I too really need this.
That link goes to DAW Plugin update to build 4.5.33 which is still in beta testing. If you can't follow the link than you will need one of the PGTeam to get you in. Will have to wait for them to come along.
Hi JVLaine, if you would like to try the pre-release build update, then please contact us directly either over live chat or email support@pgmusic.com. We try to only have the approved beta testers have access to the pre-release builds, but if it fixes your particular issue we can send it to you directly.
THIS IS THE ERROR LOG CRASH MESSAGE FROM FL Studio:
FL Studio (20.9.2.2907) [64Bit] r27090 has encountered an error and needs to restart.
Crash log saved to C:\Users\javla\Documents\Image-Line\FL Studio\Support\Logs\Crash\ folder.
Please use Ctrl+C to copy this message and report to support.
Exception: Access violation at address 00007FFC393F4626 in module 'Band-in-a-Box DAW VST3 Plugin.vst3'. Read of address FFFFFFFFFFFFFFFF Callstack: 00007FFC393A0000:00007FFC393F4626: Band-in-a-Box DAW VST3 Plugin.vst3
THIS FROM BB:
[2022.922.0, 30.4.2022 11.14.30] *** This function is completed [2022.922.0, 30.4.2022 11.14.30] Rendering file to disk: C:\bb\BBPlugin\SavedTracks\2022-04-30, 11-14-21\Guitar 3 - N A 619 Guitar, Resonator, Background Cowboy Ev 165.wav [2022.922.0, 30.4.2022 11.14.28] Rendering file to disk: C:\bb\BBPlugin\SavedTracks\2022-04-30, 11-14-21\Guitar 2 - N A 1119 Guitar, 12-String Acoustic, Strumming Ev 120.wav [2022.922.0, 30.4.2022 11.14.27] Rendering file to disk: C:\bb\BBPlugin\SavedTracks\2022-04-30, 11-14-21\Guitar 1 - N A 522 Guitar, Acoustic, Fingerpicking Ev 120.wav [2022.922.0, 30.4.2022 11.14.26] Rendering file to disk: C:\bb\BBPlugin\SavedTracks\2022-04-30, 11-14-21\Drums - RealDrums=NashvilleEven8^2-a Sidestick, HiHat , b Snare, HiHat .wav [2022.922.0, 30.4.2022 11.14.25] Rendering file to disk: C:\bb\BBPlugin\SavedTracks\2022-04-30, 11-14-21\Bass - N A 519 Bass, Electric, Pop HalfNotes Ev 120.wav [2022.922.0, 30.4.2022 11.14.24] [2022.922.0, 30.4.2022 11.12.33] *** This function is completed [2022.922.0, 30.4.2022 11.12.33] [2022.922.0, 30.4.2022 11.12.16] *** This function is completed [2022.922.0, 30.4.2022 11.12.16] Bootup was optimal, set to fast [2022.922.0, 30.4.2022 11.12.16] Bootup time in milliseconds =1,770 [2022.922.0, 30.4.2022 11.12.16] Time to scan unknown VST plugins = 5 ms [2022.922.0, 30.4.2022 11.12.15] Time to scan known VST plugins = 4 ms [2022.922.0, 30.4.2022 11.12.15] Time to scan AU plugins = 0 ms [2022.922.0, 30.4.2022 11.12.15] Time to scan ALL plugins = 9 ms [2022.922.0, 30.4.2022 11.12.15] Time to Count Plugins in ms =222. Plugins counted=21 [2022.922.0, 30.4.2022 11.12.15] Scanning for plugins... [2022.922.0, 30.4.2022 11.12.15] **** New Session started at : 30.4.2022 11.12.15
Yes I'm getting a long error message, but I dont know how to get the screen shot copied onto these forum posts.
I've just realised I misunderstood that.
To post a screenshot you need to use "full reply", either by clicking the "Reply" or "Quote" buttons (i.e., not just using the window at the bottom of the page or by using the "Quick Reply" or "Quick Quote" buttons, of if you've started with one of those, then click the "Switch to Full Reply Screen". Once you've done that, you'll have a "File Manager" link below the text window. It's rather arcane.
JV. Maybe it IS a bug in the pg plug in…but i have some questions. 1. When your creating your song from scratch in bb are you inserting vst’s using bb plug in feature ? if so see if removing the vst works. Sometimes ive found some plug ins are just no good and can make a crash. I always test out any new vst plug ins in several music software daws to see if the plug in is problematic. 2. Are you using 64 bit plug ins in the bb 64 bit ?
I’m a tad confused by the info given. If further pg fixes dont work for you with fruity , but do for other fruity users i would suspect it might be an issue in how things are set up/preferences etc. What usb sound interface are you using ?
To conclude over the years ive had various problematic vst’s sometimes that gave me probs.
Whether this is the reason in your case..i dont know. Finally some info on your pc might be useful so as to get a rounded picture of your rig/setup. Please note running everything on one drive can sometimes be problematic eg big vstis// sample libs on the win os drive….because of disk contention.
just putting forth some ideas in case its not a pg bug and/or bug has been addressed.
JV. Maybe it IS a bug in the pg plug in…but i have some questions. 1. When your creating your song from scratch in bb are you inserting vst’s using bb plug in feature ? if so see if removing the vst works. Sometimes ive found some plug ins are just no good and can make a crash. I always test out any new vst plug ins in several music software daws to see if the plug in is problematic.
My workflow is the same as in the PG Music video for DAW Plugin in FL Studio. I.e I open the FL Studio and insert BIAB VST3 DAW Plugin in the Channel Rack. Then create the "song" basis in the DAW plugin and move the wav tracks from BIAB Plugin into the FL Studio playlist. So far so good, but after a few seconds I get the error message from FL Studio ( see above) and the FL Studio crashes.
However, if I use the BIAB Daw plugin standalone and move the wav tracks from there over to FL Studio there is no crashing. This is my workaround for the time being.
2. Are you using 64 bit plug ins in the bb 64 bit ? Yes, everything is 64 bit.
I’m a tad confused by the info given. If further pg fixes dont work for you with fruity , but do for other fruity users i would suspect it might be an issue i how things are set up/preferences etc. What usb sound interface are you using ?
At this point ( i.e. before the crash occurs ) I am not yet using any interface. Everything is done inside FL Studio.
To conclude over the years ive had various problematic vst’s sometimes that gave me probs.
Whether this is the reason in your case..i dont know. Finally some info on your pc might be useful so as to get a rounded picture of your rig/setup.
I have a Lenovo Legion Y540-15IRH, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 16 GB RAM, 500 GB Disc.
Please note running everything on one drive can sometimes be problematic eg big vstis// sample libs on the win os drive….because of disk contention.
just putting forth some ideas in case its not a pg bug and/or bug has been addressed.
JV. Some more questions. 1. When starting a new songr in bb and arranging the chord layout/entering chords what sound device are you using to playback/test arrangement….??? Built in sound ? 2. What sound device are you using when only using fruity ? 3. Are you doing everything using the one lenovo internal drive?..ie Win OS AND programs AND music software AND vst’s on the one drive ?
I might be wrong in your case but be aware that one issue to be aware of is not to let one music software lock out another as this can be problematic.
THUS check that one music software isnt locking out the operation of another. if you have time post pics of your fruity sound device drivers and preferenor and same for biab.
Okay great but how do you do that same thing on a Mac?
This thread is for the plugin on Windows computers. But if you would like to see the video for adding a screenshot to the forums from a Mac computer, it is here:
