Re: [piksel-dev] new fx-api (frei0r)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


re all,

sorry for crossposting

as this discussion is quite far from the topic of piksel-dev list, i
suggest we move it on the piksel list, i hope you don't mind, all
developers are also subscribed to that list i guess.


On Sat, Nov 06, 2004 at 11:55:26AM +0100, georg@xxxxxxxxxx wrote:
> 
> > i read that spec and tried to compile and use freeframe effects in
> > FreeJ, but actually i didn't reached to get any pixel thru that.
> > 
> > i code C/C++ since about 10 years, still maybe i'm too stupid for it?
> > i got nothing working, zero :O
> > to me it just looks like incompatible windlows based code.
>  
> I don't want to answer that question, but why do applications on mac
> osx [1]  support freeframe if it's "incompatible windows based code"?
> Freeframe is an API, it has no reference to OS specific stuff!
> 
> Please stop with this mixture of ideological and technichal issues.
> Your emails are indexed by search machines and can cause confusion
> for many people.

dear Georg,

i really don't want to confuse people!
therefore in my previous mail i stated what's my technical background
and you can look up what i do on http://dyne.org to understand on which
basis of knowledge and seriety i talk. i don't consider people reading
thru the net so stupid to not be able make up their own mind as they
want. after all, you can read my code if you want to tell whether is
good or not.

*IMHO*
freeframe is not a serious effort in providing a common video plugin
API: it misses features to be employed in NLE applications, it's
reference code is a mixture of Delphi code (which can't be compiled by
any standard ANSI compiler) and it doesn't respect POSIX.1b compliancy
(see http://pasc.org ) therefore i doubt it would work smoothly on
architectures like MIPS or ARM processors.

Despite my experience (i compiled myself all the distribution you see on
http://dynebolic.org which engaged me in comiling quite some tricky
code) i never got freeframe running on GNU/Linux.
Of course i got interested in supporting the freeframe API already 2
years ago and monitored the project through time.

Now please consider the nature of the effort behind LiViDO: we are
testing it on various platforms including NEC MIPS and SGI processors,
operating systems as *BSD, OSX and GNU/Linux.
The only requirements are the gnu libC and libdl for the host, you can
compile it for all architectures supported by the GNU C compiler, even
with the --pedantic flag set ;)

Plugins will be mainly developed and released under the GPL license,
while the header is released under the LGPL license.

At last, consider that it will be easy to make a LiViDO loader of any
other plugin architecture, alltough GPL plugins can be used only by GPL
(or other free software licensed) applications - we are lucky we have
the direct advices of FSF lawyers on this list, refer to past threads
for details.



[1] http://www.pasc.org


> [1] http://www.troikatronix.com/isadora.html

i don't consider software that is not licensed under a free license,
because it prevents me from learning and understanding it.

proprietary software is destined to decay on the long term, the paradigm
of free software providing better quality is already well proven and
established across many other contexts than video manipulation.

this is not a religious issue, this is consciousness of evolution.

so i won't consider the fact that isadorka uses freeframe, it is
meaningless to me: i can't compile neither freeframe nor isadora.

ciao

- -- 
 jaromil,  dyne.org rasta coder,  http://rastasoft.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Cryptographically signed mail, see http://gnupg.org

iD8DBQFBjMSCWLCC1ltubZcRAkOKAJ4u8YIj9W8iczGuVusQL+m+j2TBxQCgjWWK
U8LEgMgp8iMOA8nLxLBikoA=
=A/4y
-----END PGP SIGNATURE-----

_______________________________________________
piksel mailing list
piksel@xxxxxx
http://plot.bek.no/mailman/listinfo/piksel
http://www.piksel.no