[golive03]

I put in drum fills and vocal overdrive markers, but it says “No drum overdrive fills were detected!” and “No vocal overdrive markers were detected!”, so I was like “Fine! I guess I can do without them!”…but then I get this as soon as the Magma Compiler gets to work:

ERROR: Audio Compiler: Could not open ‘j:/program files/reaper (x64)/audio/stereo44.wav’ for read.

ERROR: Project Compiler: Unable to calculate song length due to Audio Compiler errors

Somebody please help with all of my above issues.

[samjjones]

“ERROR: Audio Compiler: Could not open ‘j:/program files/reaper (x64)/audio/stereo44.wav’ for read.”

Is that stereo44.wav file present in that location? Can you manually navigate to that location and access the file? Was the file in-use at compilation time?

I’m guessing the subsequent error was also caused by the above, since the full project can’t compile if a subset (the audio compile piece) can’t finish.

[Bansheeflyer]

I’d get the “could not open” problem each time I’d compile in Magma and couldn’t find the actual track so I usually just make my own mute track myself by muting everything in Reaper and exporting that. Once that is fixed the other error should go away.

[Ollie]

ERROR: Audio Compiler: Could not open ‘j:/program files/reaper (x64)/audio/stereo44.wav’ for read.

ERROR: Project Compiler: Unable to calculate song length due to Audio Compiler errors

In your magma project, go on the audio tab, you should have a red exclamation point near each missing audio file, indicating it can’t find the file. If that’s your backing track, search for it. If that’s one/all of the “mix” tracks right click on all the path boxes and choose ‘44.1 khz stereo silence’ for DRUM, BASS, GUITAR, KEYS, VOCALS and choose ‘blank dryvox’ or look for your recorded dryvoxes for your dry vocals tracks.

[Kemiroch]

I used to get this error, but I eventually figured it out.

 

Actually, there are two somewhat different cases where I would encounter this error:

 

If I change an audio file after I set the muted tracks, Magma will look for the muted tracks in the location of the just added file. Re-adding the muted tracks fixes this problem (they can be easily re-added simply by right-clicking the file box and selecting the proper track from the list). I think this happens if I change the output file location also.

 

I have also encountered this error when I had a mismatched audio file (for example, all the files were at 44khz except one which was 48) and I changed the incorrect file to be correct, Magma wouldn’t believe the problem was fixed until I closed it and reopened the project (save first).

 

Hope that helps.

[Author]

Posts