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
12
General - (fb2k) / Re: Info for equalizer
Last post by Air KEN -
Flex DSP (foo_flex_dsp) v1.0
https://hydrogenaud.io/index.php/topic,124762.0.html
・File names and component names have been changed from "Dynamic DSP".

Using Title Formatting and DSP chain presets, you can switch effects for each Album and Track.
You can also use Equalizer by saving a "DSP chain preset" name such as "Equalizer-Pop".
Tagging is done by selecting the entire album.

Usage:
Japanese wiki
https://foobar2000.xrea.jp/?DSP+64bit#w099ed06

Dynamic DSP - Post 1 Usage
https://hydrogenaud.io/index.php/topic,96094.0.html

Red squares are active DSP chain presets.


・The Preview (active) mode will not automatically switch when the Flex DSP Window is open. You will need to close and reopen it.
14
Lossless / Other Codecs / Re: HALAC (High Availability Lossless Audio Compression)
Last post by Hakan Abbas -
Quote from: ktf on
Quote from: Hakan Abbas on
HALAC version 0.3.8 performs a more successful linear prediction process. [...]
Very impressive. I've ran a short variant of my comparison script (on 8 different tracks) and the results are attached.

Clearly, there is no codec that comes close to HALACs encoding speed. Moreover, this test is single-threaded only, and the way multithreading is implemented seems way more efficient than other codecs.
Thank you very much for the test and your valuable feedback. I am glad that you confirm my results.
Are there “Shakespeare Lectures” or “Armonia di Flauti” among the 8 tracks you used? Because I think these are actually mono. In the previous tests, the correlation between the channels seemed to confuse things. I was going to edit this but I forgot. I will address this in the next version.
15
3rd Party Plugins - (fb2k) / Re: foo_uie_webview
Last post by regor -
Quote from: mjm716 on
The starting point should not be, what we could recreate, but what we can newly create.
Doing the things I've already done with webview would be a nightmare or just impossible to get to work in JSP SMP, not least of all due to shit memory issues with the frameworks. @pqyt has the right idea there.
I don't see how any of that relates to my remarks. Obviously rendering HTML + JS is going to be easier for UI things since you are just working over +20 years of work from other people xd Who doubts that? That has nothing to do with the scope of the component, and if the idea is to manage a library (because foobar is a music player with a library), then you need something else, not just buil-in UI web frameworks and file paths management.

Also, people using JSP and SMP and previous components were just being lazy/selfish because everyone just created their own scripts without any kind of shared design. i.e. everyone has been repeating the same things over and over. JS frameworks doesn't work like that. Obviously it's a pain in the ass to create a chart in SMP vs web view, but you have to create a charts framework once. Then everybody can reuse that. There has not been evolution of SMP/JSP scripts because of that, just 2/3 devs creating their scripts until they got tired. There were no frameworks provided, everything had to be coded from scratch. I created my Timeline-SMP script which can be used to display arbitrary charts, library stats or a timeline with dates/artists... but anyone else can just reuse my statistics framework and create their own thing (for ex. a Spotify Wrapped alternative). It's there, with docs. No one has done it; why? Because other people just prefer to say "hey look, my component is better" and do similar things in their own component just for the sake of it. (that's pretty much the recap of the last 10 years of WSH/SMP/JSP & scripts development)

Finally obviously web view is not going to have memory issues if you are just rendering single art   ::)  I have said it many times, I can crash JSP, SMP or any JS based component as long as I add enough data. Whenever this component adds some kind of library management + tags support for handle lists, then it will be a problem if you use 32 bits and you have a library of 300K tracks. If you try to load into web View 10K covers at the same time, it will be the same. That has nothing to do with component design, data requires ram and you can not have infinite ram in 32 bits. (ex. 300K tracks x 18KB for a raw ChromaPrint fingerprint = 5 GB ram)

It seems some of you get offended if I say "simple UI things", but it is what it is. Right now. I'm not talking about the component, I'm talking about what people have been doing with it. If someone creates a script to replace biography/library tree, find similar tracks, create interactive charts by library stats, reproduce a youtube video by selected artists, etc., then it would be different. And "simple UI things" is not a derogatory name. Many things in Web view are pretty simple xd they are not in JSP/SMP. But they are just that, UI things. So I asked the dev to understand what will be the scope of the component to think about creating my own scripts here or not.
17
General - (fb2k) / Info for equalizer
Last post by UMBY71 -
Hello everyone, maybe an stupid question: is possible, save the equalizer settings for an album? Of course, then when you listen to the album, should the equalizer adapt and set up to the saved settings? If is possible how and what should I do? Thanks Umberto
18
FLAC / Re: FLAC-git Releases (Code Base v1.4.x)
Last post by rennie -
Quote from: ktf on
I keep hearing (from others in the past too) they'd like to see the number of the previous release somewhere, but never why, beyond "I'd like that" or "I don't want to look it up".

I do not have a better explanation! Sorry!

I'd like that and I don't want to look it up later on.  ;)

...and I think it would be useful to be able to see code base version immediately.

If there are really so many new unstable features in the master source I'd rather remove the word "reference" and add "(unstable)" instead.
20
FLAC / Re: FLAC-git Releases (Code Base v1.4.x)
Last post by ktf -
Quote from: rennie on
Commits that make it to the official master source code are usually intended to correct code errors.
No, they are not. I've been busy implementing a few new complex features (multithreaded encoding, decoding of chained Ogg FLAC) and I am still not done squashing bugs. So, these builds are NOT intended for general use.

Quote
Thus, I wouldn't hesitate to mention the code base in the IDs of builds to come.
But I do. The current state of the code doesn't yet feel release-worthy to me, so I really don't want people to think that it is.

Quote
Furthermore, it would be easier to understand, which code base version was used.
Please explain why.

Quote
Of course it's possible to look up the commit number and/or the its publication date, if the code base version doesn't show up in the file info[...]
Please do NOT create files that are not instantly disposable with these development builds, or accept that hic sunt dracones.

Quote
[...] but it I'd prefer to able to see it directly.
Please explain why.

Quote
And if your unsure about the stability you could call your builds "reference libFLAC 1.4.3 20241206 git-c786b1c (unstable)" for example.
I could, but I haven't seen a compelling reason why I should. I keep hearing (from others in the past too) they'd like to see the number of the previous release somewhere, but never why, beyond "I'd like that" or "I don't want to look it up".