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
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by KevinB52379 -
@Wombat - OK I tried your build again with foobar2000, and set the thread count to 4, and I tried again.

This time I get about 250x to 320x realtime, and the encoding time is about 1 hr 15 mins.  The system is more responsive....

With Case's version with these same settings I get 530x to 600x realtime with about 35 minutes to encode my library
2
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by Defender -
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.

Apparently you missed this message:
https://hydrogenaud.io/index.php/topic,125031.msg1043133.html#msg1043133

Just download and install the newest version 0.7.6.1.
3
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -
But the Peaks seem OK to me (by eye), those also seemed OK from the beginning. Only two or three version from a few days ago seemed wrong and now it seems OK again with music (and weird with this one test file but only with +3 which should not change peaks as it is supposed to recalibrate RMS only).

I again propose to implement text peak values as it would make the comparison with other meters easier. Other meter usually show the max value of the track up to the present point (the highest value reached from the beginning of the track to "now") and not the actual momentary value.
See the screenshots from the quick hack above. I never expected this to be more difficult than the curve representation of the spectrum...
4
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by wojak -
But the Peaks seem OK to me (by eye), those also seemed OK from the beginning. Only two or three version from a few days ago seemed wrong and now it seems OK again with music (and weird with this one test file but only with +3 which should not change peaks as it is supposed to recalibrate RMS only).

I again propose to implement text peak values as it would make the comparison with other meters easier. Other meter usually show the max value of the track up to the present point (the highest value reached from the beginning of the track to "now") and not the actual momentary value.
5
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?

1_mono tone 1kHz -20dBFS 44k.wav:
- your component at 0: 20/20 (RMS/PEAK)
- your component at +3: 17/17
- vst TT Dynamic Range Meter: 20/20
- Span at DBFS: 23/20
- Span at DBFS+3: 20/20
- dpMeter: 23/20
- youlean loudness meter: 23/20

So it seems that RMS should be as @Case said - lower by 3 (or third option: -3).
Peak seem OK but one strange thing that your component also shows 17 as peak when +3 while all others show 20 no matter if +3 or not.
OK. I fold. ;-)
6
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Kraeved -
@Case - I hate to bother you, but could you please post the latest binary of Helix to this thread?  I try using the latest version from Rarewares (both 32 bit and 64 bit) and they both run really slow, and slow down my system...yet CPU utilization isn't near full when encoding using foobar2000.

There is something wrong about Lancer mod 2021-05-11 hosted on RareWares. It is unable to correctly encode WAV when its sampling rate is less or equal to 11025 Hz: SSE2 version outputs silence, SSE3 outputs heavily distorted sound.

I'm off to Spain for 2 weeks tomorrow so my mind is elsewhere!! I don't think I will get to look at this until I return so please feel free to remind me if I should appear to have forgotten about it.

I was thinking about this the other day, expecting some trouble to happen. We have a few developers who release binaries here. And if the old-timers of our forum can still keep an eye on them, then what will we see if we just type "Helix MP3 encoder" in the search engine? A scattering of sites offering a version back from 2005 and some abandoned repositories. Unlike LAME, Helix MP3 encoder does not have its own page, a single point of entry. This issue cannot be solved immediately, but I see the light at the end of the tunnel. Dear @maikmerten, is it possible to compile Helix binaries automatically for x86 and x64 (two separate archives) on Github when the version is bumped, or could you update the front page by adding links to RareWares (downloads) and HA Wiki (documentation)?

7
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by wojak -
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?

1_mono tone 1kHz -20dBFS 44k.wav:
- your component at 0: 20/20 (RMS/PEAK)
- your component at +3: 17/17
- vst TT Dynamic Range Meter: 20/20
- Span at DBFS: 23/20
- Span at DBFS+3: 20/20
- dpMeter: 23/20
- youlean loudness meter: 23/20

So it seems that RMS should be as @Case said - lower by 3 (or third option: -3).
Peak seem OK but one strange thing that your component also shows 17 as peak when +3 while all others show 20 no matter if +3 or not.
8
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.

9
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...)
10
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?