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
92
3rd Party Plugins - (fb2k) / Re: Cover Utils - Database possibly corrupted
Last post by zK -
Well, I no longer have the original setup I used in 1.6.18 - I tend to only keep what works for me at the moment.

I use Windows 10 x64, but I do not migrate to the 64-bit version of foobar2000 exclusively due to the absence of the multiple grouping levels feature in the current development stage of Playlist View. With an insane and enormous amount of files to organize (I had a CD store), the SimPlaylist component is extremely essential in this regard.

But, returning to the subject in question, for my setup, the 32-bit version of the new incarnation of the player (v2) in my opinion represents the best of both worlds: that of the legacy world (v1 series) and that of the new world (v2 series), since in the current preview version 2.2 (32-bit) I can, at the same time, have access to all the old components that I like (especially SimPlaylist and its fundamental "multiple grouping levels"), as well as the all the excellent and merciful news brought by the new generation. Having kept the 32-bit version was and continues to be a blessing!

Well then. Eager to access the new features, I installed version 2.2 preview 32-bit OVER my stable version 1.6.18. From then on, my problems with the Cover Info component started.

I backed up this unsuccessful (portable) installation and proceeded with a new, entirely clean (portable) installation of the current 32-bit previw. Once this was done, I migrated - carefully and gradually - all the components that I had been using in version 1.6.18 - but I also migrated some files that I still had doubts about their need, the "config.sqlite" file being one of them.

It turned out that the problem persisted.

I did a new clean (portable) installation. I migrated everything again but, this time more attentive to the new structure originally created by the player, I stopped migrating some files that clearly belonged to version 1.6, as well as the aforementioned "config.sqlite" file.

The player and the "Cover Utils" component now behave brilliantly.

The only (and big) misfortune is that I'm having to reconfigure - one by one - all my personal settings with the player, which were lost along with the discarded "config.sqlite".

But the cost-benefit of this work is completely favorable and I don't dare make that a complaint. Quite the opposite: I only have reason to thank both those responsible for the player and the Cover Utils component, the emergence of which I can attest that I helped inspire here on the forum, since I was tired of using TagScanner and already had great admiration for the foobar2000.

For some technical reason that escapes my average understanding, all I can say, with absolute certainty, is that, by discarding the "config.sqlite" file created from the overwritten installation and keeping the original created by the clean installation, everything went smoothly normalized.

Thank you all very much, both for the player and the component.
95
MP3 / LAME fastest encoding(-q 9) gives better quality than the slowest encoding(-q 0)
Last post by Molledix -
I'm using the most recent version of LAME, LAME 64bits version 3.100, and while I was looking for the best quality settings I stumbled upon the -q flag on lame --longhelp:

Noise shaping & psycho acoustic algorithms:
    -q <arg>        <arg> = 0...9.  Default  -q 3
                    -q 0:  Highest quality, very slow
                    -q 9:  Poor quality, but fast
    -h              Same as -q 2.  
    -f              Same as -q 7.   Fast, ok quality

I tried exporting the same file using the same bitrate (a very low bitrate so I could notice the differences) and found out that the results are exactly the opposite of what they intended them to be, -q 9 gives the best quality and -q 0 gives the worst.

These are the commands I used:

lame -b32 --cbr -q 9 --gain -3 -m s --resample 44.1 --bitwidth 32 sample.wav qval9.mp3

lame -b32 --cbr -q 0 --gain -3 -m s --resample 44.1 --bitwidth 32 sample.wav qval0.mp3

And indeed -q 0 encoded very slow and -q 9 extremely fast but the results are better for -q 9.

The qval0 sounds a lot muddier, less detailed so much you can't even hear the snare drum and there's some ringing on the upper frequencies. qval9 sounds not that muddy, the melody is more detailed and the snare drum is audible here.

Is this a bug?
96
General Audio / Re: Cutoff frequencies of lossy codecs
Last post by pwygy06099 -
a higher cutoff frequency means more black space in the frequency area

What?

He means the almost always guaranteed huge emptiness in a spectrogram due to absolutely nothing anyone would listen to having high frequency data.
But it's kind of the reverse, the higher the cutoff, the less pure black. But that depends on your spectrogram's parameters. If you turn the sensitivity down all the blue/purple there would be black too.

And his frequency observations are certainly correct. For almost everyone 16k is a hard limit. Good luck even finding a little child who can hear 20k at _safe_ levels.

Unless we're getting into the realm of possible non-audio high frequency interactions, the typical cutoffs are indeed quite high.

I see he's talking ultra low bitrate which is not of interest to me personally, but I had similar thoughts in higher ranges. Why waste bits on imperceptible frequencies?
So "color" is probably a perceived benefit of more bits representing the target range.
97
General - (fb2k) / Re: Loudness contol for Foobar
Last post by silverprout -
I can. There isn't. If you tinker with volume a lot and think different frequencies need different adjustments based on the loudness you can always use the EQ to compensate. And if you find settings you like you can save presets from them.

I really need a fully automated volume control that applies Fletcher-Munson curves

Closest thing I can think of is to use something like the TDR Slick EQ M plugin that has an EL (Equal Loudness) mode, where it adjusts the EQ curve based on Fletcher Munson, but it doesn't do it automatically by loudness, you'd have to tweak the amount yourself.

https://docs.tokyodawn.net/slickeq-m-manual/#Meta_Filter_Type

Not a component/plugin, but some of the recent RME DACs have a very cool Loudness function where you can set the amount of bass and or treble boost or cut, and it will adjust these based on the output level you set, kinda like the old Loudness controls on hi-fis, but the 'Loudness' amount adapts to the actual volume level.

My comuter uses windows XP and modern DACs are not reconized (and the embeded realtek sound is great)

No such plugin. But there exist script for JScript Panel, that can automatically switch DSP presets depending on volume level - https://hydrogenaud.io/index.php/topic,119730.0.html

It seems to be a little complex for a average user, and we need some measured and calibrated speakers in order to adjust the parameters of the DSP (active XO) in order to avoid any clipping, a simple UI sould help a lot to reduce the complexity of the process.
99
General - (fb2k) / Re: Loudness contol for Foobar
Last post by darkflame23 -
Closest thing I can think of is to use something like the TDR Slick EQ M plugin that has an EL (Equal Loudness) mode, where it adjusts the EQ curve based on Fletcher Munson, but it doesn't do it automatically by loudness, you'd have to tweak the amount yourself.

https://docs.tokyodawn.net/slickeq-m-manual/#Meta_Filter_Type

Not a component/plugin, but some of the recent RME DACs have a very cool Loudness function where you can set the amount of bass and or treble boost or cut, and it will adjust these based on the output level you set, kinda like the old Loudness controls on hi-fis, but the 'Loudness' amount adapts to the actual volume level.