Film Gimp
gosand writes "DesktopLinux.com is running this story about Film Gimp. It is a movie editor based on The Gimp that movie studios have been developing for their own use for a while now. The article is an interview with Robin Rowe about Film Gimp's use, and includes some interesting info about the film industry's use of GNU/Linux desktops. One quote worth noting: 'Studios have become the leading desktop users of Linux. Three hundred Linux desktops at Dreamworks. That's amazing! While the MPAA is campaigning for new restrictions on content, the artists at the studios are using and helping create open source. Having Linux and open source as a crucial part of studio operations may help executives rethink their corporate position on open source and Linux issues.'"
Editing films is like a box of chocolates....
- Forrest Gimp.
...because it helped to generate that atrocious looking dog in the scooby-doo movie. ;)
"Quoting famous computer scientists out of context is the root of all evil (or at least most of it) in programming." - K
the artists at the studios are using and helping create open source
It seems to be implying that the studios are doing it out of love, but methinks that they are finding that it's cheaper, and more flexable (their programmers can get their hands on all the code)...
Not that this is a bad thing, just that it's not because they hate MSFT...
Tibbon
tibbon.com
Having Linux and open source as a crucial part of studio operations may help executives rethink their corporate position on open source and Linux issues
Not likely. They're in the movie business to make money, anything their customers use for free is a threat, anything they use for free is more money.
Sig is on vacation
FilmGimp? Can they not change the name to something more politically correct? ie:
- FilmChallenged
- FilmSpecial
- FilmJerrysKids
- FilmTheres"Abilitity"In"Disability"
- FilmDroolingTard
Hmm.. no, on second thought "FilmDroolingTard" is out.
Trolling is a art,
Of course, Scooby Doo would have been overpriced at "free", but that's completely beside the point.
John
Film gimp adds lots of support for superior playback. However, the biggest and most importanted different is that it uses 16 bits per channel instead of only 8 like the regular gimp. That means that instead of roughly 16 million colors, you get 16 million squared colors. This adds much less chance of rounding errors on compositing, and gives you more room to play with when adjusting brightness and color balance over 8 bit images.
The downside is that film gimp is based on an old version of the gimp, and it doesn't really look like that is going to change soon. But at least they are talking about syncing up a bit before 2.0 whereas before they seemed to be planning on waiting for the Gimp 2.0.
I'm a loser baby, so why don't you kill me.
Does anybody know if this uses anything from GNU's Free Film Project?
I haven't really heard much about the project myself and so I haven't looked, but from what I read on GNU's info page about it it seems pretty interesting. Also the GNU Octal stuff seems interesting, what about that, every decent film editor has at least rudimentary sound manipulation utilities.
If they're not, can anybody give reasons why? Projects like those and GYVE (GNU Yellow Vector Editor) are things that confirm my faith in GNU and RMS in my times of doubt.
Not to say that it's all bad for the studios or open source. The place I work for shelled out money for an open source developer to finish some of his development work on a program they wanted to use. Cheaper than buying a commercial package, and everyone benefitted.
But the biggest reasons the studios go for Linux is the cheaper/faster hardware (despite all sorts of compatibility headaches -- getting reliable 24 frame per second playback for 1k images is a little touchy) plus reduced porting costs for their legacy IRIX software and avoiding the whole Microsoft headache. The sysadmins really don't want to go there, and the studio doesn't really want to start springing for license packs for a few hundred users and a few hundred renderfarm machines.
"If a conventional monitor can't display the colors at that depth then how does the film editor know exactly what will end up on film after printing?"
I think you're looking at it the wrong way. It's not about what's displayed on the screen, it's about having enough color information to prevent color banding when doing things like brightness and contrast adjustments. The color banding is a result of rounding errors that stair-step the color values when adjusted too heavily. 16-bit images have a greater degree of accuracy, so rounding errors are reduced, as is the resulting color banding.
The end result is dithered down to 24-bits, but anything can look good at 24-bits. It's not a problem until you need to tighten in on information. It's kind of like resizing an image from 320 by 240 to 640 by 480. The image looks great at 320, but there are artifcacts to blowing it up to 640. If there was subpixel information in the original image, then the expansion to 640 would go a lot smoother. Try to imagine that in the color space.
*hoping I expressed that in a way that makes sense*