<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks for the reply and interest, Martin. See below<br>
<br>
Martin Kuball wrote:
<blockquote cite="mid200502191851.43490.MartinKuball@web.de" type="cite">
<pre wrap="">Am Friday 18 February 2005 21:09 schrieb Brad Fuller:
</pre>
<blockquote type="cite">
<pre wrap="">Is anyone interested in improving the multimedia facilities in
Squeak?
<snip>
</pre>
</blockquote>
<pre wrap=""><!---->I'm definitely interested. Unfortunately I'm not very good in writing
long Mails. I will try to sum up my plans and ideas in the next
couple of days. But here are some remarks that come to my mind when
reading your EMail.
What is Multimedia? Certainly it includes Audio and Video. But I think
there is more.
</pre>
</blockquote>
Yeah, I didn't really explain, kinda vague.<br>
I'm referring to only realtime full-motion video and sound/music only.
I wasn't refering to static graphics, text, etc. The rest seems to be
addressed well by others. To me, both audio and video are in need of
more attention.<br>
<blockquote cite="mid200502191851.43490.MartinKuball@web.de" type="cite">
<pre wrap="">
There are different levels or types of multimedia software. One type
is concerned with the creation of new content. Another type deals
with the manipulation of existing content. I think my AudioVideoLib
ist an example for the latter type. Playback another.
</pre>
</blockquote>
Right. I think we could view this in layers:<br>
* Low-level: Most of what is in the VM that addresses the
platform-specific.<br>
* Mid-level: Fundamental classes that connect to the VM and provide
fundamental <br>
facilities for upper level "apps". This could probably be divided
into two.<br>
* Upper-level: Applications for users - creation of content (like
vegas, premiere, <br>
sound forge, protools) playback of content (like windows media
player, xmms) that make<br>
use of the fundamental classes.<br>
<br>
(Perhaps it is not as clean a line as described here. But, if I
remember correctly, the sound recorder and sound playback are
intertwined a bit and several things are hard-coded (like sample-rate)
that would be better as a setting for the user. The fundamental
recording/playback should be separate from the user audio application.
A while back, I've pulled these apart and also made the AIF/WAV file
access classes more general. But, it was more for just my use and would
like to make it more general for the image. Don't hold me to this
explanatin as the current state as I'm writing this from memory of 6
months ago -- written here purely for explanation.)<br>
<br>
Approaching the problems could be addressed in layers, as well. Perhaps
there are volunteers that would like to work on the VM some that work
on the fundamental classes, etc.<br>
<br>
<blockquote cite="mid200502191851.43490.MartinKuball@web.de" type="cite">
<pre wrap="">
At the moment I'm trying to finish some missing parts of the AVI stuff
and make everything more robust. Another important point is to really
put it to use and find out the limits of what you can do with it
(speed wise I mean) and to improve the API.
</pre>
</blockquote>
that could be helpful for many.<br>
<blockquote cite="mid200502191851.43490.MartinKuball@web.de" type="cite">
<pre wrap="">
By the way I'm really excited about the things going on here at the
moment. I hope we can move squeak to a new level in the next few
month.
Martin
</pre>
</blockquote>
</body>
</html>