91
Polls / Re: Sound colors of codecs
Last post by Klymins -Edit: Here's a comparison of 88kbps WAV and 16kbps MP3: https://drive.google.com/drive/folders/1P45-_G0UyhJP82YqjRUWz7ZIidt7En6F?usp=drive_link ( EndoLoop by nosoapradio.us )
The changelog on your page looks to be Chinese, which I cannot read. Do I oversee something?The developer is Chinese. Just copy/paste the log into DeepL; for example the log for 0.5.4.1028 looks like this:
I don't know what you mean. Of course you can work in TF with floats, calculations and proper rounding with a selectable number of digits behind the dot. You just have to shift the value to a much larger integer value to work with. Since I decided I don't ever want more than 9 digits after the dot in the result that means the original float (eg text consisting of only digits and only one dot somewhere) has to be enlarged inside the routine by adding 10x 0 to work with.That's exactly my point: "TF doesn't work with floats in a natural way without 40 lines of code", not sure what's your point showing exactly what I said xd We already know it "can be done" and anyway you are using integers in the end.
You can reset any setting in advanced preferences by right clicking it and select 'Reset'. And you can reset multiple settings at once by selecting an upper branch to right click and select 'Reset branch'.Good to know. Thx.
For documentation purposes here are the currently configured tag field namesSo the general standardized tagnaming is COMPONENT_SCOPE_PROPERTY, which makes sense.
It's easy for you to verify that foo_truepeak is correct. ReplayGain result = (-18) - (loudness), so loudness = (-18) - (RG). The values stored in tags are rounded to two decimals, but the component internally calculates it directly from floating point result.Silly me. No voodoo involved.
There is no solution to other problems for the time being, and the specific changelog can be found on github for detailsSorry should have said I already use ESlyrics 0.5.4.1028. And I guess you don't want me to downgrade.
https://github.com/ESLyric/release/releases/tag/0.5.3.1020
Yes, using this string to display the Clip count in the playlist:Thanks, there seems to have been a bug ever since I added the option to save the clip info. Originally the clipping info was just displayed on the status dialog but someone wanted an ability to save it to tags, so there's now an option.
%truepeak_scanner_clipped_samples_track%
And this King Tubby CD is showing dBTP overs of up to +2.45dB on one track, but the Clip count is zero for every track.
I seem to have managed to code it in a way that when save option is enabled the counter values are stored even when nothing was scanned. You see zeroes because you didn't use the "and positions" context menu entry to scan for clipping. I'll fix for the next version.