6/12/2023 0 Comments Cinepaint youtube![]() However, there are some touch ups that cannot be done in Ufraw and which we will review here. Most of the general color adjustments, curves, brightness and so on have been done in Ufraw, as close as possible to the original RAW file. We will be using Cinepaint for that, since the program is Color Managed and supports 16bits/channel. After the image selection, a quick and dirty post-processing, a careful processing with Ufraw, now is the time for the final touch up. But thanks anyway, I'm glad there are people around who help on their spare time.OK, we are still in the process of producing a high quality (tiff 16bits/channel) image file from a RAW camera file, using Linux and a color managed workflow. If my problems are not solved, I'll consider taking a more closer look at the dev status and source when I have the time. I'm aware of the buglists you mention, but unfortunately my time is very limited right now and having done professional software development I know that simply putting a vague description on a buglist doesn't cut it - to get to the bottom of this requires some commitment, something which I simply cannot devote time for right now. Jacob: I was hoping to hear experiences from pther photographer-users. ![]() ![]() I've only worked with images of about 30 MB thus far and the software is too unstable, IMHO. Compiling from source would be the next option on my list, but since the program is listed as being used by many professional's it must have some degree of stability on some platform. Jacob Moorman (Quality of Service Manager, )īastian: at least someone else has the same problem! I mainly use PS on windows, since my scanner works there (and that's about all I use windows for nowadays.), so it's not a critical situation, but I would want to have 16-bit editing capability in Linux. While has quite an experienced set of users, for issues like this you are probably best off asking the software developers (CinePaint) or distributors (Debian). The Debian bug tracking system may be found at: These maintainers will work with the upstream software developers (in this case, the CinePaint developers) to work out problems like this. You should also consider reporting the problems to Debian they provide their own bug reporting facilities. The CinePaint project page can be seen at: Īs per the support page for this project, they offer a -users mailing list and a Bug Reporting Tracker either of these would be a good way to report the problems you've had: Before posting, you should check to see if similar problems hae already been reported (there may well be an answer to your problem in the mailing list archives). provides a common set of facilities to each project, including tools to help manage bug reports, as well as mailing lists. Have you reported the issue to the CinePaint project team? CinePaint (formerly FilmGimp) is hosted on, a web site that provides hosting for tens of thousands of different Open Source software development projects. I just long so much for 16bit support in the Gimp. Well, I guess that's why it is called like it's called. My 512MB ram are barely enough, it will swap out all the time. If it helps? I'll try it myself soon.īut the thing that bothers me the most is that clearly it is not optimized to handle large images (this may also be the root problem of the segfaults). Maybe also have a look at available configure options. ![]() That will build it against the libs on your system, and you still get a nice managed Debian-package to install. They seem to have pretty long release cycles (0.18 is from last July), so I guess another version won't help much.īut you could try to compile the package yourself with "apt-get source cinepaint" and doing "debian/rules binary" in the source directory. The Debian version I have is 0.18, so it's the same as the realease version on Sourceforge. But beware: saving in xcf does not seem to get layer masks right (they are just black when opened again). But usually I can do "enough" steps of editing before it crashes, so I just save often. I also use it, also with Debian (unstable), and have similar problems. ![]()
0 Comments
Leave a Reply. |