And Dzamburu, there is no such thing as Vorbis 2.
If there will be 2 samples. Very bad quality 1 point and other even worse 0.5 point but min. mark is 1.So the mark scale 0-100 will be more appropriate.
When a person ranks a sample as 73, he should be able to explain why he didn't rank it 72 or 74 instead.
OK, just so the discussion is not needlessly simplified by lack of suitable software, I just put support for custom rating scales into ABC/HR for Java: Binaries, Sources
Any chance you could add an option for incrementing 2000 to the calculated offsets? Currently, you have to calculate the offsets and then go through each sample and manually type in the offset.
Thanks. Do I have to enter the additional offset before calculating the offsets, after, or doesn't it even matter?
Small update: Microsoft is discussing my request internally and someone will be back in contact with me soon.
QuoteI agree with you, range 0-100 is silly.It is the range standardized in ITU for the ITU-R BS.1534 recommendation - testing of audio signals with large impairment, such as codecs at 48 kbps.
I agree with you, range 0-100 is silly.