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
91
3rd Party Plugins - (fb2k) / HTTP Control component issue
Last post by garciaj -
Hi everyone

I'm using foobar2000 v.2.1.3 [x86] and sometimes I'm using the remote control Pro for Android [Version 0.9.4.0a from July 2016].
Everything works great but recently I've noticed the following message on my Android app:
"Last version of HTTP Control component needed. Please get it on http://tiny.cc/fb2kc" (Please see screenshot attached).
When I open the download link, there's a zip file name: foobar2000 controller [PC-side setup] v2.0.1, and when I starting the installation process, I see that the component's version is: 0.97.14 (screenshot attached), which is older version then the one installed on my foobar2000 software: 0.97.28 (I got it from here.

My questions are:

1. Why do I get this message?

2. Is there any other source or newer version for the HTTP Control component?

Thanks in advance

🙏
92
Other Lossy Codecs / Re: exhale - Open Source USAC encoder
Last post by john33 -
Quote from: C.R.Helmrich on
Note that exhale only knows channel map "6" from https://wiki.multimedia.cx/index.php/MPEG-4_Audio, and since exhale is primarily meant for mono and stereo (due to the above limitations of xHE-AAC decoders), I won't extend exhale's functionality here. MPEG-H Audio coding is more efficient for multichannel, anyway.

Chris
Understood, but without the source having the channels remapped, doesn't that make the multichannel encoding worse than useless in most cases?
95
Other Lossy Codecs / Re: exhale - Open Source USAC encoder
Last post by Brazil2 -
Quote from: guruboolez on
I can't play any USAC 5.1 file.
0005.m4a

MediaInfo report:
Code: [Select]
Conformance warnings                     : 1
 UsacConfig                              : Yes
  General compliance                     : Extra zero bytes after the end of the syntax was reached (frames 0+84)

Conformance information                  : 2
 UsacLfeElement                          : UsacLfeElement support not implemented (frames 0.0+84.0+126)
 Crosscheck                              : Yes
  sbgp                                   : Yes
   roll_distance                         : MP4 sbgp is not present and this is an independent frame (IF), seeking is not optimal (frames 41+42+83+125+126)

With a button which is sending me to this page:
https://mediaarea.net/MoreInfo?mi=%7B%22creatingLibrary%22%3A%7B%22name%22%3A%22MediaInfoLib%22%2C%22version%22%3A%2224%2E03%22%7D%2C%22media%22%3A%7B%22track%22%3A%5B%7B%22Format%22%3A%22MPEG-4%22%7D%2C%7B%22Format%22%3A%22USAC%22%2C%22extra%22%3A%7B%22ConformanceWarnings%22%3A%7B%22UsacConfig%22%3A%7B%22GeneralCompliance%22%3A%22Extra%20zero%20bytes%20after%20the%20end%20of%20the%20syntax%20was%20reached%20%28frames%200%2B84%29%22%7D%7D%2C%22ConformanceInfos%22%3A%7B%22UsacLfeElement%22%3A%22UsacLfeElement%20support%20not%20implemented%20%28frames%200%2E0%2B84%2E0%2B126%29%22%2C%22Crosscheck%22%3A%7B%22sbgp%22%3A%7B%22roll_distance%22%3A%22MP4%20sbgp%20is%20not%20present%20and%20this%20is%20an%20independent%20frame%20%28IF%29%2C%20seeking%20is%20not%20optimal%20%28frames%2041%2B42%2B83%2B125%2B126%29%22%7D%7D%7D%7D%7D%5D%7D%7D
96
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by maikmerten -
These warning are harmless - that function is superfluous for the C code path (not even used) and the 32-bit ASM code path has its own version. It's just left in there so there's a human-readable version for what the ASM version is doing.

(The warning basically says: Hey, pointers are 64-bit long on 64-bit architectures, you're calculating new pointer values in 32-bit - that's somewhat suspicous! - the compiler is right, but given that this code is never called in the C versions, it's of no consequence.)

98
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Case -
Thankfully you don't need to worry about that warning. That function is possibly some old leftover as it's not used anywhere in the code.
If it was actually used things wouldn't work at all in 64-bit build. The function truncates a 64-bit memory address when it gets stored in a 32-bit variable. Attempts to access data in the new wrong location would crash badly.
100
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by Case -
Quote from: pqyt on
Not anymore.

What do you mean? The source still shows peak is divided by 1/sqrt(2) when converting the float to dB, which adds 3 dB to its value.

I have trouble accepting the supposed "RMS+3" standard that makes RMS show nonsensical numbers, but if pro-people really need things to works that way I suppose I have to accept it. But for peaks this is 100% wrong thing to do.

Getting off topic again, but I'd still like to see some specs explain where the idea came from to make RMS artifically match peaks. It's such a weird concept.