1
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.
2
FLAC / Re: FLAC encoder for arm cortex m4f with limited memory
Last post by Porcus -3
3rd Party Plugins - (fb2k) / Re: help setting up Georgia-ReBORN please
Last post by telboy1812 -4
General - (fb2k) / Re: SeekBar in Boom Player
Last post by zK -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.
Thank you for reading this petition.
5
3rd Party Plugins - (fb2k) / Re: help setting up Georgia-ReBORN please
Last post by TT -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.
-TT
6
FLAC / Re: FLAC encoder for arm cortex m4f with limited memory
Last post by radams2000 -7
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by maikmerten -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
8
AAC - General / Re: QAAC: discussion, questions, feature requests, etc.
Last post by Porcus -I get that some vendors deliver 7.1.4 files as separate .wav because they are unaware of lossless codecs that can handle it ...
9
3rd Party Plugins - (fb2k) / Re: Georgia-ReBORN - A Clean foobar2000 Theme
Last post by TT -you click on the eye icon ! when you write a message or you can use [.spoiler]Your pasted log here[./spoiler] without the red dots like this:
These are the crash logs but they won't help us, explanation is down below.
Spoiler (click to show/hide)
Spoiler (click to show/hide)
Spoiler (click to show/hide)
---
Yesterday I thought that the AllMusic fetching wasn't the actual cause of this problem, but it is indeed triggered by that.
When HTTP requests for AllMusic are initiated, fetching text/images and you exit foobar during this process,
foobar threads are still active and not properly disposed of, causing foobar to crash when an exit is attempted.
This does not work and you can reproduce the crash, if the artist has AllMusic review and it's not cached:
Code: [Select]
const checkResponse = setInterval(() => {
if (window.IsUnload) {
clearTimeout(timer);
clearInterval(checkResponse);
xmlhttp.Abort();
bioOnStateChange.call(null, resolve, reject, () => void(0));
console.log('EXITING');
fb.Exit();
return;
}
try {xmlhttp.Status && xmlhttp.ResponseText} catch(e) {return;}
clearTimeout(timer);
clearInterval(checkResponse);
bioOnStateChange.call(xmlhttp, resolve, reject, func);
setTimeout(() => {
on_script_unload();
}, 500);
}, 30);
Not sure yet how to prevent this, but foobar or SMP should kill all internal foobar processes immediately or wait until all processes have finished when the user closes foobar, then there won't be any crash...
-TT
10
FLAC / Re: FLAC v1.4.x Performance Tests
Last post by Wombat -Ok, i didn't try that.. but luckily, all others do it here. I choose compression "-4" based on the charts and own tests yeeeeeears ago, all resting compression steps ceased to exist for me, i forgot them completely.. and that continues to this day.SORRRY! Me is a bit outdated it seems. I just tried the latest flac git together with latest clang and indeed it is faster as everything else even with high compression so far! Guess i must change some things here.
But I understand that the code here should primarily be tested under stress conditions of higher compression, where the changes are more pronounced.
Attached a generic clang 03 compile without much additional optimizations for testing latest git.