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: External Tags
Last post by Porcus -
Question and possible wishlist item:
Since %last_modified% doesn't work now, how can it "Find tracks edited after External Tagging" - does it simply compare tags and report the different ones?

Because if not, that is a thing to ask for. (Rather than committing the whole thing.)
2
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Case -
ReplayGain scanner instantiation failing has nothing to do with source files.
Code: [Select]
replaygain_scanner_entry_v2::ptr rg_api;
if (replaygain_scanner_entry_v2::tryGet(rg_api)) {
  rg_scanner = rg_api->instantiate(replaygain_scanner_entry_v2::flagScanGain);
}
if (!rg_scanner.is_valid()) // Failed to instantiate ReplayGain scanner.
The code doesn't care about anything else. Core is just asked to give the component a ReplayGain scanner instance and for reasons unknown it fails for you. In my previous post I mentioned the only two reasons I knew of why RG scanner instantiation could fail. foobar2000 version was not a factor, the method has been supported for ages and works on all versions where the component works.

But now I did some more testing as I remembered an old troublemaker. Turns out https://www.foobar2000.org/components/view/foo_arg component breaks RG scanner instantiation. If you have had that component installed all your RG scan results are invalid.

PS: post editing not working after an hour is not about forum software being archaic. It's intentionally limited as editing old posts doesn't help with conversation. No one who follows the discussion would see edits done to old posts as they have already read the original posts and moved on. If you have some meaningful new information make a new post.
5
Wiki Discussion / Re: wiki 404 Not Found
Last post by Peter -
Update:
I'm actively working on restoring it and upgrading to latest mediawiki.
No worries about the content, it's been thoroughly backed up.
8
Other Lossy Codecs / Re: exhale - Open Source USAC encoder
Last post by ha7pro -
exhale-v1.2.1-14cdd94f-20250527_x64

1 out of 1 files converted with major problems.

Source: "Z:\EAC3.eac3"
  An error occurred while writing to file (The encoder has terminated prematurely with code -1 (0xFFFFFFFF); please re-check parameters) : "Z:\EAC3_5.1.m4a"
  Additional information:
  Encoder stream format: 48000Hz / 6ch / 32bps floating-point
  Command line: exhale.exe 9 "E318910B-98D2-4B18-9246-8C241372BAA3.m4a"
  Working folder: Z:\Temp\foo_converter\
  Conversion failed: The encoder has terminated prematurely with code -1 (0xFFFFFFFF); please re-check parameters



9
Other Lossy Codecs / Re: exhale - Open Source USAC encoder
Last post by john33 -
exhale-v1.2.1-14cdd94f-20250527_x64 -> broken return to prompt (i7-2600k) when encoding
exhale-v1.2.1-14cdd94f-20250527_x86 -> encode ok, preset 9, but foobar don't play it -> Unable to open item for playback (Unsupported audio track format)

mka encapsulation of the m4a same playback problem unsupported audio
Apologies, I uploaded an AVX2 optimised compile in error for the x64 version. I'll recompile and upload again. Thanks for letting me know.

Playback requires this component in foobar (for 64 bit Windows, otherwise the standard component):
https://foobar.hyv.fi/foo_pd_aac.fb2k-component

Playback of encoded files with both encoders works fine here.

EDIT: x64 compiles now updated.