[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] Movie module information

To: pygame-users@xxxxxxxx
Subject: Re: [pygame] Movie module information
From: René Dudfield <renesd@xxxxxxxxx>
Date: Mon, 27 Apr 2009 10:16:41 +1000
Delivered-to: archiver@xxxxxxxx
Delivered-to: pygame-users-outgoing@xxxxxxxx
Delivered-to: pygame-users@xxxxxxxx
Delivery-date: Sun, 26 Apr 2009 20:16:43 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=toNIxzu+pkSwQxP6wC8Hm7RDbBAUFr81H8uOEmJUmRE=; b=rixNKd+VJ00xS2DjVNyF8CGYNMbJdMNc5+OgdjESXnVQ13RULLyQ6mqEaEZRXgpYei vTEAiS7EwMFHloX+wZWFI8dtImGnO5nH4vaBfvS3FXGMOyn3jcJc7GXE8LpETxvpUpZX mk3zn21MkBYqISvkInb9qsB6AdNJ4C9AbEJbE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=HoqfEImyQ3pYwe37VwaoAscnKz3Ov98glS7aCbcPO9uV1qbGquct+MuSIfG9cGVR1I a1PJnWB5JF80mBlf7nl4phrAUgFt3QtlBUyyZFJjtP4BDLWgZd/tMDijed+ApzjgOqOR Rzt6cdE5P5bE6ObzvjV5Kaw1sujmR5wR7fUZQ=
In-reply-to: <3618a6e10904261310q4ed7571btb72f405d458412d3@xxxxxxxxxxxxxx>
References: <3618a6e10904261310q4ed7571btb72f405d458412d3@xxxxxxxxxxxxxx>
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx

Hello,

I think replicating the current movie module API is a good aim. It has all the basics really, and is quite simple.

One approach to take might be to use the cmd line version of ffmpeg... this would allow people to use the module without nessesarily recompiling pygame. The other benefit of this approach would be you'd avoid ffmpegs unstable API (they promise not to have a stable API). Pipes are a fairly fast way to go. If we can find an image/audio format that is fast with both pygame, and ffmpeg, this could work quite well I think.

Another way to do the movie module is to run the output in a separate process, and tell the movie player to use a pygame window id. People have used mplayer successfully to play movies with pygame. The test player that comes with ffmpeg uses SDL - which means this approach can be used with that too. It's very likely that if someone has ffmpeg installed, they also have the ffmpeg example player.

It's quite important to keep the API library neutral.

This way the movie module could have:
1. an smpeg backend.
2. an ffmpeg backend, using compiled ffmpeg/SDL_ffmpeg.
3. a pipe using ffmpeg backend.
4. an mplayer/vlc/ffmpeg SDL player based backend using the window id hack.

Saving movies using ffmpeg might be something to explore after playback is handled.

Especially a save to flash video option would be great for making demos of games. Also of note, is the vnc2swf project which uses pygame to record VNC sessions as flash videos.

For movie playback, using the SDL overlays can be an efficient way to playback video. It's accelerated on many computers.

cu,

On Mon, Apr 27, 2009 at 6:10 AM, Tyler Laing <trinioler@xxxxxxxxx> wrote:

Hello all,

One of the first steps I need to take for the GSoC project is to get user stories so I can build acceptance tests.

I want to hear what you guys(the users) want out of an updated movie module. What do you want to be able to do, and how?

I'm also interested in hearing what people liked and didn't like about the current movie module.

-Tyler

--
Visit my blog at http://oddco.ca/zeroth/zblog

References:
- [pygame] Movie module information
  - From: Tyler Laing

Prev by Author: Re: [pygame] PyGame Website Rewrite
Next by Author: Re: [pygame] Movie module information
Previous by thread: Re: [pygame] Movie module information
Next by thread: Re: [pygame] Movie module information
Index(es):
- Author
- Thread