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
MP3 / Re: Low bitrate MP3 (+ unsupported bitrates)
Last post by Klymins -
@Kraeved In fact, CBR is not necessary (i want it because it's easier to work with it) but i want mono because i think stereo is not going to be sound good below 20kbps or 16kbps. And, i already can produce a good quality sound with 16kbps, the reason that i want to use below is: can i make a good sound with these bitrates? 20kbps stereo sounds good and 16kbps mono sound better than it, so i thinked lower bitrates must be able to produce good sounds. @danadam You can be right, i selected libopus from shotcut but i don't trust it.

And, i must use MP3 because Flash Player does not support these newer alternatives even if some of them can sound better.
93
General - (fb2k) / Re: Old 1.x versions usage
Last post by Kraeved -
Thank you, @Peter.

I remember the day when I first installed 2.* and immediately felt out of place. Why? Because you broke changed the way portable works  — it is no longer possible to put the player in the custom folder, remove portable_mode_enabled file and (temporary) associate the player with audio files within Shell Integration page, keeping the profile in that folder as well. Users of audio forums were forced to invent tricks like using Windows junction points and writing batch scripts with tons of reg commands to simulate previous behavior. The irony is that there are more customization options like ReFacets (which I hadn't used before, preferring simplicity), but at the same time, you ignored the long-standing habit and imposed a new way of installation. Perfect is the enemy of good, as they say.

Personally, I expected improving the documentation of existing functions (right there, at least in the form of tooltips) in order to reduce anxiety and make the best use of Foobar2000. For example, ReplayGain page is still a mystery, why mono files sound quieter, what is… fast DSP reset, flush playback queue, MMCSS, which music formats are affected by “slow but accurate seeking”, what and where are “dead items” and when is it time to remove them, etc.
94
3rd Party Plugins - (fb2k) / Re: [fb2k v2] SQLite Utilities (foo_sqlite)
Last post by dpc666 -
It would be amazing if there was some way to use SQLite to generate autoplaylists. Is there a chance for something like this in the future, or is there already some way to do it I haven't noticed cos I'm dumb?

Currently I just know that I can use foo_uie_sql_tree to send SQL query results to a playlist by interacting with the panel.
95
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Porcus -
Free format is so extraordinary nowadays that one might consider to introduce a new restriction - like how LAME requires you to enter "--freeformat" to encode to such. Of course, more sorts of "overrule sanity" options may be up to some level of consideration, if one is so inclined.

(Just came to think about: Can it create "MPEG-2 only" files? Are they any problematic?)
96
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.
97
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.
98
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.
99
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.
100
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?