Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: --qlp-coeff-precision-search Question (Read 2824 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

--qlp-coeff-precision-search Question

I thought "--qlp-coeff-precision-search" was only suppose to search for a greater compression possibility.
I encoded a file using "flac -8 --verify(since all -v seems to do is show version info) ---exhaustive-model-search" and I got a file that was 11,572k.
That is down from 11,706k when using only "flac -8 --verify".
So why is it when I use "flac -8 --verify --exhaustive-model-search --qlp-coeff-precision-search" I end up with a file that is 11,601k?
Why does "--qlp-coeff-precision-search" make the file bigger and how should I know when to use this feature (that is suppose to make the files smaller from what I read) considering what just happened?

Are there any possible instances where "--exhaustive-model-search" could cause files to be larger than without this command?

--qlp-coeff-precision-search Question

Reply #1
something is wierd since '-8' include '--exhaustive-model-search'.

the encoder has to do some estimations in a few places.  the small size difference you are seeing is a result of that.  using anything beyond -8 is usually not worthwhile.

Josh

--qlp-coeff-precision-search Question

Reply #2
So what is the point of "--qlp-coeff-precision-search" if you sometimes might get larger files?
It would seem a more useful feature if the "--qlp-coeff-precision-search" output file size was auto compared to the non "--qlp-coeff-precision-search" output file size to see which one was really smaller.
That would mean that 2 estimates would have to be done but its what you would have to manually anyway in order to find out which would really be the smallest file.

--qlp-coeff-precision-search Question

Reply #3
it tends to work better on higher sample resolutions other than 16bps.

Josh