Edirol R1 issues

[gewwang]

I've been running the R1 off and on since April 30th. I thought it'd be a good idea to document the issues I've had and see if anyone else has any other issues.

The two issues I've had since my first show were
- 2 hr 12 min file limit when taping 24/44
- level meter only showing one level instead of two (not sure if this is a combination of the two channels or just one channel)

I had another issue on my last recording. There were 2 spots in the 2 hour show where there's exactly 2 seconds of overloaded digi-noise.

I also realized that there's no low battery indicator. Fortunately my batteries died between sets and I had stopped the last wav file after the previous set and started the next file during the break. So when the next set was starting I checked the R1 to make sure it was still recording and found the machine turned off. I was able to switch out the batteries and got the next set fine.

[sleepypedro]

-- the menu selection knob is affixed by a tiny little piece of tape, and it's fallen off during sets a couple of times now. really chintzy.

that said, i really like the device.  i haven't done a split signal test to compare the r1 to the modSBM, but to my ear it's an improvement.  not to mention the smaller footprint makes stealthing a complete breeze!

[gewwang]

I had another issue on my last recording. There were 2 spots in the 2 hour show where there's exactly 2 seconds of overloaded digi-noise.

This happened both Weds and now again last night. Here's a picture of the wavform. I'll be running the R1 and the modsbm>d100 until I figure out what the heck is going on.

[leegeddy]

I'll be running the R1 and the modsbm>d100 until I figure out what the heck is going on.

long live the DAT!!!!!!!!!!!!!!!! 

marc

[Craig T]

this is what we've been calling a "framing error" in PDA recording land.  this happened to me once and I was able to fix it without any audible errors.  lets see if I can find the fix over at pencomputingaudio yahoo group...

As it was explained to me by Gordon, this is a framing
error problem. I had this happen to me recording at
24/96 while stealthing New Jersey's favorite son two
weeks ago. I was in media change mode and I saw it
(the meters were peaked) making the SD card change
from the second to third card. It affected about the
last 20 minutes of the second card. The recording
right up to that point was perfect. It also affected
the gap file. The recording on the third card was
fine. I thought I was toast until Gordon told me about
a fix that a list member named Dan provided for Adobe
Audition users, which is the app I use. When I applied
it, everything went perfect and I can detect no
problems in the audio at all. Here are the steps if
you use Audition - the +2 byte offset is the setting
that worked for me on both files. I assume this can be
duplicated in Wavelab.


Open up the damaged file. Copy the damaged part of the
audio and paste
into a new file within Audition/Cool Edit. Make sure
that the bit
depth and sample rate are the same as the original
file. Save the
damaged
audio to a RAW .pcm but before saving, go to "Options"
within the File
Save dialog (near the bottom of the Save dialog) and
select "24 bit
Intel
PCM" with a byte offset of "0". Close the damaged
file. Now open up the
damaged .pcm, select the correct bit depth and sample
rate. It'll now
give
you the option to select the byte offset of the file.
Since we all know
that the byte "0" doesn't work, we only have "+1" and
"+2". One of
these
will work. I've found that taking a 10sec sample of
the damaged file
and
going through this process will let you know which
byte offset to use
in a
short amount of time. Once you know, then you can
process the big
file. When the damaged file opens up and looks normal,
then copy the
good
data and paste it into the original audio where the
damaged part is. I
usually cut out the damaged part of the original and
then paste in the
good. All you have to do next is cut out any bad parts
in the original
so
that the audio lines up correctly with the newly
pasted good
audio. Another little tidbit, so far I have found that
if you have to
use
the "+1" byte offset, you need to swap the channels
and when using the
"+2" byte offset, the channels appear to be fine. I've
only done a few
files so far and this seems to be the pattern.

[gewwang]

this is what we've been calling a "framing error" in PDA recording land.  this happened to me once and I was able to fix it without any audible errors.  lets see if I can find the fix over at pencomputingaudio yahoo group...

+T Craig. I just tried this and it did work however the sound is not good. Here's the before and after of the wavforms - 1 is before saving and 2 is after opening the .pcm raw file with +2 offset

[Craig T]

sorry to get your hopes up.  sure looks like the same "framing error" I experienced, but when I applied the offset, the waveform was normal.  that sucks if you can't fix it.   

[gewwang]

sorry to get your hopes up.  sure looks like the same "framing error" I experienced, but when I applied the offset, the waveform was normal.  that sucks if you can't fix it.   

Fortunately that clip was just stage announcements at the July 4th concert. I'll try again with another 2 sec clip of music.

[gewwang]

I ran the R1 the past two nights with a different 4GB CF (but same brand) and didn't get the "framing" error on Tuesday running for 2:30. I haven't checked last night's recording yet but it looks like the error might be isolated to my friend's card which got it twice in the two times I used it new out of the box.

[WiFiJeff]

I ran the R1 the past two nights with a different 4GB CF (but same brand) and didn't get the "framing" error on Tuesday running for 2:30. I haven't checked last night's recording yet but it looks like the error might be isolated to my friend's card which got it twice in the two times I used it new out of the box.

What brand was this?  I've had some Lexar issues in the FR-2, never a problem with Sandisk in the R1 or FR-2.

Jeff

[gewwang]

What brand was this?  I've had some Lexar issues in the FR-2, never a problem with Sandisk in the R1 or FR-2.

Jeff

It's the dane elec. I got this from a reputable retailer in the taping community and was told it was a rebranded toshiba.

http://www.dane-elec.fr/home/liblocal/DOCS/FichePdt%20Flash/FLASH%20UK/CompactFlashUK.pdf

[live2496]

this is what we've been calling a "framing error" in PDA recording land.  this happened to me once and I was able to fix it without any audible errors.  lets see if I can find the fix over at pencomputingaudio yahoo group...

+T Craig. I just tried this and it did work however the sound is not good. Here's the before and after of the wavforms - 1 is before saving and 2 is after opening the .pcm raw file with +2 offset

With 24-bit files, there are 6 bytes per stereo frame. So there are 6 possible offsets to try to reframe the data correctly.
One will be correct, one will be the audio with the channels switched L<->R . Two will be diginoise and two other offsets will likely be listenable but probably very low in level.

[mcq]

I run it on Energizer 2500mAh's, but I got some new batteries (exact same ones) and it records much longer on new batteries...

Hello! It's not easy to change my alkaline batteries in my R-1, they seem to be a little bit too long
I've even had one time a serious problem, as one of the two positive contacts of the R-1 (a kind of metallic wire almost shaped as an @) slipped of out of place as I was trying to insert a 2500mAh battery, and touched the printed circuit below... short-circuiting the battery! When I switched on the R-1, the LCD wrote "battery low" and then blanked off. The battery was hot as coal when I pulled it off...
Did someone encounter this kind of problem? What can I do to improve?
Thanks (and sorry for my bad English) 

[pfife]

mcg, welcome - I've never had that issue before, and it sounds like we are using the same batteries.... sounds like something with your unit specifically.  Sorry I can't be of more assistance.