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 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Kraeved -
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?

I believe non-spec stuff should be removed, After all, we are no longer at the beginning of the MP3 journey, when they tried all sorts of outlandish things, but proceed from what has been recognized. I tried to open a free-formatted audio file with a couple of dozen players on Windows 7 x64, and only MPV (probably with the help of mpg123 decoder) was able to read it. Even FFplay failed.

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.

It's no coincidence that almost a month ago, when I proposed a prototype of the simplified interface of Helix MP3 encoder, there were question marks instead of valid values for each of the encoding modes. If it is more or less clear with VBR — you can enter from 0 to 150, then what is acceptable with CBR? We should be clear about that both on the screen and on the wiki.

12
General - (fb2k) / Re: played queue history/log
Last post by jurzystas -
If you use Playback Statistics, you can create an auto-playlist. Click on Library menu > Playback Statistics > 'Show recently played' > (change the time frame if you like, see query syntax) > click '...' in search bar > Create Auto-Playlist. (Rename the playlist as you like)

Or for JScript Panel 3, there is a Play Log script included.
Many thanks - works! :-) Just one think (but this might be too much): the song gets logged after 1 minute approx, which means if the song is shorterned earlier - it will not get into the log. Is there maybe a place to change this timing (cannot find it in config...)
13
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -
As for RMS - I just made a live comparison of readings while playing a track and it was like that:
- your component with +3 disabled showed the same values as VST TT Dynamic Range Meter and the same as VST dpMeter5 and the same as VST Span (that one with DBFS+3 set). If I  changed Span to DBFS (without +3) it showed 3 more than all the others (inluding yours which was with +3 disabled). So it seems (again judging by eye) that your RMS set to 0 shows what other show and when set to +3 it shows different values than others.

So to me (as an amateur) it seems that Peaks now are OK and RMS might be too high by 3. Or in other word: to make all those 4 meters show the same values I have to set yours to 0 (+3 disabled) and Span to DBFS+3. Other two do not have those options to change but show the same values.
@wojak, would you please download one of the test files from https://www.soundonsound.com/techniques/sos-audio-test-files, preferably one with a dBFS number on the file name (e.g. 1_mono tone 1kHz -20dBFS 44k.wav or 19_Pink Noise stereo 20Hz_20kHz -23dBFS 44k.wav) and let us know what readings you get with other plugins?
14
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by wojak -

I have no new arguments and you still haven't convinced me. Maybe @misio can shed some light on the situation. He/She has been pushing me in the other direction. I don't care either way. But I can't follow 2 different expert opinions at the same time.

Consider me no expert - I just judge those readings by eye/ear and in comparison to other known (established?) meters. For ex. if I measured the files (with RG) and they say they have peak (true-peak) at -0,5 and your plugin and other "similar" plugins say that it is more or less -0,5 - I'm happy. There were two previous version of this plugin that said it was 2,5 (by eye) so it was different than RG and every other player plus those files did not clip (I suppose they should with peaks at 2,5). So I reported that your peaks were to high. Now they look OK to me.

As for RMS - I just made a live comparison of readings while playing a track and it was like that:
- your component with +3 disabled showed the same values as VST TT Dynamic Range Meter and the same as VST dpMeter5 and the same as VST Span (that one with DBFS+3 set). If I  changed Span to DBFS (without +3) it showed 3 more than all the others (inluding yours which was with +3 disabled). So it seems (again judging by eye) that your RMS set to 0 shows what other show and when set to +3 it shows different values than others.

So to me (as an amateur) it seems that Peaks now are OK and RMS might be too high by 3. Or in other word: to make all those 4 meters show the same values I have to set yours to 0 (+3 disabled) and Span to DBFS+3. Other two do not have those options to change but show the same values.
15
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by Defender -
Have you considered the old Peakmeter was wrong?

Of course. But the value of the old Peakmeter Spectrum (easy to check in the tooltip) is exactly the same as the one from the modern Loudness Peakmeter plugin.

Last point ... until now every version creates a hard crash to the desktop without logging when I accidentally Toggle full screen mode.
I don't care much if this will be solved, but please make it configurable not to show the Toggle Fullscreen on rightmouseclick.
No x64/x86/CUI/DUI crashes here.

I thought it would have something to do with foo_ui_hacks but that is not the case. Only thing that's probably different in my CUI/x86 is the fact I use transparency. I tested by disabling transparency on the panel that your  plugin(s) live in, but that did not help.
Disabling transparency on all panels that depend on it for a small test is just way too much work (all SMP panels and all splitters and a lot of plugins that support it have transparency enabled).
17
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by JesalRo -
Hello pqyt
I have detected an anomaly in the latest version. If you enable Leds in Peak Meter mode (Image1) and mark Left and Right (Image2) it does it correctly, but if you disable Left and Right (Image3) only the Left channel is displayed. In the previous version it did it correctly.
19
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by KevinB52379 -
If you want me to test something, let me know, I'd be happy to try and troubleshoot for you!
@KevinB52379 A few hours ago, I sent you a private message with the Helix build to test. Do you have any feedback?


I'm sorry, I missed your message.  I tried your build and I get about 259x realtime with Foobar2000 default converter options set for thread count and thread priority.  I appreciate the effor though.
20
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -
I'm foremost interested in being able to discard the old Peakmeter Spectrum. For that I prefer this tool to mimic behavior of the old plugin. Old plugin shows 3dB less than this one (even with the +3dB disabled). So please implement it the same way or just make an extra tickbox in the configuration to do enable -3dB in order to mimic the old tool.
Have you considered the old Peakmeter was wrong?

The old plugin has tooltips that show Peak MAX and RMS max. Can you enable those as well?
I put it on the list.

Last point ... until now every version creates a hard crash to the desktop without logging when I accidentally Toggle full screen mode.
I don't care much if this will be solved, but please make it configurable not to show the Toggle Fullscreen on rightmouseclick.
No x64/x86/CUI/DUI crashes here.