Just for my understanding. I removed the old version. Restarted foobar and installed the updated version.

[...]

What are all default names for custom fields you provide upon first-time installation?

Custom track peak:          replaygain_track_true_peak
Custom album peak:          replaygain_album_true_peak
Custom track gain           truepeak_scanner_track_gain
Custom album gain           truepeak_scanner_album_gain
Clipped samples in track:   truepeak_scanner_clipped_samples_track
Clipped samples in album:   truepeak_scanner_clipped_samples_album
Peak timestamp:             truepeak_scanner_peak_position
Track max LUFS-M:           truepeak_scanner_track_max_lufs_m
Album max LUFS-M:           truepeak_scanner_album_max_lufs_m
Track max LUFS-S:           truepeak_scanner_track_max_lufs_s
Album max LUFS-S:           truepeak_scanner_album_max_lufs_s
Track LUFS-I:               truepeak_scanner_track_lufs_i
Album LUFS-I:               truepeak_scanner_album_lufs_i

non-configurable fields:
LRA of track:               replaygain_track_range
LRA of album:               replaygain_album_range
DR of track:                dynamic range
DR of album:                album dynamic range

Quote from: Defender on 2024-05-18 11:28:20

2) How can I adjust offset other than entering a value in ms? In LS3 I can use my mousescrollwheel to adjust offset on the fly which is very convenient.

0.5.3.1020
 - Unified panel with desktop lyrics mouse shortcut operation:
    Ctrl + Scroll Wheel to increase/decrease the font
    Shift + Scroll Wheel to adjust the lyrics offset (it is recommended to adjust it after turning on the karaoke display mode)
    Ctrl + Alt + Scroll Wheel Previous/Next sentence

There is no solution to other problems for the time being, and the specific changelog can be found on github for details
https://github.com/ESLyric/release/releases/tag/0.5.3.1020

(I guess your value is correct and the oneliner does some truncating somewhere instead of rounding)

EDIT: If the first digit after the decimal point in your calculation is between 0 and (including) 3 results are the same, otherwise the oneliner version gives a 0.1 higher result.

Yes, using this string to display the Clip count in the playlist:

%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.

2) How can I adjust offset other than entering a value in ms? In LS3 I can use my mousescrollwheel to adjust offset on the fly which is very convenient.

Then try excel or any other tool for that (with similar expression)  since the TF heavily uses rounding and caching of decimal values to calculate things. Note there is no way to use float numbers on TF, so... it just process the decimals in additional steps.

$puts(cmt, --- CODE.ROUNDPREC ---)

$puts(round.value,$trim($get(round.value)))
$puts(round.precision,$trim($get(round.precision)))

$ifgreater($get(round.precision),9,
	$puts(round.precision,         9)
,
	$ifgreater($get(round.precision),0,
	,
		$if($stricmp($get(round.precision),0),
		,
			$puts(round.precision, 2)
		)
	)
)

$if($get(round.value),
	$puts(round.i,                 $strchr($get(round.value),.))

	$ifgreater($get(round.i),1,
		$puts(round.value,$get(round.value)0000000000)
	,	
		$ifequal($get(round.i),0,
			$puts(round.value,$get(round.value).0000000000)
		,
			$puts(round.value,0$get(round.value)0000000000)
		)
		$puts(round.i,             $strchr($get(round.value),.))
	)
	$puts(round.int,$add($cut($get(round.value),$sub($get(round.i),1)),0))
	$puts(round.fract,$substr($get(round.value),$add($get(round.i),1),$add($get(round.i),1,$get(round.precision))))
	$puts(round.round,$add(1$get(round.fract),5))

	$puts(round.res_int,$add($get(round.int), $if($stricmp($cut($get(round.round),1),1), 0, 1)))
	$puts(round.res_fract,$ifgreater($get(round.precision),0,.$substr($get(round.round), 2, $add(1,$get(round.precision))),))

	$puts(round.result,$get(round.res_int)$get(round.res_fract))
,
	$puts(round.result,)
)

Obviously the TF expression has rounding (all my DR,LUFS,PLR expression have rounding). No one should expect a basic TF expression in a totally limited language like foobar TF, which was never meant for math calcs, can output values with a lot of precision without using tons of lines of code. I mean, you should never use that as a "reference" for anything. (not saying the component may not be wrong too, but TF is wrong for sure).