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
2
Polls / Re: Sound colors of codecs
Last post by Meowdori -
If i wanted to hear something in shitty, degraded quality for some weird reason i'd use a realtime processing software rather than purposefully storing low-quality files on my disk. What if i wanted to use the high quality original material later?
3
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by maikmerten -
My best guess right now is that there's some kind of memory corruption going on. Float is twice as big as short, so the encoder falling apart in various places (mostly when accessing lookup tables) might indicate that resampling is trampling over memory somewhere.

C be like that.

Lame is a completely different (and more readable, IMO) code base and I don't expect to find something there that applies to the Helix MP3 encoder.

It's theoretically possible to replace the resampler, but one needs to be careful about licensing. The Helix MP3 Encoder has a very exotic open-source license, which *is* recognized as Free Software license, but it makes it quite a bit more complicated to figure out what other code can be legally mixed in.
5
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.
6
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?)
9
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.
10
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?