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
Other Lossy Codecs / Re: TSAC: Very Low Bitrate Audio Compression
Last post by rc55 -
Quote from: neoOpus on
I had an idea, but I'm unsure if it's a viable solution to improve things further. What if we use a lossy codec with a proven track record to compress audio files, then compare the result with the original and extract the differences? We could then encode these differences using a codec like this to achieve a sort of lossless quality while reducing the required resource requirements and compression time associated with computationally heavy codecs like this one. I'm curious to know if this hybrid approach could lead to a versatile solution that offers the best of both worlds.

I don't think this would really benefit as ultimately you are creating a lossy file so the differencing / difference encoding pass doesn't make sense. I suppose stacking different technologies is a curious one, reminds me of SBR or switching between CELT/SILK in Opus depending on content.

Perhaps blending codecs would be an interesting idea - you could have 0-16khz covered by Opus or similar and anything above that covered by a trained NN model for less sensitive frequency ranges, much like how TSAC works. I'm not a domain expert on that though.
6
3rd Party Plugins - (fb2k) / Re: Library Tree Discussion
Last post by kachidaze -
I switched from Facets to Library Tree recently and found an issue with my hotkeys, namely I've had play/pause bound to the spacebar and it's prioritized over typing in Library Tree's search function meaning I can't use any spaces in my search. The default search bars in foobar2000 and Facets let me type spaces normally without affecting playback. Is there a solution I just haven't found or do I just have to deal with it? Or any chance this could be changed in an update?
7
Audio Hardware / Re: Continuously monitor Power Amp Input or Output to see if it is maxing out
Last post by fooball -
Whatever circuit you use, there can be an impact on the noise and THD figures.  A simple diode-and-capacitor (plus a resistor to gradually discharge the capacitor) peak voltage monitor arrangement will be stealing current from the load in a non-linear manner and needs to be buffered.

Typically, power amps with built-in clipping detectors (they light a LED just before the onset of clipping) compare the output to the speakers with a proportion of the output stage's voltage rails, because the main cause of clipping is when the amp runs out of voltage headroom.  The clipping circuit only cuts in when there is an imminent problem, so distortion hardly matters at that point.

It's not an easy thing to do as an add-on, you can get signal level meters sure, but how do you then calibrate what full scale should be?
8
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by mexx -
So far I have determined the DR range values ​​with Dynamic Range Meter 1.1.1. To do this, I previously used the Replay Gain Scanner with the setting from Picture1. Everything with version 1.6.17. The result was the replay scan data also Picture2. The entry in the tags was as seen in Picture3.

Then I installed the True Peak Scanner in f2k-version 1.6.17 and ran it over the same album. The old replay gain values ​​were previously removed. The result can be seen in Picture4.

It should be noted that neither the track peak value nor the album peak value match the previous determination.

I'm not an expert here. Maybe someone can explain to me whether this is normal and whether it is due to a different calculation of the values. The differences don't seem to be that big.

With a few exceptions, the DR values ​​correspond to the values ​​from the Dynamic Range Meter 1.1.1.

My settings in the True Peak Scanner can be seen in Picture5.

Sorry for my Google Translate, but I don't speak English.

THX
mexx
9
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by wojak -
Quote from: marc2k3 on
The presence of that array is obviously not enough. The file extension has to be checked against it. Full changes here...

https://github.com/jscript-panel/component/commit/f3132412ea73ee3786f92114e6c64e1f0b6a8e8e

The cache location really needs to be the same folder for all files otherwise it will break the menu options for clearing the cache. And the filenames are not meant for easy reading by people - they current use the fb2k $crc32 function to generate a numeric hash as part of the image filename. I really don't see the value of them outside the scope of this script.

The only reason for me to put them in folders with actual music is HDD space. I have two external 4TB (8TB) disks with music with quite a lot of free space on them. And I have 256GB C:/ drive with foobar, Windows and so on. So creating lots of those pictures or databases within foobar or profile or system folders will definitely consume the much needed space quite fast (I know the pictures are small but there would be very many of them). If not possible to distribute those files into different music folders maybe it would be possible just to change the location of the folder to another drive?
As for pictures (files) names I thought that each audio file gets its own number so I could start scanning the m2ts file, the picture file would be created, then scanning would be canceled (process killed) but the faulty picture file with proper name would still be there. Then I could scan the file outside of foobar or your component - just by ffmpeg. If it would end with success I would rename the new proper file to the name created earlier by your component and put it in place of the faulty one.
By your earlier reply I assume that there is no way to scan DSD? The only problematic files for me are m2ts (beacuse of their size and lack of memory) and SACD-iso (because of DSD?).