Skip to main content
Recent Posts
General - (fb2k) / Re: Newbie questions about Volume, and Column centering
Last post by PleasantSounds -
Yes, thanks.  That's how I understood, in terms of the best quality, maintaining the full bit depth.  (Right now, I have everything set to 16/44.1, I suppose Id need to understand the advantages and any disadvantages of going to 24 bit next!)
The only disadvantages of 24-bit output would be the negligible CPU load increase associated with shifting the sample data by 8 bits, plus 50% increase in bandwidth required to send the data to the DAC, which at 44.1 kHz sampling rate is no problem at all.
Regarding the benefit:
Consider a particular 16-bit sample of value ABCD (hex). Padded to 24-bit it becomes ABCD00.
Now, if you reduce the volume by 24dB (4 bits), these samples become 0ABC and 0ABCD0 respectively.
As you can see, the 16-bit sample lost 4 bits of resolution, while the 24-bit has retained the full resolution of the original signal.
Support - (fb2k) / File Integrity Verifier 1.22 Really Slow on Multi Chapter Files
Last post by oberon0470 -
I hate to keep bothering you but I'm having a small problem with File Integrity Verifier 1.22. If I run it on multiple single files it works great. It is much faster than the previous version. If I attempt to verify a chaptered file it slows down to a crawl. It takes about 3 minutes and 26 seconds to verify a seven hour mka file with 26 chapters. The same file verifies in about 15 seconds on a portable version running v1.1.2 File Integrity Verifier. It pauses after each chapter getting longer & longer as it goes on. It does finish with everything verified correctly.
General - (fb2k) / Re: foobar2000 for mac
Last post by sled -
Hi Peter,

I'm glad to read that a search function and album art are in the works. Thanks.

The new updates, volume and output switcher, work great on my mac. However, I can't find the UPnP function.


General - (fb2k) / Re: Newbie questions about Volume, and Column centering
Last post by The_Mule -
You are doing it the right way also from the sound quality perspective: Windows gets the full resolution signal, which then is attenuated as needed. Lowering the resolution happens when the volume is lower, so that's  harder to detect.

If you reduced volume in FB, you would also reduce the bit depth of your sound and then send it to Windows for max output. In practice on a basic laptop it may make no difference, but in extreme cases it may sound less than perfect.

Setting the bit depth of your sound in both FB and WIndows to 24 bit makes this issue quite academic, as you would need to mute the signal by over 90dB before the resolution drops below 16 bit (which is what you get from the CD).

Yes, thanks.  That's how I understood, in terms of the best quality, maintaining the full bit depth.  (Right now, I have everything set to 16/44.1, I suppose Id need to understand the advantages and any disadvantages of going to 24 bit next!)

b) Had to get on an old PC with an actual CD drive to see what you meant. :P The 'File menu > Open audio CD...' dialog cannot be changed, but I think you probably mean the playlist. You can simply make a custom column.

File menu > Preferences > Display > Default User Interface > Playlist View > under 'Custom Columns' click Add New - enter a name and pattern, for example -

Code: [Select]
Name: Track #
Pattern: [%discnumber%.][%tracknumber%]
Alignment: Center

(The use of title formatting controls what / how you want information displayed. For more, go Help menu > Title Formatting Help).

Back in the playlist, add the new column by right-clicking column headers > Columns > Track #.

Cheers ;)
Great!  Yes, in the playlist.  I kept trying to change the formatting of the current column.  I need to make a new one.  Cool, thanks!
Lossless / Other Codecs / Re: 24 bit WMA Lossless decoding broken in Windows 10 1809
Last post by enzo -
Got it!

Inserting these lines when configuring the output media type fixes the decoding:
Code: [Select]
      hr = ImediaType_DecodeTo_comPtr->SetUINT32(MF_MT_AUDIO_BITS_PER_SAMPLE, bits32);
      if (FAILED(hr)) break;
      hr = ImediaType_DecodeTo_comPtr->SetUINT32(MF_MT_AUDIO_PREFER_WAVEFORMATEX, TRUE);
      if (FAILED(hr)) break;
So it looks like I was just lucky using MFInitMediaTypeFromWaveFormatEx. If I had done it another way, I would have run into the same issue and probably never found a way to successfully decode the files.

Documentation for MF_MT_AUDIO_PREFER_WAVEFORMATEX says "If the attribute is TRUE, the function converts the audio media type to a WAVEFORMATEX structure whenever possible, instead of converting it to a WAVEFORMATEXTENSIBLE structure.".

Looks like not setting this flag for the output media type might trigger a bug with some format descriptor conversion inside the Media Foundation or WMA decoder engine...
General - (fb2k) / Re: Request: Titleformat $caps3()
Last post by Daeron -
Have you tried something like this?
Code: [Select]
Put the first line in front, then replace all occurences of %title% in your script with the second line. Then you only have to edit one instance instead of all.

Have not tested if it actually works with masstagger, so your mileage may vary. Also obviously this is just a slight optimization of a process you probably already don't like.
General - (fb2k) / Re: Request: Titleformat $caps3()
Last post by davideleo -
It is more complicated.
Sentence case: "Blah! Blah blah"

It gets even more complicated: "The first men on the moon were the Americans. Who will be the first on Mars?"

Personally, rather than a new titleformatting function, I'd rather have one more option in the masstagger component to mimic functions, something like "FORMAT values from input dialog...".
For example, I have a masstagger script to stylize english titles according to musicbrainz rules. I wanted to use it for both track and album titles, so I had to make an exact copy of it and replace all %title% occurrences with %album% and if I wanted to use it for any other field I'd have to make a third copy (and remember to keep track of eventual edits for all three of them). Maybe there could be a special notation to replace the field indicator with the one received from an input dialog box, triggered by the command to run the script.
General - (fb2k) / Re: Android app awful
Last post by chihwahli -

Hello support and other users,

Replaygain on windows Foobar2000 is very easy to use, but on android, as of writing at 21 march 2019, i cannot do the same as in Windows version. In windows version I just say :

- per track replaygain

and all files are normalized per file and it is shown how much dB it is lowered. Then I just apply and the replaygain tag is updated.
But on android, i cannot scan and normalize volume to a specific amount. Not all files are recorded at the same volume.

A work around, which is not very handy, is apply replaygain with windows foobar2K, then I can play the files in Android version. But this is not efficient.

So , how can I do this in Android Foobar2000?
SimplePortal 1.0.0 RC1 © 2008-2019