search for: 1280x544

..., 2009 at 3:41 PM, Frank Barchard <fbarchard at google.com> wrote: > no, But I will say that tools wise, I have content that does not encode > with xiph and does with ffmpeg. So roughly my tool recommendation is: > > oggenc2 -o trek2.ogg trek2.wav > ffmpeg -y -threads 16 -s 1280x544 -r 23.976 -i trek.1280x544_24Hz_P420.yuv > -b 2000000 -vcodec libtheora -an trek.ogv > oggz-merge trek2.ogg trek.ogv -o trek2.ogv > > ffmpeg is not good with the audio or muxing > xiph is not good at video > > On Fri, Dec 4, 2009 at 2:28 AM, solomon kariri <solomonkariri at...

...200KB of >> memory is gone. Let me know if I should change it to do the >> request_firmware in init. >> >> There's obviously a userspace piece to this, which I'm still working >> on. But right now I have it working within certain parameters >> (e.g. 1280x544 videos), and I'm relatively confident it can be >> completed without further kernel-side changes. >> >> There's also a hypothetical concern of "what if we create an open >> firmware with a different user API". Ideally there'd be some way to >> exp...

...dea > what's going on :-) > > >> no, But I will say that tools wise, I have content that does not > encode > >> with xiph and does with ffmpeg. So roughly my tool recommendation is: > >> oggenc2 -o trek2.ogg trek2.wav > >> ffmpeg -y -threads 16 -s 1280x544 -r 23.976 -i > trek.1280x544_24Hz_P420.yuv > >> -b 2000000 -vcodec libtheora -an trek.ogv > >> oggz-merge trek2.ogg trek.ogv -o trek2.ogv > >> ffmpeg is not good with the audio or muxing > > ffmpeg will also screw up the video > > >> xiph is not good...

...memory is gone. Let me know if I should change it to do the >>> request_firmware in init. >>> >>> There's obviously a userspace piece to this, which I'm still working >>> on. But right now I have it working within certain parameters >>> (e.g. 1280x544 videos), and I'm relatively confident it can be >>> completed without further kernel-side changes. >>> >>> There's also a hypothetical concern of "what if we create an open >>> firmware with a different user API". Ideally there'd be some way...

https://bugs.freedesktop.org/show_bug.cgi?id=82255 Priority: medium Bug ID: 82255 Assignee: nouveau at lists.freedesktop.org Summary: [VP2] Chroma planes are vertically stretched during VDPAU playback Severity: normal Classification: Unclassified OS: All Reporter: emil.l.velikov at gmail.com

.... The downside is that ~200KB of > memory is gone. Let me know if I should change it to do the > request_firmware in init. > > There's obviously a userspace piece to this, which I'm still working > on. But right now I have it working within certain parameters > (e.g. 1280x544 videos), and I'm relatively confident it can be > completed without further kernel-side changes. > > There's also a hypothetical concern of "what if we create an open > firmware with a different user API". Ideally there'd be some way to > expose what kind of fir...

...coders at startup a few times. The downside is that ~200KB of memory is gone. Let me know if I should change it to do the request_firmware in init. There's obviously a userspace piece to this, which I'm still working on. But right now I have it working within certain parameters (e.g. 1280x544 videos), and I'm relatively confident it can be completed without further kernel-side changes. There's also a hypothetical concern of "what if we create an open firmware with a different user API". Ideally there'd be some way to expose what kind of firmware is loaded, but I t...