Skip to main content
Recent Posts
3rd Party Plugins - (fb2k) / Re: foo_beefweb - modern web interface
Last post by hyperblast -
I've uploaded new version.

Changes in v0.3:
  • Added button that locates currently played track
  • Fixed volume and mute state not being synchronized
  • Added "Cursor follows playback" option
  • Implemented proper escaping for array query string parameters
  • Added playlist sort operations
  • Added "Play next/previous artist/album" operations

Have fun!
General - (fb2k) / Why can not foobar do what most other BASS players can do by default?
Last post by Radosny -
Guys, I hope it is just simple solution. I just can not believe it would work like that.
I can not open any file that has not been closed yet. (to which the data is still being saved by another program)

Aimp, Xmplay, 1by1 even winamp have no problem in such a situation.
I have downloaded foo_winamp_input_050309 to enable some winamp input plugins but before I start implement such an exotic solutions I ask You: Am I doing something wrong?
please help
Support - (fb2k) / Should fb2k report bits per sample for ffmpeg-generated lossy-in-Matroska?
Last post by Porcus -
Played around with remuxing .opus into .mka , and found that foobar2000 reports them as 32 bits. Repeated with AAC and Vorbis: 32. (Same with webm.) Repeated with an .mp3: 16, so it is not consistent.

Then I dug up some old (-> might be older ffmpeg?) Matroska files with AAC, and found them to be reported as 16.

For all that I know, ffmpeg could write misleading information to the container. Tried ffmpeg 4.0.2 and 3.4. Could anyone reproduce?
Opus / Re: Opus 1.3-rc2
Last post by jmvalin -
Why does opusdec.exe include OpenSSL? Doesn't this belong in a program that connects to the web, like a streaming player or browser? No other cli audio decoder has web components in it.
opusdec is now based on opusfile, which actually supports streaming, so you need OpenSSL for https.
AAC / Preferred settings for AAC?
Last post by rectifica -
I don't have equipment as such and would like to save file space while retaining quality.
I've had a look around and VBR Q 45 w/ 96khz looks to be sufficient. I don't mean to generalize since everybody's ears are very different to the next, just wanting to know what you settings you use!!

96khz or 128 is what im leaning toward as of rn

Opus / Re: Opus 1.3-rc2
Last post by j7n -
Why does opusdec.exe include OpenSSL? Doesn't this belong in a program that connects to the web, like a streaming player or browser? No other cli audio decoder has web components in it.
Opus / Re: Opus gapless and glitchness encoding
Last post by j7n -
Recent Foobar versions have a configurable advanced setting for ReplayGain in Opus. The program can either store it in the global gain header field or a tag, it can also clear the header gain field. Album gain written to the global gain field, as happened by default in the past, wouldn't cause sudden jumps in amplitude, since the gain would be the same for all tracks. Glitches due to changing track gain happen in all formats. There was a proposal by Frank Klemm for a gradually changing AGC type of track gain, but it was never implemented.

For music with extreme sub-bass, either sourced from vinyl or artifical electronic music, you could prefilter it with a highpass filter, so that the mandatory Opus HPF does very little. This is far from ideal, but is one way of addressing the issue.
Opus / Re: Opus gapless and glitchness encoding
Last post by -
A critical problem with opus is the single entry for a replaygain-like value.  No separate track and album values, just the one, and no way to say if it is track, or is album, or is who knows what.  It defaults from what I've seen to 5 dB (from memory, and I suppose that is minus 5 dB) regardless the source.  If you use something else to calculate a replaygain value, that value is stuffed into the single entry available for an opus track.  It's not a tag, like replaygain is in .ogg, or .mp3, but a little cubbyhole for that value.  It's a disaster since there's no telling what the value is for (album or track), and if you go by the opus docs, it's required to be used.

FWIW, even if you have already adulterated the track with a replaygain scanner, the player in the link below plays opus tracks gaplessly ("no glitches" by definition then), but you have to remember to keep RG off (using the RG button).  Still, this is one reason I can't take opus seriously for music because RG is important.  It needs both track and album RG-value slots.

The last one on this page,100209.0.html

Point is, check that a rogue RG value isn't in the tracks you play.  That will cause audio glitches as the level goes up or down.
Opus / Re: Opus 1.3-rc2
Last post by krcroft -
jmvalin:  Where can we download the 32-bit binaries for opusfile 0.11?  The latest version at is still opusfile 0.9.
We've not been able to build them at this point. None of us uses Windows and while we generally do our best to provide binaries, it doesn't always work out (in this case I think it was OpenSSL dll problems while cross-compiling).

I think this is a good area to target before the 1.3 release - being able to cleanly build the Opus suite (opus, opusenc, opusfile, and opus-tools) including step by step instructions using the currently maintained tool sets like: msys 1.0, msys-w64, msys 2.0 32bit, and mysys 2.0 64bit.

I'm also a 100% linux user (where auto tools just works), but I recently added Opus support to dosbox via integrating opusfile into SDL Sound, and thus wanted to test various windows builds.. and it was fraught with subtleties.
SimplePortal 1.0.0 RC1 © 2008-2018