Am 07.10.2015 um 10:55 schrieb Tobias Ellinghaus:
> Am Mittwoch, 7. Oktober 2015, 09:35:04 schrieb Christian Mandel:
>> Am 07.10.2015 um 08:40 schrieb Christian Mandel:
>>> Am 06.10.2015 um 21:15 schrieb Tobias Ellinghaus:
>>>> Am Dienstag, 6. Oktober 2015, 19:24:31 schrieb Tobias Ellinghaus:
>>>>> Am Dienstag, 6. Oktober 2015, 17:29:54 schrieb Tobias Ellinghaus:
>>>> So much self referencing. So wow. Very mail.
>>>>
>>>>>> Am Dienstag, 6. Oktober 2015, 07:16:04 schrieb
> darkta...@911networks.com:
>>>> [...]
>>>>
>>>>>>> Easy for people with experience in Lua. Do you have some sample for
>>>>>>> newbie like me?
>>>>>>
>>>>>> No sample, sorry. The general idea would be to register a new export
>>>>>> storage and just output the list of images while not actually exporting
>>>>>> anything. I will try to write some sample code later.
>>>>
>>>> As promised here are the three versions. The first two will only work in
>>>> builds from git master, the last should also work in stable releases
>>>> (1.6.8 at the moment). I don't have a build of that handy so I can't
>>>> test, so there might be problems though.
>>>
>>> Tested and works with 1.6.8. I had to manually remove version 0 and 1 to
>>> make it work (just to mention if others want to try). Pictures with
>>> duplicates are printed multiple times, as many lines as image versions
>>> exist (may or may not be desired).
>>
>> Thinking longer about it, I guess for the purpose of the OP (mass
>> processing of images with command line dt) it makes more sense to write
>> a list of selected xmp files. For easier scripting, a combination "raw
>> xmp" side by side could be beneficial, even if the information is
>> redundant since the xmp knows about the raw.
>
> Good point. You can get the xmp with
>
> f:write(i.path.."/"..i.filename.." "..tostring(i)..".xmp\n")

It works, but there's one issue. It will write the xmp location even if 
no xmp file is present (e.g. if you switch off the xmp generation for 
every file in the preferences). Will command line dt rely on the 
physical xmp file or will the entries in the db suffice? (I don't need 
this, I'm just curious.)

Thankfully, this observation reminded me to switch on xmp generation 
after some tests a couple of weeks ago where I switched it off and 
forgot to enable again :-)

Best regards

Chris



------------------------------------------------------------------------------
Full-scale, agent-less Infrastructure Monitoring from a single dashboard
Integrate with 40+ ManageEngine ITSM Solutions for complete visibility
Physical-Virtual-Cloud Infrastructure monitoring from one console
Real user monitoring with APM Insights and performance trend reports 
Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911&iu=/4140
_______________________________________________
Darktable-users mailing list
Darktable-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-users

Reply via email to