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: xHE-AAC : The Death of OPUS?
Last post by sld -
The state of lossy music encoding is disheartening. Breakthroughs for the benefit of humanity rather than for profit, such as Vorbis and Musepack, faded before reaching an apex because the authors changed the priorities for some reason. LAME also stalled. Yet killer samples to illustrate the flaws are still here. Some audiophiles with coding skills who patched psychoacoustic models disappeared. Dear visionaries who are good at math, has your mojo dried up, swallowed up by age, illnesses, streaming services and the petty bourgeois swamp? Or are all your efforts now focused on improving hash functions and quantum-resistant cryptography? It seems that only @bryant is still kicking with the development of lossless WavPack, although we recently discussed how to refine its hybrid mode. And QOA, the only fresh lossy codec in recent times, gains no traction as if the author released it only to prove the idea of doing better than Vorbis, hoping that Public domain license would encourage others to continue the undertaking.
Developers are not robots or isolated nerds/geeks.
They have lives and families. Life (and regrettably death) happens to them.
These codecs are their creation and the fruit of their efforts. If they can no longer sustain the efforts or are no longer around on earth, the right thing to do with one's hyperpassion for codecs is to pick up the skillsets where they left off and continue investing the same efforts they made. Not make a point of scolding them at every forum opportunity.
2
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -
By the way, just to add to the above... I know it can be adjusted manually but it would be nice if it can "auto scale" so when people download my Darkone tweak theme, they don't have to do that.
It's not a scaling issue.

Either I use 'fractional' pixels and then people complain that the spacing between the bars is uneven; or I use 'full' pixels and you get a trailing space because the total width of (bar count x bar width) is less than the available width of the component. Damned if I do and damned if I don't.

The only option left is to stick with 'full' pixels and to divide the unused space left and right of the bars. And I'm sure someone will complain about that too.
3
Support - (fb2k) / Re: the seekbar is working wrong
Last post by Aliaksandr_by -
may be, I think problem is with foo_out_wasapis


foo_asap
foo_audiomd5
foo_cuesheet_creator
foo_deaf
foo_dsd_converter
foo_dsd_processor
foo_dsp_utility
foo_input_dvda
foo_input_ffmpeg
foo_input_sacd
foo_input_tta
foo_openlyrics
foo_openmpt54
foo_out_asio
foo_out_wasapis
foo_playcount
foo_renamer
foo_skip
foo_sqlite
foo_uie_albumlist
foo_uie_sql_tree
foo_vis_spectrum_analyzer
6
FLAC / Re: FLAC - stored main chunk length differs from written length
Last post by bryant -
On to the wrong.wav
...
As far as I can tell,
flac, TAK and OptimFROG reject it
...
Add refalac to the list, and thanks Bryant for the attention.
I have fixed this in WavPack with this commit by rejecting such WAV files.

While I was fixing this I looked at other formats and see that CAF also has this redundancy and, unlike WAV, the format documentation clearly states that having unpacked samples is valid and gives a detailed example of the 24-bit sample in 32-bit container case (values are shifted "up" for both BE and LE).

I created a few sample files like this and found that WavPack handled them fine, except for not verifying that the proper bytes were zeroed. I tried other programs and FFmpeg and Audacity (via libsndfile) both fail on these files. The only other program that handled them correctly was (no surprise) @nu774 's Foobar2000 CAF component. Good job!

If anyone is interested, I can attach them to the thread.
 
10
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by Markuza97 -
potential of this encoder

What potential? Nobody is going to use this.
LAME's last quality update was over 10 years ago. Developers squeezed everything they could from MP3.
It is mature and stable encoder, tested by many experienced members here.
If you believe people will suddenly change to Helix you are wrong.

All I can see in this thread is developers wasting their time on something useless only to get yelled at in return.

We need golden eared peoplle like you to find out if there is a way to tell them apart.

lol'd :)