Tether preview problems in C1Pro4 with Canon cameras
I shoot high volume fashion catalogs, and have always happily used C1Pro3.7 with Canon 1ds MarkII's. We postponed upgrading to new cameras until C1Pro4 was more stable.. so we just made the upgrade. Unfortunately we have run into a problem that makes C1Pro4 unusable for us..... has anyone found a workaround?
During tethered shooting with 1ds MarkIII's, under Auto Select New Capture we have the choice of When Ready or Immediately. When we choose Immediately the capture preview is heavily pixelated so it's unusable for our clients who are watching the monitor, and it moves to the next pixelated capture before showing a rendered preview (3.7 would give us a second of rendered preview which was enough to make a decision on if the shoot was going in the right direction). When we choose When Ready, it only shows the most recent fully rendered preview and completely skips all the other captures before then, so we only see the preview of one capture out of every 15 or so.
Is there any way to fix this problem in C1Pro 4?
During tethered shooting with 1ds MarkIII's, under Auto Select New Capture we have the choice of When Ready or Immediately. When we choose Immediately the capture preview is heavily pixelated so it's unusable for our clients who are watching the monitor, and it moves to the next pixelated capture before showing a rendered preview (3.7 would give us a second of rendered preview which was enough to make a decision on if the shoot was going in the right direction). When we choose When Ready, it only shows the most recent fully rendered preview and completely skips all the other captures before then, so we only see the preview of one capture out of every 15 or so.
Is there any way to fix this problem in C1Pro 4?
0
-
The largest problem here is not CO4, it is compared to 1DsMKii you are trying to push a 1.4x larger file through USB which is half the speed of firewire. (keep in mind that USB is a much more heavier protocol then IEEE1394 which means that speed and actual speed is two different things.)
Capture Integration did some interesting test with capture to preview test here
http://www.captureintegration.com/tests/comparisons/
Which display quite clear how much faster CO4 is compared to CO30 -
Unfortunately I don't think that is the problem. We tested the same workflow with our trusty 1ds MarkII and a 5D MarkII and experience the same problem of skipped previews.
Interestingly, when we test the workflow on a MacPro tower the problem disappears. We only experience the problem on a MacPro laptop... our main one has 3ghz processor with 8GB of RAM and a 256GB solid state drive... but we have tested it on two others and experience the same problem. On the surface this would make it appear to be some sort of processor speed issue, but we don't think that is it either.
We can actually force the computer to go to the most recent capture when "When Ready" is selected by just scrolling to the next thumbnail preview manually. But when we let the software take control of going to a preview "When Ready" it just skips to the very last image capture. It seems to be some sort of bug in how the "When Ready" option works on a laptop. The actual time it takes for an image to resolve to a clear preview is exactly the same on both the laptop and MacPro tower, so it doesn't make sense that the processor speed or file size is actually the problem.0 -
I would raise a support case here, I believe there is in the instance you write something on the laptop that is causing this (since it works on the desktop and you say the generation time is the same) maybe some kind of preview generating or folder monitoring program. 0 -
I did start a support case, which was forwarded to R&D. Not sure if that means I will ever get a firm answer.
After further testing on our end, we found that images were skipped in "When Ready" mode even on a MacPro tower when tethered to a Canon camera. Just not as many were skipped and not as consistently. The software would only skip one or two previews after every four or five previews came in without problem. It happened with a Canon 5dMarkII, 1dsMarkII and 1dsMarkIII. We tested on three different MacPro towers as well. All results were the same.
After all this testing we also found some inherent instability in C14 and also some annoying bugs (custom tool tabs constantly disappearing for instance). But we could live with that. We can't live without our clients being able to see the images preview on screen as we are shooting. We have finally given up, and have moved our workflow to shooting into the Canon EOS Utility and managing the files in Adobe Bridge.
I hope that Phase One can solve these software problems so that someday we can consider using Capture One again.0
Post is closed for comments.
Comments
4 comments