I notice that there have been a number of posts with "Access Violation" errors in BIAB. This post is rather lengthy but I have written it so as to give others some "food for thought" if an "Access Violation" error arises. This post may or may not solve your particular situation but it might help. I have fully documented:

(a) how I produce this error;
(b) how I solve it.

If you simply want to get to the end result, you might like to skip to point #4, Summary.

NOTE: In the below, I have used a demo style. If you try to replicate this error out of curiosity, please make sure that you save the style's demo with a new name so that you don't overwrite the existing style.

Style: Burkes @ 210 bpm (a MIDI style)
Using demo file modified as below
  • Bass: #538 – Bass, Acoustic Pop Sw 190
  • Piano: MIDI
  • Drums: MIDI
  • Guitar: #374 – Guitar, Acoustic, Strumming Hank Sw 190
  • Strings: MIDI
  • Melody: as per demo file
  • Soloist: #818 – Guitar, Electric, Soloist Country Classic Swing Sw 190

1. How I get the error
  • Load song demo for Burkes.STY and return to the chord sheet window
  • Add Reatrack instruments (as above) to Bass and Guitar.
  • Mute Melody.
  • Use “Soloist” button to activate soloist.
  • Select Realtrack #818 and generate solo in “Middle chorus only”. (When I play the song now, it sounds fine.)
  • Save the song with some temporary, new name. (On my computer, a message pops up and tells me that the Soloist has been locked and that the Realtrack solo has been saved... etc. At this stage, if I unfreeze the Soloist and save the song again, the Soloist will freeze on saving. )
  • Save song with the frozen Soloist.
  • Exit BIAB.
  • Restart BIAB and open song.
  • When I try and generate the song, I get the error Access violation at address 00405F74 in module bbw.exe. Read of address 00000004 at 00405F74
  • Click OK.
  • Now when I try to generate the song, I get a pop-up message saying Playback generation is already in progress. Load another song if this message persists.
  • If the above does not cause the problem for you, try un-checking "Soloist" under the "Freeze" icon and then save.

NOTE: If I load another song with Realtracks in it at this stage, I get now get an Access Violation error. I can load a MIDI-only song and generate it ok.

2. A partial fix for the problem
  • Load a MIDI-only song, generate it and let it play for a few bars to check that it works. Exit BIAB.

This allows me to now load in a Realtrack files. However, the file with the saved frozen Soloist is still problematic.

3. How I get the problematic “frozen” song back
  • Start BIAB and load the problem song
  • Right-click on “Soloist” on the menu bar and “Erase” the Soloist track.
  • Save the song. At this stage, the song will still not generate for me
  • Exit BIAB and restart it (after saving the song with the Soloist data erased).
  • The song now plays for me.


4. Summary
  • Seems like my problem is caused by the Soloist's freezing when being saved and then reloaded after BIAB has been restarted.
  • Unfreezing the Soloist track, erasing all data from it, saving the song and restarting BIAB allows me to load the song again without incident.

FINAL NOTE: Mostly, I can get the problem to occur (around 90% of the time) but very occasionally I cannot. I have yet to discover why this is the case.

I'd be interested to know if others can produce this error or if it is mine alone! Hope this information helps.

Noel.

Last edited by Noel96; 01/03/10 05:42 AM.

MY SONGS...
Audiophile BIAB 2025