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.
Last post by TT -
It is displayed in the Playlist Manager at the top bar of the Playlist, see screenshot. Just mouse hover over the top bar of the playlist and it will show.
On foobar startup when nothing is playing, it will automatically show the total length of all tracks, if you select multiple tracks it will calculate these lengths, and if you select all tracks CTRL + A it will display again the total length.
Edit: looking at that thread, I don't see any particular reason it should be any better or worse. There was some discussion on what had to be done to get it compatible with even older CPUs, but that was a hypothetical thing, I remembered wrong.
Last post by zK -
I fully support the thoughts expressed here in this thread. I was on the verge of creating one exactly in the same regard, but judging by the absolute identity of purposes, I thought it would be more useful to use this space.
The Boom player is the lightest player on Planet Earth. I was very well served by the MPC-BE player for quick playback of audio files, especially when I'm in front of a new album and want to have a quick overview of its contents.
Boom player is surprisingly even more responsive than MPC-BE, but the absence of the SeekBar feature literally KILLS the program's usefulness. Using the "<< >>" buttons as an alternative is not a valid option and is therefore terribly counterproductive.
I've been a devoted fan of foobar2000 for many, many years. As I had a recently closed CD store, I use it for the purpose of organizing a large (huge) library of audio and video files (I use the "mpv" component) that I ripped on the computer. There is no other player/organizer of audio and video files in the world that offered me as much speed in tasks as foobar2000 (I took care to test everything that exists), all thanks to the excellent workflow offered by extraordinary customization that can be done in the software. For anyone who knows what they're doing, foobar2000 is clearly and comfortably way above the top.
As a result, having integrated a theme into foobar2000 that I developed and constantly enriched over the years, I have preferred to use an accessory player for quick auditions. "Boom" would be - by far - this player. It offers a taste of foobar2000 without having to resort to theme switching.
So, first of all, I would like to express my immense gratitude to those responsible for foobar2000. A large file organization that could last around a year was possible to complete in a few weeks, thanks to the software's aforementioned customization capacity.
And finally, I fully endorse the thoughts expressed above so that, with due respect, the addition of the so-called "SeekBar" feature to Boom is effectively considered.
you need to have cover.jpg/png or folder.jpg/png or front.jpg/png in your music album's root directory or you need to have the album covers embedded into your music files.
Last post by maikmerten -
Some more resampling data points:
22050 -> 48000: case 7, works 22050 -> 44100: case 6, works 22050 -> 32000: case 7, works 22050 -> 24000: case 7, works 22050 -> 22050: case 5, works 22050 -> 16000: case 9, ear-damaging, mangled, screaming and screeching sound, ffmpeg decoder unhappy
16000 -> 48000: case 7, works 16000 -> 44100: case 7, works 16000 -> 32000: case 6, works 16000 -> 24000: case 7, works 16000 -> 16000: case 5, works
In short, indeed appears to be *down*sampling that is problematic. 22050 to 16000 is especially nasty, don't try with headphones!
edit: For sake of completeness:
48000 -> 48000: case 5, works 48000 -> 44100: case 9, segfault in hmp3/src/l3math.c:688 48000 -> 32000: case 8, no audio 48000 -> 24000: case 8, ear-damaging, mangled, screaming and screeching sound 48000 -> 22050: case 9, ear-damaging, mangled, screaming and screeching sound 48000 -> 16000: case 8, segfault in hmp3/src/cnts.c:285
Last post by Porcus -
8 channels in separate .wav, I have seen that, and if they are indeed delivered that way then obviously it is fair to ask how to handle it, but ... - why one file per channel?
I get that some vendors deliver 7.1.4 files as separate .wav because they are unaware of lossless codecs that can handle it ...