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
21
General - (fb2k) / Re: -3dB gain
Last post by Case -
Since you also use ReplayGain you should use the preamp sliders in ReplayGain. That way the clip prevention knows about your gain reduction and can take it into account, and the signal only needs volume adjustment performed once. With Amplifier the signal would be scale twice, which would be less efficient.
22
Polls / Re: 2023 Lossless format poll
Last post by Kartoffelbrei -
Alac remains as the giant calculated middlefinger towards anyone trying to manage an audio library ... a solution to an apple-made problem: ignoring flac in the filesystem and not offering conversion to alac
25
General - (fb2k) / Re: Title formatting/syntax for proper bitdepth
Last post by Case -
Curious 80's tech. The Motorola chips used in there were actually based on 24 bit words. Wikipedia tells the Motorola has two special registers allowing them to operate together as one 48 bit register. And some accumulators being able to handle even 56 bit numbers. Those processors at least would have had no trouble keeping the signal as 24 bits at all times. Can't find word length of the special HDCD DSP, PMD-100. Its successor PMD200 seems to have been based on Motorola 56300, apparently just a newer model in the same 24-bit chip series.
If these decoders were always able to handle 24 bit numbers then I really don't see the point of truncating the output to 20 bits at all. Even if analog world performance can't exceed 120 dB SNR, there's no reason to truncate. At least these hardware devices allowed the 24 bit decoding too, no idea why WMP then did not.

Quote from: Porcus on
By the way, does that humpty-bump around 20 kHz at https://forums.stevehoffman.tv/threads/was-the-potential-of-hdcd-squandered.743909/page-2#post-18478289  relate to the flaws you have found?
No. I actually see that hump on all the HDCD test tracks I just ran through frequency analysis, whether decoded or not. Tiny hump but visible. Possibly from noise shaped dither?
The differences with HDCD decoders only affect parts of the tracks. Oldest foo_hdcd for example produced DC offset error in all parts it touched. Other than that the difference signal between "bit-perfect" WMP output is just faint noise without any spectral spikes.
26
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by Majestyk -
Quote from: oops on
Quote from: Majestyk on
I'm a little perplexed by this. I thought the Tuning option that had the check mark would be the only active one. These settings imply otherwise. Does it really matter what the non selected Tuning option is set to?
The implication that all the settings matter and apply is the correct interpretation. So, it definitely matters what the non-selected tuning option is set to. The "check mark", only means this is the one that will be affected by the mouse wheel and middle mouse button.

Got it, thanks.
28
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by oops -
Quote from: Majestyk on
I'm a little perplexed by this. I thought the Tuning option that had the check mark would be the only active one. These settings imply otherwise. Does it really matter what the non selected Tuning option is set to?
The implication that all the settings matter and apply is the correct interpretation. So, it definitely matters what the non-selected tuning option is set to. The "check mark", only means this is the one that will be affected by the mouse wheel and middle mouse button. The combination of all settings is what sets the behavior. The "Reset" option sets most of the non-layout settings back to their defaults. I tried using/making a custom bitmap, the square radio mark, to hint that this menu selection is selected for modification but still mutually exclusive with the others in the same popup menu.

There is a bit more logic that goes into this. Four specific examples might help illustrate some special behaviors:
  • If you select a skin that is not a BIN (i.e., ZIP from AIMP or LVU), then the Zero option is grayed out and disabled implying it is not used.
  • If you select one of the loudness modes (i.e., BS.1770 or R 128), then the Zero and Range options are grayed out and disabled.
  • The newly-added tuning parameter switching through the mouse wheel is aware of these special behaviors. It would not allow moving into a disabled tune setting. However, it does allow moving out.
  • Locking the tune, disables that popup menu freezing all of the settings at their current values.

I'll add some wording to the documentation to make this point and hopefully clear up confusion going forward.
29
Support - (fb2k) / Re: Fresh computer install, foobar refuses to scrobble with last.fm
Last post by Ravari77 -
That is the exact progression I followed when I attempted it last time. I went ahead and did it again, and for good measure, I logged out of my last.fm account. Nothing changed. I did not get the "Connect application > YES, ALLOW ACCESS", but I'm not sure if that would have made any difference.



For further reference, here is my list of connected applications: