plonevideo team mailing list archive

[Nate Aune <natea@xxxxxxxxxxxx>]

Making progress... after making those two changes, now it appears that
flowplayer is passing the videos to the transcoding daemon.

but the daemon is having a problem with these files (they are H.264 .mov files)

2009/11/27 17:23 -0500 [-] Scheduler thread running
2009/11/27 17:28 -0500 [-] ['low', 'high']
2009/11/27 17:29 -0500 [-] New job
FFmpeg version SVN-r14381, Copyright (c) 2000-2008 Fabrice Bellard, et al.
  configuration: --prefix=/opt/local --disable-vhook
--mandir=/opt/local/share/man --enable-shared --enable-pthreads
--disable-mmx --cc=gcc-4.0 --enable-gpl --enable-liba52
  libavutil version: 49.7.0
  libavcodec version: 51.60.0
  libavformat version: 52.18.0
  libavdevice version: 52.0.0
  built on Oct 31 2009 14:31:25, gcc: 4.0.1 (Apple Inc. build 5490)
http://127.0.0.1:8080/transcodetest/videos/tml-ah_m480p.mov: Unknown format
2009/11/27 17:29 -0500 [-] Transcoder returned 256 {'path':
'videos/127.0.0.1:8080/transcodetest/videos/tml-ah_m480p.mov/low/tml-ah_m480p.flv',
'type': 'video/x-flv'}
2009/11/27 17:29 -0500 [-] New job
2009/11/27 17:29 -0500 [-] errored back!
2009/11/27 17:29 -0500 [-] callbackURL =
http://admin:admin@127.0.0.1:8080/transcodetest/videos/tml-ah_m480p.mov/@@streaming_RPC
FFmpeg version SVN-r14381, Copyright (c) 2000-2008 Fabrice Bellard, et al.
  configuration: --prefix=/opt/local --disable-vhook
--mandir=/opt/local/share/man --enable-shared --enable-pthreads
--disable-mmx --cc=gcc-4.0 --enable-gpl --enable-liba52
  libavutil version: 49.7.0
  libavcodec version: 51.60.0
  libavformat version: 52.18.0
  libavdevice version: 52.0.0
  built on Oct 31 2009 14:31:25, gcc: 4.0.1 (Apple Inc. build 5490)
http://127.0.0.1:8080/transcodetest/videos/tml-ah_m480p.mov: Unknown format
2009/11/27 17:29 -0500 [-] Transcoder returned 256 {'path':
'videos/127.0.0.1:8080/transcodetest/videos/tml-ah_m480p.mov/high/tml-ah_m480p.flv',
'type': 'video/x-flv'}
2009/11/27 17:29 -0500 [-] errored back!
2009/11/27 17:29 -0500 [-] callbackURL =
http://admin:admin@127.0.0.1:8080/transcodetest/videos/tml-ah_m480p.mov/@@streaming_RPC

here is the output from Zope:

collective.flowplayer running profile low
collective.flowplayer running profile high
collective.flowplayer: ConvertDaemon call pending
CALLBACK http://admin:admin@127.0.0.1:8080/transcodetest/videos/tml-ah_m480p.mov/@@streaming_RPC
collective.flowplayer: ConvertDaemon call
6e598b3692e558564fa1bd96b3d9baca2077fa03
CALLBACK http://admin:admin@127.0.0.1:8080/transcodetest/videos/tml-ah_m480p.mov/@@streaming_RPC
collective.flowplayer: ConvertDaemon call
77c97fd554ac03f7ae09048842f2b9226467fcc9

Is this as much as it's supposed to do at this point, or am I missing something?

thanks,
nate



On Fri, Nov 27, 2009 at 3:46 AM, victor rajewski <vik@xxxxxxxxxxxxxxx> wrote:
> 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
>



-- 
Nate Aune - natea@xxxxxxxxxxxx
http://www.jazkarta.com
http://card.ly/natea
+1 (617) 517-4953