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.
Recent Posts
1
3rd Party Plugins - (fb2k) / Re: NEW ESLyric v0.5 - an alternative lyric show component
Last post by sveakul -
Quote from: Defender on
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:

Changes
    Fix the problem that layout modifications do not take effect in real time
    Repair the problem that the search window displays the wrong right-click menu
    Optimize some high DPI related experiences
    Optimize(?) Lyrics search result filtering
    Optimize the display of lyrics processing rules in the context menu.
    Optimize the experience of some settings in Advanced Settings UI
    Add the rule of removing the blank character at the beginning of a line in lyrics content.
2
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by regor -
Quote from: Defender on
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.

Doing all that every-time you have to operate with 1 float number is ridiculous (what about needing 10?)
5
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
Quote from: Case on
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.

Quote from: Case on
For documentation purposes here are the currently configured tag field names
So the general standardized tagnaming is COMPONENT_SCOPE_PROPERTY, which makes sense.
Only the tags for clipped samples use a different convention.
6
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by jaro1 -
Thanks for this overview.
I lack the relevant knowledge to look for the error in the right place, but the presence of those segfaults as defined probably also means that the error will not be in the resampling process itself, but "to the left or right of it" (as you described in the edit), e.g. also because the upsampling is working and transparent, maybe..? ..and i understand "corrupted stuttery audio" as something more fatal than just distortion of a sonically non-transparent resampler.  

Can code analysis in Lame be helpful here, how are these code "bindings" resolved there in case of downsampling activation?
Maintaining downsampling support seems to make sense only if this problem is fixed. If that won't happen, wouldn't changing the logic under which downsampling has to be used or by disabling downsampling support, be a workaround? But of course this could also have a negative consequence(s).

The article in the HA wikipedia on the Lame encoder, section "Resampling".. in the sense of the last sentence in this section I have a question.. If, after all, there was a bug in the code of the internal resampler, is it theoretically possible to perform a total replacement of internal resampler with e.g. a libretro resampler?
8
3rd Party Plugins - (fb2k) / Re: NEW ESLyric v0.5 - an alternative lyric show component
Last post by Defender -
Quote from: always.beta on
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
Sorry should have said I already use ESlyrics 0.5.4.1028.  And I guess you don't want me to downgrade.

Thank you. Adjusting timings works fine with CTRL+ALT+ScrollWheel and SHIFT+ScrollWheel.
CTRL-ScrollWheel I already found since it is the same in some of the other panels/scripts I use.

As a suggestion, maybe an idea to have access to a kind of help page accessible on rightclick in the that sums up these special mouse commands?

The changelog on your page looks to be Chinese, which I cannot read. Do I oversee something?

I'll patiently await updates for this excellent tool regarding my other requests.

Thx
9
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by darkflame23 -
Quote from: Case on
Quote from: darkflame23 on
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.
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.
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.

Thank you!
10
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Case -
Quote from: Defender on
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?
Removing a component in foobar2000 doesn't touch configuration.

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

But for documentation purposes here are the currently configured tag field names:
Code: [Select]
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