summaryrefslogtreecommitdiff
path: root/doc/man
diff options
context:
space:
mode:
authorRemco Bloemen <Remco.Bloemen@gmail.com>2009-09-28 22:29:16 +0100
committerRemco Bloemen <Remco.Bloemen@gmail.com>2009-09-28 22:29:16 +0100
commit62a2bebae1e21a1c40e81d396d046af2db79eddb (patch)
tree2483444180f1308906e39ad78cf9049172984317 /doc/man
parent21f1b993013b54f3909d2fa497fd6a9a9e147190 (diff)
downloadxine-lib-62a2bebae1e21a1c40e81d396d046af2db79eddb.tar.gz
xine-lib-62a2bebae1e21a1c40e81d396d046af2db79eddb.tar.bz2
Incorrect int-to-float conversion in the JACK output plugin
Using bitmeter, I found that xine's jack output suffers from the problem mentioned at the bottom of bitmeter's home page. "Although JACK itself works entirely with IEEE floating point values the conversion to and from analog audio uses integers, as do popular audio storage technologies like DAT and Red Book CDs. For correct operation JACK software which uses such integers should use the same conversion ratios as JACK itself. e.g. 16-bit samples should be divided by exactly 32768. A common mistake is to choose the value 32767 instead. You can't hear this, or see it with ordinary meters, but the bitmeter shows a clear signature for audio processed in this way. The 8th bit of the mantissa (counting the rightmost as the 0th) is orange, indicating that an unusually high percentage of samples have this bit set." (from http://users.ecs.soton.ac.uk/njl98r/code/audio/bitmeter/ via Google cache)
Diffstat (limited to 'doc/man')
0 files changed, 0 insertions, 0 deletions