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
CD Hardware/Software / CD rip has numerous timing problems
Last post by graveller39 -
hi folks,

I have a CD I've been trying to rip, but it was taking forever with EAC.  I also tried CueRipper and finally used Roxio Easy CD & DVD Burning to get what looks like a successful rip (sounds ok), but it took at least a couple of hours.

When I tried EAC, I used burst mode, as secure mode just wasn't going to do it.  I aborted after three tracks, but the log file indicated numerous timing problems - no suspicious positions which is what I'd expect if the disc were damaged.  The disc looks pretty good and plays without any audible issues on my CD player.

Any ideas what might be causing this or if there's any way to get a rip I can confirm as error free?
3
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by KevinB52379 -
Also not working here "An error occurred while writing to file (The encoder has terminated prematurely with code -1073741515 (0xC0000135); please re-check parameters"
Btw. did you just set the flag -flto? I could do one with gcc.

Edit:  Did one with gcc flto. Roughly the same speed here as without.

I've managed to reproduce the problem under my vm env, my fault for not including the -static in LDFLAGS, here's the re-complied version.

FINALLY!  A version of Helix MP3 that converts fast besides Case's version!

This version DOES NOT hang up my system in a weird way and cause foobar to be basically nonresponsive!

ALSO - FASTEST encoding speed yet converting from internal SSD to internal SSD at 2500x encoding speed!

This version works, yay!
5
Support - (fb2k) / foobar2000 2.1.4 crashes during ReplayGain scan
Last post by cyborg -
Foobar2000 2.1.4 crashes every time I execute ReplayGain scan on a file in my PC. First time I noticed the same problem when I updated foobar2000 2.1 to 2.1.3. When I downgraded fb2k back to 2.1 the problem disappeared. Same thing happened with 2.1.4. I made a fresh portable install of fb2k 2.1.4 and executed the ReplayGain scan, fb2k crashes every time. I included the crash dumps which were generated by the portable fresh install of 2.1.4 version. I have tested the ReplayGain scan on mp3, FLAC, Musepack, Opus, Ogg Vorbis and WavPack files, it doesn't seem to be dependent on file format.
6
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by punkrockdude -
If anyone is interested

Linux amd64/x86_64 Glibc 2.39
Clang 18, O3 LTO PGO

Code: [Select]
CC=clang # was gcc

#CFLAGS_COMMON=-O3 -fprofile-generate=/tmp/ -c -I$(SRC_PREFIX)/pub -DIEEE_FLOAT -D_FILE_OFFSET_BITS=64 # 1st run
CFLAGS_COMMON=-O3 -flto -fprofile-use=/tmp/profile.profdata -c -I$(SRC_PREFIX)/pub -DIEEE_FLOAT -D_FILE_OFFSET_BITS=64 # 2nd run

#LFLAGS=-lm -lstdc++ -O3 -fprofile-generate=/tmp/ # 1st run
LFLAGS=-lm -lstdc++ -O3 -flto -fprofile-use=/tmp/profile.profdata # 2nd run
8
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by JoshuaChang -
Also not working here "An error occurred while writing to file (The encoder has terminated prematurely with code -1073741515 (0xC0000135); please re-check parameters"
Btw. did you just set the flag -flto? I could do one with gcc.

Edit:  Did one with gcc flto. Roughly the same speed here as without.

I've managed to reproduce the problem under my vm env, my fault for not including the -static in LDFLAGS, here's the re-complied version.
9
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Wombat -
Also not working here "An error occurred while writing to file (The encoder has terminated prematurely with code -1073741515 (0xC0000135); please re-check parameters"
Btw. did you just set the flag -flto? I could do one with gcc.

Edit:  Did one with gcc flto. Roughly the same speed here as without.
10
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by Defender -
@pqyt

First of all thank you for this excellent tool. I can (almost) get rid of 18 instances of PeakMeter Spectrum by substituting them with 6 instances of yours.
 
Since peakmeter is working perfectly in 100% windows scaling, I moved on to testing this plugins behavior with different windows scaling and encountered problems in all scaling (except 200% and 300%). Happens both in horizontal and vertical peakmeters. The rest of this message will only address the vertical peakmeter (without axe legends).

See the attached jpg's that also displays some debug information. I also included the code I use to determine the panel width for the number of channels and windows scaling.

