Sorry. You misunderstood me.
I know you (and I) cannot run that stream without stuttering with fooBar only. So fooBar needs to be fixed.
It would be nice if this problem was acknowledged by the developer and put on a todo list.
you would have no issue if the flags were zero before passing them in.Of course, but it's still a bug. The caller must receive the value, especially if the function itself returned true
If all you are interested in is uncompressed music to test with, then there's an enormous lot of free-of-charge stuff on Bandcamp. Also on Soundcloud - but you probably need to fire up your search engine, and the interesting thing is that artists sometimes then upload directly from their DAW. There are some floating-point PCM around, which cannot be compressed by FLAC (use WavPack).*.flac is *.wav compressedActually, it usually only compresses the audio and not the files - but that is usually what you want. The non-audio part of the .wav container is not that interesting, especially not if you ripped a CD (which isn't from a file in the first place).
The big difference is if you are dealing with audio editing software. Then use the format it supports.
for (auto ptr : mainmenu_commands::enumerate())
{
for (const auto i : std::views::iota(0U, ptr->get_command_count()))
{
pfc::string8 display;
// component consuming menu items sets flags to zero every time
uint32_t flags{};
// don't rely on provider resetting it inside here
ptr->get_display(i, display, flags);
}
}
Sorry. You misunderstood me.external mpvmpv to foo_record has been stable for 2hrs with zero stutter/dropout ... fantastic.fooBar should be able to run these streams with no stuttering without having to run external tools.
mpv to foo_record has been stable for 2hrs with zero stutter/dropout ... fantastic.fooBar should be able to run these streams with no stuttering without having to run external tools.
EDIT: Wait... it works on x64 versionYep. But it's a pure coincidence) I hasten to inform you that there is a bug in the foo_listenbrainz2 plugin, due to which the plugin can report literally anything about the state of the unchecked menu, in other words, we can simply get numeric garbage. Therefore, in 32 and 64 bit versions it turned out differently, just was unlucky with 32 bits) But when menu is checked it is always correct, that's a fact.