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 2x2TB, 1x4TB SSD Desktop-ASUS-I7 Win10Pro 32GB 2x1.5TB, 2x2TB, 1x4TB 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.
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.
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 2x2TB, 1x4TB SSD Desktop-ASUS-I7 Win10Pro 32GB 2x1.5TB, 2x2TB, 1x4TB 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.
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.
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.
Add updated printing options, enhanced tracks settings, smoother use of MGU and SGU (BB files) within PowerTracks, and more with the latest PowerTracks Pro Audio 2024 update!
Download and install this to your RealBand 2024 for updated print options, streamlined loading and saving of .SGU & MGU (BB) files, and to add a number of program adjustments that address user-reported bugs and concerns.
Did you know... not only can you download your Band-in-a-Box® Pro, MegaPAK, or PlusPAK purchase - you can also choose to add a flash drive backup copy with the installation files for only $15? It even comes with a Band-in-a-Box® keychain!
For the larger Band-in-a-Box® packages (UltraPAK, UltraPAK+, Audiophile Edition), the hard drive backup copy is available for only $25. This will include a preinstalled and ready to use program, along with your installation files.
Backup copies are offered during the checkout process on our website.
Already purchased your e-delivery version, and now you wish you had a backup copy? It's not too late! If your purchase was for the current version of Band-in-a-Box®, you can still reach out to our team directly to place your backup copy order!
Note: the Band-in-a-Box® keychain is only included with flash drive backup copies, and cannot be purchased separately.
Handy flash drive tip: Always try plugging in a USB device the wrong way first? If your flash drive (or other USB plug) doesn't have a symbol to indicate which way is up, look for the side with a seam on the metal connector (it only has a line across one side) - that's the side that either faces down or to the left, depending on your port placement.
Update your Band-in-a-Box® 2024 for Windows® Today!
Update your Band-in-a-Box® 2024 for Windows for free with build 1111!
With this update, there's more control when saving images from the Print Preview window, we've added defaults to the MultiPicker for sorting and font size, updated printing options, updated RealTracks and other content, and addressed user-reported issues with the StylePicker, MIDI Soloists, key signature changes, and more!
A few excerpts:
"The Tracks view is possibly the single most powerful addition in 2024 and opens up a new way to edit and generate accompaniments. Combined with the new MultiPicker Library Window, it makes BIAB nearly perfect as an 'intelligent' composer/arranger program."
"MIDI SuperTracks partial generation showing six variations – each time the section is generated it can be instantly auditioned, re-generated or backed out to a previous generation – and you can do this with any track type. This is MAJOR! This takes musical experimentation and honing an arrangement to a new level, and faster than ever."
"Band in a Box continues to be an expansive musical tool-set for both novice and experienced musicians to experiment, compose, arrange and mix songs, as well as an extensive educational resource. It is huge, with hundreds of functions, more than any one person is likely to ever use. Yet, so is any DAW that I have used. BIAB can do some things that no DAW does, and this year BIAB has more DAW-like functions than ever."
Convenient Ways to Listen to Band-in-a-Box® Songs Created by Program Users!
The User Showcase Forum is an excellent place to share your Band-in-a-Box® songs and listen to songs other program users are creating!
There are other places you can listen to these songs too! Visit our User Showcase page to sort by genre, artist (forum name), song title, and date - each listing will direct you to the forum post for that song.
If you'd rather listen to these songs in one place, head to our Band-in-a-Box® Radio, where you'll have the option to select the genre playlist for your listening pleasure. This page has SoundCloud built in, so it won't redirect you. We've also added the link to the Artists SoundCloud page here, and a link to their forum post.
We hope you find some inspiration from this amazing collection of User Showcase Songs!
Our User Showcase Forum receives more than 50 posts per day, with people sharing their Band-in-a-Box songs and providing feedback for other songs posted.
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