The following text looks quite complicated but is more easy if you look at the jpg.
Based on how your plugin behaves/displays I guess you are calculating barwidth (vertical peakmeter) by first determining the total gauge gap by first multiplying the (unscaled) configuration value gauge gap times the number of channels (bars) to be displayed minus 1. Then I guess you scale this total gauge gap, subtract that value from the panelwidth and divide the result by the number of channels to find barwidth per bar. By scaling a calculated unscaled total gauge gap this value will be to high (except winth 200% and 300%), and subsequently your barwidth/barheight will be lower than I intended.
When you display bars, you apply single gauge gaps between channels leading to pixels that are left over and are distributed to the left of leftmost bar and to the right of rightmost bar.

In the attached jpg I included my scaled total gauge gap is 14 and I'm pretty sure you use 15.75 either truncated to 15 or rounded up to 16. Which leads to the behavior I described above.

Code: [Select]
// UNSCALED
$ifgreater($get(channels),7, $puts(px.h_bar, 13), // 13 max to display Above logo with Top plugin disabled
$ifgreater($get(channels),5, $puts(px.h_bar, 13), // 13 max to display Above logo with Top plugin enabled
$ifgreater($get(channels),4, $puts(px.h_bar, 14), // 15 max to display Above logo with Top plugin enabled
$ifgreater($get(channels),3, $puts(px.h_bar, 16), // 20 max to display Above logo with Top plugin enabled
$ifgreater($get(channels),2, $puts(px.h_bar, 21), // 27 max to display Above logo with Top plugin enabled
$ifgreater($get(channels),1, $puts(px.h_bar, 21), // 41 max to display Above logo with Top plugin enabled
$puts(px.h_bar, 32) // 83 max to display Above logo with Top plugin enabled
))))))

$puts(mx.w_bar,         6) // Unscaled - Single bar width - Desired unscaled bar width for PeakMeter vertical

$puts(wh_gauge_s,       1) // Unscaled - Single gauge gap - Desired unscaled gauge gap
$puts(wh_gauge_t,       $mul($sub($get(channels),1),$get(wh_gauge_s))) // Unscaled - Total  gauge gap

$puts(px.h_std,         $add($get(wh_gauge_t), $mul($get(px.h_bar),$get(channels)))) // Unscaled - Panel height needed - PeakMeter horizontal
$puts(mx.w_std,         $add($get(wh_gauge_t), $mul($get(mx.w_bar),$get(channels)))) // Unscaled - Panel width  needed - PeakMeter vertical


// SCALED
$puts(wh_gauge_s,       $muldiv($get(wh_gauge_s),%scale%,100)) // Scaled - Single gauge gap - truncated
$puts(wh_gauge_t,       $mul($sub($get(channels),1),$get(wh_gauge_s))) // - Total  gauge gap - calculation based on truncated scaled single gauge gap / NOT BASED BY SCALING UNSCALED TOTAL GAUGE GAP

$puts(px.h_bar,         $muldiv($get(px.h_bar),%scale%,100)) // Scaled - Single bar height - truncated - PeakMeter horizontal
$puts(mx.w_bar,         $muldiv($get(mx.w_bar),%scale%,100)) // Scaled - Single bar width - truncated - PeakMeter vertical

$puts(px.h_std,         $add($get(wh_gauge_t), $mul($get(px.h_bar),$get(channels)))) // Scaled - Panel height needed - PeakMeter horizontal - calculation based on truncated scaled single bar height / NOT BASED BY SCALING UNSCALED TOTAL BAR HEIGHT
$puts(mx.w_std,         $add($get(wh_gauge_t), $mul($get(mx.w_bar),$get(channels)))) // Scaled - Panel width  needed - PeakMeter vertical - calculation based on truncated scaled single bar width / NOT BASED BY SCALING UNSCALED TOTAL BAR WIDTH


In my opinion calculation should be as follows:
1) Scale the single gauge gap and store the result truncated in an integer.
2) Calculate total gauge gap by multiplying the value of 1) times the number of (channels minus 1)
3) Deduct from the panel width the value of 2) and width needed for 1/2 axe legends
4) Divide the value of 3) by the number of channels and store the result truncated in an integer (barwidth per bar)
5) ... continued with total leftover pixels and distribution to the left & right of the panel

I think the issue lies in 1) and 2). In my code it is the two lines under // SCALED.

Please investigate ...