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
Support - (fb2k) / Unrecoverable playback error Element not found. (0x80070490)
Last post by aczisny -
I've recently started getting regular unrecoverable playback errors while using Foobar2000.  I've been on 1.6.8 for a while and recently tried moving to v2.0 beta 15 x64 on windows 10 but the errors on that version are just as prevalent.  The errors aren't consistently on the same song (When not forcing crash on error I can select the song and play again) and usually crash mid-song.  I've attached a couple crash reports where you can see that it crashed on a particular song, I played that song again, and then sometime later it crashed on a different song.
5
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by john33 -
Changing the Revision number to 0 in hmp3 results, in my tesfile, in 196 fewer bytes being written which is reflected in the padding being reduced by the number.

I'm not sure I follow. Did you edit xhead.c to simply write "version 0" into the info tag version field and suddenly fewer bytes are emitted?

I used http://gabriel.mp3-tech.org/mp3infotag.html as specification. Sadly, I don't see information on what version that spec describes, so I just assumed it would be the presumably more recent one ("version 1").
Yes, that's all I did. Bizarre, I know, but I can't follow the lame code well enough to understand what's going on.
7
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by maikmerten -
Changing the Revision number to 0 in hmp3 results, in my tesfile, in 196 fewer bytes being written which is reflected in the padding being reduced by the number.

I'm not sure I follow. Did you edit xhead.c to simply write "version 0" into the info tag version field and suddenly fewer bytes are emitted?

I used http://gabriel.mp3-tech.org/mp3infotag.html as specification. Sadly, I don't see information on what version that spec describes, so I just assumed it would be the presumably more recent one ("version 1").
8
Development - (fb2k) / Re: New SDK with foobar2000 v2.0 features released (2022-08-10)
Last post by oblikoamorale -
A component is compiled against 2022-08-10 SDK.

Autoplaylist is created with autoplaylist_manager's add_client_simple(). Consequent calling of remove_client() on said playlist completely removes search results (empties playlist) in 2.0 beta 15, while in 1.6.14 (and before, for as far as I remember) search results stay in playlist, and it's just gets stripped of autoplaylist status.

Is this the intended change and I should adopt a different strategy? Thanks.

Sample code:
Code: [Select]
auto apm = autoplaylist_manager::get();
auto plm = playlist_manager::get();
playlist = plm->get_active_playlist();
apm->add_client_simple(query, sort_pattern, playlist, autoplaylist_flag_sort);
if (apm->is_client_present(playlist))
    apm->remove_client(playlist);
10
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by john33 -
A slight conundrum. According to LameTag 0.4.1, the latest 'lame-svn-r6507-trunk' writes Revision 0 to the lametag. Strangely, LameTag 0.3.1 fails to read the lametag beyond indicating the lame version. Changing the Revision number to 0 in hmp3 results, in my tesfile, in 196 fewer bytes being written which is reflected in the padding being reduced by the number. fb2k appears to be Revision agnostic as it displays the correct information for both files and decodes correctly. Probably of no consequence but just struck me as odd.