Zum Hauptinhalt gehen

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

Capture Pilot updated to v1.1, Nice...

Rudy Torres
I have updated Capture Pilot version 1.1. Thank you Phase One. It's working well.
I did read on line 2 of the listed new features, Capture Pilot can now be used beyond a local network.
Ummm, How? lol

I may be over thinking this, I often do.
But, how do we port forward an App's Folder (in use) using a Dynamic IP.
Example: If I'm in Austin, TX how does my client in New York see the images I'm shooting using Capture Pilot.
Maybe a video tutorial would help.
Or, is this just a button that I have overlooked.

I am using CO v6.01. Do I need v6.1?

- rudy / El Paso, Tx
0

Kommentare

5 Kommentare

Datum Stimmen
  • Mikkel Selsøe
    [quote="Rudy1" wrote:
    I have updated Capture Pilot version 1.1. Thank you Phase One. It's working well.
    I did read on line 2 of the listed new features, Capture Pilot can now be used beyond a local network.
    Ummm, How? lol

    I may be over thinking this, I often do.
    But, how do we port forward an App's Folder (in use) using a Dynamic IP.
    Example: If I'm in Austin, TX how does my client in New York see the images I'm shooting using Capture Pilot.
    Maybe a video tutorial would help.
    Or, is this just a button that I have overlooked.

    I am using CO v6.01. Do I need v6.1?

    - rudy / El Paso, Tx


    You will need 6.1 to support rating and color tagging in Capture Pilot 1.1, but remote servers should work with 6.0.1 (however I can recommend updating to the latest version to get better performance). In order to connect to a remote server, in the server list tap the plus sign in the top right corner and enter the IP/host name and port number. The port number can be found in the advanced tab of the Capture Pilot tool (if it's set to auto, mouse over and the port number will be revealed in the tool tip). Router configurations is different from setup to setup, but ususally you will need to enable port forwarding in your router and enter your public IP in the Capture Pilot client.
    0
  • Rudy Torres
    IT WORKS!!!!!
    Fantastic!
    I had a client in Albuquerque looking at images earlier today of their product I'm shooting.
    Thanks so much for this. You have no idea how important this is going to be... Or maybe you do.

    - Rudy
    El Paso / Texas
    0
  • Wilson Lee
    Hello,
    that's is a nice function.
    However, I've got no luck here, I was enabled the port forwarding or virtual server in my router,
    forwarding public port say 443 to private port 5000 of my capture computer... but Capture Pilot still cannot find the server.
    Can anyone who familiar with network setting give some help ?
    I am using DLink DIR655. I am able to forward the IP cam port to public successfully but Capture Pilot is not working.

    Thanks.
    0
  • Adrian Lyon
    Wilson1...

    I also had problems getting Capture Pilot going remotely but managed in the end.

    First problem was even though I defined a port in C1 it changed when I activated the server so I had to reset accordingly the port forwarding in my router. I still couldn't get it going though until I used completely different internet connections or both devices. On my router (even using the guest network) Capture Pilot couldn't connect to the server but once they were on two different connections it worked straight away, which is great and I love it.

    You may know all this but other things to check possibly; your external IP address (plenty of website can identify it for you if it's not static) and your C1 machine's internal IP address on your router (which I needed for my routers port forwarding). Both of these can change from time to time I think which means it could be a bit of a pain to use on a regular basis.

    Hope that helps.

    And Phase, it would be great to see an OSX version as well at some point, especially with the OSX app store now active. Many more clients have laptops rather than iPads and the iPhone is really a bit to small for serious use. For me quite an attractive use for this technology is when a client can not attend the studio and could view the shoot online at their desk most likely using their laptop or desk top.
    0
  • Paul Steunebrink
    [quote="Adrian141" wrote:
    You may know all this but other things to check possibly; your external IP address (plenty of website can identify it for you if it's not static) and your C1 machine's internal IP address on your router (which I needed for my routers port forwarding). Both of these can change from time to time I think which means it could be a bit of a pain to use on a regular basis.

    Maybe I can help with some additional tips to Adrian's great advice.

    As stated, with a remote server setup your internet router must be found by the device with the Capture Pilot app. This can be an IP address or a host name (which must be translated into an IP address). You can check for the router's external (public) IP address by visiting particular websites (http://www.myipaddress.com/ for example). You can also look it up the router's configuration by logging into the router. This external address is not always fixed, and can change after a power reset of the router.
    A host name or DNS name that reflects the current address would be more user friendly and predictable for the user with the Capture Pilot app. A dynamic DNS (DynDNS) service is an interesting feature for this because it automatically keeps track of IP address changes. The host name however remains the same! You can often configure DynDNS in modern routers.

    Once the router is found, the incoming request must be forwarded to the proper computer on the internal network. Port forwarding is a common and free way to do that. You must configure this in the router. Key is that you assign a specific port request (TCP port 443, https) to a specific internal IP address.

    Regarding the internal IP address of the Capture Pilot server, typically your (tethering) system with Capture One 6, the problem is that this is typically not fixed. Internal addresses are assigned dynamically by a feature called DHCP (server), also in general handled by your internet router as well and can change every day if you have more computers on your internal network. Fortunately, you can bind an IP address to your computer's network interface card by means of a unique number in that card, the MAC (not Apple related) or hardware address. This is called DHCP Reservation but can have a different name in your router. You have to enter your hardware address, which look like 00:17:f2:cd:8e:ab. Note that your notebook has a unique hardware address for each interface (Ethernet and WiFi/Airport). You can find this address in Network Utility or System Profile.

    To summarize this lengthy post, first setup your DHCP reservation for your internal system with Capture One 6. Next, set port forwarding to the proper port to that internal address. Last either check your external IP address through a website or configure DynDNS in your router. Now you are ready to go with your Capture Pilot app to a remote server.

    Last but not least a security concern. Port forwarding opens your internal network for external requests, which is by default entirely closed, by a small margin. This makes your internal network less secure. Personally I find permanent port forwarding not an acceptable risk but YMMV. To mitigate this risk, use a separate firewall device and place all other computers behind this firewall. Only your Capture server is now at risk. Of course when not capturing you can connect this machine to the more secure network segment behind the firewall device.
    0

Post ist für Kommentare geschlossen.