Dear musician colleagues,
I have recently a problem with BiaB 2018. Under Windows 7 and also under Windows 10:
If I want to play a complete 5 minute song (realtime tracks only) with BiaB, my ROLAND UA-101 audio / MIDI interface will immediately produce a noise, the song will not play, BiaB crashes. A few days ago I did not have this problem with this song yet. I have not changed anything on my PC system since then.
I've been using BiaB for a few years now and have never had any issues or crashes with this program.
I post a small part of the error message. I have send this to PG MUSIC, too. Maybe here or there is a specialist among you who knows from the data, where the problem lies.
--------------
An exception error has occurred. You can continue to use the program, but should likely save your work and reboot program.
Access violation.
------------------------------------------------------------------------------
Exception log with detailed tech info. Generated on 19.02.2018 20:32:47.
You may send it to the application vendor, helping them to understand what had happened.
Application title:
Application file: C:\bb\bbw.exe
------------------------------------------------------------------------------
Exception class: EAccessViolation
Exception message: Access violation at address 1F822639 in module 'Rdaw1049.dll'. Read of address 00000108.
Exception address: 1F822639
------------------------------------------------------------------------------
Main thread ID = 6084
Exception thread ID = 6084
------------------------------------------------------------------------------
Exception stack
Stack list, generated 19.02.2018 20:32:45
(00001639){Rdaw1049.dll} [1F822639]
------------------------------------------------------------------------------
Call stack for main thread
Stack list, generated 19.02.2018 20:32:47
[770B0C72]{ntdll.dll } ZwGetContextThread
------------------------------------------------------------------------------
Mike, welcome to the forum.
I can't tell anything specific from this error report except to suggest that exception errors and access violations are often due to insufficient rights of the user account. The remedy is to Run BBW.EXE As Administrator. Let us know if you've tried that, or if you don't know how to do that.
The fact that it always worked before doesn't mean it isn't remedied by this; Windows changes frequently with updates, and BIAB has regular updates, too.
...... Windows changes frequently with updates ...
a song called 'Windows Trouble', and it's to be listed under blues in your default BIAB folder ... - Seriously, give us more information like what kind of hardware you use, f.i. USB can be the culprit; indeed try 'run as administrator'. Rdaw1049.dll is a roland drver, check for updates? . F
I noticed a few mentions on Google that the driver, Rdaw1049.dll, could be attacked by malware.
Just to be clear about "Run as administrator"...
This is different from logging into Windows as admin. To start BIAB using 'Run as administrator', right-click on the program and select 'Run as administrator'.
When I read your post, my first thought was that it could be a driver issue with your Roland. Like Fiddler suggests, I'd see if a more recent update is available.
Hi Mike,
Rdaw1049.dll is the driver for a Roland interface. Was the Roland device connected to your computer when you opened Band-in-a-Box? If it was, the you likely just need to reinstall its driver.
If it wasn't connected, either connect it before launching BIAB again, or delete the files "intrface.bbw" and "mysetup.dk" from the BB\Preferences folder. That will allow Band-in-a-Box to open without trying to access the device.
Please let us know if this doesn't solve your problem.
Thanks
Kent
PG Music
I noticed a few mentions on Google that the driver, Rdaw1049.dll, could be attacked by malware.
All malware scouts i use in windows 10 besides 360TS antivirus (be aware that it occasionally removes OK stuff too based on false positives, but you can restore them) is S&D Spybot, Malwarebytes free, and spywareblaster (it seems not to be updated a much compared to a year ago). Plus privacyfirewall, reccomendable. Tip: most antivirus packages include an upload tool for testing possible affected dll files.- F
Dear colleagues,
a greeting to all who have given me to my problem tips ...
I ran BiaB as an administrator and was able to easily play various songs from the bb directory. Then I loaded my self-created song, which is the problem. It's just a raw sketch of a new song. I would like to continue working on it, but as soon as the song is to be played, I try different Realtracks, which are known to be rendered before playing, immediately comes from the UA-101, the noise and BiaB the error message that I have already sent you in part. It seems only with this song! Should I send you the file? So it could be tried, if the file, my song-sketch, runs without problems.
My ROLAND UA-101 (audio / midi interface) with Windows 10 driver works well with CUBASE 9.5 PRO.
I have the same BiaB / Roland UA-101 problem on my other PC with Windows 7. I switched to Windows 10 and a new computer only a few days ago. I worked with the Windows 7 machine and BiaB for almost 8 years and never had a problem.
I've just received the tip from Kent - PG Music, I'll try it right now ---
Mike
Hello Kent,
Of course I can delete the two files, but I need the UA-101 audio / midi interface after all ...? As I may have already mentioned, BiaB works very well with the many sample songs of the program, but if I load my song file and it should be played, then the program crashes. It is strange that I worked and experimented with the song for at least two hours, tried real-time tracks and rendered a lot ... it always ran smoothly ... but eventually the crash .... maybe I should once a new BiaB-Fester open and re-enter the chords, load various real-time tracks ... then save under a different name .... maybe then the song / file is played without disturbances, but it is still strange ...
Deleting the two files as suggested by Kent only resets BIAB fully to default settings. Then you test BIAB, and finally connect the Roland and set your drivers. It's basically a way to make sure BIAB works fine without the Roland, as a means of isolating the problem.
Just to be clear about "Run as administrator"...
This is different from logging into Windows as admin. To start BIAB using 'Run as administrator', right-click on the program and select 'Run as administrator'.
When I read your post, my first thought was that it could be a driver issue with your Roland. Like Fiddler suggests, I'd see if a more recent update is available.
I have the latest Windows 10 driver for the audio midi interface UA-101 installed.
It can not be the driver of the UA-101, because I have the same problem recently with my Windows 7 computer and BiaB (now currently BiaB 2018 V.512), with which I have worked for almost 8 years without problems. There were never any problems with the UA-101 and BiaB.
It seems that only with my new song are these problems that I'm working on right now and that I'm not getting ready at the moment. BiaB's own song files are played without any problems. There are no driver problems, nothing.
Deleting the two files as suggested by Kent only resets BIAB fully to default settings. Then you test BIAB, and finally connect the Roland and set your drivers. It's basically a way to make sure BIAB works fine without the Roland, as a means of isolating the problem.
OK, I'll test it right now ... thank you
It seems that only with my new song are these problems that I'm working on right now and that I'm not getting ready at the moment. BiaB's own song files are played without any problems. There are no driver problems, nothing.
You could try export it as midi file, and then re-import, take notes of the RTs used first etc ... F
I deleted the two named files in the Preferences folder and started BiaB.
Basically nothing has changed:
BiaB owned/included songs are played without any problems. Of course, I could only see the song progress on the monitor because the UA-101 audio midi interface was disconnected from the computer.
Then I invited my "new" song, started, crash ...
Something must have got mixed up in the program, so that the error occurs again and again.
The whole thing with the connected UA-101 and the deleted files, I have not tried again, it is definitely not on the ROLAND device. It has to be in my "new" song file.
Now I can copy the two deleted files back to the Preferences folder, because it's all as usual, my "new" song will not play after the rendering of the realtracks, although a few days ago I'll experiment with it for at least two hours have ... The error, the problem is not the UA-101 driver, no malware, no virus ...
Whether it will be useful if I re-enter the song in a new BiaB project window, with all the chords, etc. ... maybe the problem is resolved ...?
Mike
Yes, this test is to narrow down the problem, which it looks like you have done. Corrupt song files are rare but they can occur. Try reconstructing the song in another song of a different name, and see.
Yes, this test is to narrow down the problem, which it looks like you have done. Corrupt song files are rare but they can occur. Try reconstructing the song in another song of a different name, and see.
Thanks Matt (and all the other colleagues),
For the first time I have this problem ...
So I'm going to re-enter the song .... tedious work ... but if it helps (hopefully)
If I have achieved something, however, I will contact you again. THANK YOU!
Mike
Mike,
Try using RealBand to open your Band-in-a-Box file. Once the file loads save the file under a new name but keep the same file suffix (SGU or MGU). You may find once the file is used and saved by another program the file works. Sometimes opening a file with a different program will have the side effect of repairing the file. RealBand can open files with both the SGU or MGU file suffix.
Sometimes the simplest solution is to 'Save As' and rename it, as this writes the song to a new location on the hard drive and can eliminate some hardware issues. Just a thought.
Sometimes the simplest solution is to 'Save As' and rename it, as this writes the song to a new location on the hard drive and can eliminate some hardware issues. Just a thought.
Meaning time for a 'checkdisk' with 'fix errors' ?
Sometimes the simplest solution is to 'Save As' and rename it, as this writes the song to a new location on the hard drive and can eliminate some hardware issues. Just a thought.
I do this every time I have a major change to my songs. I label them songtitle, songtitle-1, songtitle-2, etc. If you need HD space just delete those songtitles that lead to your finished piece of music.
Mike,
Try using RealBand to open your Band-in-a-Box file. Once the file loads save the file under a new name but keep the same file suffix (SGU or MGU). You may find once the file is used and saved by another program the file works. Sometimes opening a file with a different program will have the side effect of repairing the file. RealBand can open files with both the SGU or MGU file suffix.
Hi Jim,
it worked! Thank you for this tip! I then loaded the file with the new name in BiaB and waited trembling, whether after the process "Generate and Play" again the noise from the UA-101 can be heard with immediate BiaB crash - he did not come .... super, Great. So I have saved a lot of work (and time) with the new harmony and arrangement work.
Sometimes the simplest solution is to 'Save As' and rename it, as this writes the song to a new location on the hard drive and can eliminate some hardware issues. Just a thought.
Correctly! So it is .... thanks for the support.
Meaning time for a 'checkdisk' with 'fix errors' ?
I will make. My system is only a few days old, but a check will not hurt ...! Thank you!
I do this every time I have a major change to my songs. I label them songtitle, songtitle-1, songtitle-2, etc. If you need HD space just delete those songtitles that lead to your finished piece of music.
A good thing ... I will do in the future ... learn from the experience of others can never be wrong ...!
Mike, Glad that our advice helped and you were able to save all your effort.