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

1DX Tethering to CaptureOne via Ethernet (Canon Response)

Comments

3 comments

  • NNN635160030527962252
    I will!
    0
  • Daniel Goldwasser
    I too have been disappointed and frustrated by this for over a year. Though as you have likely discovered it is a low priority for almost everyone involved including the relatively few other 1DX owners/users on this forum. How can we clearly demonstrate a lost opportunity or impaired functionality and thus motivate change is the critical question in my mind.

    I'm a bit confused from your post "...does not tether to C1 via the 2x faster Ethernet Connection, I have been in touch with Canon Support team who have confirmed that even through EOS Utility the speeds achieved on transfer are in fact slower than using USB2."

    This sentence it a bit confusing. Is tethering using the ethernet connection "2x faster" or "slower than USB2". These seem to be contradictory. My guess it that the bottleneck is inside the camera on sensor readout or something, and not a cable/port limitation.

    Could it be the different modes of ethernet tethering (FTP, WFT server, EOS utility, Media Serv)?
    In my workflow EOS utility mode is the only one that is useful.

    I have done repeated testing on various Macs with OS 10.8 and found that using Canon EOS utility to tether with either the USB or Ethernet is moderately faster than using CaptureOne to tether. Faster is defined as how many frames I can shoot in a 2 minute test period and how quickly the buffer clears. Though the benefits and simplicity of using C1 to connect usually outweigh the speed hit. Also tethering with USB tends to be about 10-15% faster than using the Ethernet (as canon support has stated)

    If we can really convince canon to modify their SDK to allow tethering through the Ethernet cable, and then get PhaseOne to devote resources to implement it, what would be the real world gains? If it turns out to be the same speed or slower than the USB connection, what's the point? Granted ethernet cables are longer & less expensive and have a more secure physical connection to the camera, but beyond that I don't see either side willing to invest the effort.

    I'll try to contact Tibor at canon support as well, but I think the first step is in finding out what the bottle neck is. Sure the Ethernet is theoretically way faster than USB2, but it may be hampered by something else in the camera that no software or firmware patch can fix.

    sorry for the rambling and long post.

    Daniel
    0
  • LSdigi.com
    [quote="Daniel1111" wrote:

    This sentence it a bit confusing. Is tethering using the ethernet connection "2x faster" or "slower than USB2". These seem to be contradictory. My guess it that the bottleneck is inside the camera on sensor readout or something, and not a cable/port limitation.


    Hey Daniel

    Sorry for the confusion. Tethering via Ethernet should be 2x faster according to specs (1000Mbit/s vs 480Mbit/s), and as far as I understood the bottleneck was EOS Utility itself, as apparently tethering to FTP was achieving proper speeds. If canon could "serialise" the ethernet connection, PhaseOne wouldn't need to implement anything as it would be tricking it into thinking its using normal usb connection - according to Drew this is what Nikon have successfully done with their D800.
    0

Post is closed for comments.