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. ⚠️

Images not captured on CF Card

Comments

10 comments

  • MidWestTech
    You can't shoot tethered and write to the card, there is no setting to accomplish this.

    Having a card in the camera while shooting tethered hinders performance anyway.

    One thing you are going to want to make sure you have correct is that only the provider you need is selected in the preferences menus, that is often the first place to look for performance issues related to tethered shooting.
    0
  • johnnaccarato
    Thanks @midwestTech! At least I know I wasn't going crazy...
    0
  • Jonthepom
    [i]Having a card in the camera while shooting tethered hinders performance anyway.[/i]

    I didn't know that. I shoot tethered and always leave the cards in the camera. What improves if I remove them?
    0
  • MidWestTech
    Sorry Jon, just saw this reply.

    Some manufacturer's SDKs are written in such a way that having a card in the camera can cause connection or reconnection issues with the software. This seems to be less of an issue than it used to be post version 7.1.2, at this point it may just be a habit I have gotten myself into.
    0
  • Permanently deleted user
    [quote="johnnaccarato" wrote:
    I recently did a shoot and noticed that while tethered, none of the images were stored on the CF card. Is there a setting where it will store on the CF card AND on the desktop/laptop?

    I just couldn't find it anywhere and the program kept crashing and making me nervous.

    Thank you.


    Not with Capture One directly. Capture One's tethering is not at all robust with or without a CF card in the camera. It has little or nothing to do with the manufacturers SDK, it is Capture One's limitations.

    It is perfectly possible to shoot to both your CF card and tether at the same time, you just have to use another more robust software for tethering and if you still want to use Capture One you can set up capture one to use a hot folder that will import files as they come into the folder you set up for your teething software to capture to.

    It is IMO preferable to capture to both a CF card and a computer so as to have redundancy and for example not have to stop shooting if you lose your connection.

    This will depend on what camera you are using too.

    What camera are you using?
    0
  • MidWestTech
    [quote="FredBGG" wrote:
    It is perfectly possible to shoot to both your CF card and tether at the same time, you just have to use another more robust software for tethering and if you still want to use Capture One you can set up capture one to use a hot folder that will import files as they come into the folder you set up for your teething software to capture to.


    And then you can have the joy of letting all of your images show up slower into C1Pro and with no adjustments. In my world, the people watching the images come in on the screens have an expectation of color correct viewing and having to stop shooting to play catch up and make images look right is a non-option. If your environment varies, the usefulness of this workflow varies as well, but keep in mind that you will still lose the ability to "copy from last" when using a hot folder and beyond trying to GUI script this portion of the work flow to get C1Pro do this automatically, it can't be done. This copy from last using hot folder functionality has been formally requested of Phase in the past.

    [quote="FredBGG" wrote:
    It is IMO preferable to capture to both a CF card and a computer so as to have redundancy and for example not have to stop shooting if you lose your connection.


    The changes implemented in 7.1.2 have increased the reliability of the connection and made reconnecting after a dropped connection an option where it never was before. If you are still using an older version, I suggest you update. If you still have a lot of dropped connections, you might want to troubleshoot the connection.

    [quote="FredBGG" wrote:
    Capture One's tethering is not at all robust with or without a CF card in the camera. It has little or nothing to do with the manufacturers SDK, it is Capture One's limitations.


    Yes, it is the SDK that controls where the camera is writing to, not the tethering software. Phase has had a long track record of not reengineering the SDKs that other camera brands provide for a myriad of reasons, chief among them is that no one like getting sued. Phase isn't stupid, they manage a fairly robust intellectual property library and they know the ins and outs of what they should and should not do in this area.

    If you care to show me some code or a plist from your favorite SDK that proves me wrong I would be happy to take a look.
    0
  • Permanently deleted user
    [quote="MidWestTech" wrote:

    And then you can have the joy of letting all of your images show up slower into C1Pro and with no adjustments. In my world, the people watching the images come in on the screens have an expectation of color correct viewing and having to stop shooting to play catch up and make images look right is a non-option.


    Setting the correct color balance in camera is actually very simple to do.

    If corrections cannot be applied automatically when using a hot folder is a limitation of Capture One.

    No problem doing so with Lightroom.

    You say that playing catchup to make adjustments is non-option..... it's a sad limitation. On many shoots it is more important to have redundancy and shoot as reliably as it is to shoot direct to a CF card. It is also important to have redundancy. In particular on location or at a rental studio where after the shoot laptop/computer needs to be transported.

    I'm not sure what you shoot, but to use your words "in my world" or to say it in a less aloof manner ... in many of my shoots re-shooting due to data loss or down time due to instability is a huge problem. Production costs, time and subject matter (often a-list with a per hour cost/value many times higher than the rest of the production).
    0
  • Permanently deleted user
    [quote="MidWestTech" wrote:


    The changes implemented in 7.1.2 have increased the reliability of the connection and made reconnecting after a dropped connection an option where it never was before. If you are still using an older version, I suggest you update. If you still have a lot of dropped connections, you might want to troubleshoot the connection.




    I'm running 7.2.2

    Stability issues are not the connection. Connection works with other software.
    0
  • Permanently deleted user
    [quote="MidWestTech" wrote:


    Yes, it is the SDK that controls where the camera is writing to, not the tethering software. Phase has had a long track record of not reengineering the SDKs that other camera brands provide for a myriad of reasons, chief among them is that no one like getting sued. Phase isn't stupid, they manage a fairly robust intellectual property library and they know the ins and outs of what they should and should not do in this area.



    SDK stands for Software development kit. It is a software development kit. Details, instructions and code that is used to develop software. It is untimely the software that used the sdk that produces the connection.

    If as you say it is the SDK that controls where the camera is writing then why is it that several other applications I use that are developed using the Nikon SDK can write to both the card and the computer, either or as well as both at the same time.
    0
  • MidWestTech
    [quote="FredBGG" wrote:
    If as you say it is the SDK that controls where the camera is writing then why is it that several other applications I use that are developed using the Nikon SDK can write to both the card and the computer, either or as well as both at the same time.


    The camera determines where the data is being written in a more general sense. You are a Nikon shooter. It wasn't too long ago that in order to tether a Nikon camera to any software that you had to go in to the menu and select the nature of the PC connection. Thankfully that got figured out (thanks Nikon). The camera's firmware is being manipulated by commands in the SDK to tell the camera to send images over the connection to the computer instead of writing them to the card. You can agree or disagree with that if you wish, but how else does software use an SDK but to manipulate the areas of the camera's functionality that the manufacturer decides to open to third party development. Obviously they allow and disallow certain things control-wise. You can speculate if the SDKs being provided to Adobe and Phase are identical. Phase is on record as saying that this function is not an official and sanctioned part of the SDKs they receive.

    As an aside, wouldn't you think that writing to two places would create a performance hit? It does everywhere else in the computing world.

    [quote="FredBGG" wrote:
    Setting the correct color balance in camera is actually very simple to do.

    If corrections cannot be applied automatically when using a hot folder is a limitation of Capture One.


    It is simple to do in Capture One as well. It will read the white balance off of the RAW which will get you close, but not all the way to a completely color managed image. Want to experiment? Import some of your files at the color temp they were shot at. Do they display at the exact color temp they were shot at when you view them in C1Pro? Mine don't. The ICC profile seems to be doing its thing on the files and adjusting them 50-150 degrees from where they were shot depending on camera model.

    [quote="FredBGG" wrote:
    On many shoots it is more important to have redundancy and shoot as reliably as it is to shoot direct to a CF card. It is also important to have redundancy. In particular on location or at a rental studio where after the shoot laptop/computer needs to be transported.


    I agree 100% and making sure that data is secure is a big part of what I do. that is why I shoot to SSDs and back them up to mirrored RAIDs. If you do a little digging, you will find that shooting directly to a mirror is not recommended, even if it is internal to the machine. If you value the adjustments that you are shooting with and have taken time to develop the look that is being applied, a CF card is a poor substitute to a second or third redundancy of your work that already has the settings applied, even if it is not an instantaneous backup, this strategy has never come back to bite me and the only person I know who had an issue with this method suffered from the backup being ungracefully disconnected in the midst of a transfer and even so did not lose any more or less work than they would have from backing up from the CF or SD card.

    [quote="FredBGG" wrote:
    I'm not sure what you shoot, but to use your words "in my world" or to say it in a less aloof manner ... in many of my shoots re-shooting due to data loss or down time due to instability is a huge problem. Production costs, time and subject matter (often a-list with a per hour cost/value many times higher than the rest of the production).


    "In my world" means that just about everyone on here is using the software for a slightly different purpose. Without knowing yours, it is hard to determine what workflow issues and opportunities are a big deal or not. That is all that was meant. If your world includes high production costs, high cost of the subject matter's time, etc than we are operating in similar worlds and with similar pressures. Knowing what does and does not work well with your tools is an essential part of being able to successfully navigate these high stakes shoots.

    Instead of complaining about what you see as weaknesses in this tool, perhaps your time would be better spent asking people who are doing similar work and using the tool successfully what they might be doing differently than you. For example, one of the biggest issues I have seen on here with Nikon shooters has been that a lot of them shooting D800s are trying to do so on latest gen iMacs (incredibly weak bus) and/or with USB3 cables that are longer than supported spec with no powered hub/repeater. These issues are not Phase's fault any more than they are mine or yours, but they do have solutions that allow people to shoot with rock solid connections all day, every day. The spirit of this forum is to provide a place for users to help each other answer questions and solve the problems that arise, not to vent, rant, name call, etc. It would appear that you are only here to argue and talk down Phase and their products.
    0

Post is closed for comments.