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
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -
There's some confusion with the settings in v0.7.6.0. Peak is now right as you don't do any extra calculations to it.
But RMS is incorrect. You always divide the real RMS value by 'Amax', which is the same as adding 3 dB to its value. Then in addition you offer an optional 3 dB addition to it.
I just followed the article I quoted earlier. Like I said many times before: I'm not an audio engineer and don't understand this stuff half of the time. But when the specs are this confusing and 'people in the know' are debating definitions I prefer to stand by the sideline until the dust is cleared and a clear spec becomes available.

Edit: The current code produces correct(?) results with all the files I found here (https://www.soundonsound.com/techniques/sos-audio-test-files) and here (https://www2.iis.fraunhofer.de/AAC/multichannel.html).
Also the peak visualization bars go hidden here half the time (I have them moving horizontally from left to right). When I was playing stereo file, the right channel bar went invisible. I had to tweak the height of the UI element to make it visible. Then I played a mono file and now the size was incorrect for that size and it's invisible.
I don't think the bars should go invisible under any circumstances.
It's a render bug caused by Direct2D or the driver. I thought I had solved it with the optimized calculations because I could no longer reproduce the bug here (after updating the GPU driver). It has to do with drawing the LED bitmap on odd coordinates. The filled rectangles don't have this problem, AFAIK.
2
General - (fb2k) / Old 1.x versions usage
Last post by Peter -
Looking at crash report statistics, I have noticed that lots of people still use version 1.6.16, that is last 1.6.x before 2.0.
I understand that some just don't want 2.x features, that's why I made version 1.6.17 - in September 2023 - with important bug fixes - most notably fixes for libwebp exploits. Unfortunately, few people seem to have noticed it, 1.6.16 is still way more popular.
If you're on 1.6.x, please make sure you have the latest iteration of it. Really.

That said, if there are any special wishes for bug fixes (not feature updates) to be backported to 1.6 or 1.5 series, please post them here.
I'm considering backporting of Windows Imaging Component interop from 2.x to 1.6 to get rid of libwebp entirely, then you can't see webp covers on old systems but don't have to worry about updating libwebp with security fixes.
3
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by Case -
There's some confusion with the settings in v0.7.6.0. Peak is now right as you don't do any extra calculations to it.
But RMS is incorrect. You always divide the real RMS value by 'Amax', which is the same as adding 3 dB to its value. Then in addition you offer an optional 3 dB addition to it.

Also the peak visualization bars go hidden here half the time (I have them moving horizontally from left to right). When I was playing stereo file, the right channel bar went invisible. I had to tweak the height of the UI element to make it visible. Then I played a mono file and now the size was incorrect for that size and it's invisible.
I don't think the bars should go invisible under any circumstances.
4
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by maikmerten -
Yeah, the "malformed" files appear to be free format. I wasn't aware Helix could do those, so that's a nice finding. Lame can decode those (e.g. "lame --decode gudki.22khz.mono.mp3"). As far as I can tell, Helix did exactly what you asked it to do, sadly many decoders cannot properly deal with this form of MP3.

Helix has a few checks to discourage settings that are deemed non-recommended. For instance, for 44.1 kHz files, it won't go below -B48 and will just barf "ENCODER INIT FAIL" at the user. When taking away those checks, Helix can, e.g., create "passable" 80 kbps 44.1 kHz CBR files with intensity stereo, but I so far refrained from relaxing those checks in fear that the encoder might explode in unexpected ways.
5
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Case -
A quick reply before taking a proper look...

Unlike LAME, the -B flag of Helix sets the value for each channel, [...] to get 24 kbps, I entered 12. But this time the encoding did not go as expected.
For the first files the encoding went as you specified. The mono files have only one channel so the bitrate remained at the level you asked.

a) gudki.11khz.mono.mp3 and gudki.22khz.mono.mp3 are malformed files (24 293 bytes), apps refuse to open them
The file is outside specs, also called "freeformat". There are some decoders with freeformat support, but of course it makes no sense to use such formats anywhere.
I think the best option is to disallow incorrect settings, what do you think?
8
3rd Party Plugins - (fb2k) / Re: Playback Statistics Questions
Last post by anamorphic -
Yes I think it would (when the track is played) if the database has no rating set. Unless you import tags to database first like I said...

It might be useful to add a couple playlist columns - one for %rating% (database) and one for $meta(rating) (tags) - so you can compare.

After you right-click a track > Playback Statistics > 'Import statistics from file tags', and once you can see the two columns match (so database and tags have the same rating), and once you have done that for every track in the library, then it would be safe to enable Synchronize Tags option. (It only syncs when tracks are played, not immediately)

Side note: To display stars for ratings, use a display script such as %rating_stars_fixed% (database) and $pad($repeat(★,$meta(rating)),5,☆) (tags)