Topic: Edirol R-09 bad file

[hobbes4444]

Hey now, I don't want to appear too lazy    but I just cannot get this file straightened out and I really want to get these 2 sets out there.  This is the first show that Ms Vega has done with her daughter singing background on a couple of tunes. 

So I want to grovel for some help.  If some kind soul who has fixed files with these header and offset issues could please help out I would be extremely grateful!  I can send the original and somewhat fixed file (replaced the header with audiohack and have a recognizable file, but shows up as white noise) in addition to discs, etc; whatever you want!  I know there have been guides posted here, but after many many hours of following the advice trying to get this file sorted out, I just can't get it right and I can't take it anymore!  So please please please. . .

[Do.com]

I actually had something similar happen last night.  My recorder froze up at 51 minutes into a show   The only way to get the thing to do anything was to open the battery door and take them out to reboot the device.  So now I have an incomplete source as well as a file that won't open in editors.  I'm not impressed....

I think I found a much easier way to do this, not sure if it will work for you guys but it did for me.

1) Open the WAV file that is giving you trouble in CDWave. 
2) It will ask you if you want to adjust the size of the header.  Click YES. 
3) Then it will say it reports that the file header has a size of zero and do you want to continue.  Click OK.
4) Make a track somewhere before the band starts, only save the second track, let it discard the first track.
5) The new file you created will now open properly in any editing program.

Like I said, this worked for me, and maybe not for you but I thought it would be worth trying.

Clint

[hobbes4444]

I actually had something similar happen last night.  My recorder froze up at 51 minutes into a show   The only way to get the thing to do anything was to open the battery door and take them out to reboot the device.  So now I have an incomplete source as well as a file that won't open in editors.  I'm not impressed....

I think I found a much easier way to do this, not sure if it will work for you guys but it did for me.

1) Open the WAV file that is giving you trouble in CDWave. 
2) It will ask you if you want to adjust the size of the header.  Click YES. 
3) Then it will say it reports that the file header has a size of zero and do you want to continue.  Click OK.
4) Make a track somewhere before the band starts, only save the second track, let it discard the first track.
5) The new file you created will now open properly in any editing program.

Like I said, this worked for me, and maybe not for you but I thought it would be worth trying.

Clint

Well I did try some of the other suggestions similar to this one.  I didn't try creating a new track.  But when this file opened up in cdwav it was white noise.

Were you using a 4 Gb card by chance? 

[Do.com]

Yep - 4 gig Transwhatever - same one everyone else has.

[china_rider]

The cheap way to do it...

Create a one byte file with an ascii null (byte value 00).

Use the dos copy command to join that one byte file and your pcm data. something like copy /b file1+file2 newfile.
(I'm not sure on the syntax, but something like that).

Import that into your application. This will shift all of the framing by one byte.

Reiterate as necessary.

P.S. The Samplitude SE version may support the import feature. For 49 euro it is a good deal. But I have not used the SE version, so I am not certain of whether it has the import w/offset feature. Likely it does as this is a basic program function.

Just thought I would put in my .02 that this quick and dirty way worked for me...  T+ for the quick and dirty solution... Just how I like it. :-}

Here is the command I used......

Code: [Select]

copy /B d.bin + CR09_0005.wav test1.wavd.bin = 1 byte file containing '00'
CR09_0005.wav = backup copy of the fubared wav file directly from the 09
test1.wav = resulting .wav file that plays properly. :-}

Thanks again,
Dana

[hobbes4444]

The cheap way to do it...

Create a one byte file with an ascii null (byte value 00).


Import that into your application. This will shift all of the framing by one byte.

Just thought I would put in my .02 that this quick and dirty way worked for me...  T+ for the quick and dirty solution... Just how I like it. :-}

Here is the command I used......

Code: [Select]

copy /B d.bin + CR09_0005.wav test1.wavd.bin = 1 byte file containing '00'
CR09_0005.wav = backup copy of the fubared wav file directly from the 09
test1.wav = resulting .wav file that plays properly. :-}

Thanks again,
Dana

This is great info.  Thanks!!  Could you also post how you created the d.bin one byte file for us computer illiterates! 

Thanks again to all of the experts here for creative solutions to this problem.  Maybe the problem will go away if we ever get 4gig support. . .

[china_rider]

In ultraedit select a new file.  Type in any character.  Hit Ctrl-h to goto hex mode.  You will see one set of double digit numbers.  Change to 00 and save.  I only had to run the copy command once.  However, if your offset is more than one you will have to run it more than once.

[JD]

Not sure if this will help anyone here or not.

Last night I taped a show on my R-09 that came out slightly larger than 2Gb. As others here have experienced I was not able to replay the file in the R-09. I was able to copy it to my PC. It would play in Winamp but Soundforge and my other wave editing programs would not open it because of a codex problem?

CDwave would open it and I was able to chop it to smaller chunks but still was unable to open them in the wave editors. My guess is there was a problem in the header info? Flac frontend would not accept these files either.

What I ended up doing was converting the two files to FLAC via CDWave and then opening them back to Wave files.
The size of both files changed by about 8 bits, and are now able to be opened in Soundforge.

I am not sure what really happened or if this was the right way to go about this, but it worked.

Now, off to upgrade the firmware in the R-09.

Oh yeah, if you have the opportunity to catch a Big Bad Voodoo Daddy show, by all means do it. Great time, great performance!

[gmm6797]

Do we have 110% confirmation that the new firmware is perfectly seamless?