Please be aware that much of the software linked to or mentioned on this forum is niche and therefore infrequently downloaded. Lots of anti-virus scanners and so-called malware detectors like to flag infrequently downloaded software as bad until it is either downloaded enough times, or its developer actually bothers with getting each individual release allow listed by every single AV vendor. You can do many people a great favor when encountering such a "problem" example by submitting them to your AV vendor for examination. For almost everything on this forum, it is a false positive.
Last post by j7n -
The 24-bit field in the header means that the DTS was originally created from this bit depth. As DTS is a lossy codec, the encoded waveform is always an approximation of the original signal, and usually decoded to 24 or 32 bits anyway. The higher range is effectively only used during the quietest sections.
You can choose the bit depth to use under "Converter setup" - "Choose output file format" - "Output bit depth". A 24-bit FLAC will be very large, about double the size.
The wrongly reported number of channels only happens if your DTS is encapsulated into a fake WAV or other format. You can strip the WAV header, use a .dts file extension, then the DTS will play in most programs than can play videos, but you can't use it to burn a CD easily, or verify with Cuetools.
Last post by Skie -
Thank you Rollin for your kind reply. I did "almost" the same thing ... that is, in the Processing section I didn't check "Enable decode postprocessing". After I did that, the results were as expected. One thing that makes me wonder (and something irritating) is that when I check the properties of the dts file (the original one) it shows 2ch, i.e. stereo, even though the spectrogram shows 6ch. It is normal or something can be done to show 6ch like in this FLAC after conversion.
I assumed there was an option to convert asian characters to a latin string in iOS because using the DS Audio app (https://apps.apple.com/us/app/ds-audio/id321495303), songs are sorted by pinyin and grouped into the resulting letters in the side nav correctly. For example, 王菲 is spelled in pinyin as WangFei which is then sorted under W and grouped in that bucket. I think it would require detecting and converting asian characters to latin script rather than a custom sort or character classification.
For iOS it seems like Core Foundation allows the conversion of asian unicode characters to pinyin. I am less familiar with android but I assume there is the equivalent
Last post by vinnie97 -
Wow, haven't been to HA in a while. Vorby is no longer king and Apple has brought their lossy counterpart to the forefront apparently. What about at 60 kbps? My tin ears (not a lot of classical in the collection either) don't mind that average bitrate with Vorbis.