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: Quite OK Audio (QOA)... anyone ?
Last post by Case -
Librempeg code. (I got couple of clicks when converting >2 hour OST 48kHz music to .QOA dunno is it bug because of my changes or because of original algorithm)
I encoded a test audio album with librempeg and had very nasty beeps and squeks in the first track at around time mark 2:45. I verified the same track with the reference qoaconv encoder and it didn't produce any glitching.
3
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by Tropoje -
Album list panel 2.0.2

After restarting the PC, the settings under General -> Views are lost

Before the reboot
X
X

After the restart
X
X

What is interesting is that after closing foobar (red cross X) and start the program again, everything is ok

Windows 11 Pro latest build
foobar2000 v2.1.5 x64
Foobar installed in Windows

6
3rd Party Plugins - (fb2k) / Re: foo_upnp
Last post by evangelion_air -
As Windows 11 only has an x64 version, I believe x86 will soon be eliminated (Realize that the linux distributions x86 repository is also optional).
It is a pity that this plugin (foo_upnp) does not have an x64 version and there may be no more updates.
I still haven't found a way to use foorbar(ios version) to play PC music library directly, unless you use the 32-bit version of foobar on your PC and install this plugin.
9
General - (fb2k) / Re: ReFacets
Last post by Case -
It looks to me like your crash log doesn't show any ReFacets activity in the call stack but it's filled with foo_mpv. Are you certain it's not foo_mpv crashing?
10
3rd Party Plugins - (fb2k) / Re: External Tags
Last post by Case -
That command seems to compare the timestamp returned by the metadata handle to the timestamp returned by the file format's decoder instance. At the moment I'm not certain why I made it this way but I'm sure it worked correctly at least at the time of writing.

I'll need to find my motivation to re-engineer this component. I'm sure I can make it smarter and its code simpler with all the new interfaces Peter has added.