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
11
MP3 / Re: 320 sounding better than V0?
Last post by sld -
V0 saves bits where the psychoacoustic model deems it unnecessary to use 320 kbps, and can invest the saved bits into places where more are needed. However, both 320 kbps and V0 are insanely high in quality, outside of well-characterised problem samples, you shouldn't be able to detect any differences from the original lossless format. Unless you were trained specifically in psychoacoustics before, or you're a 16 year old (or any age, but dog whistles strongly annoy you) with excellent audio hardware (that exhibit very low levels of THD, crosstalk etc).

Or you have some aural... quirks... that push you to either extreme of the gaussian curve of human listeners.

Regardless of the reasons, please ABX first.
12
General - (fb2k) / Re: DTS decoding in foobar v2
Last post by Bogozo -
Finding 96/24 or HRA made from 16-bit in the wild is highly unlikely anyway, so not really a problem.

But detectiing 96/24 as 24 bit while HRA is detected as unknown bitdepth still seems inconsistent.
15
3rd Party Plugins - (fb2k) / Re: foo_beefweb - modern web interface
Last post by rusoftware -
Here are some screenshots of my remote controller app based on Beefweb.

Edit: changing images host since the previous one doesn't work as expected






Still need to know how to listen to Foobar events. Any documentation or knowledge would be much appreciated.

Thank you!
18
foobar2000 mobile / Re: Preview of foobar2000 mobile v1.4
Last post by pyr452 -
Quote from: Peter on
I hope this addresses FTP server hammering issues some have been suffering from.
The new release was like Christmas for me, but I'm afraid to report: the problem with "421 Unauthorized client limit reached" still exists.
What did you change? Is there a hardcoded "x connections per minute" or "sleep x seconds" value, that could be made configureable via the options?
I don't mind waiting for 30-60mins to get the indexing done, as long as it succeeds.

The new beta is still only able to index about 1/3 of my whole song library.

Edit: There seem to be additional new entries in the indexing error log saying "225 ABOR command successful", which I don't remember to be there before.
They also sometimes popup when trying to play a file.
Towards the end of the indexing error log, the messages change to "network error".