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
Lossless / Other Codecs / Re: Tested: Lossless decoding speed, multithreaded - and fast verification
Last post by ktf -@ktf, of course there is nothing wrong with the file? The blame is squarely on ffmpeg?I see nothing wrong with the file. Maybe the problem is that it consist of a single block?
* ffmpeg -threads 1 decodes nearly twice as fast as reference flac at -5, but several times slower at low block sizesOf course I dove into that, because if FLAC can be twice as fast, that would be great! But I cannot reproduce, not on Linux nor Windows, not on SSD nor ramdisk. Can you check your results and see whether a different way of collecting times gives you the same result?
3
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, went down to 16 kbps, and ended with 12 kbps MP3 and AAC SBR, which sound not just intelligible, but satisfying. What can Opus offer here?
4
Support - (fb2k) / Re: foobar2000 for Mac: bugs & wishes
Last post by koupa -The ability to change between playlist sidebar and album list. I use F2K "for ever" in windows and now it seems another program. Almost crippled.
Great upgrade the 2024-04-26. The album list does the work.
Now for DSD support.
5
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.
6
Opus / Re: Opus v1.5.2
Last post by Marsu42 -Why is there such a huge difference in size between the encoder (676 352 bytes) and the decoder (5 625 344)?
It's at least partly due to the LACE/noLACE postprocessing for low bitrate voice.
"Building with --enable-osce increases the binary size by about 1.6 MB, roughly 0.5 MB for LACE and 1.1 MB for NoLACE. " https://opus-codec.org/demo/opus-1.5/
7
Uploads - (fb2k) / Re: foo_converter.dll.cfg
Last post by marc2k3 -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.
8
Support - (fb2k) / Re: foobar2000 for Mac: bugs & wishes
Last post by Guildencrantz -9
Support - (fb2k) / Re: Playback ERROR in v2.2 preview 04-26, exclusive mode
Last post by Peter -What exact system (Windows version, audio device) is this? I know what changes broke this but can't reproduce.
10
Lossless / Other Codecs / Re: HALAC (High Availability Lossless Audio Compression)
Last post by Hakan Abbas -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 ...).