![]() |
Re: Fremantle GStreamer
Quote:
|
Re: Fremantle GStreamer
Run this script and post the output. It won't save a picture, it should just give me information about the captured buffer. Then I'll post back an n900 save solution while I work on a more general one. This is fun; I haven't flipped bits in a long while.
Code:
#! /usr/bin/env python |
Re: Fremantle GStreamer
1 Attachment(s)
I've cut file creation down to under
numpy could be just what the doctor ordered. |
Re: Fremantle GStreamer
I f you want to go beyond http://wiki.maemo.org/Documentation/...mera_API_Usage then I recommend you to ask to maemo-developers where some of our Multimedia developers are following.
|
Re: Fremantle GStreamer
1 Attachment(s)
Code:
/* Initialize the the Gstreamer pipeline. Below is a diagram I quickly tried modifying things so that the image queue path doesn't run until a snapshot is requested, but I haven't had luck there yet. So, even though a file isn't created until the button's clicked, the Image queue and the Image filter are processing every frame. On my n800, that's 640x480 @ 15 fps. For the n900, that would be more like 2592x1944 @ 25 fps. According to the specs, the supplied video recorder does 848x480 @ 25 fps with unknown sound quality. Pretty good, and I'm guessing the supplied camera app doesn't use the above pipeline. But if it does, which I doubt, there seems to be room for improvement. The problem here is that you really only want to be pushing the decimated view finder pixels until it's picture time, so I really just want some hardware decimated camera buffer. Instead, with a pipeline like this, I'm using the CPU to decimate the feed. Currently, I'm using a view window of 320x240. From the n900 demos, it looks like they're using close to the whole 800x480. And since I haven't figured out how to no-op the Image queue until photo request, I have two unnecessary loads. My next two steps are to see if I can change the Camera src capabilities on-the-fly, and also see if I can dynamically link and unlink the Image branch from the tee when taking a picture. The first might need a pipeline start-and-stop, but the second might just need a simple switch that I haven't found yet. But most importantly, are the camera and video apps open source? :) |
Re: python / gstreamer / camera / xvimagesink issues
1 Attachment(s)
Attached is a hard-coded, proof-of-concept that works on my n800. Look at it closely 'cause you'll probably have to change a few things to get it working on the n900. Including, but not limited to, anything that says:
Code:
if self.machine == 'armv6l': More info about what I've been doing can be found here. |
Re: python / gstreamer / camera / xvimagesink issues
I tried several Vala Gstreamer samples from http://live.gnome.org/Vala/GStreamerSample -- the last one is working well with N900 when v4l2camsrc is used instead of videotestsrc.
While this is not a Python, you can easily see how to use gstreamer correctly and I can confirm that this approach works well on the device with both cameras (front and rear). |
Re: python / gstreamer / camera / xvimagesink issues
Just a note, guys. The original post (from the thread that this post was originally in before sjgadsby unceremoniously dumped everything in the right thread) is talking about Diablo and the tablets, not Fremantle and the N900...
I know that's where everyone's head is these days, but read closely... :) |
Re: python / gstreamer / camera / xvimagesink issues
Quote:
|
Re: python / gstreamer / camera / xvimagesink issues
I wish I had looked at the original post's timestamp :)
|
All times are GMT. The time now is 11:36. |
vBulletin® Version 3.8.8