MR-8 File Error 0D

  • Thread starter Thread starter mrx
  • Start date Start date
M

mrx

New member
Just got that last night - I was able to cut the offending bar and it went away (it was after the song), but wonder if anyone has determined an exact cause. I know I've seen it mentioned.
 
Yes it happened to me but I did the same thing you did. I think clifchamb had to wipe his whole song because it came up about 14 seconds into the song or something like that....it's a mystery to me beacuse it hasn't happened to me since. I will say that when it happened to me, I was listening to the song when I tried to copy it. I haven't done that since either.
 
In my case I had created a new song on the PC and copied everything onto the MR-8. The first track I dubbed ran a bit longer than the track from the computer, so maybe length had something to do with it, too. I wrote to Fostex for an explanation (and asked if there is an OS upgrade on the horizon. I'll let you know what they say.)
 
Just heard from Fostex support on this - sounds like they are swamped and are trying to track this down. I got it again - in both cases it was about a bar after the end of a WAV I imported from the computer, so it must have to do with the WAV not matching the .ADL file. If the lengths are off, the MR-8 seems to get lost. At least they're working on it!
 
bdbdbuck said:
Yes it happened to me but I did the same thing you did. I think clifchamb had to wipe his whole song because it came up about 14 seconds into the song or something like that....it's a mystery to me beacuse it hasn't happened to me since. I will say that when it happened to me, I was listening to the song when I tried to copy it. I haven't done that since either.
Click to expand...

Are you guys referring to the infamous "incorrect parameter" message I sometimes still get when I copy a stereo wave file from the mR-8 to the PC? FOstex got back to me and said they have never heard of the problem and to erase and recreate the stereo wav file (which I already did like 80 times that day and got the same message duh). I wrote back telling them to take a look at the Official Fostex discussion board to see that I wasn't the only person who has experienced this. Again this bug seems to be rando and I can easily work around it now.


clif
 
Clif,

This is a different error - it's happened on two different songs, both during playback or recording, when it hits a specific point in the song. It looks like if you edit a WAV on a PC and the length changes, the MR-8 gets confiused at the end. In both cases I started tunes with hand-edited .adl files, so I'm sure that's the cause.
 
You must log in or register to reply here.
Back
Top