Re: [Gimp-user] Re: Rotoscoping
Mark Rubin <[EMAIL PROTECTED]> wrote: > > For me, the most important feature of filmgimp/cinepaint is the > support for greater than 8 bits per color component (16 bit integer > and 32 bit floating point). Hear, hear! This is the only reason I have filmgimp on my system - the ability to edit 16-bit files from my cameras prior to doing final 8-bit work in Gimp. I would be very happy if I didn't have to use filmgimp for this, as (has been indirectly pointed out) the interface is rather old-fashioned. The first problem is it doesn't have a drag-n-drop interface similar to that used by gimp-remote (which I use for passing files to the Gimp from my database) and goes on from there. __ David Burren ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Re: Rotoscoping
Hi, Mark Rubin <[EMAIL PROTECTED]> writes: > Last week I attended a public meeting chaired by the cinepaint project > lead. I know very little about the reasons behind the cinepaint/gimp > split. I do think it's unfortunate that the split is hindering the > development of an open-source image editing program combining the > richness and maturity of gimp 1.2/1.3/2.0 with the color precision of > cinepaint. Support for more color models with more precision as well as better color management is one of the main goals of GIMP's future development. I don't think the split is effectively hindering this. Sven ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Re: Rotoscoping
"Sven Neumann" <[EMAIL PROTECTED]> writes: > > > Which begs for the question: why is current gimp not extended to > > include the film-gimp specific features? > > Who says it isn't? GAP already provides quite a lot of that > functionality (and more). Other features such as support for more > color spaces are being worked on. For me, the most important feature of filmgimp/cinepaint is the support for greater than 8 bits per color component (16 bit integer and 32 bit floating point). > The cinepaint developers clearly expressed that they are not > interested in such a merge. Last week I attended a public meeting chaired by the cinepaint project lead. I know very little about the reasons behind the cinepaint/gimp split. I do think it's unfortunate that the split is hindering the development of an open-source image editing program combining the richness and maturity of gimp 1.2/1.3/2.0 with the color precision of cinepaint. = -- MARK [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Re: Rotoscoping
Hi, Stefaan Himpe <[EMAIL PROTECTED]> writes: > > In my opinion > > it is a shame that some good hackers are wasting their time on this > > codebase. > > Which begs for the question: why is current gimp not extended to > include the film-gimp specific features? Who says it isn't? GAP already provides quite a lot of that functionality (and more). Other features such as support for more color spaces are being worked on. > Maybe after the bug week, a merge month can be organized? The cinepaint developers clearly expressed that they are not interested in such a merge. Sven ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Re: Rotoscoping
Hi, > In my opinion it is a shame that some good hackers are wasting their time on this codebase. Which begs for the question: why is current gimp not extended to include the film-gimp specific features? Maybe after the bug week, a merge month can be organized? Just a (probably too naive) newbie question, Stefaan. ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
