Skip to main content


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
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by brichanfiana -
I can't imagine what I could have changed between those versions that would cause a different usage of the sample rate. The sample rate is taken from the audio chunk as supplied by fb2k, over and over again; I assume post-processing.
Before the first audio chunk arrives 44100Hz is assumed.
pic 1: This image shows the same song in with foobar 2000 2.1.2 preview 0219 and the PGGB-RT plug-in in the same state.

The source is 384KHz, so the range up to 192KHz and up to the upper Spectrum analyzer limit setting of 96KHz is well displayed, but I thought the previous did not display above 48KHz (up to 96KHz) (see previous See Pic 2 in post).
I have had similar symptoms since Beta1, but had repeatedly reverted back to, which is why I was late in reporting it.

pic 2 PGGB-RT file details dialogue
Unfortunately, the file information in PGGB-RT seems to bring the 24/96 Original Flac information.
If it is taken from Audio Chunk, it will be displayed in the same way as Spectrum in v0.7.0.0, regardless of the PGGB-RT information.
Furthermore, v0.7.1.0 only showed up to around 22KHz when playing 16/44KHz FLAC resampled to 32/352.8KHz on the PGGB-RT.

It would be best if I could read the source code directly and report back, but I am also a developer and I am traumatised to read and write source code because I am mentally beaten.

Sorry to add another report on v0.7.1.0 rc-2, but I have set the colour of the Spectrum Bar to Foobar 2000 Dark Mode, but after saving, I quit Foobar 2000 once, and after that, when I start Foobar 2000, the colour of the Spectrum Bar is displayed as Prism 1. The colour of the Spectrum Bar is displayed as Prism 1.
The colour of the Spectrum Bar is set to Prism 1, but in Configure it is set to Foobar 2000 Dark Mode, so as soon as the Bar Colour is selected, it reverts to the original colour.
However, when the Foobar 2000 is restarted again, the colour is Prism 1.

Config Reset has also been tried, but the same symptoms occur.
CD Hardware/Software / Re: Optical drive enclosure with IDE interface?
Last post by polemon -
Well, IDE/ATAPI drives use SCSI commands and replies, so there is no analog data being transmitted. But to my knowledge, there exist SCSI and ATA imaging devices, mostly used for data preservation and forensics.
I'm not sure how much abstraction regular (windows, etc.) drivers provide. Sending raw SCSI / ATA commands and collecting the information directly might be an approach for better data collection.

I'm mainly speaking from a position of convenience, it might be easier to simply attach a device to the optical drive, image everything using raw SCSI / ATA commands, create an image internally and either save that to an SD card or some sort of internal memory which can be then accessed through USB for instance. I hope my explanation make sense...
The resulting image can then be archived and interpreted at will, without the need to re-read the original optical data (or hard disk data, for that matter).
I know that the forensic hardware I'm talking about is able to check for read errors, so they do have at least some way to access lower-level data of the storage device in question, other than just streaming binary data from the medium. The forensic software for some of them is able to provide graphs displaying that data, etc.
These forensic devices are really slow, reading a 200GB mechanical PATA drive takes hours.

However, let's be clear here, a 700MB (or 74min red book CD) is kinda small in this day and age. Even if imaging a medium like that takes two hours, people won't really care as this only has to be done once.

When it comes to anything later, like DVDs and Blu-Ray discs, I'm not sure, I've never used Blu-Rays, and I'm not sure how the controller talks to DVD drives (I mean, all I know, is it uses SATA, but I don't know the way data is requested and interpreted).

Tempting: , cross fingers and hope for the best - and be prepared to throw it away and thrift and old computer to use when you need it.
I used a bunch of these over the years, and when it comes to optical drives, they're hella flaky. The only drive that worked reliably with one of these, was a laptop CD-RW/DVD combo drive that normally goes into an older Fujitsu (?) laptop. The drive attaches over SATA internally, and that's what the little adapter was able to interface with. When it comes to IDE/ATAPI optical drives, I had no luck whatsoever. I tried with like 20 drives from different manufacturers over the past 15 or so years, none of them worked correctly. Problems were on one hand the adapter itself, but also the drivers, being kinda confused about what is connected there over USB. They do work surprisingly good with regular hard drives, though. Even the cheapest ones I had and still have, worked perfectly fine interfacing with 2.5" PATA hard drives, etc.

As a side note, the best luck I had with "external" optical drives, was a drive meant for installation into 1U servers (so technically it was an internal drive!). It was a "slim" device, similar to laptop drives, the weird thing though, was that internally didn't attach over SATA, but USB. It didn't use a regular USB cable, but one of those things that go into internal USB connector headers (see attached pic). In case you're wondering about the "weird looking USB connector", that thing is called "USB key A" and it can be directly converted to USB-C with a purely passive adapter. So, in other words, that was a USB-C drive. It required external power, but it was by far the best optical drive I've used. It read literally anything (anything up to DVDs) without any fuss at all. Too bad it didn't survive me moving house five years ago...

