Hi! Thanks a lot for the analysis!
I've been down with a self-inflicted fever (yellow fever vaccination), but that was also my first thought. I think we are missing the part where we apply the default settings for the batch photos in general for batch export - this includes the DCP profile and the camera default settings, which should all be applied to batch exports. Regards, Klaus Post http://www.klauspost.com 2010/12/14 Edouard Gomez <[email protected]> > > ----- "Edouard Gomez" <[email protected]> a écrit : > > Returns a photo->dcp != NULL when the photo has been selected once in > > the GUI, and NULL if it has never been loaded in the main GUI. As DCP is > > hardly avoidable nowadays, this may induce a failure somewhere deeper and > > later in the code (supposing the dcp profile is not lazily loaded when > > required) > > There seems to have no DCP lazy chooser/loader. > > For photos with a returned NULL dcp, I changed the pointer with the > debugger to my usual d90 dcp profile loaded by a previous photo. And the > export worked like a charm. > > So the bug seems to be narrowed down to: > If a photo hasn't been loaded in the GUI, then no DCP profile is binded to > the photo during batch export and the batch export fails silently somewhere. > > Time for bed tonight, more fun tomorrow :-) > > -- > Edouard Gomez > > _______________________________________________ > Rawstudio-dev mailing list > [email protected] > http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev >
_______________________________________________ Rawstudio-dev mailing list [email protected] http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev
