Comments on: Schrödinger One Point Zero Point Zero http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/ Just another WordPress weblog Sat, 22 Nov 2008 09:44:03 +0000 http://wordpress.org/?v=2.2.2 By: Ben Schwartz http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-90 Ben Schwartz Sun, 24 Feb 2008 17:23:37 +0000 http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-90 admin: very interesting. I'll have to try it out. The next question is real-time encoding... admin: very interesting. I’ll have to try it out.

The next question is real-time encoding…

]]> By: Francesco Romani http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-87 Francesco Romani Sun, 24 Feb 2008 09:21:11 +0000 http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-87 admin: thanks, looks like an interesting starting point. I've still some perplexities (about stuff like headers handling and packing encoder output into container), but I'll dig a bit more into test code/source code before asking again. ;) I could send to you the address of the experimental(bzr) repo with my code if you like. admin: thanks, looks like an interesting starting point.
I’ve still some perplexities (about stuff like headers handling and packing encoder output into container), but I’ll dig a bit more into test code/source code before asking again. ;)
I could send to you the address of the experimental(bzr) repo with my code if you like.

]]> By: admin http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-85 admin Sun, 24 Feb 2008 00:56:18 +0000 http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-85 Francesco: testsuite/encode and testsuite/decode are the best (only?) starting points for understanding how the API works. You might be able to convince me to do some of the porting work myself. Ingo: http://bugzilla.schleef.org/ (temporary, but there will be a redirect when it moves) Ben: When I ran the decoder on an XO a month or so ago, it had trouble keeping up with a SD (standard definition, i.e., DVD) stream, but there have been some speed improvements since then, and additional work targetted for the XO could still improve things more. 320x240 would not be a problem at all. Francesco: testsuite/encode and testsuite/decode are the best (only?) starting points for understanding how the API works. You might be able to convince me to do some of the porting work myself.

Ingo: http://bugzilla.schleef.org/ (temporary, but there will be a redirect when it moves)

Ben: When I ran the decoder on an XO a month or so ago, it had trouble keeping up with a SD (standard definition, i.e., DVD) stream, but there have been some speed improvements since then, and additional work targetted for the XO could still improve things more. 320×240 would not be a problem at all.

]]> By: Ben Schwartz http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-83 Ben Schwartz Sat, 23 Feb 2008 23:43:14 +0000 http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-83 I've been working on video stuff for OLPC. We have assumed that Dirac would be far too CPU-intensive for the XO machine, but I don't know that anyone has actually asked. What decode frame rate would be achievable on the XO at 320x240 with Schrodinger? The XO's CPU is a Geode LX700 (433 MHz). It has relatively poor floating point performance using x86 FPU instructions, and somewhat better using 3DNow instructions. The GPU supports YUV overlays and scaling, but not general scaling or other OpenGL-related facilities. I’ve been working on video stuff for OLPC. We have assumed that Dirac would be far too CPU-intensive for the XO machine, but I don’t know that anyone has actually asked. What decode frame rate would be achievable on the XO at 320×240 with Schrodinger?

The XO’s CPU is a Geode LX700 (433 MHz). It has relatively poor floating point performance using x86 FPU instructions, and somewhat better using 3DNow instructions. The GPU supports YUV overlays and scaling, but not general scaling or other OpenGL-related facilities.

]]> By: Ingo http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-81 Ingo Sat, 23 Feb 2008 22:30:46 +0000 http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-81 So, where would you like bug-reports? ;-) So, where would you like bug-reports? ;-)

]]> By: Francesco Romani http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-77 Francesco Romani Sat, 23 Feb 2008 09:30:30 +0000 http://www.schleef.org/blog/2008/02/22/schrodinger-one-point-zero-point-zero/#comment-77 Hi there, I'd like to add support in transcode (http://www.transcoding.org) but I have some troubles finding helpful docs and/or code samples. Could you please point me to something helpful? I'm asking because I find the docs bundled into schro package sometimes lacking, and the gstreamer module source code isn't so easy to grok. Thanks and congrats for great work! Hi there,
I’d like to add support in transcode (http://www.transcoding.org) but I have some troubles finding helpful docs and/or code samples.
Could you please point me to something helpful?
I’m asking because I find the docs bundled into schro package sometimes lacking, and the gstreamer module source code isn’t so easy to grok.
Thanks and congrats for great work!

]]>