I know Op is looking for an enclosure for his IDE/ATAPI drive, but perhaps looking for a decent USB-drive like that is also a viable option - be it USB-C or one of the earlier connectors?
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by Cannonaire -
I've got a weird issue going on now.
In my 32 bit Portable install, I am running the latest version of Columns UI and the Album List Panel. I decided to uninstall the Dynamic Fields plugin as I no longer need it. After doing so, the Album List Panel refuses to populate until I make it hidden then unhide it in layout. Very weird, and I can find no fix for this, so I just chocked it up to years of cruft and jank in my 32 bit install. I had a backup of my folder and that still works correctly, but the bug persists if I try to remove dynamic fields.

This is where it gets weird!

Since I was finally ready to move to 64 bit, and with that kind of jank going on in my 32 bit install, I decided now's the time. I spent all day starting from scratch with a fresh install of 64-bit foobar2000 portable, and I meticulously copied every important setting I had in 32 bit by hand. I did import my Columns UI layout though. Since it's 64 bit, the dynamic fields plugin doesn't even work with it so that was never an issue. I made sure every component was updated except I still had an older version of Columns UI Album List Panel as the only thing left to update. As soon as I update to the latest version, the panel refuses to populate again. I'm at a loss now. I could leave it on the older version, but that isn't a great solution.

I tried removing the panel entirely and putting it back, same problem. Seems to just break if I update it. It just won't populate with any information until I hide it and unhide it or do something to it in Layout. Any advice?

I'm on 1.0.0 of foo_uie_albumlist and even moving to 2.0.0 breaks it.
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by marc2k3 -

Not worthy of a changelog entry but the crappy transparency effect for CUI toolbars is once again available when added as panels. Even with my supposed removal of it, flickering can still happen so it might as well stay. All flickering can be avoided by using standard panels in proper splitters - not PSS.

edit: I didn't mean to say transparency in CUI toolbars is crappy - it's essential. Adding toolbars as panels to use with PSS sucks. :P
General - (fb2k) / Re: Loudness Range (LRA) measuring in Foobar
Last post by Defender -
Fyi I have integrated the EBUR 128 Scanner from ffmpeg into foobar in the tags automation tool (see Playlist Tools at my sig).
i.e. LRA can be calculated and added directly to a tag within foobar, not requiring anymore musicBee or its plugin.
ffmpeg executable is a requisite, obviously.

The cmd line required in the process to output to JSON is this one, in case anyone cares (*):
Code: [Select]
"%FFMPEGPATH%" -i "%TRACK%" -af loudnorm=dual_mono=true:print_format=json -nostats -f null -  2>&1 | > "%JSONOUTPUT%" FINDSTR /BIR "{ .*\" }"

Works fine on my side, although it requires aprox. 8 secs per track in my PC. Will be available on the next release.

(*) It took me some time to figure how to redirect the output of FINDSTR to a file, since the redirection does not work at the end of the pipe. Hate cmd...

Hi, I just stumbled on this post. It's a rather old post and I tried to find a more recent post, but every search I ever do over here returns comes up empty.

I used your code to implement PLR Album and PLR track  with optional colorschemes. I do have some tiny and one bigger questions.

1) What are the DR values you use to apply the colorscheme for DR.
2) Is the PLR precision of 1 decimal (which is not rounded but cut off) relevant in your opinion.
3) Am I correct to assume that LRA would supersede the necessity of displaying PLR and DR.

4) The idea of being able to calculate LRA yourself looks really good. Searched your reference to your Playlist tools but I was not able to find how to use it. I do have ffprobe and ffmpeg installed. I'd like the idea of either an extra option on a rightclick to scan the track or tracks selected (like replaygain or dynamic range meter) which would publish results in the tags or something that would work from the track(s) properties screen (via Tools?). Is something like that possible?
FLAC / Re: More multithreading
Last post by Wombat -
I have pushed some changes to the multithreading code. It is too soon to say for sure, but it seems to fix some of the problems.

While the changes could impact performance, in my own tests it doesn't seem measurable. If anyone wants to double-check, the last two compiles here are probably usable for that.

Not sure about the problems but for many 16/44.1 and several 24/96 files i didn't find any.
The recent git when i compile it as the one before gives ~191x speed for -j20 -8ep with 16/44.1 against former ~192x speed on my 5900x.
No speed concerns for sure.
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by Majestyk -
Maybe I'm doing something wrong (I haven't been using this long) but my style color is always reset when I reboot fb2k. For example if Bar Spectrum is set to Fire, when I reboot it's set to Prism 1.

Although if I go back to Styles after a reboot, and click on Bar Spectrum, it will say Fire and give me the Fire colors. It just won't give me those colors unless I manually click on Styles/Bar Spectrum after a reboot.