Actually, I believe I said that already in an other post but Chinese car stereos, mostly those cheap ones on ebay have a tendency to support open source codecs. Even though mine didn't advertise that it did, it supports APE, FLAC, OGG and OPUS. If you happen to own one of those I would suggest you to do a test. While on the outside some of them may look identical the internals might differ and they may support more or less codecs than the ones that they advertise.
Um, it will be great to have a graph indicating quality (mean opinion scores MOS) of different codecs at least in range of 8-128 kbps. Not sure if it's feasible for bitrates higher than 128 kbps.
And create a wiki.hydrogenaudio page for that purpose.
funny you mention cars, as I did also type it in my original post before editing it out. Wouldn't that be great to have that support in cars. But I guess with streaming being "the future", then the digital files most people have is still mp3.I think the biggest thing right now is getting it supported in software and hardware so it can be used more widely. It seems to be the way forward.By the time Opus finally gets widely supported by car stereo manufacturers I'm in.
I'd like to see car manufacturers simply make the car stereo easily accessible to a variety of media devices; 3.5mm jack, usb connection, maybe allow CD playback still that supports lossy files such as mp3s and opus... hell, even data-DVD support to playback lossy files. The headphone jack and usb support would be easy and I've seen some cars with that in as standard; but not enough.
foobar2000 1.3.16 can't play/decode wav pcm with samplerate 2822400 Hz. It reports "Unsupported format or corrupted file". But it can play this file if file is compressed with wavpack.
XMPlay can play original wav without problem.
I read up somewhere that a properly designed DAC can accurately output an audio stream.
This discussion of DACs misses the most important technical points related portable music player enjoyment. The first two technical specs that relate to portable player enjoyment are voltage output and source impedance. Get these right and you can at least hear the !!@% thing, which I humbly submit are the most important aspects of a music player.
Think I'm kidding - imagine that you have been sent to a desert island with a Samsung S5, one of the most popular mainstream phones, with its minuscule ca. 400 mv peak output and a pair of highly inefficient 'phones. You have all the music and electric power on the island and you can't hear $#!^!
In many cases, one or both are not given by the vendor's blurb, and sometimes they are great, but the vendor is unwisely keeping his light under a bushel basket.
Other factors like storage capacity and format of add-on storage, music file formats supported and ease of use are probably next.
Then comes DAC quality which can be broken down into the two most important specs which are dynamic range and frequency response, but both of them are so cheap to surpass the reasonable requirements for, that they might even be safely ignored.
Also, relatively sophisticated features like the DIY ear tuning provided by a little piece of software for Android called Neutralizer can be very significant to your enjoyment of your portable music player which well may be a phone or a tablet.
Last post by Peter -
Good find, thanks for reporting.
Looks like these files got their last MPEG frames clobbered by tags; the tool actually to blame for this is either the encoder or a previously used tagger.
So, here's what happens-
Before removal of the tags, foobar2000 scans for the last apparent MP3 frame, finds a valid header but doesn't notice that the frame overlaps with the tags, and decodes it - though decoding produces nonsense as the payload is malformed. This also affects detection of MP3 stream duration.
After removal of the tags, foobar2000 rejects the last frame entirely as its signaled size exceeds the file size, hence shorter decoded duration.
You can recreate the same scenario by chopping the file using a hex editor, from the first "APETAGEX" up.
I'm fixing this to prevent future confusion, editing tags should never affect decoded or reported duration, and we should not read into bad data if it can be trivially detected.
Nothing got lost, the data that foobar2000 no longer tries to decode was bad already, editing tags with foobar2000 is safe.
I think the biggest thing right now is getting it supported in software and hardware so it can be used more widely. It seems to be the way forward.By the time Opus finally gets widely supported by car stereo manufacturers I'm in.
Though I may turn the tables on my own as soon as I finally upgrade my smart phone to one with external storage support, who knows.
Last post by nu774 -
Since then, are those "popclicks" still there with no delay option ?Actually, I'm routinely using it for encoding video soundtrack. Don't use it for music.
Easy to drive headphones are not all earbuds or IEMs either (a common perception mistake people make far too much)
What about the other way around? I would be surprised if I bought an IEM off the shelf and found out it was too hard to drive, but threads like these are for eliminating unpleasant surprises.
But too loud volumes could be an issue, I guess? If you hit the pain threshold at volume level 2 of 10 (or was it 11?) and destroy the IEM at 5, you have a bad combo.
Is compatibility vs "any reasonable portable headphone" any issue nowadays?
There's probably a few players that are designed for difficult to drive headphones but my opinion on those is that isn't as worth the money that could spent on other things that are much more worth it.
Easy to drive headphones are not all earbuds or IEMs either (a common perception mistake people make far too much), you can get some good full size headphones that are easy enough to drive.