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
Opus / Re: Opus v1.5.2
Last post by Kraeved -
It's at least partly due to the LACE/noLACE postprocessing for low bitrate voice.

Low bitrate voice? It reminds me of this topic where we were looking for a way to compress 11025 Hz 16 bit mono file (history.wav) with speech and some music in the background. We started with 24 kbps and ended with 12 kbps MP3 and AAC SBR, which sound not just intelligible, but satisfying. What does Opus have to offer here?
3
Lossless / Other Codecs / Re: HALAC (High Availability Lossless Audio Compression)
Last post by mudlord -
When my improvements are over, it can be a codec that everyone can use.

Yep. I tried explaining to Kraevad that sometimes up until that point, a project is not for everyone *or anyone* at all, and that its purely a prototype. Like I have some personal projects which still have things cooking or I don't feel are up to any sort of standard that I feel comfortable to be public, so things like widespread vectorization/threading or even GPU support are not there yet, so I stick to SSE4/AVX2/NEON/GL4.6 until that time comes, because I am more focused on getting things working *at all* rather than any semblance of widespread appeal.
5
Uploads - (fb2k) / Re: foo_converter.dll.cfg
Last post by marc2k3 -
Nope, you can't keep the old .cfg file with fb2k v2. As you've discovered, it will read data from these files if it finds them on startup but then nuke it when fb2k is closed.

It's quite possible you have other component .cfg files in your configuration folder and that's perfectly normal. When components are compatible with v1, they continue to use the old configuration files. Only components made exclusively for fb2k v2 have their settings saved in config.sqlite - and this obviously applies to foo_converter bundled with the latest versions.
6
Support - (fb2k) / Re: foobar2000 for Mac: bugs & wishes
Last post by Guildencrantz -
Another problem is that now there are two menu items both called Album List: one shows it in a separate window (naturally, I created a shortcut for it) and the other is responsible for the one living in the side bar. Now my shortcut only shows me the Album List in a separate window but does nothing to the one in the side bar (though it is shown in the corresponding menu item). I think that something should be done with this, though I’m not sure what exactly (renaming menu items probably? but how?).
8
Lossless / Other Codecs / Re: HALAC (High Availability Lossless Audio Compression)
Last post by Hakan Abbas -
@Kraeved; I have already mentioned that Player only works with Halac 0.2.7. Also, I did not specify this with an error message. For the next version, I will add this measure to both Decoder and DLL. OK.

Thank you very much for your great suggestions, Case. Such comments are really necessary.
Best option for API would be not to rely on filenames at all.
DLL/SO will not deal with file operations. OK.

And partial decoding is of course very important for realtime playback.
DLL/SE should only take memory address, frame number and data length. OK.

My component now includes parser for WAV, RF64, BW64 and W64 formats just in case such things pop out of HALAC so that it can play them.
DLL/SO should give us the necessary information such as header(channel count, bit rate...) and metadata. OK.

Oh yeah, and you should specify what calling convention the functions use.
This should be more important especially for Windows. OK.

I will add them in the next version. If I need to repeat, these are the usual problems in the software process and the solution can be produced quickly. However, I need to focus on what I need to focus on (speed, ratio, prediction, entropy ...).
10
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by maikmerten -
@Case thanks a lot for noticing and providing a fix, now pushed onto the dev-branch: https://github.com/maikmerten/hmp3/commit/4e16101b85cdd5171a85facaf3ea9be4327712da

@Replica9000 CTRL+C indeed is baked into the usual operating systems. It sends a signal to the executed program (SIGINT). Programs can choose to react in any way they deem fitting. With the recent changes, hmp3 chooses to stop encoding in a "graceful" manner.

The speed increase on the dev-branch most likely is from now compiling with link time optimizations (-lto flag).

Btw, here's hmp3 encoding my test CD album of choice:

Code: [Select]
real	0m9,585s
user 0m9,436s
sys 0m0,140s

And this is Ubuntu's Lame 3.100 binary decoding the resulting MP3 to WAV:

Code: [Select]
real	0m10,609s
user 0m9,297s
sys 0m1,288s

In real-time, hmp3 is faster *en*coding than Lame is *de*coding ;-)

(ffmpeg's MP3 decoder appears to be twice as fast)