lossyWAV 1.3.0 Development Thread
Reply #237 – 2011-01-18 21:35:14
...., but nothing > -2.5 (i.e. portable has been ABX'd). Nothing greater than -q 2.5, I believe.I'm not entirely sure of the purpose of lossyWAV going into the non-transparent territory < 300 kbps when transform codecs do such a good job there. But then it's interesting to see how far it can be pushed, I guess. To me, the further down the quality scale that the apparent transparency point exists, the better - no?With his restless efforts we can achieve the same quality level now at a bitrate which is not far beyond 300 kbps using for instance -q 0 -t -A (or a bit more defensive setting for the cautious one). Totally sprung - I just can't stop tweaking the code.... I think if use -t and quality is equal or greater than -q 5 it can consider to use --limit 16000 replace --limit 15159 in default because for most of people , 16k is safe in mental efforts in MP3 and doesn't increase too much bits if -t is stable , it can replace old -q setting in default I would rather leave the --altpreset system alone - you can always modify the default upper frequency limit for calculations in --altpreset by adding "-l 16000" on the command line. It should be restated that the frequency defined by --limit is for the calculation which finds the lowest part of the signal. It does not affect where the added noise due to rounding goes - that is defined by whether (or not) the user selects shaping (fixed shaped noise), adaptive shaping (behind the signal, sort of....) or does not select shaping at all (full spectrum noise). [edit] I forgot to add - there are users who have expressed unhappiness previously when the resultant bitrate at the lowest quality settings increased during development - my desire to drive the apparent transparency point down the quality scale is mainly prompted by the wishes of these users. [/edit]