As Tobias explains this is a bug and already fixed, so please ignore my question and sorry for the noise.
Best regards Chris Am 08.12.2015 um 13:37 schrieb Christian Mandel: > Am 08.12.2015 um 03:40 schrieb Steven Fosdick: >> My guess is that the camera does not record the raw image data any >> differently when held in portrait mode so the RAW file, as seen by >> darktable, is still effectively landscape but there is a marker set by the >> camera in the EXIF data that says something along the lines of "this was >> taken portrait". When darktable imports the picture it automatically >> applies the orientation module to get the picture into portrait orientation >> and that therefore counts as a modification. > > That explanation sounds reasonable, however, ... > >> If I go to one of my portrait pictures and turn off the orientation module >> it reverts to landscape. > > ... this does not happen for me (at least not if done by removing the > history). If I take a portrait oriented picture and revert all changes > by clicking on 0 on the history stack, the picture is still vertically > oriented. It seems that the modules stay on independent of the history > stack. Nevertheless, the "changes" marker disappears for this picture. > If I switch all modules off manually, the picture orientation changes to > landscape, I get a weird whitebalance etc. However, the picture is > marked as changed. Clicking on "discard" in the lighttable's history > stack module reapplies the three initial modules and marks the picture > as changed. > > For landscape pictures, the behaviour is more or less exactly the same. > There's only one difference: it is not marked as changed. When I enter > the darkroom the 3 modules, including rotation, are applied > automatically and the picture is marked as changed. This mark is removed > by the "discard" button. > > Up to now, I thought of the "changes" marker as a way to tell if I see > the embedded preview from the raw or an actual development preview of > darktable. But it seems I misunderstood the concept. The manual is not > very specific about this marker (or I missed an important part). > > For me, after all, it feels somehow inconsistent, it would be great if > anybody could explain (or link to an explanation of) the exact behaviour > and the reasons behind. > > Thanks and best regards > > Chris > > >> On 7 December 2015 at 09:21, Christian Mandel <c.man...@gmx.net> wrote: >> >>> Hi all, >>> >>> for a while I wonder that freshly imported images are randomly marked as >>> changed (with the +-wave icon). Now it seems that I have discovered a >>> pattern: it affects only the portrait oriented images (Canon 5DII), and >>> probably all of them. The dt version is 1.6.9, 64 bit on ubuntu 15.04, >>> build from Pascal's ppa (1:1.6.9-0pmjdebruijn1~vivid). Checking older >>> film rolls it seems that this only happens with recent dt versions and >>> that it happens during import. Do you have an explanation? >>> >>> Thanks & best regards >>> >>> Chris > > > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 > ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
