It gets even more complicated: "The first men on the moon were the Americans. Who will be the first on Mars?"
Sure, but if you want to do as much correct automatically first to minimize manual patchwork, then converting the first men on the moon were the americans. who will be the first on mars? into The first men on the moon were the americans. Who will be the first on mars? would be an improvement. If you are German, you need a bit more work though.
(And can someone please tell the idiots at Discogs that Capitalizing Every Word In Every Language Is Damn Wrong?)
Yes, thanks. That's how I understood, in terms of the best quality, maintaining the full bit depth. (Right now, I have everything set to 16/44.1, I suppose Id need to understand the advantages and any disadvantages of going to 24 bit next!)
The only disadvantages of 24-bit output would be the negligible CPU load increase associated with shifting the sample data by 8 bits, plus 50% increase in bandwidth required to send the data to the DAC, which at 44.1 kHz sampling rate is no problem at all. Regarding the benefit: Consider a particular 16-bit sample of value ABCD (hex). Padded to 24-bit it becomes ABCD00. Now, if you reduce the volume by 24dB (4 bits), these samples become 0ABC and 0ABCD0 respectively. As you can see, the 16-bit sample lost 4 bits of resolution, while the 24-bit has retained the full resolution of the original signal.
Last post by oberon0470 -
I hate to keep bothering you but I'm having a small problem with File Integrity Verifier 1.22. If I run it on multiple single files it works great. It is much faster than the previous version. If I attempt to verify a chaptered file it slows down to a crawl. It takes about 3 minutes and 26 seconds to verify a seven hour mka file with 26 chapters. The same file verifies in about 15 seconds on a portable version 184.108.40.206 running v1.1.2 File Integrity Verifier. It pauses after each chapter getting longer & longer as it goes on. It does finish with everything verified correctly.