Hi,
This issue has rised with camera stack, but is it more common lack ?
Posted the below story as a commit reply, but this is probably more
suitable home for such discussion.
I'm pondering that Meego target devices will continue needing the
special pipelines, rules and settings, but the rest is by far generic.
Adaptation branches could eventually leave large frameworks intact of
such changes and the conditional juggling with static gstreamer element
names for example could be leased to minimum. But, is there tools to do
this ?
BR,
-Teemu
-------- Original Message --------
Subject: Re: [meego-packaging] [meego-commits] 15856: Changes to
Trunk/meego-app-camera
Date: Thu, 7 Apr 2011 09:42:42 +0200
From: Teemu Tuominen <[email protected]>
To: [email protected] <[email protected]>
Hi,
The issue about having flexibility to select encoding pipelines for
different target devices, use cases and derived concepts feels rising
atm. This is probably one step to deal a part of it locally in
application for camera stack - that doesn't provide such thing ?
I was thinking we could advance it in Qtm camerabin backend level.
Instead the backend currently has statically named elements (including
sources, codecs/filters and sinks), there could be a solution that
allows pipeline configurations to be provided by external independent
package. E.g. *-config packages made for reference hardware adaptations
would suit for this.
I would propose to start such effort in Meego by adding rules like done
in this patch and store them externally by using some expandable
solution& common language. Do we have such ?
More commonly, whole multimedia should support configurable sets of
elements and pipelines that are preferred (dealt by merit), shown as
user options or in blacklist etc. So, just another ascii config file
would just not live long. I'm used to this with MS DirectShow, but
cannot see anything atm dealing with this in common around Qt/Qtm context.
Is there related plans with common multimedia and or ready-made and
suitable APIs to just start working on it ?
BR,
-Teemu
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
