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.
Topic: lossyWAV 1.4.2 Development (was 1.5.0) (Read 112528 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: lossyWAV 1.4.2 Development (was 1.5.0)

Reply #150 –
@Nick.C What's our next step here? What should be improved here, LossyWAV or Vorbis?
• Join our efforts to make Helix MP3 encoder great again
• Opus complexity & qAAC dependence on Apple is an aberration from Vorbis & Musepack breakthroughs
• Let's pray that D. Bryant improve WavPack hybrid, C. Helmrich update FSLAC, M. van Beurden teach FLAC to handle non-audio data
 

Re: lossyWAV 1.4.2 Development (was 1.5.0)

Reply #151 –
Quote from: Kraeved on
@Nick.C What's our next step here? What should be improved here, LossyWAV or Vorbis?
In my opinion Vorbis should be fixed to properly handle chunks of odd length, in line with the Microsoft/IBM RIFF specification, based on the EA/Commodore IFF specification that preceded it.

A quick and nasty solution would be for lossyWAV to increase the length and stated size of the FACT chunk, if required, to ensure that it is always even, however this would perpetuate support for applications that don't handle WAV files correctly.
lossyWAV -q X -a 4 -s h -A --feedback 2 --limit 15848 --scale 0.5 | FLAC -5 -e -p -b 512 -P=4096 -S- (having set foobar to output 24-bit PCM; scaling by 0.5 gives the ANS headroom to work)