Handling other proprietary files

[OldRadioGuy]

ASP handles (and recognizes) JPEG, TIF and RAW files extremely well, but what about the proprietary formats of the photo editors? There are times when one needs to save a file in PSPIMAGE, PSD, PLD, etc. formats for later work in the image, because adjustments applied might be lost saving to a TIF file. How have you guys who are experienced Bibble users handled this situation?

Bob

[tomsi42]

It has never been a problem for me, as I see AfterShot as either a front-line tool or an end-to-end tool. Usually, I try to do all my post-processing in Bibble (i will switch to ASP when all the plugins I use are available for ASP). In the few cases I want more, I will save to a TIFF and continue in my other editor. I know that Photoshop Elements lets me save layers in a TIFF file, but I am not sure if ASP can read thos TIFF files.

[afx]

ASP handles (and recognizes) JPEG, TIF and RAW files extremely well, but what about the proprietary formats of the photo editors? There are times when one needs to save a file in PSPIMAGE, PSD, PLD, etc. formats for later work in the image, because adjustments applied might be lost saving to a TIF file. How have you guys who are experienced Bibble users handled this situation?

Simply, Bibble is not a DAM. It has a pseudo toy DAM component, but if you really need a DAM, get something real, like iDImager, iMatch, ....

cheers
afx

[bananahead]

One of the early things that needs to be done for both ASP and PSP is that they need to become aware of each other.

My default behaviour is to save from ASP to 16 bit TIFF and then open in PSP. I would be very happy if I could save as PSP from ASP instead.

[claudermilk]

ASP handles (and recognizes) JPEG, TIF and RAW files extremely well, but what about the proprietary formats of the photo editors? There are times when one needs to save a file in PSPIMAGE, PSD, PLD, etc. formats for later work in the image, because adjustments applied might be lost saving to a TIF file. How have you guys who are experienced Bibble users handled this situation?

Simply, Bibble is not a DAM. It has a pseudo toy DAM component, but if you really need a DAM, get something real, like iDImager, iMatch, ....

cheers
afx

Precisely! It is also not a pixel editor. If you need one, get PhotoShop, PaintShop Pro, etc.

I treat Bibble (nee, ASP) the same as tomsi43 does. Either it provides the first stage feeding the pixel editor, or it is the entire editing process, outputting a finished file. I never try ot back up from the pixel editor to the RAW converter. I'm not sure how that would even work on a technical level anyway.

[ashmoore]

Indeed, the initial purpose for Bibble was as a raw processor, so it was not even aimed at jpegs initially.
So its true purpose is to create either final images or images to be handed off to at pixel editor like photoshop or PSP at which point it has no more involvement with the image.

[grubernd]

i do about 99% (or more) only in aftershot.
the rest goes out as 16bit TIFF, gets edited, maybe saved as an interim (proprietary) file, then resaved as 16bit TIFF when done. i put those files side-by-side into the folder with my raws (because they are rare and few) and make final output (web, etc) from ASP again.
i dont expect ASP to handle such boxes of pandora like PSD, PSP or XCF.
in terms of longterm archiveability this is a very good and stable workflow - flat TIFFs with no extra fuss can be read by almost any software handling images. even photoshop files are not 100% compatible up and down versions, so deciding at one point that an image is "done" is a good thing.