Anyone else change their 10D workflow?

I changed the way I processed my digital RAW files after I upgraded from the D60 to the 10D.

I shoot raw
breezebrowser converts to 16 bit tiffs, NOT linear. (no sharpening)
Edit in photoshop (no sharpening)
Print in Qimage with a set sharpeing.

Results are better then all the linear conversion work I did with the D60!

Greetings-
We are in a critical period here. Because of the problem with the 16bit Linear conversion (problem with the SDK), alternative workflows must be developed. It is likely that Canon will not respond to this problem. I'm not sure anyone has even brought it to their attention. If anyone is getting good results through some interesting workflow- please post it here!

Thanks-
Bob

PS: Dang..just got the call..my 10D is in!

I haven't shot much beyond tests yet, but Photoshop, using Adobe Raw (hacked to recognize the 10D) and Fred Miranda's 10D SC pro action are getting me good results so far.

The only 'real' shots so far (I have had the camera for a week now) are at http://photo.fx4.net …ry/list.php?exh​ibition=24

Scott

Do you plan on using the LPbatch from Fred when it is released?

Is there any point in purchasing the LPbatch and the CS Pro? Don't they both sharpen?

I have been using breezebrowser to convert my RAW files, it seems to work ok.

>Do you plan on using the LPbatch from Fred when it is released?

No, but that is mostly Canon's fault. Canon File Viewer for Mac OS X takes 54 seconds to convert from RAW to tiff, Adobe Raw plugin takes 6, to convert to a properly adjusted 16bit tiff (the results are much like LPbatch - no linear to non-linear action needed) I have not seen any advantage to a Linear conversion workflow over a Adobe Raw conversin workflow (not to mention, I already bought the Adobe Raw plug-in). I may once Fred gets LPbatch tweaked to the 10D, but it would have to be a lot of difference to accept a 9 times (and more, depending on how fast the batch runs) increase in processing time.

The abysmally slow times for Canon File Viewer is due to the App being ported (poorly) rather than written optimised for OSX, and that it (apparently) makes no use of Altivec ( http://developer.apple​.com/hardware/ve/ )

And I really like the way AR works (and I can batch process raw files with photoshop if I don't wish to tweak them)