GEM-dev March 2005

gem-dev@lists.iem.at

11 participants
18 discussions

OSx Compile missing src files
by Wesley H. Smith 27 Mar '05

27 Mar '05

Hi, I'm almost to the compilation stage of this process. I have all of the libraries compiled and loaded into the GEM project, but I'm still missing 3 files and their headers. The wayward code files are called: /Base/GemOutput.cpp /Controls/gemcontrol.cpp /Controls/gemwindow.cpp I performed a CVS checkout yesterday following the example on gem.iem.at and these files didn't come with it. I also have a download of GEM with src files, but they weren't there either. Where can I get these? muchas gracias, wes

2 1

RE: [GEM-dev] CVS osX
by Wesley H. Smith 26 Mar '05

26 Mar '05

Ok, so a friend of mine helped me with the CVS stuff, so I'm on my way. No need to reply to my original post. best, wes

1 0

CVS osX
by Wesley H. Smith 25 Mar '05

25 Mar '05

Hi, I'm tring to compile the GEM xcode project and thus need the GemLibs. I tried cvs -z3 -d:pserver:anonymous@cvs.gem.iem.at:/cvsroot/pd-gem checkout Gem GemLibs but I got an error "login aborted use cvs login", so I tried cvs login -z3 -d:pserver:anonymous@cvs.gem.iem.at:/cvsroot/pd-gem checkout Gem GemLibs but this gave me an error "cvs login: No CVSROOT specified! Please use the `-d' option". I thought I had used the -d option in the above line. I tried a couple of variations but was unable to find anything helpful in the man pages. Any suggestions out there? muchas gracias, wes

1 0

Re: [GEM-dev] Re: meanwhile, in gempixutil...
by james tittle 22 Mar '05

22 Mar '05

On Mar 18, 2005, at 6:57 AM, IOhannes m zmoelnig wrote: > james tittle wrote: >>> could you please test the attached file ? >> ...sure! I'll be working on this tonight after work: I didn't get > > so did they work then ? > i'd rather have these changes committed to the cvs, as they at least > have the clamping and are more (i say: "more" :-)) standardized than > the last code. ...just tested 'em, and they seem much better so far...maybe not faster in osx(tho I was testing on a 720x480), but then that'll come with the altivec...I was pretty astonished to see that the old rgba conversions actually lightened the picture, and I could only chain together 2 pix_rgba/pix_yuv's before noticeable color screw-ups occurred! ...I'm now migrating the altivec stuff that I've done so far into your new GemPixUtil.cpp that ya sent, so if you wanna commit it, go ahead, or just wait and I can do it when I get this stuff merged... james

2 1

Re: [PD] gem & cinepak video on linux
by IOhannes m zmoelnig 19 Mar '05

19 Mar '05

