Jump to navigation Jump to search
Opus release planning
This page is for organizing todo items for the initial opus release. Some items would best be dribbled out after the initial release while others are more release critical (tools binaries, test vectors, examples)
Release management / marketing work
- Windows binaries
- Mac binaries
- Get binary packages of opus and opus-tools working for major distros
- Ogg Opus test vectors
- More 'brochure' level text about Opus and its advantages
- More images/graphs/art for the site (PEAQ sweeps?)
- Overhaul of the comparative page
- demo pages
- static demo with music, voice; like this one
- remote control encoder (oneman)
- emscripten decoder
- A recording of a remote jamming event (bemasc)
- update Greg's CELT try-tool for libopus
- Son-of-Monty-CELT-demo (An in-the-weeds technology demo)
- Improved documentation (e.g. an API overview doc that isn't a doxygen dump), "idiots guide to using libopus"
- Client applications beyond Firefox, esp VLC and foobar2000. See OPUS TODO for a list.
- fix remaining fixed point overflows (gmaxwell/jmspeex)
- Make opus_custom_demo read/write little endian on BE hosts.
- Boring standard makefiles for many systems (VMS too? haha)
- Oggdropish GUI for opusenc
- Additional tools (validator, gain, udp streaming example)
- libao for opus-tools
- LP-mode CBR (boundary conditions, iterations, harmonic average)
- Fix -fstack-protector-all (e.g. mingw32) or remove it
- MIN32/MAX32 used stupidly in celt/ where the arguments evaluated twice.
- why does --speech + 24kbit make opus tools code stereo where its mono without speech?
- make test_opus_encode test more stupidly low rates.
- random duration for the first/last frame in opus-tools
- short block high rate waste in mdct mode
- (mdct mode) silence detection
- Prod the second implementation (Tim's) into something (quasi-)releasable