foobar2000 portable (for audio encoding)

[hello_hello]

foobar2000 portable 2.25.8.zip 15.3 MB

Encoders (32 bit).zip 146.5 MB (all encoders are 32 bit)

Encoders (64 bit).zip 284.2 MB (a mixture of 32 and 64 bit encoders)

Unfortunately foobar2000 is no longer XP compatible.
If you're running a 32 bit version of Windows, the "Encoders (32 bit).zip" file is the one to download, otherwise download "Encoders (64 bit).zip"

About the portable foobar2000 in the zip file:

The link above is for a portable, 32 bit version of foobar2000 2.25.8 (as a couple of the GUI components used in this configuration only come in 32 bit flavours, however it can still use 64 bit encoders). I've uploaded this as there's often threads asking how to convert audio files. This version of foobar2000 has conversion and encoder presets for converting just about any format to any format.

You only need to extract the zip files somewhere, move the Encoders folder to C:\Encoders, move the "foobar2000 portable" folder to wherever you like, and run foobar2000.exe from there. It's setup to be both an audio player and a converter (I use it for the latter almost daily). It's a "business only" configuration. It doesn't display album art or visualizations etc (aside from the output meters), but it displays a fair bit of information about audio files. The left side of the GUI is dedicated to displaying your media library and won't display anything unless you tell FB2K where to find it. The right side of the GUI has tabs at the top for displaying playlists, and tabs below for displaying information about the files in those playlists.

There's lots of conversion presets. They can be used as a guide for creating your own. There's even more encoder presets. I rarely use many of them, but they've been saved as a reference so I don't need to remember the required command lines.

The text display section on the lower right side of the GUI requires a mono-space font, otherwise the text won't line up. If the mono-space font it's configured to use isn't available for your version of Windows (it should be for Windows 10 and 11), right click on the text area and select "settings" to change it. It'll need to be changed twice, for the text areas under both the "Playing" and "Selected" tabs.

The first attached screenshot shows this foobar2000 setup running on Windows 11. The second is a similar screenshot of it running in Wine on Linux, and the third screenshot shows how the portable version will look when it's first run (although it's a screenshot of an old version on XP which is no longer supported).


[Attachment 72444 - Click to enlarge]


[Attachment 72445 - Click to enlarge]


[Attachment 72446 - Click to enlarge]

[hello_hello]

Deleted out of date info.

[shans]

