Re: [PD] Gem compilation for abling [pix_film] to open video file (read homer.avi)

2008-05-12 Thread tommaso bianco

Hi Iohannes,
yes, now it is working. I installed avifile-dev, as well as 
libquicktime-devel, and it is now able to read both the .avi and .mov files.

Now I can start play for real :-)

Here's attacched the output of the configure.
I had to uninstall libmpeg3-devel because it was giving a file not found 
for libmpeg3.h.


Tommaso


IOhannes m zmölnig wrote:

tommaso bianco wrote:
  

Hi all,

I suppose I have to bind the compilation with some codec library in my 
system, but which and how?



correct.
you have to have libavifile-dev (here it is: libavifile-0.7-dev; it
might be something like avifile-devel on a fedora machine) installed at
configure-/compile-/run-time.

Gem's configure will automatically detect the presence of this library
and use it at compilation time.

fgmadsr
IOhannes

___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list

  
checking for Base/configLinux.h.in... yes
checking for g++... g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether compiler accepts -fPIC... yes
building Gem with Controls-objects
building Gem with Geos-objects
building Gem with Manips-objects
building Gem with Nongeos-objects
building Gem with Particles-objects
building Gem with Pixes-objects
building Gem with openGL-objects
building Gem without Vertex-objects
checking for sin in -lm... yes
checking for main in -lz... yes
checking for dlopen in -ldl... yes
checking how to run the C++ preprocessor... g++ -E
checking for X... libraries , headers 
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for main in -lX11... yes
checking for main in -lXext... yes
checking for XF86VidModeGetAllModeLines in -lXxf86vm... yes
checking for main in -lXext... (cached) yes
checking for OpenGL-framework... no
checking for glInitNames in -lGL... yes
checking for gluLookAt in -lGLU... yes
checking for AGL-framework... no
checking for Carbon-framework... no
checking for QuickTime-framework... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for PKG_IMAGEMAGICK___CFLAGS... -fopenmp  
checking for PKG_IMAGEMAGICK___LIBS... -lMagick++ -lWand -lMagick  
checking for PKG_TIFF_CFLAGS... 
checking for PKG_TIFF_LIBS... 
checking for tiff-config... no
checking for TIFFOpen in -ltiff... yes
checking for PKG_JPEG_CFLAGS... 
checking for PKG_JPEG_LIBS... 
checking for jpeg-config... no
checking for jpeg_read_header in -ljpeg... yes
checking for PKG_LIBQUICKTIME_CFLAGS... -I/usr/include/lqt  
checking for PKG_LIBQUICKTIME_LIBS... -lquicktime -lGL -lpthread -lm -lz -ldl  
checking for PKG_LQT_CFLAGS... 
checking for PKG_LQT_LIBS... 
checking for lqt-config... yes
checking for PKG_MPEG3_CFLAGS... 
checking for PKG_MPEG3_LIBS... 
checking for mpeg3-config... no
checking for mpeg3_check_sig in -lmpeg3... no
checking for PKG_MPEG_CFLAGS... 
checking for PKG_MPEG_LIBS... 
checking for mpeg-config... no
checking for OpenMPEG in -lmpeg... no
checking for PKG_AVIFILE_CFLAGS... -I/usr/include/avifile-0.7  
checking for PKG_AVIFILE_LIBS... -laviplay  
checking for PKG_FFMPEG_CFLAGS... 
checking for PKG_FFMPEG_LIBS... 
checking for ffmpeg-config... no
checking for av_open_input_file in -lavformat... yes
checking whether (AVStream)-codec is of type *AVCodecContext... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking linux/videodev.h usability... yes
checking linux/videodev.h presence... yes
checking for linux/videodev.h... yes
checking for PKG_IEEE1394_CFLAGS... 
checking for PKG_IEEE1394_LIBS... 
checking for ieee1394-config... no
checking for main in -ldv... no
checking for PKG_FTGL_CFLAGS... 
checking for PKG_FTGL_LIBS... 
checking for ftgl-config... no
checking for main in -lftgl... no
checking for PKG_ARTOOLKIT_CFLAGS... 
checking for PKG_ARTOOLKIT_LIBS... 
checking for artoolkit-config... no
checking for arInitCparam in -lAR... no
checking for pthread_create in -lpthread... yes
checking for X... libraries , headers 
checking for ANSI C header files... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h

[PD] Gem compilation for abling [pix_film] to open video file (read homer.avi)

2008-05-11 Thread tommaso bianco
Hi all,
I'm simply trying to get a simple video (homer.avi) working with 
[pix_film], but there is a problem:

