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
82
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by maikmerten -
One thing I've been pondering for a future release is improving hmp3's ability to serve as a web-radio encoder. MP3 still is very much in use there for maximum compatibility. Also, it seems most radios use CBR (meh) - and CBR is pretty robust in Helix.

Currently, hmp3 buffers quite a lot of data before flushing output to file or stdout: The encoding application will wait for ~126 KB before triggering a flush (variable "bs_trigger" in tomp3.cpp). For 128 kpbs streams, that's about 10 seconds of delay, for low-bitrate streams like 32 kbps (for that authentic dialup multimedia experience), that's about 40 seconds of delay.

For web radio, I guess it's best to flush encoded frames directly. This is trivial to fix, and I consider flushing packets directly if the output is stdout...

@Case Any opinions if "always quick flush to stdout" makes sense - or should this be behind a switch ("-QF" for quick flush or "-LD" for low delay....)

Flushing every packet (to stdout, to file can be another story) doesn't seem to impact performance significantly, so I wonder if a switch makes any sense at all here.

Code: [Select]
time hmp3 test.wav - > test.mp3

(Duration of test.wav: 01:15:01.00)


Flush on every packet:

real 0m8,593s
user 0m8,467s
sys 0m0,108s

real 0m8,591s
user 0m8,445s
sys 0m0,138s

real 0m8,615s
user 0m8,448s
sys 0m0,128s


Flush every ~126 KB:

real 0m8,594s
user 0m8,515s
sys 0m0,072s

real 0m8,666s
user 0m8,565s
sys 0m0,092s

real 0m8,571s
user 0m8,457s
sys 0m0,112s
84
3rd Party Plugins - (fb2k) / Re: foo_vis_text (Text Visualizer)
Last post by Swi -
I'm not good (bad) figuring it out in CSS and Javascript. Can someone else implement the above suggestion? (How add in window "Text Visualizer" streaks/strips with: slider playback and slider volume, add fadness/boldness to/for fonts .artist, .track; make window with frame "Text Visualizer" transparents).
85
Lossless / Other Codecs / Re: HALAC (High Availability Lossless Audio Compression)
Last post by Air KEN -
@Hakan Abbas

Sorry. Encoding failed.

wav to halac
flac to halac
foobar2000 v2.1.5 x64
CPU: AMD Ryzen 7 7840HS

Settings are as follows.

Encoder file: C:\Encoder\HALAC\HALAC Version 0.2.9\HALAC_ENCODE_V.0.2.9_x64_avx.exe
Extension: halac
Parameters: %s %d -mt=8 -fast -ow
Format is: Lossless
Highest BPS mode supported: 16bit
Do not convert in multiple threads

HALAC Decoder (foo_input_halac) v0.1.3 is installed.
86
3rd Party Plugins - (fb2k) / Re: foo_vis_text (Text Visualizer)
Last post by pqyt -
Hello pqyt and Others. Cans/mays add in window "Text Visualizer" streaks/strips with: slider playback and slider volume, add fadness/boldness to/for fonts .artist, .track; make window with frame "Text Visualizer" transparents, and add show via/through regular expressions what be (to) take .artist, .track from the filename? For example what be (to) take from file name (from “Artist - Title1”), Artist and title via/through regular expression "(.+) - (.+)".
The plugin uses HTML and a Chromium-based engine. Any styling and visualization can be done with CSS and Javascript. The same goes for regex. Javascript is your friend. Maybe another user with better CSS/Javascript skills can help you. And for full control have a look at foo_jscript_panel3.
87
3rd Party Plugins - (fb2k) / foo_tag_normalizer - Tag Normalizer
Last post by Just_Addict -
I probably need to direct this at you @Case.

I've searched hi and lo but search isn't my best friend...

Is there a topic for general recompile requests?

I'm asking because I found a recompile on https://foobar.hyv.fi for Tag Normalizer, and for the life of me can't find any thread dealing with this one. Since it was listed there I asdumed it would support Dark Mode (even though it's not mentioned on the overview page). The results dialog still comes up in Light Mode, I assume that's because it's not specifically mentioned to support Dark Mode.

At any rate, if there's a reason or need to update/recompile it again, could Dark Mode please be added?
89
Lossless / Other Codecs / Re: HALAC (High Availability Lossless Audio Compression)
Last post by Hakan Abbas -
@Hakan Abbas
Please tell me the settings for foobar2000 convert.

HALAC_ENCODE_V.0.2.9_x64_avx.exe
HALAC_ENCODE_V.0.2.9_x64_sse2.exe

------
Encoder: Custom
Encoder file: halac_encode.exe
Extension: .halac
Parameters:

Bit depth
Format is: Lossless
Highest BPS mode supported:

Option switches
compression ratio:
speed: Normal or Fast
------

Thanks.

I guess Foobar's Lossywav support is not complete. And it seems to remove the metadatas and then process them.
X
90
Lossless / Other Codecs / Re: HALAC (High Availability Lossless Audio Compression)
Last post by Hakan Abbas -
Could you release a new version with a "-high" argument which gets a bit higher compression ratio than default but 25-50% slower compression and decompression speed?
[attach type=image]30512[/attach]
The graph above shows the change of compression ratio since the first version of HALAC. HALAC is a speed-oriented study and the last thing I want to compromise on speed is. The lossless compression rate of audio data is really limited in most cases.

SQUEEZE CHART is an archive that also contains different types of music used in audio compression tests. It gives an idea in a general sense. Since the first version, there has been an improvement of about 1% in the compression ratio at the same speeds (encode has been slightly faster). At extremely high speeds, this is really not bad. Depending on the current situation, it is a little difficult to predict how much further progress can be made.

HIGH mode has been requested from different people before. I will focus on the compression ratio in later versions. Because I've already mentioned that there is a little more space in this regard.

I started to get interested in the compression ratio with version 0.2.6. However, I had to enter the Player and DLL topic in accordance with the incoming requests. Now, as soon as I have time, I am trying to complete the new dynamic library I have developed for HALAC in a flexible and error-free way. Changes are also made to the file structure and working style in accordance with incoming requests.
Can you post the new chart, please? With 0.2.8 and 0.2.9!

The difference between Version 0.2.8 and 0.2.9 is structural. Therefore, there is not much difference in terms of speed or compression rate. There may be some developments in this area after 0.3 version. In the meantime, the uncomplicated frame size is reduced from 1 MB to 512 kb.