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
6
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Case -
I initially had two decimals but I changed it to integer right before release. I'll change it back if that's what people want.

How about the tag field names, does anyone know if some tool already uses some tag field names for these things? I'd like to utilize common tags.
And this worries me a bit, I have been using the latest compiler for about 24 hours now. Any stability issues? I can revert to older toolchain.

And of course I want to know what Defender's comment about negated PLR was about...
7
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by wojak -
PLR is difference between highest peak and loudness, calculated as 'peak_db' - 'LUFS-I'. Only way it would be negative is if peak was somehow smaller than loudness.
All places I saw quoting PLR numbers printed them without decimals, like https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Titleformat_Examples#Peak_to_Loudness_Ratio_.28PLR.29. I figured it's like the DR number that people want to see as integer.

Hi,
Since TP and LUFS are presented with two decimal places, I think PLR should also be that way.

External meters like Youlean also use decimals.

The formula I use in Columns is based on:
$puts(PLR,$if(%replaygain_track_peak_db%, $puts(PLR,$sub($mul($replace(%replaygain_track_peak_db%,.,),10),$sub($mul($replace(%replaygain_track_gain%,.,),-10),18000))) $puts(PLR_TEN,$left($right($get(PLR),3),2)) $puts(PLR_ROUND,$ifgreater($get(PLR_TEN),40,$add($get(PLR),100),$get(PLR)))$iflonger($get(PLR_ROUND),4,<$left($get(PLR_ROUND),2)<.$substr($get(PLR_ROUND),3,3),$left($get(PLR_ROUND),1)<.$substr($get(PLR_ROUND),2,2)),))$if2($get(PLR),?)
8
foobar2000 mobile / Bogus rejection from Google Play
Last post by Peter -
Quoting last response from Google:
Quote
Status: Latest app update not accepted into Android TV on Google Play

We’ve reviewed your appeal request and found that your app, foobar2000 (com.foobar2000.foobar2000), still contains eligibility issues. We’ve included details below about the specific issue with your app and what you can do to meet the requirements for Android TV.

Step 1: Fix the eligibility issue with your app

During review, we detected the following eligibility issue and were unable to accept your app for Android TV:
No full-size app banner

Your app (version code 847) does not contain a full-size app banner and/or icon, or it is not visible in the launcher. We are targeting 1080p, which we consider xhdpi. Apps should include the banner in the xhdpi (320 dpi) drawables folder with a size of (320px × 180px) and the icon with a size of (512px x 512px). Please refer to our Provide a home screen banner article and UI Patterns documentation.

The title should help users identify apps in the launcher. Please refer to our Visual design and user interaction documentation for more information.

    For example, your icon does not fill the entire icon space. See attached screenshot.
Screenshot they attached:


Can anyone more competent at Android development explain to me what the heck this is about?

High-resolution TV banner is included. I don't know what their problem with the icon is. From the above, I'm not really sure if the problem is icon, banner, or something else.

Offending app bundle is same as these APKs.

Thanks in advance.
9
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Case -
PLR is difference between highest peak and loudness, calculated as 'peak_db' - 'LUFS-I'. Only way it would be negative is if peak was somehow smaller than loudness.
All places I saw quoting PLR numbers printed them without decimals, like https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Titleformat_Examples#Peak_to_Loudness_Ratio_.28PLR.29. I figured it's like the DR number that people want to see as integer.
10
Support - (fb2k) / Re: Unintended/accidental AVX requirement of 64-bit version
Last post by Peter -
Indeed, VS2019 supports C++20 and compiles latest foobar2000 sources without any apparent issues so far.

Another thing, VS2022 v17.10 output crashes hard if interfaced with older vcruntime DLLs, like, ones that foobar2000 has been including until now. It looks like using latest VS2022 for foobar2000 components is a bad idea becasue they'll crash in foobar2000 install having too old runtime.

Less related thing, Apple has a loose clown in their compiler deparment too, their latest linker defaults to turning C++ code into something that instacrashes on Mac OS older than 12 or so, as if they couldn't obey deployment target. I'm also using old tools there because latest can't be trusted.