--
[pix_filmNEW]: opening homer.avi with format 1908
...
error: [pix_filmNEW]: unable to open file: homer.avi
--

The Gem library included in CCRMA Pd version 0.39.3-extended-rc5 works 
in loading the file, but I can not use it because it does not support 
the GEM_SINGLE_CONTEXT variable set to 1 needed for the creation os the 
gemwin with the fglrx driver (topic discussed recently in [PD] gem 
crash using fglrx driver in ubuntu).

I suppose I have to bind the compilation with some codec library in my 
system, but which and how?
Thanks for helping me!

Tommaso

___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] gem crash using fglrx driver in ubuntu

2008-05-09 Thread tommaso bianco
Hi,
I confirm. It definitively works for me just after setting the 
environmental variable (in ~/.bashrc) GEM_SINGLE_CONTEXT=1.
Before that, X was shutting down and going back to the gdm login after 
each Gem window creation.
The environmental variable GEM_SINGLE_CONTEXT=1 must be on both in 
compile time and in run time.
Tommaso

IOhannes m zmölnig wrote:
 Tim wrote:
   
 Ok just built the latest sources disabling hidio and gem2pdp because of
 errors, and it looks like verything is back to normal. I set
 GEM_SINGLE_CONTEXT=1 too. Cool. Thanks
 

 so it does not crash with GEM_SINGLE_CONTEXT=1 (?)
 does it (still) crash without setting it?

 fgmasdr
 Ihannes

   

___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] gem crash using fglrx driver in ubuntu

2008-05-07 Thread tommaso bianco
Me too, I'm not able to play with Gem under Fedora 8 with fglrx driver.
I'll give more info about this problem.

* Here's my Fedora and graphic driver versions:
Linux localhost.localdomain 2.6.24.4-64.fc8 #1 SMP Sat Mar 29 09:54:46 
EDT 2008 i686 i686 i386 GNU/Linux
display: :0.0  screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI MOBILITY RADEON X700
OpenGL version string: 2.1.7412 Release

* Here's the Gem lib (cvs compiled) loaded by Pd:
GEM: Graphics Environment for Multimedia
GEM: ver: 0.91-cvs
GEM: compiled: May  7 2008
GEM: maintained by IOhannes m zmoelnig
GEM: Authors :Mark Danks (original version)
GEM:Chris Clepper
GEM:James Tittle
GEM:IOhannes m zmoelnig
GEM: with help by Guenter Geiger, Daniel Heckenberg, Cyrille Henry, et al.
GEM: found a bug? miss a feature? please report it:
GEM: homepage http://gem.iem.at/
GEM: bug-tracker http://sourceforge.net/projects/pd-gem/
GEM: mailing-list http://lists.puredata.info/listinfo/gem-dev/
GEM: compiled for SIMD architecture: MMX
GEM: using MMX optimization

* Here's the dmesg output concerning the X server crash
[fglrx] PCIe has already been initialized. Reinitializing ...
[fglrx] Reserve Block - 0 offset =  0X7ffb000 length = 0X5000
[fglrx] Reserve Block - 1 offset =  0X0 length = 0X4
[fglrx] Reserve Block - 2 offset =  0X7fbb000 length = 0X4
[fglrx] interrupt source 20008000 successfully enabled
[fglrx] enable ID = 0x0004
[fglrx] Receive enable interrupt message with irqEnableMask: 20008000
[fglrx] interrupt source 1000 successfully enabled
[fglrx] enable ID = 0x0005
[fglrx] Receive enable interrupt message with irqEnableMask: 1000


Hope this helps :-)
Tommaso

IOhannes m zmoelnig wrote:
 Tim wrote:
   
 I have this problem too. I don't think it will be as simple as
 tweaking any config files though. Perhaps the eventual arrival of DRI2
 will improve things. I don't know too much about the fglrx situation
 either, other than what I've read at the Phoronix forums. Perhaps help
 can be found there.

 This issue came after the Hardy upgrade though, right? weird. I may
 try compiling against opengl 1.5, as I did in gutsy.
 


 does the problem still persist in recent Gem builds?
 (with recent i mean *post* 2008-05-05)

 i would be interested to hear how things perform with my recent hacks.
 additionally it would also be good to hear from linuxers using intel-gfx 
 cards whether these changes have improved anything on their side.


 fgamsdr
 IOhannes

 ___
 PD-list@iem.at mailing list
 UNSUBSCRIBE and account-management - 
 http://lists.puredata.info/listinfo/pd-list

   

___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list