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 -
Quote from: Wombat on
Don't confuse @KevinB52379 to much.
Old hmp3 versions work, @JoshuaChang version works within foobar.
A solution at the source is worthwile in this case.

I was willing to give Hyperfire a shot...but to be honest I thought the same thing as you. 

If the original version of Helix 64 bit works from ReallyRareWares, and @JoshaChan version works perfectly with foobar...then something else is the issue.

Also as I mentioned, I've used LAME (both 32 bit and 64 bit), FAAC 1.30, OPUS, Ogg Vorbis AoTuV, FDKAAC - all from RareWares, and they all behave normally, so I don't think it's a temperature/overheating issue.  This is with foobar and all cores/threads being used.  Perfect fine speed and system responsiveness.

I do think it is interesting that CPU utilization never reaches 100% like it does with Joshua's version, old Helix and Case's 32 bit binary.
6
General - (fb2k) / Lame Settings for Foobar Conversion, CBR 128
Last post by 2zrg -
Hi there,

I am looking for the parameters for foobars Mp3 conversion within this settings:



I just want to create a CBR 128 lame profile (for car audio). (I dont't know if I have to use --replaygain.)

Can somebody help me out?

Thanks
9
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Kraeved -
Quote from: KevinB52379 on
How come when I click your Hyperfire link it brings me back to this hydorgenaudio Helix thread?
Can you provide a download link to try this? 

The link in that message takes you to an example of how to use Hyperfine, so that you don't have to go through the user's guide in search of the proper commands. To date, the latest version available for download on Github is 1.18.

When troubleshooting, the first thing I do is look for a minimal reproducible example, i.e. I simplify the chain of events that lead to the problem. By measuring the audio encoding using several builds of Helix MP3 encoder in the terminal, we will know for sure whether Foobar2000 affects the slowdown in any way or not. If there is a comparable slowdown to the point that the system becomes unresponsive in the terminal as well, you can continue to encode via Foobar2000. Also, when the encoder outputs its report in the terminal, you may witness phenomena like counters going crazy, which will give the developers a clue on how to fix things.
10
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by KevinB52379 -
Quote from: Kraeved on
@KevinB52379, what if you discard Foobar2000 as an intermediary for a while and encode right in the terminal using Hyperfine, a cross-platform tool for warming up the system and measuring the execution time of the binaries? For example, @misio discovered and I verified that visualization via VST plug-ins works much slower in Foobar2000 than the same plug-ins in audio editors (DAWs), and surprisingly, interaction with WavPack files turned out to be the slowest.

How come when I click your Hyperfire link it brings me back to this hydorgenaudio Helix thread?

Can you provide a download link to try this?