I seem to get pixel P30 files and they never render through Iview and expressions 2?
Any else have this happen or am I missing something..
I use it a lot with tons of old cr2 files and labeling and sorting is FAST..
But with the P30 files slow to load and thumbnail and image are Pixelated..
Strange Phase is using it but the .TIF files do not render correctly..
It's because most of the processing in a Phase file is done in the conversion software, i.e. C-1, Raw Developer, Lightroom, Photoshop, etc, so when you drop a raw phase file into Expression media/I-view you are just seeing the small embedded preview that doesn't have noise reduction or any processing information, other than white balance. Especially noise reduction, because if you'll notice on the back of your camera, the higher iso you go the rougher the preview gets.
This is one of the reasons you see such a semi rough preivew on most medium format backs, because unlike a dslr (or the new Pentax) there really is no in camera processing, so consequently until Phase has some form of in camera processing, even a new and much improved lcd will not have much effect on the current preview.
In regards to speed of rendering the Phase previews, I've always found they render out pretty quick, mostly because it's a very small embedded preview.
The one great use I have for I-view/Expression media is since I shoot multiple cameras for multiple reasons, sometimes during the same session, I can load all the raw files from all the cameras, drag and drop to put the raw files in place, rename all the raw files so they are in sequence and a logical order, then copy those renamed raw files into a disk I label as master. Then obviously duplicate that disk for security. Then after a few quick checks to make sure everything
copied correctly and will process, I throw away the previous originals as they have a different naming structure.
P.S. One work of caution when renaming. Keep the names as short as possible. We recently completed a large project (10,000 files) where the client wanted specific names that were quite large. Not knowing (or maybe I knew but not remembering) that older Microsoft systems truncated, and changed the names of any file that is long than I think 8 characters (I may be wrong about the actual number), the file numbers the client sent the AD who in turn sent them to us went from 001_blue_dog_runs_wild to bc87j4 which meant we had to visually search for each file.