patrick wrote: > > done that (mpeg3toc my mpeg2 movie), but when i open it in (GEM: ver: > 0.90 / Linux) it crash big time: no error. tried with pix_film and > pix_movie. oh! > > should i run gdm to help you find why? (but, i don't know how). yes, please for a start just do something like #> gdm pd % run -lib Gem crashtest.pd ....(crash) % backtrace and send me the backtrace mfg..ads IOhannes > > patrick

2 1

compile GEM on OSX (gemlib etc...)
by Zack Settel 18 Mar '05

18 Mar '05

I would like to compile GEM on my OSX platform. Ben B. has managed, but has tales of woe. I was hoping to at least diminish the task by trying to locate a pre-compiled gemlib, which I could just link in, rather than having to compile it as well. But perhaps someone has a better way???? Any help on the matter (configuring a Gem Dev. Env. for OS X) would be MUCH appreciated!! thanks, Zack Settel

1 0

Alpha channel support
by B. Bogart 17 Mar '05

17 Mar '05

Hey all, After seeing tom's nice work online I realized I've been missing something in Gem. He is using alpha channels in video using Gem on winXP!! This is a feature I've been hoping for for years. (in 2003 when creating Oracle I had to use still-images and pix_masks to create anti-aliased text on a video background.) So being inspired by Tom I gave a real effort to alpha channels on OSX. The GREAT news(!) is that I can load images with pix_image (tiffs) with intact alpha channels! It is truely a beutiful thing to see! So after this success I went to video. I tried three cases (it seems aftereffects only exports videos with alpha channels compressed with TIFF, TARGA, and PNG. So for fun I exported alpha channel videos and tried to load them in Gem. Every single one loads fine according to the pix_film and pix_movie output, BUT only shows a green square in the render. Looking further I realized that my Gem 090 does not load any quicktime movies compressed with TARGA, TIFF or PNG. Could someone give this a try on thier OSX machines? I did not try all the codecs, but I know DV, cinepack, photojpeg and sorenson certainly work. I think I reported the same trouble with the animation codec a while back. I don't care much for Gem supporting all codecs personally, but it would be very nice If we have one codec on OSX that supported alpha channels working (TARGA, TIFF or PNG) the latter two being my preference. This also brings up the issue of "similar" functionality working on all platforms. In theory we should be able to load alpha channels from TIFF images on all platforms, as well as loading Quicktime movies using the TIFF codec with alpha channels. :) Thank you Gem developers!!! b. Thomas Ouellet Fredericks wrote: > I can correct most of the stuff but I do not understand the error : > > MPEG3: unsupported! > > I made the mvoies with quicktime pro 6.3. They are actually TGA image > sequences, millions+ of colors. What alpha format does quiktime for > linux support? > > The movies are read with [pix_movie] followed by an [alpha] box. > > Tom > > > On Wed, 16 Mar 2005 11:13:44 +0100, Frank Barknecht <fbar(a)footils.org> wrote: > >>Hallo Thomas, >>Thomas Ouellet Fredericks hat gesagt: // Thomas Ouellet Fredericks wrote: >> >> >>>On Tue, 15 Mar 2005 23:29:09 +0100, Frank Barknecht <fbar(a)footils.org> wrote: >>> >>>>Krzysztof Czaja hat gesagt: // Krzysztof Czaja wrote: >>> >>>Could you please send me a print-out of the errors, I will correct the patch. >> >>I attached all error messages until the Gem window appears. I did look >>around a bit in your patch already, but I could find dashed objects. >>However I surely haven looked in every patch yet. ;) >> >>Ciao >>-- >> Frank Barknecht _ ______footils.org__ >> >> _ __latest track: "scans" _ http://footils.org/cms/show/41 >> >> >> > >

2 2

Re: [GEM-cvs] Gem/src/Base GemMan.cpp,1.36,1.37
by IOhannes m zmoelnig 09 Mar '05

09 Mar '05

Jamie Tittle wrote: > Update of /cvsroot/pd-gem/Gem/src/Base > In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16801 > > Modified Files: > GemMan.cpp > Log Message: > IOhannes: the gl headers and such are in GemMan.h: > why would you want to put them in GemMan.cpp? because they were already there ? the only real change i made was the use of "#if !defined DONT_INCLUDE_GLEXT && !defined __APPLE__" instead of "#ifdef INCLUDE_GLEXT" (really! i have also changed the indentation of the other preprocessor-directives a bit. that's why the diff was so big) > I'm a big fan of including headers in, um, the header :-) well, i think this might be discussable (although i don't have a theoretical background in such things): 1. i think it is good style to include header-files that are only needed to make the "body" (this is: .c/.cpp) compilable in the body instead of the header. in the header only those files should be present that make the header "compilable". e.g is i use GL_RGBA in my header, then i have to include gl.h; if no reference to any gl-related thing can be found in the header, why include it ? 2. sometimes it is good to include "some" .h-files in the header because they are needed by all body-files that include the header (even though the header-file itself does not depend on the includes) that having said, i admit that i don't want to flame about where to include header files. i have just put them into GemMan.cpp because all related headers where already there (or probably i myself didn't put them there at all, but they had been there since ever) i really just had encountered a bug within GemPixUtil.h due to using INCLUDE_GLEXT instead of DONT_... and then i grepped all occurences of INCLUDE_GLEXT and replaced them. Btw, the "GL/ vs. OpenGL/" thing is due to apple's use of framework's... > yes i know this. that's why i have put in the "nevermind". it just makes things unnecessarily complicated (but that is what live is anyhow) keep rocking mfg.ads.r IOhannes

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

GEM-dev March 2005