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
1
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Defender -
but may i know how can I display or read Dynamic Range and True Peak Scanner values ?
just because i like to use properties alt+enter , but i there is nothing in the information about these values
i know think even mp3tag can show them
I assume you are talking about tags?  The scan results you choose can be written to tags automatically by selecting the appropriate choice in Preferences/Advanced/DR Meter and ../True Peak Scanner/Tag Writing.  Alternatively, they can be written on demand after a manual scan viewing from the results dialog.

The values from the tags can be displayed in your Foobar track list in their own columns (if you have the screen real estate!) using Custom Columns with the right regex expression--some of the regex gurus here have already posted those up one of the components' threads here.  Or by manually viewing the tag(s) in Foobar's tag editor.
Hi
i use  DarkOne4Mod v1 theme , so i can not add values just because i don't know how to do
about the foobar tag editor , i think you are talking about properties , i can read only in the metadata tab and column Ui Main
thanks
Assuming you use the vanilla version of DarkOne4 v1:
1) ELP. You have two free fields that you can define in ELP (col2 and col3). Enable one of the two fields, put [%dynamic range%] in the accompanying txt field. I guess you can figure out how to also make use of the other field.
2) NGP. Go to Preferences\Display\Colums UI\Playlist view and add/configure an extra field for [%dynamic range%].
3) Replace the panel Item Properties to a JS3 panel and load it with Properties + Other Info from samples. It will show all available tags for an audiofile.

I made some screenshots after changing my skin layout (basically DO4v1 as well) as much as I still can to vanilla mode.

Happy modding
3
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Defender -
"Write log" button writing a single log is neither a bug nor a limitation - it writes a log of the results allowing you to manually alter the save location and the name. If you want to save one log per directory enable the automatic log writing option in preferences.
Hi Case
I see ,could be a cool feature , think about to select 10 albums , scan dr meter and save each log per directory
the point  is about
Quote
If you want to save one log per directory enable the automatic log writing option in preferences.
have to enabled or disabled and can change the folder mod date
would be cool a button that can act to save on each folder
just an idea or a feedback
thanks Case
Different thread, same answer:
https://hydrogenaud.io/index.php/topic,125719.msg1044649.html#msg1044649
4
General - (fb2k) / Re: Foobar2000 v2.2 preview upsampling Thank you!!
Last post by Gabriel Schwartz -
I am running Foobar2000 on an old Lenovo laptop with an i5-6200U processor and 16g of RAM.  It was able to upsample all 2-channel file types to DSD256 (16/44.1 thru 24/192 and DSD64) using the 32bit version.   When I upgraded to the 64 bit version (v2.1.5), I had a terrible time getting upsampling to DSD to work. I finally read somewhere on one of the threads that changing the Output/buffer length to between 100-150ms would work and it did...sort of.  It was still unstable and often froze between tracks.  I'm far from a computer expert but it didn't make sense to me that I was having issues when my CPU utilization rarely went above 40% and memory utilization was always around 20% regardless of the native rate of the input file that I was attempting to upsample and if I did ANYTHING on the desktop, play would immediately quit.

I loaded the v2.2 preview, recently, and am VERY HAPPY to report that it works flawlessly. I now have to set Output/buffer length to higher level  (which is what I needed to do in the 32 bit version especially when upsampling DSD64-->DSD256).  The proc utilization now makes sense to me.  Play is stable and as the input file rates increases, the proc. util increments to a higher plateau.

THANK YOU SO MUCH, Peter, and all who contribute to this terrific application for all of your hard work!!


You do know that upsamling DSD is done by converting it to PCM first.
Why would you want to do that?
5
General - (fb2k) / Foobar2000 v2.2 preview upsampling Thank you!!
Last post by Kurt7 -
I am running Foobar2000 on an old Lenovo laptop with an i5-6200U processor and 16g of RAM.  It was able to upsample all 2-channel file types to DSD256 (16/44.1 thru 24/192 and DSD64) using the 32bit version.   When I upgraded to the 64 bit version (v2.1.5), I had a terrible time getting upsampling to DSD to work. I finally read somewhere on one of the threads that changing the Output/buffer length to between 100-150ms would work and it did...sort of.  It was still unstable and often froze between tracks.  I'm far from a computer expert but it didn't make sense to me that I was having issues when my CPU utilization rarely went above 40% and memory utilization was always around 20% regardless of the native rate of the input file that I was attempting to upsample and if I did ANYTHING on the desktop, play would immediately quit.

I loaded the v2.2 preview, recently, and am VERY HAPPY to report that it works flawlessly. I now have to set Output/buffer length to higher level  (which is what I needed to do in the 32 bit version especially when upsampling DSD64-->DSD256).  The proc utilization now makes sense to me.  Play is stable and as the input file rates increases, the proc. util increments to a higher plateau.

THANK YOU SO MUCH, Peter, and all who contribute to this terrific application for all of your hard work!!
8
foobar2000 mobile / Re: Gapless broken on Android
Last post by lostgirl22 -
If I open the console, I see the message "Playback interrupted, source is stalling..." is logged between each line showing "Opening track for playback" followed by the location on the SD card. Also, turning on or off the option to use read-ahead for playing local files in the advanced options doesn't seem to help.
10
foobar2000 mobile / Gapless broken on Android
Last post by lostgirl22 -
I've been using Foobar2000 mobile on Android for a few years, since Google Play Music was withdrawn. Proper gapless support has always been very important to me, and it has always worked flawlessly. However, in the last week or so I've noticed it seems to be broken.

My files are all in m4a format, encoded using the Apple iTunes AAC encoder by Foobar2000 on Windows, mostly from CDs ripped to FLAC. They are stored on an SD card in my phone. The files aren't the problem because there are thousands of them, some years old, and they all used to play fine without gaps. My phone is a Moto G73 5G running Android 14. I've tried turning on, and turning off, all battery saving optimisations, using OpenSL audio output, listening via several different Bluetooth devices, or wired headphones, or the phone's speaker, and disabling the Dolby Atmos app. None of it makes any difference and I can't think of anything else. There is a short half-second gap between tracks – but if you then immediately rewind to the end of the previous track to try to repeat it, the gap disappears. But then it's back for the next track, and if you leave an album to play through, the gaps are always there. It seems to make no difference if the app is foregrounded or backgrounded. I don't know if the issue was introduced by the update to Android 14, or by the recent Foobar2000 app update, or something else, and I'm at a loss how to fix it.

Can anyone help? Are others seeing the same issue? Many thanks.