plonevideo team mailing list archive

[victor rajewski <vik@xxxxxxxxxxxxxxx>]

On Thu, Nov 26, 2009 at 7:05 PM, Nate Aune <natea@xxxxxxxxxxxx> wrote:
> Ok, I modified my buildout
> (http://svn.plone.org/svn/collective/plonevideosuite/trunk/config/transcoding.cfg)
> to use Vik's collective.flowplayer transcode-support branch, but now
> when I upload a video file, I get this error:
<snip>
> Vik - any idea why the global name 'server' is not defined?

in events.py:169, server should be transcodeServer as declared on the
previous line - didn't test before checking in :-/

Also, on line 188, profile should be transcodeProfile

I'll have some more configurable code to check in in the next 24 hours.

Dimitris and I were discussing splitting this functionality away from
collective.flowplayer into a seperate product, which would handle the
following things:
* notifying the transcode daemon of a file to transcode
* accepting the transcode daemon's callback
* storing the url of the transcoded file as an annotation OR storing
the transcoded file itself as an annotation
* Making the video view use the transcoded version

How does this sound? Are there features missing?

Also, I was thinking in the ideal world we would have three transcoding options:
1) small site, occasional video, transcoding is done via plone itself
by executing a system command and consuming the generated file into
the ZODB. Python threads be damned
2) medium site, transcoding daemon runs on the same server as the
plone. videos transcoded via the transcode daemon can get consumed
into the ZODB and served via plone. transcoding daemon and plone would
have communicate the file paths to each other.
3) large site, transcoding daemon runs on seperate server and serves
the transcoded video files. Transcoding daemon sends a URL to plone,
which stores only the URL.

Initially I'll be focussing on option 3, then 2. What are people's thoughts?

ciao

vik