Opus 1.1a BABYEATER build Options

[NullC]

Ever mindful of the world's population problems, the Opus development team is excited to present a new highly experimental build of Opus which is expected to eat 100% more babies than prior editions. It is also expected have (potentially) improved transient handling performance:

https://people.xiph.org/~greg/opus-tools_ba...ater-deluxe.zip (Edit: replaced with updated version, see below)

What this does is adapts the frame-size dynamically based on transient analysis prior to encoding. Leave the opus-tools framesize knob alone (in this test build it controls the amount of look-ahead used for the analysis, and 60ms is the default and only tested value).

It would be super-helpful to compare this with the regular 1.1 alpha at various rates and point us to any interesting results you find (e.g. where it does obviously worse or better, or where it catches fire and/or eats household pets instead of babies). Obviously you shouldn't be encoding your music archives with this stuff yet.

This post has been edited by NullC: Feb 13 2013, 01:07

[Gainless]

That's nice to hear, would be great if it could get fixed in the next version

[jmvalin]

That's nice to hear, would be great if it could get fixed in the next version

I just checked in a fix in git. It's basically a second (simplified) frequency-domain transient detector that catches a few of the transients that are missed by the main detector. In the case of the transient at 7.5s in your file, the reason it wasn't caught by the main detector is that the transient was in the mid-range, but drowned in HF noise. Anyway, until I can get you actual builds, here's what it sounds like with the fix at 128 kb/s and 192 kb/s.

Attached File(s)

 Muse_128_kbps.wav ( 3.06MB ) Number of downloads: 64
 Muse_192_kbps.wav ( 3.06MB ) Number of downloads: 45