Dimitris Moraitis <[email protected]> wrote on 25/11/2010 21.45.00: > > I'm quite happy that flowplayer internally make this. We need to release > > another redturtle.video version sooner or later for the same customer, and > > this new feature can simplify our code, but still I'm thinking if this is > > or not the right way... > > I don't think it's the best way to go since collective.flowplayer is an > integration of flowplayer for Plone while video metadata is useful > regardless of the player used. > > A better option would be to create a generic video/audio metadata > extraction component, e.g. collective.hachoir or collective.mediainfo > which could be used by collective.flowplayer, redturtle.video, > p4a.video, plumi.content, etc. >
Yeah, you are right. A separate package will be the best choice. Still, I'm was not aware of the mediainfo project. hachoir is quite usable in python environment. You know if one package is better the the other? Creating a collective.hachoir can be quite simple, giving to Plone an utility to extract metadata from media. > Ideally, that component would keep in sync the file's metadata and the > object's dublic core metadata when possible. We've done something > similar for photo IPTC metadata in: > http://pypi.python.org/pypi/unweb.iptc > This could be a very interesting example, thanks! Saluti/Regards Luca Fabbri - RedTurtle Technology E-mail: luca.fabbri AT redturtle DOT net Web Site: http://www.redturtle.net Phone: +39 0532 1915958 Fax: +39 0532 287070 _______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss
