Topic: Iriver optical sampling question (was "Recomended build for optical ...")

[Chuck]

Perhaps you imported it into your editing program at the wrong sample rate? I have noticed this problem sometimes when working with CuBase.

Thanks - since that level meter was there with the option to adjust it I couldnt' figure out quite what was waht since it was obviously responding to the adjustments on the pre.

Next question (I posted this in ask the tapers, but it bears repeating here in an iRiver-specific thread too):  Okey dokes...

I ran a test last night - mics and pre are talking, there's a signal, batteries fresh etc.  However,   it came out like the freaking chipmunks on steroids - clearly running fast (it's pretty funny, actually) - and when I u'l'd it to the puter it was telling me it was 64k instead of 44.1 that was set on the Mic2496.  How did the sample rate get screwed up?    The iRiver told me it was "same as source" so I can't figure out any way of setting it specifically.   Also, I can't get it to repeat the fault - my concern, of course, is that if I don't know what caused it I don't know how to avoid it so any pointers on how to ensure this doesn't happen again warmly welcomed!  Thanks.

 

[divamum]

Tx for the further replies.

As for the file, playback was funky on the unit itself (before uploading) so I guess it was something at the iRiver end.

Ran it twice today: once going optical-in via the CS2496 at a rehearsal tonight - mostly satisfied except for a $*()@& ventilation system hum in the 40-60k range (next stop: learning about noise filters, I guess).  Also, there were a couple of digital "pops" in one place - jsut the once (am I right in thinking that's just a digital error? Any way of avoiding, or just one of those things that happens?)

Was less happy when I ran  the CMC8s straight into it earlier this afternoon to stealth my daughter's choir concert - it seems that the newer firmware makes a big difference in many ways, and it's like running a whole new machine.  Biggest problem is that the mics REALLY picked up the hdd noise, much worse than it has EVER been. Not sure why - they were too close, but when this has happened before it's been a faint background whirring - annoying, but not actually deafening; this time it was like a Boeing revving up right next to the microphones.  Weird. 

As I say, there is a steep learning curve going on here.... more after Tuesday when I'll be running it again for the performance!

[whatboutbob]

Was less happy when I ran  the CMC8s straight into it earlier this afternoon to stealth my daughter's choir concert - it seems that the newer firmware makes a big difference in many ways, and it's like running a whole new machine.  Biggest problem is that the mics REALLY picked up the hdd noise, much worse than it has EVER been. Not sure why - they were too close, but when this has happened before it's been a faint background whirring - annoying, but not actually deafening; this time it was like a Boeing revving up right next to the microphones.  Weird. 

Just for the record, divamum was accidentally recording using the internal mic.

[petur]

Was less happy when I ran  the CMC8s straight into it earlier this afternoon to stealth my daughter's choir concert - it seems that the newer firmware makes a big difference in many ways, and it's like running a whole new machine.  Biggest problem is that the mics REALLY picked up the hdd noise, much worse than it has EVER been. Not sure why - they were too close, but when this has happened before it's been a faint background whirring - annoying, but not actually deafening; this time it was like a Boeing revving up right next to the microphones.  Weird. 

Just for the record, divamum was accidentally recording using the internal mic.

Just for the record, I've changed the text from 'Mic' to 'Internal Mic'

But as something still is fishy with current builds (re recording) I'd hold off a bit with updating to the latest build

[cgrooves]

Just for the record, I've changed the text from 'Mic' to 'Internal Mic'

But as something still is fishy with current builds (re recording) I'd hold off a bit with updating to the latest build

+T
That should clear up a lot of confusion for people new to recording via iRiver.

[divamum]

Thanks Petur.

Update on the sampling issue that prompted this thread:    I figured out how it happened, cuz I reproduced it (I caught it this time, at least).  So, in case somebody else ever needs to know:

It appears to reset (wrongly) sampling rates if the optical cable is unplugged/plugged while the iRiver is switched on in standby and/or if you try to press "record" before you have plugged in the cable (it seems that if the source is selected as digital, the unit won't start recording UNTIL the cable is seated in position).  The soluution is a simple reboot, then plug in BEFORE going to record.

I'm using it with a Core mic2496, btw.

[petur]

Yes, samplerate is measured for real (*) the moment you start recording.
I can't remember exactly what happens if you're recording into a compressed format, it could be the encoder gets reconfigured (pre-rec data wiped).

(*) the value that is put in the header of the recorded file