Saving projects

If you could save entire projects, similar to the DSS, that would be very helpful.

Otherwise, I think the program is great.

Is it even considered that RAW files from Sony and Olympus are supported?

Yes that would be a very nice feature and I believe it's on "THE list" for future releases.

Hi, 

I raised this some time ago and Mabula said it was on his list. I just logged in now to see if there had been any progress as I'm just about to set up 5 session LRGBHa pre-processing.

This is going to take me a long time to set up, and especially check I haven't got any files wrong - which sadly I frequently manage to screw some file up somewhere - wrong flat/session/colour for wrong sub etc.

It would be mega useful to be able to come back another day and run the calibration again.

Being able to just save the "Load" step would be a major benefit and surely would be a minor change. Perhaps this could be done whilst waiting for the full project save.  

@mabula, how about it Mabula 🙂 ?

Sorry Mabula has been on a holiday. I pm-ed him to get involved on the forum for some of these questions. Thanks for your patience! (@mabula-admin)

Thanks, would be good to get an update but it will wait until Mabula returns, we all need our holidays 🙂

I was just thinking about how this could work, for example saving source data locations of the files involved or saving a copy. My preference would be to save a copy of loaded files within the APP directory as separate folders (Lights, Darks, Flats etc). This approach should then be extendable to saving the complete project at some point.

Using the source files would save space but things get moved/renamed over time. I hit this issue yesterday, I spent all day using APP pre-processing and rerunning calibration with different settings. During the day I ran SGPro Image Grader on some of the images and it renamed them to include HFR data - after which the APP Calibration could no longer find them and stopped working until I renamed them back manually.

Thanks

Jon

I think you can make a case for both saving with and without the image files.  You definitely want to save settings and file pathnames.  But with CMOS cameras and short exposures, some of my projects have over 1000 files loaded.  Saving a copy of all those would be very slow and take up a lot of disk space.  In those cases I just want to save the pathnames and settings.  E.g., I may want to create a project that has my settings and pathnames to files that don't change for a particular imaging system, e.g. master darks, bias and BPM.

Cheers,

Rowland