Dnia 2009-03-24, wto o godzinie 09:27 -0700, Hakan Lindestaf pisze: > So you mean I should play two videos at the same time, on top of each > other?
No, drag and drop your video _file_ onto the window video.py opens so that it would play it (after taking note of gst-launch's CPU usage and stopping it). > I'd be fine with 10%, my problem is that in Elisa it's on the > magnitude of > double the cpu time vs gst-launch. That eats up all margin. Yup, that's probably a bug you're trying to find. > But it works well in gst-launch, what's the difference? Can I see the > "chain" that elisa is using vs. gst-launch -v? Elisa uses Pigment which uses OpenGL to render things on the screen. That means all decoded frames need to be 'copied' to the graphics memory and have colorspace converted to be used by OpenGL and then rendered and read and displayed afterwards. With xv (that's what your playbin uses probably) you don't need the colorspace conversion and your video gets copied directly to the graphics memory where it's then read and displayed. The overhead is caused by that Elisa uses OpenGL (and that won't change anytime soon). What's more the overhead is proportional to the image itself (big image - lots of pixels that need to be copied / converted). > Nah, that's not really an option, I'm looking for a convenient media > center > that my wife and son can use, don't want to convert videos for hours > before > they are available. Also, it's working great in gst-launch so I don't > understand why it would be so much slower in Elisa if it's using the > same > technique. It's not, really. The problem you're seeing is not decompression but rendering. Still, see how big overhead you're getting in gst-launch vs. video.py and give us a shout. -- Michał Sawicz <[email protected]>
