mp3 encoding can introduce artefacts into the music. These artefacts are not restricted to any particular part of the frequency spectrum. In general, said artefacts will be less apparent the higher the bitrate used to generate the compression. I can definitely hear the effects of this compression on mp3 files generated at 128Kbps or lower, and quite often at higher settings than this. It's quite easy to test yourselves. Any mp3 converter should allow you to set the bitrate and generate multiple bitrate representations of the same data.
I upload 192Kbps files to my free kiwi6 account. I use this bitrate in order to maximise the amount of downloads I can get from this free account without crossing the threshold into the paid account category. This bitrate is fine for most purposes, but I have found that these files can be quite tiring to listen to on my HiFi for long periods.
I upload 320Kbps mp3 files to SoundCloud. These files generally sound very good on my home system, but I have noticed rare occasions where strange effects become apparent after encoding. These effects are repeatable when using the same codec. Anybody downloading one of my SoundCloud files will get the 320Kbps version. Note that the streaming SoundCloud player produces a 128Kbps representation of your uploaded files (whatever the format. It is often possible to hear things in the streaming SoundCloud player which are not present in the uploaded file. These effects are most easily audible in (but are not limited to) the high and low frequency spectrum bands. Another worry which I have concerns the conversion of mp3 files to mp3 files. If you think about it, it's quite obvious. mp3 is a "lossy" compression, so generating a 320Kbps mp3 from a wav file will result in data loss of some kind. Generating a 128Kbps mp3 file directly from a wav file will NOT produce the same results as generating a 128Kbps mp3 file from a 320Kbps mp3 file which was originally spawned by the same wav file, as data loss will occur twice during the process.
This is why Bandcamp (whose streaming player is also 128Kbps, I believe) allows you to select wav or flac (a lossless compressed format) as a downloadable format so that the audio can be enjoyed in its original glory.
I upload 192Kbps files to my free kiwi6 account. I use this bitrate in order to maximise the amount of downloads I can get from this free account without crossing the threshold into the paid account category. This bitrate is fine for most purposes, but I have found that these files can be quite tiring to listen to on my HiFi for long periods.
I upload 320Kbps mp3 files to SoundCloud. These files generally sound very good on my home system, but I have noticed rare occasions where strange effects become apparent after encoding. These effects are repeatable when using the same codec. Anybody downloading one of my SoundCloud files will get the 320Kbps version. Note that the streaming SoundCloud player produces a 128Kbps representation of your uploaded files (whatever the format. It is often possible to hear things in the streaming SoundCloud player which are not present in the uploaded file. These effects are most easily audible in (but are not limited to) the high and low frequency spectrum bands. Another worry which I have concerns the conversion of mp3 files to mp3 files. If you think about it, it's quite obvious. mp3 is a "lossy" compression, so generating a 320Kbps mp3 from a wav file will result in data loss of some kind. Generating a 128Kbps mp3 file directly from a wav file will NOT produce the same results as generating a 128Kbps mp3 file from a 320Kbps mp3 file which was originally spawned by the same wav file, as data loss will occur twice during the process.
This is why Bandcamp (whose streaming player is also 128Kbps, I believe) allows you to select wav or flac (a lossless compressed format) as a downloadable format so that the audio can be enjoyed in its original glory.
Comment