Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Chris Siebenmann
> On Sunday, July 26, 2015 18:21 Chris Siebenmann wrote: > > I don't have a useful answer in general[*], but there is a relatively > > lesser known darktable feature that may be helpful to you. Darktable > > normally saves a copy of the XMP in the generated JPG file and it also > > supports reload

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Patrick Shanahan
* David Vincent-Jones [07-26-15 22:09]: > On Sunday, July 26, 2015 18:21 Chris Siebenmann wrote: > > I don't have a useful answer in general[*], but there is a relatively > > lesser known darktable feature that may be helpful to you. Darktable > > normally saves a copy of the XMP in the generated

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread David Vincent-Jones
On Sunday, July 26, 2015 18:21 Chris Siebenmann wrote: > I don't have a useful answer in general[*], but there is a relatively > lesser known darktable feature that may be helpful to you. Darktable > normally saves a copy of the XMP in the generated JPG file and it also > supports reloading the XM

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Chris Siebenmann
> I have filed a feature request [1], but I'm getting the feeling that > I'm the only one having this problem. How do you guys make sure that > you will never accidentally destroy a particular history stack? I don't have a useful answer in general[*], but there is a relatively lesser known darkt

Re: [Darktable-users] OpenMP problem

2015-07-26 Thread andrew_terekhov
Strangely the issue was gone after I reinstalled Mate packages and then installed Cinnamon desktop. From: "andrew_terek...@yahoo.com" To: Tobias Ellinghaus ; "darktable-users@lists.sourceforge.net" Sent: Sunday, July 26, 2015 1:09 PM Subject: Re: [Darktable-users] OpenMP problem E

Re: [Darktable-users] OpenMP problem

2015-07-26 Thread andrew_terekhov
Everything looks fine: $ ldd /opt/darktable/bin/darktable|grep gomp    libgomp.so.1 => /lib64/libgomp.so.1 (0x7f109c198000) $ /opt/darktable/bin/darktable --version this is darktable 1.7.0+1818~g3c930c6 copyright (c) 2009-2015 johannes hanika darktable-de...@lists.sf.net compile options:  

Re: [Darktable-users] Nokia Lumia 930 Challenge

