1
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.
2
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by fooball -3
Site Related Discussion / Re: keep getting: An Error Has Occurred
Last post by fooball -That's a bit too much going the other way.And your rationale is...?
But whatever, this is getting off topic.Only if you want to stifle debate.
4
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by KevinB52379 -When I use Case's version of Helix Win32 build, I get about 1000x to 1300x realtime encoding those same files.
I've tried everyone's 64 bit builds and 32 bit builds with the same results....
Except for Case. Does he put some magic in his compile?? LOL
You are correct, I have a Zen3 8 core processor that can handle 16 threads (AMD Ryzen 7 5700g @ 3.8ghz base...it has integrated graphics and the system has 32GB of DDR4 RAM and 1tb nvme gen3 SSD (Samsung 980 1tb).
I'm willing to try any other builds if anyone wants me to, but so far, Case's version is the only one that seems to work properly with fast encoding speeds and doesn't cause the system to basically hang...with his version the system does slow down, but it still responds. And encoding speed remains fast and consistent with full cup utilization. With everyone else's builds the cpu utilization never reaches 100% even though I have foobar encoding settings set to automatic for thread count and default priority.
Oh, I have the latest chipset drivers and graphics drivers from AMD.
Sorry to be so wordy but just trying to provide info.
5
Support - (fb2k) / Re: Foobar 2.1.4 Crash
Last post by Case -6
3rd Party Plugins - (fb2k) / Re: foo_chacon
Last post by MarkP -Wishing a 64-bit version will be available.
I second this
Thirded - would love to have a 64bit version.
7
Support - (fb2k) / Foobar 2.1.4 Crash
Last post by jakedean22 -i was using 2.1.3 after upgrading my portable installation from 1.6 i thought it was time to try the newest version. My music is stored on a network drive and whenever i was changing tags or moving files it would randomly crash. i could never figure out what specifically. i ignored it, updated to 2.1.4 and within 5 mins crashes again. i have had about 4 tonight. i want to stay on 2k but i can only stop the crashes when using 1.6.
i updated over the top of my existing installation but also tried a completely fresh one, that didnt work either. i searched other crashes and saw turning off hardware acceleration was an option, turns out mines already off. please see attached crash, if someone can interpret the violation i would be very appreciative. i also send the logs within Foobar.
8
MP3 / Re: Low bitrate MP3 (+ unsupported bitrates)
Last post by Kraeved -Now i tried GXLame and Helix but they did not give ~12kbps.
gxlame.exe --abr 12 -h in.wav out.mp3
Code: [Select]
GXLame-t5
CPU features: MMX (ASM used), SSE (ASM used), SSE2
Using polyphase lowpass filter, transition band: 5379 Hz - 5513 Hz
Encoding history.wav to history.mp3
Encoding as 11.025 kHz single-ch MPEG-2.5 Layer III (14.7x) average 12 kbps qval=0
Frame | CPU time/estim | REAL time/estim | play/CPU | ETA
324/324 (100%)| 0:00/ 0:00| 0:00/ 0:00| 56.994x| 0:00
8 [169] *********************************************************************
16 [138] *********************************************************
24 [ 13] ******
32 [ 4] **
40 [ 0]
48 [ 0]
56 [ 0]
64 [ 0]
-------------------------------------------------------------------------------
kbps mono % long switch short %
12.3 100.0 90.1 5.6 4.3
Writing LAME Tag...done
ReplayGain: -0.2dB
9
Site Related Discussion / Re: keep getting: An Error Has Occurred
Last post by 2012 -The security reason to use VPN went away with HTTP... and what's left is if you want to conceal your own IP address for nefarious reasons.
That's a bit too much going the other way. But whatever, this is getting off topic.
10