Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Crop shifting during tethered capture

Dan Trotter
Hi guys,

I've recently switched to windows 10 & upgraded to capture one 10. Today I upgraded to 10.2 in the hope it would be fixed but it's still there.

Having an issue where the crop slowly changes across multiple tethered captures. For example, I set the crop on the first image, and about 50 images down the track the crop has kept the same ratio but has gradually reduced in size. Please see the following links for examples:

https://www.dropbox.com/s/vljg4p9dbxsa1 ... 8.png?dl=0

https://www.dropbox.com/s/xrratd3ycwzle ... 9.png?dl=0
0

Comments

7 comments

Date Votes
  • Dan Trotter
    Bump
    0
  • Dan Trotter
    Really guys, no help at all?
    0
  • HansB
    You posted on the user (to user) forum. And if no other user has seen it or has an idea you may not receive an answer. I don't use crop as next capture adjustment, therefore I cannot tell you anything about it.

    It looks like a bug, so contact Phase One by support case.

    To file a support case, have a look at their website, https://www.phaseone.com/.
    Or use one of these direct links:
    http://support.phaseone.com/, https://www.phaseone.com/SupportMain.aspx

    At the bottom, you can choose the support you are looking for.
    You'll need to log in at this point if you have not already done so.

    The rest is self explaining:
    Personal information and a description of your question, bug, or feature request.


    Regards,
    Hans
    0
  • SFA
    Purely as speculation, might it be something related to lens correction?

    Do the original RAW file dimensions, after RAW conversion, look the same?


    Grant
    0
  • Dan Trotter
    Thanks Hans, I didn't realise this was a user only forum. I have put the question to phase one at the links provided.

    @Grant, wouldn't think it's anything to do with lens correction, I just use the default settings there. I don't use C1 for RAW conversion, and the problem happens during capture so even if they came out ok it wouldn't solve my problem. My clients are watching the screens as the images come through, slowly the crop goes out & we have to correct it every 50 images or so.
    0
  • SFA
    [quote="NNN636179471601844359" wrote:
    Thanks Hans, I didn't realise this was a user only forum. I have put the question to phase one at the links provided.

    @Grant, wouldn't think it's anything to do with lens correction, I just use the default settings there. I don't use C1 for RAW conversion, and the problem happens during capture so even if they came out ok it wouldn't solve my problem. My clients are watching the screens as the images come through, slowly the crop goes out & we have to correct it every 50 images or so.


    OK.

    So are you shooting tethered jpg directly into C1?

    Not RAW captures and not using a Hot Folder.

    But if the ratio is still the same and in portrait mode the full width of the image is still the basis for the constraints on the crop (that certainly seems to be the case in the first image linked though it is not quite so certain in the second) the only other logical variable would be original pixel dimensions of the incoming jpg file. (However your screen capture indicates that the files displayed are Canon RAW files. Some processing will have been applied to convert the data to an image on screen.)

    Either that or something that is not at all obvious in any way.

    It will be interesting to hear what Support have to say.


    Grant
    0
  • Dan Trotter
    Shooting RAW directly into C1 via tethered capture. No conversions, just previews of the original RAW files. As you can see from the supplied images, the cropped pixel dimensions slowly get smaller while the fixed ratio (7x9) is maintained. The original dimensions are are always consistent as you would expect from a RAW file.

    Yes hopefully support finds something! Thanks for your help though
    0

Post is closed for comments.