Media Pro 1.4 Slower Than iView Media Pro 3.1.3
I have been a die-hard user of iView Media Pro since it was a small company in Battersea. I love it from its no-frills, down-to-business interface, because it works with real speed, and I can customise it easily with Applescript. Just brilliant.
I use a Leaf Aptus 22 and Nikon D800E. I have recently migrated from Leaf Capture to Capture One Pro 7, which I am enjoying very much. It means I can have the same workflow with both cameras and live view on both. Its ability to get the best out of high ISO files from the Nikon is second to none.
In this general state of euphoria with Capture One Pro 7, I decided to upgrade my DAM licence to Media Pro as well. Most disappointing. The interface is not as clean and legible as the original iView Media Pro. I wish there was a preference that allowed one to switch the interface from original to new. It also feels slower. I noticed several posts on this, so I tried to find a way to quantify it.
iView Media Pro 3.1.3 continues to work beautifully on my system. It renders Nikon RAW files properly, and uncompressed MOS files too, via the Apple RAW converter. Obviously, 22MP and 36MP files slow it down, but it's still a snappy operator. I can not remember the last time it froze or crashed.
Media Pro (1.4.0.660044) has the obvious advantage of integration with Capture One Pro, and the ability to read and render edits made in Capture One Pro. That's great. No argument there. Just that it feels so lethargic in operation.
For this test, I created a new iView Media Pro and Media Pro 1.4 catalogue, and dragged four fresh, un-edited RAW files from the Nikon into it. I selected all four files, followed by <cmd></> for the lightbox, and timed them with a stop watch. Both apps were set as equally as possible: in particular "use embedded preview" was un-ticked, "rendering in foreground for all images" (which is faster) was ticked in Capture One Media Pro.
iView Media Pro 3.1.3
Apple Render Engine
0' 26"
Capture One Media Pro 1.4.0
Apple Render Engine
0' 33"
Capture One Media Pro 1.4.0
Phase One Render Engine
4' 21"
The experiment suggests that users of Phase One Media Pro would benefit from switching to the Apple render engine when sorting a load of exposures quickly, only using the Phase One render engine when it's critical to see the image with all its edits.
It's odd, because Capture One Pro 7 renders quite quickly, so I hope it will be made to work just as fast in Media Pro eventually.
I use a Leaf Aptus 22 and Nikon D800E. I have recently migrated from Leaf Capture to Capture One Pro 7, which I am enjoying very much. It means I can have the same workflow with both cameras and live view on both. Its ability to get the best out of high ISO files from the Nikon is second to none.
In this general state of euphoria with Capture One Pro 7, I decided to upgrade my DAM licence to Media Pro as well. Most disappointing. The interface is not as clean and legible as the original iView Media Pro. I wish there was a preference that allowed one to switch the interface from original to new. It also feels slower. I noticed several posts on this, so I tried to find a way to quantify it.
iView Media Pro 3.1.3 continues to work beautifully on my system. It renders Nikon RAW files properly, and uncompressed MOS files too, via the Apple RAW converter. Obviously, 22MP and 36MP files slow it down, but it's still a snappy operator. I can not remember the last time it froze or crashed.
Media Pro (1.4.0.660044) has the obvious advantage of integration with Capture One Pro, and the ability to read and render edits made in Capture One Pro. That's great. No argument there. Just that it feels so lethargic in operation.
For this test, I created a new iView Media Pro and Media Pro 1.4 catalogue, and dragged four fresh, un-edited RAW files from the Nikon into it. I selected all four files, followed by <cmd></> for the lightbox, and timed them with a stop watch. Both apps were set as equally as possible: in particular "use embedded preview" was un-ticked, "rendering in foreground for all images" (which is faster) was ticked in Capture One Media Pro.
iView Media Pro 3.1.3
Apple Render Engine
0' 26"
Capture One Media Pro 1.4.0
Apple Render Engine
0' 33"
Capture One Media Pro 1.4.0
Phase One Render Engine
4' 21"
The experiment suggests that users of Phase One Media Pro would benefit from switching to the Apple render engine when sorting a load of exposures quickly, only using the Phase One render engine when it's critical to see the image with all its edits.
It's odd, because Capture One Pro 7 renders quite quickly, so I hope it will be made to work just as fast in Media Pro eventually.
0
-
I see what you mean, and yes, it's rather slow. Especially for the light table.
In my experience, the light table is used for further inspection of the individual files, just like in the old days with real slides. However, MP already offers the full preview (one of the 3 view modes) and i find myself selecting my pictures in there and moving to CO7 to act as a light table / raw converter. This greatly speeds up my workflow, especially since my CO edits are captured and visible in MP.
It took me a while to adapt to this workflow, but it leaves MP delivering its strength, which IMO is cataloging of files.
YMMV of course, but this way i get the best out of both P1 apps.0
Post is closed for comments.
Comments
1 comment