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
Wiki Discussion / Re: wiki 404 Not Found
Last post by Peter -
Taken offline because someone/something appears is DoSing the server. Will be back shortly.

Extensions will be restored, I'm looking at them one by one, if they're actually still needed. This stuff was set up over 10 years ago and I wasn't in charge of it then.
2
General - (fb2k) / Re: Why can jump volume? To me jumping and in my yard(. My foobar2000 1.6.18.
Last post by Chibisteven -
Quote from: Swi on
With the "Advanced Limiter" DSP, the volume began to jump less, but It's all the same jump pleasantly and the volume at the end it gets quieter/silence, with the "Advanced Limiter" or without! Change, please, this topic on "Why jump volume foobar2000 1.6.x with output "Default: Primary Sound Driver"?"

foobar2000 outputs floating point when using the "Default: Primary Sound Driver".  When what you're playing is too loud or the DSPs you're using cause too much of a volume increase you can have pumping problems where the volume goes from loud to soft because of Windows' built-in limiter as you're simply exceeding the maximum allowed.  The "Advanced Limiter" caps it at 0 dB which can cause the pumping problems to disappear.  Try reducing internal volume either through using ReplayGain by turning down the preamps or using a DSP until the pumping stops.  You can use foobar2000's peak meter under visualizations to see if you're still going over 0 dB or not.
4
Wiki Discussion / Re: wiki 404 Not Found
Last post by korth -
At first glance I noticed fewer installed extensions but assumed it was still a work in progress.
User groups are a bit different too.
5
Wiki Discussion / Re: wiki 404 Not Found
Last post by Peter -
Sorry it took me so long.
It's back and mostly working, running on latest mediawiki.
If things go haywire, it's been thoroughly backed up and can be reverted to current state.
Some things look weird, front page clickpic in particular. Looks like clickpic template isn't working properly, I've not been able to figure out why, hopefully someone can enlighten me or edit it.
User account registration is currently disabled until I get all glitches ironed out.
6
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by ngs428 -
Quote from: Case on
That should not be a problem, I was fully prepared for such scenario and log will even report different codecs in use. I found single crash entry from crash logger from this component, it was related to scanning highly corrupted tracks and some tracks looked like they couldn't get decoded at all. The log writer had too light error checking for scan results and it tried to access per-channel data that it never managed to scan.
Should be fixed in the just released version 0.5. I'd appreciate it if you could test with the same files that failed earlier.

I gave this a test and using the 0.5 version Foobar does in fact crash, it did 3 times in a row on me.  Then after the 3rd crash and restart I was able to run them together without issue on several attempts.  So at this point, it is random, but did happen.....  I tested a FLAC and short MP3 file together.    
8
foobar2000 for Mac / Re: foobar2000 for Mac: bugs & wishes
Last post by Guildencrantz -
One more thing:

When you first invoke the Equalizer window after the launch of foobar2000, it appears with a significant delay. When you invoke it for the second or third time, it appears as fast as all other windows (Album List, ReFacets, etc.). But if you relaunch foobar2000 and invoke Equalizer again, you'll see the same delay.
10
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by musicmusic -
Ah! Thanks, now it makes sense. It's still a bug – the configuration format is not supposed to change between 32-bit and 64-bit builds. (This was thoroughly checked in Columns UI, but evidently not in Album list panel...) I'll have to think of a creative way to fix it now it's happened...