2015-07-26 Thread Tobias Ellinghaus
Am Sonntag, 26. Juli 2015, 17:19:44 schrieb Matthias Bodenbinder: > Hi, Hi. [...] > saved dng + jpg. The jpgs are smaller than the dng. jpg = 3072x1728 (= 5 > MP) while the dng is 5367x3024 (= 16 MP, advertized with 20 MP. [...] I didn't look at the images but did you try using the same approa

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Tobias Ellinghaus
Am Sonntag, 26. Juli 2015, 15:51:36 schrieb Stefan Klinger: > Hi Jan, > > On 2015-Jul-26, Jan Kundrát wrote with possible deletions: > > I'm storing all of my XMPs in git and all my .CR2s in git-annex. > > I've just tried this. After restoring from a backup, I see DT doing > non-changes on the co

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Tobias Ellinghaus
Am Sonntag, 26. Juli 2015, 16:49:50 schrieb Stefan Klinger: [...] > Also, I want to have the XMP files > to do a backup (I'd rather store them than the DB which might not work > with DTs next Version...) Not saying that it would anything but a strange idea to backup the db. However, we never (I

[Darktable-users] Nokia Lumia 930 Challenge

2015-07-26 Thread Matthias Bodenbinder
Hi, I recently got a Nokia Lumia 930. One interesting feature about this smartphone is its ability to deliver raw files (DNG). I gave it a try and saved dng + jpg. The jpgs are smaller than the dng. jpg = 3072x1728 (= 5 MP) while the dng is 5367x3024 (= 16 MP, advertized with 20 MP. Dont know w

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Stefan Klinger
On 2015-Jul-26, Patrick Shanahan wrote with possible deletions: > * Stefan Klinger [07-26-15 09:26]: > > Also, there will be a lot of "Untracked files" listed by > > `git`, because DT creates an XMP just for looking at a picture... > > Core Options --> uncheck "create sidecar" > But, iianm, then

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Patrick Shanahan
* Stefan Klinger [07-26-15 09:26]: > On 2015-Jul-26, Jan Kundrát wrote with possible deletions: > > I'm storing all of my XMPs in git and all my .CR2s in git-annex. > > Hey, that's a neat idea! It nicely works locally, and also makes it > easy to tell apart those XMP files I actually wanted to c

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Jan Kundrát
On Sunday, 26 July 2015 15:51:36 CEST, Stefan Klinger wrote: > I've just tried this. After restoring from a backup, I see DT doing > non-changes on the committed XMP files: I've seen a variation of this when upgrading the underlying libraries and DT. I've never seen this otherwise, AFAIK, but I j

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Stefan Klinger
Hi Jan, On 2015-Jul-26, Jan Kundrát wrote with possible deletions: > I'm storing all of my XMPs in git and all my .CR2s in git-annex. I've just tried this. After restoring from a backup, I see DT doing non-changes on the committed XMP files: diff --git a/DSC_9270.NEF.xmp b/DSC_9270.NEF.xmp

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Stefan Klinger
On 2015-Jul-26, Patrick Shanahan wrote with possible deletions: > I would guess the best solution would be for you to adjust your work flow > and computer habits to best benefit your output. I have 30years of computer habits: Store changes when you like them. But DT does not work this way, it just

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Stefan Klinger
On 2015-Jul-26, Jan Kundrát wrote with possible deletions: > I'm storing all of my XMPs in git and all my .CR2s in git-annex. Hey, that's a neat idea! It nicely works locally, and also makes it easy to tell apart those XMP files I actually wanted to create from those that DT just created because

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Patrick Shanahan
* Stefan Klinger [07-26-15 08:52]: > Hi there, > > as a newbie I'm trying to experiment a lot with what DT can do. > However, I find it hard to not accidentally destroy a history stack > that turns out well, or that I want to consider "fixed" because I have > ordered a print of it. Unfortunately

Re: [Darktable-users] Write-protected XMP files

2015-07-26 Thread Jan Kundrát
On Sunday, 26 July 2015 14:45:56 CEST, Stefan Klinger wrote: > How do you guys make sure that > you will never accidentally destroy a particular history stack? I'm storing all of my XMPs in git and all my .CR2s in git-annex. Cheers, Jan -- Trojitá, a fast Qt IMAP e-mail client -- http://trojita

[Darktable-users] Write-protected XMP files

2015-07-26 Thread Stefan Klinger
Hi there, as a newbie I'm trying to experiment a lot with what DT can do. However, I find it hard to not accidentally destroy a history stack that turns out well, or that I want to consider "fixed" because I have ordered a print of it. Unfortunately, DT is rather trigger-happy when destroying an

Re: [Darktable-users] Segmentation fault when trying to profile denoise

2015-07-26 Thread Tobias Ellinghaus
Am Samstag, 25. Juli 2015, 10:18:06 schrieb Urs Schütz: [...] > To test the noise profiles locally, run: > darktable --noiseprofiles /[pathToNoiseprofile]/presets.json That only works with development versions, the stable series (1.6.x) still uses compiled in noise profiles. > Regards, Urs To

Re: [Darktable-users] OpenMP problem

2015-07-26 Thread Tobias Ellinghaus
Am Sonntag, 26. Juli 2015, 07:42:36 schrieb andrew_terek...@yahoo.com: > I use Fedora 22 64 bit Mate and Darktable built from git. Everything worked > great, DT used all 8 cores. Then I decided to try XFCE. I didn't like it > compared to Mate and promptly removed it. After that DT started using onl

[Darktable-users] OpenMP problem

2015-07-26 Thread andrew_terekhov
I use Fedora 22 64 bit Mate and Darktable built from git. Everything worked great, DT used all 8 cores. Then I decided to try XFCE. I didn't like it compared to Mate and promptly removed it. After that DT started using only 1 core instead of 8. I tried rebuilding DT, reinstalling it from package