[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AW: [Gnash-dev] from Hong Yu: Gnash/server/asobj/LoadVars.* need fix

From: Hong Yu
Subject: Re: AW: [Gnash-dev] from Hong Yu: Gnash/server/asobj/LoadVars.* need fix for running videos
Date: Wed, 30 Jan 2008 10:59:29 +0800
User-agent: Thunderbird (X11/20071031)

Thanks for your encouraging suggestions! To contribute to Gnash project is exciting and benefits our team as well.

On the other hand, we have found that flash videos from YouTube are of H.263 format, and flash videos from Twango ( are of VP6 format. Therefore yesterday we upgraded our FFmpeg from the newest source. However, running Gnash-cvs version with Twango still saw error about 'internal data flow error' in the log during video stream downloading. It is unclear whether this be related to the GStream layer. We decide to first look into the issue, which is our top priority at present.

Best regards,

Hong Yu

Bastiaan Jacques wrote:

On Tue, 29 Jan 2008, Hong Yu wrote:
Thanks for the suggestion! We have modified '' (see attached) a little bit (with reference to gnash-0.8.1/ to enable ffmpeg as media-handler in the configuration. However, we find that you have hard-coded GST in your source code as the media-handler (server/parser/video_stream_def.h); so that we have to use '--enable-media=gst' in order to proceed to build and install.

Therefore, if you would still consider the ffmpeg option, could we help with, for example, coding the ffmpeg related media-handling components? We are working for embedded platform, so we would appreciate it if the GStreamer's 7MB size libraries could be removed. Thank you!


Because we're no longer maintaining the ffmpeg backend we have not
attempted to preserve the abstraction layer we previously had. However,
reintroducing it is fairly straight forward. This would produce the
problem that the ffmpeg video handler will be incompatible with our
abstraction layer, unless you pick it up to bring it up to speed
with the rest of our new code.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]