Meeting Minutes of 21.7.2004

Martin Bayer <[email protected]>
Newsgroups gmane.comp.video.gephex.devel
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

1. Intruduction

The meeting took place on June 21, 2004, at 14:00 CET. The following
people were present:

~   Martin Bayer
~   Georg Seidel
~   Philipp Promesberger

2. GUI for 0.5

The main focus of our first gui for 0.5 should be on the use as a live
vj tool. A concept with similarities to audio mixers with channels,
busses was discussed.

The requisites for a prototype are a video input and a output server, a
scheme scriptable gephex core that replaces konsolenphex. It was decided
to delay the gui issues till then.

2. Scheme

Scheme[4] will be the language for interfacing the c++ gephex core. The
core is a library. And its functions are exported to a scheme environment.

An open issue is the appropriate scheme interpreter for us. The options
guile[1] and mzscheme[2] will be evaluated by Georg. The usefullness of
~ swig[3] as ffi compiler should be checked.

The next step is to import all core functions in the scheme world and
reemplement the konsolenphex in scheme.

3. ffmpeg

ffmpeg[5] will be used for videofile decoding and will replace
libavifile[6] in the long run.

The steps to use ffmpeg in gephex are:
- - import the current cvs version of ffmpeg into an arch repository and
provide a possibility to import the cvs changes. The name for the ffmpeg
arch should be ffmpeg--cvs--0.35. cscvs[7] seems to be a tool that
achieves that
- - use configs[8] to include the ffmpeg sources in the gephex sources at
contrib/ffmpeg
- - update the build system of gephex 0.4 to configure and build the
ffmpeg subtree
- - write a frboutput driver for gephex 0.4 that uses ffmpeg

Phillipp will look at these issues.

4. IO Server

In 0.5 there will be extra processes called servers for i/o. These will
replace all i/o units in 0.4. E.g. the videofile decoding will be moved
~ into a videoinput server. The gephex core requests frames from the
server, the server decodes the frames and sends them to the core.

We have started to design the lowlevel api for the ipc protocoll and
discusses several technical issues. Martin will send a summary of the
design decisions regarding this to the list and will implement a prototype.


[1] http://www.gnu.org/software/guile/guile.html
[2] http://www.plt-scheme.org/software/mzscheme/
[3] http://www.swig.org/
[4] http://www.swiss.ai.mit.edu/projects/scheme/

[5] http://ffmpeg.sourceforge.net/
[6] http://avifile.sourceforge.net/
[7] http://wiki.gnuarch.org/moin.cgi/cscvs
[8] http://www.flibuste.net/libre/tlarefexport/texinfo/tla_9.html#SEC80

- --
GnuPG (ID B3D1B1BB) C2F4 F775 5022 1891 48F4  761D 0A6D E2E7 B3D1 B1BB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA/650Cm3i57PRsbsRApTzAJ9Vm+ND27SY6A5xsMvJzuM4nCTrvACfSA+M
MtxpDHClaUTLx/Buo9qs4eQ=
=nuDd
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.