91
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.
92
General - (fb2k) / Re: title formatting for substitutions within strings
Last post by Porcus -Note that $replace(str,search1,replace1,search2,replace2) is generally not the same as $replace($replace(str,search1,replace1),search2,replace2).
93
General Audio / Re: Can higher bitrates sometimes sound worse than lower ones
Last post by Porcus -94
General Audio / Re: The "business model" of hybrid codecs with correction files
Last post by Porcus -What about hardlinking? Create a "hardlinked mirror" of the entire collection, and then delete *.wvc from it afterwards.
- Correction files are supposed to live in the same directory as the lossy files, which makes it very inconvenient to copy an entire lossy collection to a DAP (say, my iPhone). I could write a BASH script (and I just might) to move lossy files and correction files to twin directory structures. That way I could just drag and drop the lossy directory structure to my iPhone. But I also would need to run that script in reverse to join lossy and correction files back together.
Caveat: As far as I understand, the end-tags of .wv mean that retagging won't have to create a temporary file (thus breaking the hardlink structure) - but who knows if application X will do so?!
Also, you will have to use a player that actually plays lossless .wv+.wvc. foobar2000 for Windows does, so I'd be surprised if foobar2000 for MacOS cannot - but I think ffmpeg-based players will have to disregard the .wvc , limiting your choices.
95
Support - (fb2k) / Re: BUG: foobar2000 2.x Seekbar Issues
Last post by Case -When a track change is near, foobar2000 has always started decoding the next track in advance. That is necessary for gapless playback - there can be no pause in the signal chain. The time when next track starts decoding depends on your output buffer length + DSP chain latency. For example if output buffer is 10 seconds long and DSP latency is 10 seconds, the next track will start decoding 20 seconds before you hear the end of the current track. But that is just decoding, the next track won't be played until after the very last sample of the current track finishes.
There are of course exceptions, like if you use a DSP that mixes two tracks together. Then you can start hearing parts of the next track before current track changes visually. But that is not the default behavior and you should know if you have installed and enabled such DSPs
Also note that a bug in output component or in DSP related to latency reporting will cause all playback time tracking to be wrong.
Since you seem to have an issue related only to most recent foobar2000 versions, it has to be something else than the known tiny occasional seekbar twitch. You could verify if it's reproducible in a clean portable install, easy way to rule out any third party components.
If clean install worked correctly, you could post your configuration details, like output component and DSPs. Or simply test changing settings one at a time until the problem goes away, then you know what part is at fault and can report it.
96
General Audio / Re: The "business model" of hybrid codecs with correction files
Last post by Nick.C -My music archive is FLAC and is converted to lossyFLAC for use on devices with limited storage capacity as and when required. I don't make use of the correction feature at all (apart from testing during development)
As a codec, rather than a DSP, WavPack has the significant advantage of being able to reconstitute lossy & correction files "on the fly".
97
Support - (fb2k) / foobar2000 v2.25 preview 2025-05-12 / 2025-05-09 problem with Radio streaming
Last post by ApacheReal -As widely demonstrated in the video: https://www.youtube.com/watch?v=mQwKnp17JV0
The problem has been reported by several users with different configurations and skins both with M-Tag and External Tags 1.5.14
The problem is already present and detected in the JS Playlist sample.
A simple test is to see what the Playback State Display Formatting returns.
Therefore, pending resolution, I am returning to the stable version foobar2000 v2.24.5
Greetings.
98
Support - (fb2k) / Re: foobar2000 2.25 Preview 2025-05-09 -> UPnP
Last post by LouCypher -According to the change log it had been added only UPnP server and client but not control point functionality which would be required for this use case.
99
Support - (fb2k) / BUG: foobar2000 2.x Seekbar Issues
Last post by KMDXM -Recent 2.x versions of foobar2000 seem to have a seekbar issue where the marker on the playback bar continues to move for a short period of time before jumping back to the paused position. What's more is that near the end of audio files, foobar2000 2.x preemptively plays the audio file that follows in a playlist or queue, which I found especially noticeable when seeking back to earlier points in ending files.
I have tested an installation of foobar2000 v2.0 on a desktop computer to see if these issues are also present, and they were nowhere to found, at not noticeably.
100
3rd Party Plugins - (fb2k) / Re: foo_youtube
Last post by BlindHedgehog -about being unable to open item for playback.
Have latest Foo_YouTube, FooBar2k2.25 Preview and all Foo_YouTube's subcoments are up to date.