I get this message (particularly in jukebox) and everything goes haywire timing wise. I'm on windows 10 with BIAB 2016. I've sent this in yesterday to Pgmusic, so it's early days, but I wondered if anyone else had seen it? I tried using only Realtracks at approximately their original speed, give or take 20 bpm but it continues to happen seemingly randomly. Different songs each time and more often in Jukebox mode.
Basically, if I can't sort this, I can't use BIAB live - so back to rendered wave files and no midi automation in BIAB which would be a drag, as I've now got my midi automation up and running.
Thanks.
Neil
Windows 10 Home 20H2 Build 19042.487 BIAB 2021 (Build 818) Intel(R) Core(TM), i3-4160, CPU @3.60 GHz RAM 16 GB, 64 Bit X64-based processor Zoom UAC-2 (USB 3 interface-built in midi) VoiceLive 3 Extreme, Sputnik Valve Condenser Mic
Are you "running BIAB as administrator". That's the first thing I'd try (well, maybe the second... I might try resetting BIAB to defaults first and the reselecting appropriate drivers and relevant configuration items.
John
Laptop-HP Omen I7 Win11Pro 32GB 12TB SSD Desktop-ASUS-I7 Win10Pro 32GB 12TB SATA
I get this all the time on both my laptop (Win10) and my desktop (Win8). I have been having this error message pop up periodically since RealTracks first came out back in 2009. My friend in another location, who also has BIAB installed on his desktop system, also gets this same message on a periodic basis. It usually happens when we add additional RealTracks to the Melody or Solo track but not always. It is hit and miss all the time. It might be OK when you load a particular song but crashes the next time that same song is loaded or regenerated.
Trust me, after 6 years of using RealTracks and trying just about everything known to man, I have not been able to eliminate the problem.
It is not a show stopper for me, it is just one of those still lingering annoyances of using BIAB in its present form.
I never get it on a pure MIDI song, only songs that have RealTracks since I think that this particular part of the program only deals with RealTracks. But since I am not a programmer, I am only guessing at this as a layman.
I just attribute it to bad programming and just restart the program and reload the particular song I am using at the time and it usually reloads OK.
I do find it interesting that when I look at the properties of dllelastiquePro.dll on my desktop, the details tab shows a date modified of 11/22/2010. Not sure if that is the last time that particular DLL file was actually coded or not. If so, it seems we are due for an updated version.
BIAB2026 Windows 10 Pro (Never Windows 11!) WA6NCB
Looking at the name of the file, it seems to be related to zplane's Élastique software that PG Music use for modifying the Realtrack audio files when they are assembled into a backing track. That's why I wondered if maybe the "Silence" track was having an effect.
You mentioned that this access error seems to arise more often when RTs are on the Melody or Soloist position. Again, this is in keeping with the the original poster's placement of Silence.
What is your sound setup and do you use MME or ASIO?
Thanks for the response, and I'll try all the suggestions.
I don't normally have Realtracks on soloist or melody tracks. I am however, using midi controllers on those tracks. It's the only way I can get it to work. I have my Nova guitar multi effects controlled on the soloist track (midi channel 16) and my Voicelive 2 controlled on the melody track (midi channel 4). It works a treat for changing controls. I found I couldn't consistently get control changes to work when they were both on the same track but pointed at different midi channels.
I do find I have to empty the tracks first to get the midi working which for me is a bit hit and miss. The trouble with using midi controllers is that it's all sort of self taught and from help on the forum as it's not covered in the manuals. I guess it's a bit obscure.
My problem is that if I can't run my BIAB tracks through jukebox automatically, it's all a bit troublesome. As the other commentators have mentioned, the error appears randomly and varies as far as which song it is. From what I'm hearing, it doesn't sound like it's me doing something wrong or stupid per se.
Perhaps it's time to move to Realband
Last edited by lambada; 01/11/1602:24 PM.
Windows 10 Home 20H2 Build 19042.487 BIAB 2021 (Build 818) Intel(R) Core(TM), i3-4160, CPU @3.60 GHz RAM 16 GB, 64 Bit X64-based processor Zoom UAC-2 (USB 3 interface-built in midi) VoiceLive 3 Extreme, Sputnik Valve Condenser Mic
Then, with the program closed, please right click on your Band-in-a-Box shortcut and select Properties | Compatibility | check "Run program as administrator" and click apply. Then just double click on your Band-in-a-Box icon to launch the program.
If the issue persists, please let us know.
Windows 10 Home 20H2 Build 19042.487 BIAB 2021 (Build 818) Intel(R) Core(TM), i3-4160, CPU @3.60 GHz RAM 16 GB, 64 Bit X64-based processor Zoom UAC-2 (USB 3 interface-built in midi) VoiceLive 3 Extreme, Sputnik Valve Condenser Mic
My current setup on my Desktop is running the sound through my Scarlett 2i2 Audio Interface using their built in ASIO drivers. Before in the past, I have had it running through my old Line6 Audio Interface using their built in ASIO. I have also ran it straight into my MB built-in Realtek sound system using both MME and ASIO4ALL and gotten the error message.
I also run everything using full Admin Privileges via changes in my Windows Registry Group Policy settings.
Outside of using an updated dllelastiquepro.dll file, I have tried just about everything I can think of to eliminate the error message from occasionally popping its ugly head up.
Also, my initial install of BIAB is the 2009 version. Everything I have after that all the way up to version 2016 is via upgrades only.
I have had it pop up using Windows 7, 8, 8.1 and 10 both on an AMD Processor and MB and an pure Intel Processor and MB.
Last edited by jcland; 01/11/1605:18 PM.
BIAB2026 Windows 10 Pro (Never Windows 11!) WA6NCB
Even though you have Windows set to run with full administrator privilege, I would still try setting the specific BBW.EXE to "run as administrator". The rules for administrator privilege changed with Windows 7 (and carried through 8 and 10). I've found just setting the UAC to the lowest level isn't always the same as specifically stating "run as administrator".
John
Laptop-HP Omen I7 Win11Pro 32GB 12TB SSD Desktop-ASUS-I7 Win10Pro 32GB 12TB SATA
Way ahead of you on that one John. One of the 1st things I did when I encountered the error message years ago was to 'change' BBW.EXE to run in full admin mode. That did not fix it.
I also changed UAC setting long before I even installed BIAB or any other program on my computer. Since I build all my own desktops, I have full control on what is installed, no bundling here.
My Administrator settings are done deep in the registry via the Security Policy settings which I modify.
I have been in the computer tech business for about 40 years now so I have tried just about everything. I am not an expert by any means and this one not only stumps me, it really bugs the heck out of me!
Still working on the problem and will be trying an experiment today by reinstalling BIAB again from 2009 on via my upgrades.
Oh and BTW, I have, in the past, done a clean install of Windows 7 and 8 and only put in BIAB and I still get the error message so I know for a fact the problem is not caused by a 3rd party program install. It is just Windows and BIAB.
BIAB2026 Windows 10 Pro (Never Windows 11!) WA6NCB
I've clicked on the Administrator check box, just in my icon and no difference. Now it's happening every few songs. It's making the jukebox basically worthless (sigh).
Edit: I just ran the Windows 10 compatibility option on the BBW.exe file and it churned away telling me it had made some changes. Anyway, so far it has played about 10 songs in jukebox without a problem. My screen looks a bit chunkier, and I've no idea what else it did, but if it continues to work, I'll be very relieved. Happily watching my effects units automatically flickering away and changing settings via midi......
Last edited by lambada; 01/12/1605:57 AM.
Windows 10 Home 20H2 Build 19042.487 BIAB 2021 (Build 818) Intel(R) Core(TM), i3-4160, CPU @3.60 GHz RAM 16 GB, 64 Bit X64-based processor Zoom UAC-2 (USB 3 interface-built in midi) VoiceLive 3 Extreme, Sputnik Valve Condenser Mic
We haven't heard of that issue before, and since it's been happening to you since 2009, that means it isn't due to Windows 10, and was happening with earlier versions.
I'd suspect it's something song-specific, or as you suggest, track specific (Melody or Soloist track). I doubt that its caused by the Elastique.dll, since its happening certain tracks. Just as an experiment, you could turn on or off the setting Prefs-RealTracks-High Quality Tempo/Pitch Stretch, to see if that makes a difference. If the issue persists, please email us a song where it happens, referencing this thread. (possible causes other than a bug in BIAB, could be faulty hard drive, bad memory, out of memory (many tracks, long song)
I need to make a correction/clarification on my initial post. The problem started showing up after the 2011 upgrade since the new method using High Quality Tempo/Pitch Stretching was not in the 2009 or 2010 version of BIAB.
I also notice that since the 1st inception of this ability to do high quality stretching using the file dllellastiquepro.dll, that particular file has never been updated since it 1st was installed in 2011.
I did an experiment this morning by installing a new copy of BIAB starting from 2009. When I upgraded the 2010 version to 2011 and the file dllellastiquepro.dll showed up in the BB directory for the 1st time, I moved that file out of the BB directory to see if my 2012 upgrade would replace that missing file with a possible newer version. I did this same process upgrading to 2012.5, 2013, 2014, 2015 and finally 2016.
Each time I moved the file dllellastiquepro.dll out of the BB directory before doing the next sequential upgrade and each time the file dllellastiquepro.dll showed up in the BB directory after doing the next upgrade. However, the properties of the file were exactly the same. In other words, the file dllellastiquepro.dll has had the same property details since version 2011 of BIAB came out. File size was 437,272 Bytes and the modification date was 11-22-2010. What I see is that dllellastiquepro.dll has never had an update since 2011.
I would be more than happy to work with someone on this to finally resolve my long standing problem. We work on 3 different computers and all 3 has had this error at some time. My last encounter was yesterday after regenerating a song we added a RT to.
I will turn off the High Quality switch and give it a try. As far as hardware, I doubt seriously that is the problem since we have had this happen on 2 desktops and 1 laptop. Desktops use AMD processors and the laptop uses an Intel I7 processor. All 3 computers have 8 gig of memory. I run BIAB on a separate 2 TB 7200 RPM Seagate HD on my Desktops and a 2 TB Hardrive on the Laptop. Sound system are different on all 3 systems as are the video cards. I have tried all combinations of running no anti-virus or malware software, shutting down all un-necessary programs in the background, full admin settings in the Security Policy setting on all 3 computers and so on. I have been playing with this problem on and off for over 4 years now. Next time the problem shows up, I will send PG Support as much detail as I can.
BIAB2026 Windows 10 Pro (Never Windows 11!) WA6NCB
For what it's worth, I have used the Jukebox feature in a live praise & worship setting every weekend for over eight years now, updating the BIAB program each and every year and always adding all new RealTracks, and I have never seen this message.
I use RealTracks on everything but strings but I never use the "Silence" track nor do I ever put any RealTracks on the Melody or Solo tracks, so maybe that has something to do with your problem. I am currently using Windows 7 (for about the last 3 years) but I used Windows XP in the past and, again, have never, ever seen this error message.
Jim Psalm 33:3 Sing unto him a new song; play skillfully with a loud noise.
XPro & Xtra Styles PAK Sets On Sale Now - Until May 15, 2026!
All of our XPro Styles PAKs and Xtra Styles PAKs are on sale until May 15th, 2026!
It's the perfect time to expand your Band-in-a-Box® style library with XPro and Xtra Styles PAKs. These additional styles for Band-in-a-Box® offer a wide range of genres designed to fit seamlessly into your projects. Each style is professionally arranged and mixed, helping enhance your songs while saving you time.
What are XPro Styles and Xtra Styles PAKs?
XPro Styles PAKs are styles that work with any version (Pro, MegaPAK, UltraPAK, UltraPAK+, or Audiophile Edition) of Band-in-a-Box® 2025 (or higher). XPro Styles PAKS 1-10 includes 1,000 styles!
Xtra Styles PAKs are styles that work with the UltraPAK, UltraPAK+, or Audiophile Edition of Band-in-a-Box® 2025 (or higher). Xtra Styles PAKs 1-21 includes 3,700 styles (and 35 MIDI styles)!
The XPro & Xtra Styles PAKs are not included in any Band-in-a-Box® package.
The XPro Styles PAKs 1-10 are available for only $29 ea (reg. $49 ea), or get them all in the XPro Styles PAK Bundle for only $149 (reg. $299)! Listen to demos and order now! For Mac or for Windows.
The Xtra Styles PAKs 1-21 are available for only $29 ea (reg. $49 ea), or get them all in the Xtra Styles PAK Bundle for only $199 (reg. $349)! Listen to demos and order now! For Mac or for Windows.
Note: XPro Styles PAKs require Band-in-a-Box® 2025 or higher and are compatible with ANY package, including the Pro, MegaPAK, UltraPAK, UltraPAK+, and Audiophile Edition.
The Xtra Styles require the UltraPAK, UltraPAK+, or Audiophile Edition of Band-in-a-Box®. (Xtra Styles PAK 19 requires the 2025 or higher UltraPAK, UltraPAK+, or Audiophile Edition. They will not work with the Pro or MegaPAK version as they require the RealTracks included in the UltraPAK, UltraPAK+, or Audiophile Edition.
Supercharge your Band-in-a-Box today with XPro Styles PAKs and Xtra Styles PAK Sets!
With the release of Band-in-a-Box® 2026 for Mac, we’re rolling out a collection of brand-new videos on our YouTube channel. We’ll keep this forum post updated so you can easily find all the latest videos in one convenient spot.
Whether you're exploring new features, checking out the latest RealTracks or Style PAKs, this is your go-to guide for Band-in-a-Box® 2026.
Band-in-a-Box® 2026 for Mac is here and it is packed with major new features! There’s a new modern look, a GUI redesign to all areas of the program including toolbars, windows, workflow and more. There’s a Multi-view layout for organizing multiple windows. A standout addition is the powerful AI-Notes feature, which uses AI neural-net technology to transcribe polyphonic audio into MIDI—entire mixes or individual instruments—making it easy to study, view, and play parts from any song. And that’s just the beginning—there are over 100 new features in this exciting release.
Along with version 2026, we've released an incredible lineup of new content! There's 202 new RealTracks, brand-new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 5, two new RealDrums Stems sets, XPro Styles PAK 10, Xtra Styles PAK 21, and much more!
Special Offers
Upgrade to Band-in-a-Box® 2026 for Mac and save up to 50% on most upgrade packages during our special offer—available until May 15, 2026. Visit our Band-in-a-Box® packages page to explore all available upgrade options.
2026 Free Bonus PAK & 49-PAK Add-ons
Our Free Bonus PAK and 49-PAK are loaded with amazing add-ons! The Free Bonus PAK is included with most Band-in-a-Box® 2026 for Mac packages, but you can unlock even more—including 20 unreleased RealTracks—by upgrading to the 2026 49-PAK for just $49.
Band-in-a-Box® 2025 for Mac® users: Build 904 now available!
If you're already using Band-in-a-Box® 2025 for Mac®, make sure to grab the latest update! Build 904 is now available for download and includes the newest additions and enhancements from our team.
One of our representatives will be happy to help you over the phone. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday, and 8:00AM to 4:00PM PST Saturday. We are closed Sunday. You can also send us your questions via email.
One of our representatives will be happy to help you on our Live Chat or by email. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday; 8:00AM to 4:00PM PST (GMT -8) Saturday; Closed Sunday.
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean