I was trying to dedicate some time to profile rawstudio using the perf profiler available with recent linux kernels.
And I'm quite pleased with its ease of use compared to oprofile :-) However, for profiling/benchmark reproductabilty purposes, i was hoping i could easily build a RS_QUEUE and start a batch processing. I've read rs-batch.c and... hmmm, a too big challenge just for benchmark purposes :-) GUI code is so deeply nested in the processing code that i don't see how i can process an image w/o starting the GUI. The plan was to simply replace the test function so that it loads files and process them one by one, using a specific settings file. Out of curiosity, I tried to find if there was a simple filename>photo>processing function and I've been a bit surprised the rs-batch code would do the processing quite differently from "export as" or "quick export". Am i missing something obvious ? Shouldn't a single photo or multiple photos processing be the same code path ? Is it planned for the core processing of a photo to be decoupled from the GUI direct calls ? GUI updates can be handled through carefully designed hooks/callbacks. -- Edouard Gomez _______________________________________________ Rawstudio-dev mailing list [email protected] http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev
