Topic: iRiver accidentally switched to 66.000k, recording sounds like chipmunks WTF!?

[mikesalvo]

subject says it all. In a drunken pre 3rd set stooper, must have hit the switch by accident and changed it. When I imported the file into Audacity, the band sounds like chimpmunks.

how can I fix this!?

[rhinowing]

stretch to 150% of the original length maybe

[mikesalvo]

im not really sure if this is the problem, because I recorded a show last night on what must have been the same settings, and its fine.   this is bizarre....

[jkbyram]

you powered it up before plugging in the optical cable. it needs the have the optical cable already plugged in and on when you power the iriver. i had that happen and was able to open the file in wavelab and then save it as 44.1 with no issues.

[Brian Skalinder]

This may help:  http://taperssection.com/index.php/topic,117279.0.html

[Gordon]

This may help:  http://taperssection.com/index.php/topic,117279.0.html

WaveLab

    * Open the file
    * In Edit | Audio Properties select desired sample rate value
    * File | Save As and confirm Wave (PCM) attributes are defined properly, mainly:  set Sample Rate to the same sample rate as the data and Bit Resolution to the same value as the original file.
    * Save the file to the desired filename

this works perfectly.  I did it a few years ago when my v3 was set to 88 (using a jb3).  and just a few weeks ago tony was here and had the same thing as you.  worked like a charm.

[mikesalvo]

ok, I dont have wavelab, and I cant do this using Audacity. I dont see a wavelab link in the software section of TS. Anyone? +beers to the replies so far.....taping+booze= the occasional pain in the ass!

[goatfarmer]

Actually, you can do it in Audacity. The same thing has happened to me before. Click on the down arrow in the title bar window that lists your file name next to your wave form. You'll see "Set Rate". Select that and choose 44100. G'luck.

-Doug

[atleast6characters]

{{{{{{healing vibes for your .wav, brah}}}}}}
 

[bugg100]

you powered it up before plugging in the optical cable. it needs the have the optical cable already plugged in and on when you power the iriver. i had that happen and was able to open the file in wavelab and then save it as 44.1 with no issues.

Kevin is right. A flaw with the iRiver is that you MUST let the optical lock onto a stable signal from the UA-5.  Boot the iRiver LAST after the optical locks on the UA-5.  this takes about 15-20 seconds after the ua-5 is powered up.....

The wav header is the only problem with your file.  Can you open a raw file in Audacity?  If so it will ask for what you think the file is before opening it...   44.1 or 48 depending on what your UA-5 was set for.

Just for fun, you can play back the file with the iRiver and correct pitch down with the joystick during playback. Your file is safe!

[SmokinJoe]

Mike, if you can't figure it out, PM me.  You can ftp it to my server, I'll fix it, and you can pull it back.

FYI... what I will do is remove the wav file header and re-add it using "sox" on linux.

[mikesalvo]

you powered it up before plugging in the optical cable. it needs the have the optical cable already plugged in and on when you power the iriver. i had that happen and was able to open the file in wavelab and then save it as 44.1 with no issues.

Kevin is right. A flaw with the iRiver is that you MUST let the optical lock onto a stable signal from the UA-5.  Boot the iRiver LAST after the optical locks on the UA-5.  this takes about 15-20 seconds after the ua-5 is powered up.....

The wav header is the only problem with your file.  Can you open a raw file in Audacity?  If so it will ask for what you think the file is before opening it...   44.1 or 48 depending on what your UA-5 was set for.

Just for fun, you can play back the file with the iRiver and correct pitch down with the joystick during playback. Your file is safe!

ya this is def. what happened. I remember it happenning to. The fix was so easy. right there in front of me the whole time. Much thanks to all for helpin me fix this easy-ass problem.

SmokinJoe, thanks for the offer! Coincidentally, it pretty much all Jim Tufts fault, as he was the one who put me in the "house list" at the bar. GO MAINE! 

[Chomps]

This has happened to me several time...Like someone said you powered up the iriver and the optical cable was not plugged in. Lesson learned but it is an easy fix.