[michelangelo]

Hello all. 
After a lot of work I managed to have a full, correct installation of Flame 9.5. Thanks to everyone who shared his knowledge in this forum. It was a long and complex process figuring out all the necessary bits and collect all the information out there... but here we are. Irix 6.5.30. Hardware: Octane 2, 400 Mhz single CPU and V10 graphic. A simple extra scsi hard drive is used as framestore. 
I have a clone of the same installation / drive but set up to use an external fibre channel raid for serious (more or less) playback. And here's Flame in all its splendour.

                       

As a professional compositing supervisor it's amazing to be able to play again with this software.. I will try to implement some of the modern Nuke ideas into this.. and set up some batches to replicate some more modern nodes / setups.

[indigofan]

Awesome, got it up and running as well, still need to go through some tutorials... Does it only accept still image sequences or will it take video files? If so which format?

[michelangelo]

As rule of thumb image seq. Flame 9.x support QT import but not sure about codecs (for sure uncompressed). Also frame rate conversions etc are a headache. 
Hence in comp land we always use sequences no matter what. Also if a render crashes, you have the frames rendered up to that point : P

[indigofan]

OK that helps greatly as I was trying forever to import SGI movie files to no avail.. Will try and pinpoint which format is actually supports for video formats
.

[vishnu]

Much as I hate to be a bother, could you be so kind as to ldd the flame binary? Does it link against Motif? My guess is it doesn't, I'm guessing they did the same thing the early Netscape did, they bought a source code license to Motif and hacked the hell out of it themselves, then statically linked their hacked library into the binary. That's what PTC did with their Unix versions of Pro/E, they had a thousand developers who hacked the Motif source code to pixel per pixel match the MS Windows GUI... 🤥

[michelangelo]

Much as I hate to be a bother, could you be so kind as to ldd the flame binary? Does it link against Motif? My guess is it doesn't, I'm guessing they did the same thing the early Netscape did, they bought a source code license to Motif and hacked the hell out of it themselves, then statically linked their hacked library into the binary. That's what PTC did with their Unix versions of Pro/E, they had a thousand developers who hacked the Motif source code to pixel per pixel match the MS Windows GUI... 🤥

No idea sir.. I'm completely ignorant about all this : P I play with pixels more than with computers : P

[vishnu]

No idea sir.. I'm completely ignorant about all this : P I play with pixels more than with computers : P

Ah well, never mind then, My assumptions about how they created their user interface are probably correct, or, at least, correct enough. If there is such a thing... 😆

[chulofiasco]

Much as I hate to be a bother, could you be so kind as to ldd the flame binary? Does it link against Motif? My guess is it doesn't, I'm guessing they did the same thing the early Netscape did, they bought a source code license to Motif and hacked the hell out of it themselves, then statically linked their hacked library into the binary. That's what PTC did with their Unix versions of Pro/E, they had a thousand developers who hacked the Motif source code to pixel per pixel match the MS Windows GUI... 🤥

This is from an O2 running Flint:


PELE 20# ldd flint_IRIX_6.3_ip32_10k
        libInventor.so.3  =>    /usr/lib32/libInventor.so.3
        libdmedia.so  =>        /usr/lib32/libdmedia.so
        libXi.so  =>    /usr/lib32/libXi.so
        libXext.so  =>  /usr/lib32/libXext.so
        libX11.so.1  =>  /usr/lib32/libX11.so.1
        libgen.so  =>    /usr/lib32/libgen.so
        libaudio.so  =>  /usr/lib32/libaudio.so
        libaudiofile.so  =>      /usr/lib32/libaudiofile.so
        libFL.so  =>    /usr/lib32/libFL.so
        libvl.so  =>    /usr/lib32/libvl.so
        libGLU.so  =>    /usr/lib32/libGLU.so
        libGL.so  =>    /usr/lib32/libGL.so
        libm.so  =>      /usr/lib32/libm.so
        libheap_malloc3X.so  =>  /usr/discreet/lib32/flint_5.5O2/libheap_malloc3X.so
        libmalloc.so  =>        /usr/lib32/libmalloc.so
        libCsup.so  =>  /usr/lib32/libCsup.so
        libC.so.2  =>    /usr/lib32/libC.so.2
        libc.so.1  =>    /usr/lib32/libc.so.1
        libawareaudio.so  =>    /usr/lib32/libawareaudio.so
        libGLcore.so  =>        /usr/lib32/libGLcore.so
        libvice.so  =>  /usr/lib32/libvice.so

[vishnu]

So it links against X11 but not against Xt, interesting! GTK did the same thing, writing their whole widget set based on X11 only.