weird ftp/mp3 issue
weird ftp/mp3 issue
i've noticed recently that a couple of mp3s i've uploaded to my ftp server (using Fetch 4.0) have turned out a little glitchy when i load them up off the web. playing the same mp3 on my itunes shows that the file is fine, but the uploaded version will have some sporadic digital pops. anyone have any ideas what's causing that? is it Fetch? i've used Fetch forever, but i'm open to a better ftp program for macs if that's the problem.
- apropos of nothing
- dead but not forgotten
- Posts: 2193
- Joined: Tue May 13, 2003 6:29 am
- Location: Minneapolis, MN
- Contact:
- sonicmook56
- steve albini likes it
- Posts: 357
- Joined: Tue Mar 09, 2004 3:05 pm
- Location: Echo Park
- Roman Sokal
- buyin' gear
- Posts: 531
- Joined: Thu May 15, 2003 10:29 pm
- Location: Hamilton, Ontario, Canada
- Contact:
- digitaldrummer
- cryogenically thawing
- Posts: 3525
- Joined: Wed Nov 23, 2005 9:51 pm
- Location: Austin, Texas
- Contact:
if you download the file and it is still the same (do a binary compare) then there something in the "streaming" effect when you play it off the server. that could be virus scanner, internet bandwidth, server bandwidth, the palyer's buffer settings, lots of stuff...
if you compare the files and they are not the same, then you have fallen into the trap many before you have as well. FTP and HTTP are unreliable protocols. yes, really. they do not incorporate any kind of checksum to make sure they got the whole file intact. for example, I once uploaded some WAV files to a CD duplicating house and when I got my CDs back, they had several minutes of silence at the end of the CD. during the transfer, something went wrong. their upload application did a http or ftp transfer of my files. the process opened a file on the target side of the correct size, then starting transferring blocks of data. at some point the transfer was interrupted but the app did not know. My files appeared to be the same size on both sides, so it all looked good. when we re-looked at the waveform there was clearly several minutes of "dead air" at the end of of the file.
anyway, the easist way to fix that kind of scenario is to zip or compress the file on the way up, then have the dupe house uncompress it--this will tell you right away if its good or not. Another way is to do a MD5 checksum on your original files, then compare them on the other side. Of course, if you are just blindly uploading to some ISP's web hosting site (like many of us), you can't always do these things. this is soemthing anybody that does transfers of audio files across the internet needs to be aware of.
Mike
if you compare the files and they are not the same, then you have fallen into the trap many before you have as well. FTP and HTTP are unreliable protocols. yes, really. they do not incorporate any kind of checksum to make sure they got the whole file intact. for example, I once uploaded some WAV files to a CD duplicating house and when I got my CDs back, they had several minutes of silence at the end of the CD. during the transfer, something went wrong. their upload application did a http or ftp transfer of my files. the process opened a file on the target side of the correct size, then starting transferring blocks of data. at some point the transfer was interrupted but the app did not know. My files appeared to be the same size on both sides, so it all looked good. when we re-looked at the waveform there was clearly several minutes of "dead air" at the end of of the file.
anyway, the easist way to fix that kind of scenario is to zip or compress the file on the way up, then have the dupe house uncompress it--this will tell you right away if its good or not. Another way is to do a MD5 checksum on your original files, then compare them on the other side. Of course, if you are just blindly uploading to some ISP's web hosting site (like many of us), you can't always do these things. this is soemthing anybody that does transfers of audio files across the internet needs to be aware of.
Mike
- sonicmook56
- steve albini likes it
- Posts: 357
- Joined: Tue Mar 09, 2004 3:05 pm
- Location: Echo Park
-
- gettin' sounds
- Posts: 126
- Joined: Mon Nov 08, 2004 9:38 am
- Location: Portland, OR
- Contact:
i have this problem when I bring an MP3 into Final Cut Pro that I streamed using the LAME encoder -- it sounds great everywhere, but in final cut there are some blips and blops, I wonder if it has to do with sampling rates.. they were in 41k and i think video is usually 48.. but i think FCP compensates for that.
dunno!
dunno!
this kind of thing used to happen to me way back in the day.
I would use this program to fix it after the fact: http://www108.pair.com/fma/uncook95.htm
Don't know if that program will work on the newer Windows operating systems or if it will actually solve your problem. But you never know...
Roy
I would use this program to fix it after the fact: http://www108.pair.com/fma/uncook95.htm
Don't know if that program will work on the newer Windows operating systems or if it will actually solve your problem. But you never know...
Roy
www.rarefiedrecording.com
"No matter how corrupt, greedy, and heartless our government, our corporations, our media,
and our religious and charitable institutions may become, the music will still be wonderful." -Kurt Vonnegut
"No matter how corrupt, greedy, and heartless our government, our corporations, our media,
and our religious and charitable institutions may become, the music will still be wonderful." -Kurt Vonnegut
Who is online
Users browsing this forum: No registered users and 427 guests