This error is driving me nuts. I get it in about 50% of the songs I'm working on (I'm using Realband 2014 in Windows 8.1, 64 bit). The full message is: "Access violation at address 009421A2 in module 'realband.exe'. Read of address 57640000 at 009421A2." Mostly what I am doing is building bass and drum backing tracks with a combination of midi files and realtracks/drums. I usually get the error when I'm all done and saving/rendering a wav file.

I have read several posts concerning this issue in the forums and tried all the suggested fixes (run as administrator, reboot, etc.) and none worked. I could not find a post offering a solution that worked for them so thought I try a new thread.

I totally dissected one song removing each track one by one trying to source the error and even after deleting every single track in the song I still got the error when rendering a wav file. The only solution I have found is to throw everything out and start from scratch rebuilding the song... and that's no solution.

Any thoughts would be appreciated. One more observation, you may be able to recreate this error by deleting a few bars at the beginning of a song from from all of the tracks you have used. That's the only action that I know for sure creates this error on my system.

I'm about ready to move on to different software. Maybe I'll just use Realband to create some tracks to work with in Cakewalk.

You are closer to the final conclusion than you know...

I get all of my "access violations" in BIAB.

I've developed an entirely new lexicon of swear words.

I don't mind spending my time trying for a good creative solution but it's agonizing to spend all of your time just trying to nurse the program into giving you the result you want, the result it gave you last time. This program is just not ready for prime time. It looks like a toy and works like one too.

Wanna borrow some swear words? They're pretty good.

MME or ASIO? RB has been know to have difficulty with ASIO.

MME

nomoss,

When you say you tried using "run as administrator", did you set this by right-clicking on either Realband.exe, or the Realband shortcut, selecting "Properties" and then setting the administrator mode?

Regards,
Noel

I tried both. Either way I get the access violation error when deleting some bars at the front of the song.

As a thought - after playing around with tracks both audio and Midi, have you used Tracks > Consolidate Audio at any time?????.


Deleting or adding sections of audio into a Track can create a number of separate files which can cause a problem if the addresses of the separate files are disordered in any way. Consolidation brings all these separate files into one continuous file.

Thanks but no luck. I tried consolidating the audio on a simple backing track which has two realtracks and two midi tracks and then deleting the first two bars. There is no or midi data in the deleted bars but yet I got the same access violation error. Generally I'm not doing anything very fancy just maybe shortening the tracks, changing the endings or adding volume changes.

Do you have the latest update for Realband (Build 7)? If not, the link below will take you to the update page.

http://www.pgmusic.com/support.realband.htm

Regards,
Noel

That actually helped thanks! At least in the one instance I have been able to document which is described above. I guess this was an un-confessed coding error.

I take that back. I'm still having the same problem with build 7. GRRRR. I hate this f***ing program.

Had a song working perfectly sounding great, tried to add another chorus and now it's toast. Got to start all over again. This program is junk.

Another wasted four
hours.

I was able to replicate your issue by following your step by step actions.
Not 'good' behavior but a slight modification to your methods will likely result in joy.

Instead of using 'Delete', use 'Cut'.
I have never had an error when doing this.
Highlight what you want to remove.
Use Edit-Cut (instead of Delete)

*Make sure the selection in the resulting Pop Up is what you want; the Close Gap option gets rid of the space occupied by whatever you are cutting (closes it up), so it will cause the rest of the track to move to accommodate.

The Leave Gap option removes just the data and leaves the time span empty without affecting the rest of the track.

Know that when doing this the From-Thru settings can be used to refine your settings.

Thanks rharv, I'll keep it in mind going forward but I have generally cutting and pasting not just deleting. I redid and overwrote the song I was working on the other day so I can't go back and test it.

In new work I'm doing as much as I can in BB and only doing final track by track edits in RB taking only baby steps and going back to the working BB file when I get the dreaded access violation error.

Another thing to try; right after it happens, go to File- Open Backup

Most users don't remember that RB saves a backup of the current version when you save the file. So you may have a few good versions sitting on your system.

Kinda like Source Control for audio.
When you Save you are committing your changes as the current version, and RB appears to just save the song over the previous version.
In reality on most systems it makes a backup of the original, then saves the new version.

Can be a good tip to keep in mind to save work you think you lost.

I suspect there is something in your workflow that is causing this .. could even be a rogue plugin or some choice (like the Delete as opposed to Cut example).