Re: [darktable-dev] Options shouldn't be tied to Filmstrip
* Heiko Bauke [04-30-19 20:34]: > Hi, > > Am 27.04.19 um 23:06 schrieb Stefan Klinger: > > Yeah, I'll do that: Stop nitpicking, Patrick. The user suggested that > > the UI could be designed better, and rightly so. And he made > > constructive suggestions, so let's discuss them, constructively. > > I also find the current behavior not intuitive. I often disable/hide the > film strip to have more space to display the edited image and module > options. But I also apply often predefined styles. On default, the button > to select a style becomes invisible if the film strip is disabled/hidden > unless one reenables via the mentioned buttons. > > I only became aware of this keyboard short cut because it was mentioned in > this thread. It is bad that there is no intuitive way to turn of the film > strip while keeping access to styles and other options below the center > image in the darkroom module. you can keep them visible/accessable just by enabling the bottom panel, and keep the filmstrip hidden, toggle with -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Options shouldn't be tied to Filmstrip
Hi, Am 27.04.19 um 23:06 schrieb Stefan Klinger: Yeah, I'll do that: Stop nitpicking, Patrick. The user suggested that the UI could be designed better, and rightly so. And he made constructive suggestions, so let's discuss them, constructively. I also find the current behavior not intuitive. I often disable/hide the film strip to have more space to display the edited image and module options. But I also apply often predefined styles. On default, the button to select a style becomes invisible if the film strip is disabled/hidden unless one reenables via the mentioned buttons. I only became aware of this keyboard short cut because it was mentioned in this thread. It is bad that there is no intuitive way to turn of the film strip while keeping access to styles and other options below the center image in the darkroom module. Heiko -- -- Number Crunch Blog @ https://www.numbercrunch.de -- Cluster Computing @ https://www.clustercomputing.de -- Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Raw import using color matrices
Hi, Please write a bug report on github to discuss the issue. You can attach the files there, or put them on a drive if necessary. Thanks rawfiner Le mar. 30 avr. 2019 à 10:28, Florian Hühn a écrit : > Hi, > > I am currently facing an issue where the red channel of imported images in > darktable contains corruptions (black areas and ghost images) when i use > "standard color matrix" (camera raw) or "embedded matrix" (dng file). > Color profiles like Rec709 work as expected. Also converting the raw file > using dcraw and importing the resulting tiff in darktable (sRGB color > profile) works fine. I already made sure that dcraw and adobe_coeff.c of > darktbale use the same color matrix for my camera, so I expected similar > results. I cross checked with dcraw, rawTherapee and my camera > manufacturers raw software - all show the picture as expected, only > darktable shows corruptions. > > What would be the best place to discuss this issue? Attaching huge raw > files to a mailing list might not be the best option, I guess. > Should i open a bug report for this? Currently it seems to me as if > darktable somehow handles color matrices differently from all the other > programs, but I'm not an expert on this topic. Maybe I am missing something > critical? > > Cheers, > Florian > > ___ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Lighttable/Selected/Duplicate broken in 2.6.2 on macOS?
Can anyone confirm this is or is just my installation? I get the message 'duplicating 1 image' but no duplicate ever shows up in my collection. .mm ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Raw import using color matrices
Hi, I am currently facing an issue where the red channel of imported images in darktable contains corruptions (black areas and ghost images) when i use "standard color matrix" (camera raw) or "embedded matrix" (dng file). Color profiles like Rec709 work as expected. Also converting the raw file using dcraw and importing the resulting tiff in darktable (sRGB color profile) works fine. I already made sure that dcraw and adobe_coeff.c of darktbale use the same color matrix for my camera, so I expected similar results. I cross checked with dcraw, rawTherapee and my camera manufacturers raw software - all show the picture as expected, only darktable shows corruptions. What would be the best place to discuss this issue? Attaching huge raw files to a mailing list might not be the best option, I guess. Should i open a bug report for this? Currently it seems to me as if darktable somehow handles color matrices differently from all the other programs, but I'm not an expert on this topic. Maybe I am missing something critical? Cheers, Florian ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
