TheoraTodo: Difference between revisions

From XiphWiki
Jump to navigation Jump to search
No edit summary
(→‎1.2: add bits from my todo list)
 
(2 intermediate revisions by 2 users not shown)
Line 2: Line 2:


= libtheora reference implementation =
= libtheora reference implementation =
== 1.2 ==
* (done) Activity masking (greatly improved perceptual quality)
* (done) Rename speedlevel 2 to 3 and provide a new speedlevel 2
* (done) ARM4/6/7/Neon assembly support
* (done) C64x+ support
* Fix SAD-for-SATD in intra analysis from Ralph's speed level patch.
* Testing testing testing
* Decoder speedups (improvements to ARM/c64x platform support)
* Encoder speedups (additional short-cutting in fast modes)
* Temporal RDO
* Quantizer matrix improvements (Shift the range up to make higher rates achievable)
* Mode selection improvements (split 3qi roles?)
* Codebook re-optimization (Greg has code for this; waiting for other changes to settle)
* Review open tickets
* Review patches from the major distros
== 1.1 ==
* complete Ogg mapping description in the spec
* update RTP mapping spec
1.1.0 was released on 2009-09-24.


== 1.0 ==
== 1.0 ==
Line 17: Line 42:


1.0 was released on 2008-11-03.
1.0 was released on 2008-11-03.
== 1.1 ==
* complete Ogg mapping description in the spec
* update RTP mapping spec
1.1.0 was released on 2009-09-24.
== Theora II ==
* see [http://web.mit.edu/xiphmont/Public/theora/demo2.html Theora: The push for 1.0, Thusnelda project update 20080320] ('''beyond 1.0 spec''' section) and [http://web.mit.edu/xiphmont/Public/theora/demo.html Theora "the push for 1.0" update]: xiphmont articles on theora future. See also other [http://advogato.org/person/rillian/diary/109.html Theora development articles]
<del>According to the [http://xiph.org/minutes/2008/theora-meet-20080401.txt 2008-04-01 Theora meeting] ''that's on the six-month timeframe''.</del>


= Application Support =
= Application Support =
Line 46: Line 60:
* write a stand-alone output encoder plugin that does best-practices export
* write a stand-alone output encoder plugin that does best-practices export
* do a gui transcode tool, a little like ffmpeg2theora, but pulling from the native quicktime decoders and writing out theora + vorbis/speex. Must have a drag and drop interface with sensible quality presets, metadata insertion. Bonus points for integrated stream sourcing and [http://wiki.creativecommons.org/CcPublisher upload] to various free sharing sites with appropriate CC licensing.
* do a gui transcode tool, a little like ffmpeg2theora, but pulling from the native quicktime decoders and writing out theora + vorbis/speex. Must have a drag and drop interface with sensible quality presets, metadata insertion. Bonus points for integrated stream sourcing and [http://wiki.creativecommons.org/CcPublisher upload] to various free sharing sites with appropriate CC licensing.
== Misc ==
* prove wrong / obsolete all those [http://lwn.net/Articles/261694/ 1], [http://web.mit.edu/xiphmont/Public/theora/demo.html 2] "Theora is crap" claims


== Dynamic/variable keyframing ==
== Dynamic/variable keyframing ==

Latest revision as of 09:56, 29 March 2011

This is the todo list for the theora project. If you're interested in helping out please try one of the ideas below, and coordinate with us on the mailing list or irc.

libtheora reference implementation

1.2

  • (done) Activity masking (greatly improved perceptual quality)
  • (done) Rename speedlevel 2 to 3 and provide a new speedlevel 2
  • (done) ARM4/6/7/Neon assembly support
  • (done) C64x+ support
  • Fix SAD-for-SATD in intra analysis from Ralph's speed level patch.
  • Testing testing testing
  • Decoder speedups (improvements to ARM/c64x platform support)
  • Encoder speedups (additional short-cutting in fast modes)
  • Temporal RDO
  • Quantizer matrix improvements (Shift the range up to make higher rates achievable)
  • Mode selection improvements (split 3qi roles?)
  • Codebook re-optimization (Greg has code for this; waiting for other changes to settle)
  • Review open tickets
  • Review patches from the major distros

1.1

  • complete Ogg mapping description in the spec
  • update RTP mapping spec

1.1.0 was released on 2009-09-24.


1.0

During TheoraMeeting200804 it was stated that before 1.0, the following should happen:

1.0 was released on 2008-11-03.

Application Support

Easy Transcoding on Windows

It's difficult for some people to create theora files outside the command line. We need a simple tool that does drag-and-drop transcoding, with a gui for metadata and license marking, and some simple cleanup like crop/scale/rotate and color adjustment. This could be just a wrapper around ffmpeg2theora.

Albeit technically it would be possible (and simple) to do GUI wrapper for ffmpeg2theora it may be wiser to write a completely new application which uses DirectShow to decode the given media file. This way the encoder wouldn't have to ship with evil patented decoders and still can transcode any source the computer can play in e.g. Windows Media Player. - Maikmerten 12:06, 30 July 2007 (PDT)

Quicktime export

It is important that content creators be able to easily create theora videos.

  • write a stand-alone output encoder plugin that does best-practices export
  • do a gui transcode tool, a little like ffmpeg2theora, but pulling from the native quicktime decoders and writing out theora + vorbis/speex. Must have a drag and drop interface with sensible quality presets, metadata insertion. Bonus points for integrated stream sourcing and upload to various free sharing sites with appropriate CC licensing.

Dynamic/variable keyframing

Setting keyframes dynamically could increase both quality and compression. Have a look at this: [1].

That paper is not really applicable any more. Libtheora tracks an estimated cost of coding a frames as an intra and will switch if its expects a net win. In multi-pass encoding we could use this data for optimal placement (via Dijkstra over the directed graph formed by all possible keyframe constraint windows in all contiguous segments where the estimated cost of using a keyframe is positive), although preliminary testing didn't show much benefit. This may be due to accuracy problems in the current estimates.