foobar2000 1.5.3 Portable.zip[/URL] (104MB because there's lots of goodies included).

The link above is for a portable version of foobar2000 1.5.3 (XP compatible encoders).

I have downloaded the Zip file. Scanned it by virus total and found 2 engines detected this file.

https://www.virustotal.com/gui/file/8993a3bcc7fb5c9e899d63b066e9902d5eff15c740719ac347...3a01/detection

For information please.

Anyway, I have been using FB2K with your presets for conversion of various formats almost every day. Thanks for your offerings.

[hello_hello]

You're welcome.

I looked at your link and it appears the file was scanned with a bunch of antivirus engines and two of them resulted in false positives. The rest of them declared the file to be clean.

I'm going to replace the zip file in the opening post with a new version shorty. I discovered the bundled ffmpeg wasn't built with the Rubberband filter that some of the speedup/slowdown encoder presets use, and as a result of checking that I also discovered I'd named the ffmpeg/Rubberband encoder presets incorrectly, so I've fixed those. I'll upload a new zip file without ffmpeg. That'll reduce the file size quite a bit, and I'll add a link for the most recent XP compatible version of ffmpeg to the opening post at the same time.

[hello_hello]

For anyone who's interested, I've updated foobar2000 to version 2.0 and there's an updated link in the opening post.

[hello_hello]

For anyone who's interested, I've updated foobar2000 to version 2.25.8 and there's an updated link in the opening post.

[cholla]

@ hello_hello ,
I have the version you gave me.
It is for Windows 7 32-bit. I shows to be v2.25 with no additional .# .
Is there a way to check if it has ffmpeg built with the Rubberband filter ?
I have never used any preset with the Rubberband filter so I likely won't change it.
If I decided to use just the ffmpeg in the newer version. Would it work for my OS ?
If you know.
I have done some changes to the GUI & added some components. So I do not want to update f2k unless it is really necessary.

On a side note I ran into this the other day.
F2K would not play a file as .aac .
All I had to do was change the extension to .m4a & the same file played with no problem.


[Attachment 92221 - Click to enlarge]

Playing a video & it can also do full screen.

[Attachment 92222 - Click to enlarge]

[hello_hello]

cholla,
You must have installed a different version at some stage, but everything you need to retain your configuration, aside from the audio encoders themselves, is in the Profile folder. If you're using a portable installation of foobar2000 it'll be in the folder where foobar2000 is installed. For a non-portable installation it's wherever Windows prefers programs to store their data files these days.

If you use foobar2000's File menu, there'll be a menu item Folders/Browse Profile Folder, so you can use that to find your profile folder's location if need be. Everything unique to your foobar2000 setup is in the profile folder (aside from the encoders), so if you back it up you can mess with the foobar2000 configuration as much as you like and go back to the original configuration by replacing the Profile folder with your backup copy. Or you can install a fresh version of foobar2000 and copy the backup of your profile folder to the appropriate location to restore your previous configuration. Updating foobar2000 shouldn't touch the Profile folder, but having a backup copy just in case is still a good idea.

The easiest way to check if the version of ffmpeg you're using was built with RubberBand would be to try one of the encoder presets that use it to see if it works. The version of ffmpeg included in the zip file now is 64 bit so it won't be any good to you.

Apparently these 32 bit ffmpeg builds should work on Win7, provided UCRT is installed.
https://github.com/defisym/FFmpeg-Builds-Win32/releases
Just replace the ffmpeg exes in the Encoders folder with the new versions, and if there's problems revert back to the ones you're currently using.
ffmpeg-master-latest-win32-gpl.zip is probably what you want.

[Alwyn]

For anyone who's interested

I am! Thanks HH, it's a great program for levelling my MP3s and MP4s.

[cholla]

You must have installed a different version at some stage

I'm using the version I got from you. 2.25
I have added some components to do what I want & need.
Then I set up the UI or GUI like I wanted.
I now have done the same to the 2.25.8 .

The easiest way to check if the version of ffmpeg you're using was built with RubberBand would be to try one of the encoder presets that use it to see if it works.

I tested one of the Rubberband presets & it worked. So it must be installed.

The version of ffmpeg included in the zip file now is 64 bit so it won't be any good to you.

I verified this with

ffmpeg -version

in the Encoders folder.
It has this message:

This version of C:\Users\User\Downloads\foobar2000_2.25.8\Encoders \ffmpeg\ffmpeg.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher.

I replaced with the ffmpeg for Windows 7 32-bit that I got from autodidact in his topic.
I also have the Apple iTunes audio toolbox files added to that ffmpeg.
https://forum.videohelp.com/threads/414767-ffmpeg-7-0-1-and-Windows-7

[cholla]

@ hello_hello,
Is there a way to force foobar2000 to use the Apple aac codec ?
Also is there a way to identify which .m4a is Apple aac at verses fdk aac.
The two I converted with ffmpeg command line look identical in MediaInfo .

[noemi7]

@ hello_hello,
Is there a way to force foobar2000 to use the Apple aac codec ?

The best is quaac and here is info how to configure it in Foobar: https://github.com/nu774/qaac/issues/73 Of course download the latest version and not the linked in the thread.

[cholla]

I had a qaac preset in the fb2k I got previously from hello_hello.
I've updated to the newer version of fb2k with the previous presets.
I added a preset that exactly matched the one in the example noemi7 posted.
I had a qacc version almost as new so I did not update it.

This is a line from MediaInfo using qacc:
Writing application : qaac 2.85, CoreAudioToolbox 7.10.9.0, AAC-LC Encoder, TVBR q127, Quality 96
This is the conversion from ffmpeg using -c:a aac_at for the codec:
Writing application: Lavf62.12.100
This is the conversion from ffmpeg using -c:a libfdk_aac for the codec:
Writing application: Lavf62.12.100

All 3 show these:
Format profile: Apple audio with iTunes info
Codec ID : mp4a-40-2

How do I determine which m2a's use Apple aac_at as the codec ?

[hello_hello]

I've zipped up an encoders folder containing only 32 bit encoders and added a link for it to the opening post, and I've done the same for the 64 bit encoders, so the Encoders folder is a separate zip file now. They both should be fairly up to date. I haven't checked them thoroughly since updating them, and while I don't anticipate any problems, if anyone comes across any that don't work, please let me know.

[noemi7]

How do I determine which m2a's use Apple aac_at as the codec ?

You may ask a bat flying around your house if it can find a difference Seriously, I doubt you'll hear the difference between high quality encoding of aac and aac_at when they both use the same bitrate and sampling rate.

If MediaInfo doesn't report details, you won't be able to figure what is what. It's also overall problem with AAC codec that depending on its variant, it's often impossible to get even basic info like the exact bitrate.