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.
I think i have the same problem, my cpu is zen2 4650g(6c12t), i got around 280~300x under command line @ single thread with autodidact's clang build or rarewares' gcc build, I also compiled helix myself with clang plus linktime optimization, my version got around 480x. maybe that's the key. here's the binary, you can try it.
To be honest since i did read this i thought you have the same problem as @KevinB52379. Ho does foobar multithreaded react on your system with the other builds?
I don't see anyone replying to your original wondering about the need for --noreplaygain. That command line parameter is there to make the encoding faster by preventing lame from computing a track gain for the file. If you don't care about ReplayGain, calculating the gain values is a waste of processing power. If you do care about ReplayGain, calculating only the track based values is most likely a waste of time. It's better to let foobar2000 calculate both track and album based values once encoding is done. And not only is foobar2000's scanner more optimized and faster, it also offers several advanced options people may like.
The -S is there also for performance reasons. It tells the encoder it doesn't need to waste any cycles printing progress/histograms to the non-existing console screen that no one can even see.
System hang. The file progress bar increases, but the files being encoded with foobar2000 never changes, and I never see the elapsed time, estimated time, encoding speed, and the 'pause" and "abort" buttons never appear.
You keep describing what the problem looks like in Foobar2000 and ignore the suggestion to test Helix MP3 encoder in the terminal. Start encoding one relatively large WAV file (e.g. merge songs from the same album into one WAV file) and describe what you see. The encoder outputs its own status report with various counters.
I planned on trying this actually, it's just that new compiles keep coming in, so I tried them with my current encoding setup with foobar2000, that's all.
I've managed to compile the binary using visual studio 2022, it runs quite slow at my env(about 1/3 speed compared to clang version), but you can test if it will hang your system @KevinB52379 .
This version works perfectly too. It's a little slower than the clang version you uploaded a few days ago, but it doesn't cause that system hang!
@JoshuaChang - so far your two binaries have worked as expected on my system, thank you!
System hang. The file progress bar increases, but the files being encoded with foobar2000 never changes, and I never see the elapsed time, estimated time, encoding speed, and the 'pause" and "abort" buttons never appear.
You keep describing what the problem looks like in Foobar2000 and ignore the suggestion to test Helix MP3 encoder in the terminal. Start encoding one relatively large WAV file (e.g. merge songs from the same album into one WAV file) and describe what you see. The encoder outputs its own status report with various counters.
I've managed to compile the binary using visual studio 2022, it runs quite slow at my env (about 1/3 speed compared to clang version), but you can test if it will hang your system
Good to know. There are no longer many options that can cause the issue you are facing. I think antivirus or other security product that scans or sandboxes executables is the only thing that can do this. The converter in foobar2000 uses very low priority by default and you said you haven't increased it. These encoders don't touch priorities so they do their tasks with leftover cycles. Memory consumption is no different between compiles.
You must have some high priority process(es) running on the same core as the UI processes and steal all the processing power from the UI operations. Or a sandbox goes haywire and consumes all the system memory. Swapping will make machine slow even with SSD.
Hi @Case - I can provide some more information if you'd like.
1. I use AVG Internet Security as my security suite. In AVG I have excluded my foobar2000 directory (I use foobar in portable mode). At one point, I even disabled realtime protection before encoding to see if this helped, nothing changed. Would you like me to try uinstalling AVG?
2. As I stated, I have an HP Pavilion with AMD Ryzen 7 5700g, and I'm using the integrated graphics. I cannot install a dedicated graphics card as the system is limited to a 180 watt PSU and the motherboard and power supply use proprietary connections. My system also has 32GB DDR4 3200 RAM (this is the max capacity and the RAM is matching). I'm using a 1TB Samsung 980 SSD (PCIe Gen3).
3. As stated, I do use a screen magnification program called Zoomtext, and I thought for sure this was the culprit, but even when this program is shut down, I still have these issues.
4. I do use a program called Process Lasso - this program is supposed to prevent the system from slowing down. Now that I think about this, maybe I should try uninstalling this to see if this is the culprit too.
P.S. I do think it's interesting though that no other encoders with foobar cause this issue, don't you? Or that Joshua's build and your 32 bit build work as expected.
Last post by JoshuaChang -
I've managed to compile the binary using visual studio 2022, it runs quite slow at my env(about 1/3 speed compared to clang version), but you can test if it will hang your system @KevinB52379 .
Last post by Case -
Good to know. There are no longer many options that can cause the issue you are facing. I think antivirus or other security product that scans or sandboxes executables is the only thing that can do this. The converter in foobar2000 uses very low priority by default and you said you haven't increased it. These encoders don't touch priorities so they do their tasks with leftover cycles. Memory consumption is no different between compiles.
You must have some high priority process(es) running on the same core as the UI processes and steal all the processing power from the UI operations. Or a sandbox goes haywire and consumes all the system memory. Swapping will make machine slow even with SSD.
Last post by KevinB52379 - @Case - Thanks for this compile, but unfortunately, same results. System hang. The file progress bar increases, but the files being encoded with foobar2000 never changes, and I never see the elapsed time, estimated time, encoding speed, and the 'pause" and "abort" buttons never appear. The only thing that changes is the progress bar. It didn't take over an hour to encode like all the other slow compiles...but it was no where near as fast as @JoshuaChang version. His version encodes over 5,000 flac files in under 9 minutes with no system hangs or slowdowns.
Last post by jakedean22 -
yeah absolutely, appreciate your time i will try look at BitDefender as the culprit, gives me something to look into as before i wasnt sure what it was. thanks man.
