pitivi-pitivi-bounces@lists.sourceforge.net wrote on 22.08.2007 17:56:33:

> On 8/22/07, dellasantina@farm.unipi.it <dellasantina@farm.unipi.it> wrote:
> > On Mon, 2007-08-20 at 10:05 -0300, Nathan Ryan wrote:
> > > This one made my antennae perk up.  Might there be a way to take this
> > > one step further and have the original clips themselves contain this
> > > information, so that when they are imported into the program it is
> > > automatically embedded?  This would be helpful when searching for clips
> > > to put on the time line.  Again, really only useful in large projects,
> > > but that's the kind of work I deal with on a daily basis.
> > > My ideal situation would be definable fields so you could enter
> > > whatever
> > > information was pertinent to the project - actor name, maybe...
> > > director, time of day, time code, location. Possible? Must be. Easy?
> > > I dunno.
> >
> > Having the possibility to set these meta-informations in the original
> > clips would surely be the best approach, unfortunately the situation is
> > a step more complex:
> >
> > If we want these informations to be stored inside the videoclip
> > container, we need that videoclip container supports adding arbitrary
> > tags. As far as I know the majority of media container formats allow to
> > store only some predefined tags; a strict minority of container formats
> > allow you to set arbitrary tags, one example is the matroska container
> > (http://www.matroska.org). We cannot rely on this approach for
> > retrieving information, since it is container-dependent.
> >
> > Another approach is to let the desktop manager store tags along with the
> > videoclip files, this method implies your system supports adding tags to
> > files.
> > In the linux world this possibility is currently a work-in-progress
> > feature, since both the KDE project (with "nepomuk") and the GNOME
> > project (with "tracker"?) are going to implement this feature in the
> > upcoming versions. Even this approach is not practicable at the moment.
> >
> > What is concretely possible at the moment is to add tag support inside
> > pitivi architecture (in composition and/or sources definition), so that
> > users can set tags from inside pitivi and search scenes that match
> > queried tags; then, when the desktop manager will properly support file
> > tagging, it'll be matter of importing tags stored by the desktop
> > managare inside pitivi.
>
>   Good to see i'm not the only one seeing the whole picture here :) So
> yes, basically there's two way: the proper way and the ugly way.
>   The proper way would be the way Apple is going, which is that you
> have a media library (itunes?) handling all the multimedia files, with
> tags attached to them. Then your app can easily search/add/remove tags
> through that. But that's an outside feature.
>   The ugly way... is to store that data in pitivi. With the current
> design, it shouldn't be hard to add extra tags to timeline objects or
> factories. Oh, and it's also the fastest way to do it :).
>
>   Edward

May be place information in separate file, say - "clip.avi.media_info"?
Information from "*.avi/mpg.media_info" files can be automaticaly(if exists)
placed in current project(not pitivi project file). Then it can be re used
in others (not only one) projects.


Paul




> >
> > Would you mind filling a feature request in pitivi's bugzilla for this
> > feature?
> >
> > Luca Della Santina
> >
> > > > > 5) In the source(composition) structure it would be very useful to
> > have an
> > > > > "actor" field defining who is the main actor of the video clip, the
> > > > > instrument type for an audio clip, the spoking person for a subtitle
> > item.
> > > > > It could seem a file overhead at first glance, but it comes very
> > handful
> > > > > when working on long projects, since it allows us to provide scene
> > > > > searching based on the main actor, which is a far more efficient way
> > than
> > > > > seeking the whole project using the time slider.
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > _______________________________________________
> > Pitivi-pitivi mailing list
> > Pitivi-pitivi@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/pitivi-pitivi
> >
>
>
> --
> Edward Hervey
> Multimedia editing developer
> http://www.pitivi.org/
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Pitivi-pitivi mailing list
> Pitivi-pitivi@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pitivi-pitivi