← Camera index

● Manufacturer-documented path

JVC
GY-HC500SPC

The sports-production GY-HC500SPC uses the HC500-family upload pipeline: automatic or manual delivery to four configurable FTP/SFTP/FTPS/FTPES profiles, resumable FTP-family transfers, and HD+Web Slot-B proxy chunking during recording. Built-in Ethernet avoids an accessory for wired operation; supported HOST USB adapters provide Wi-Fi or cellular paths.

2019FTP · SFTP · FTPS implicit · FTPES explicit

Direct camera client

TRANSPORT

built-in wired Ethernet LAN + supported Wi-Fi adapter through HOST USB + supported cellular adapter through HOST USB

The documented network paths available to the camera or its required transmitter.

PAYLOAD

recorded video clips on SD media

File behavior is quoted conservatively until a Camera to Anywhere fixture reproduces it.

TRIGGER

automatic upload after recording / automatic chunked upload during supported recording modes / manual clip upload / browser-triggered clip upload

Transfer can begin from the documented camera-side behavior shown here.

STATUS

Documented.
Not lab-verified.

The model is covered by the shared HC500/HC550/HC500SPC manual. High-Speed recording disables clip FTP; chunked upload is format-dependent; FTP resume is unavailable with SFTP. Physical Camera to Anywhere interoperability is not yet lab-verified.

MANUAL EVIDENCE

3 cited locations

Menu labels, behaviors, and warnings on this page are paraphrased from official manufacturer material.

Inspect every citation ↓
BEFORE YOU TOUCH THE MENU

Prepare the camera.
Prepare the route.

Gather these items first, then enter the Camera to Anywhere job credential exactly as issued. The camera sends to the public ingest edge; your private destinations stay downstream.

PREREQUISITES
  1. 01

    Current GY-HC500SPC-compatible firmware and the current family manual/supplement.

  2. 02

    Built-in Ethernet or a supported HOST USB Wi-Fi/cellular adapter.

  3. 03

    A test clip; HD+Web proxy media setup for live chunk testing.

  4. 04

    Camera to Anywhere host, protocol, port, credentials, and path.

  5. 05

    Approved secure-protocol fingerprint.

CONNECTION FIELDS

Alias

Event/destination label such as C2A-Court-1.

Makes the selected route obvious to the operator.

Protocol

FTP, SFTP, FTPS implicit, or FTPES explicit.

Matches the Camera to Anywhere listener.

Server

Hostname or IP only.

Identifies ingress.

Port

Exact issued port.

Connects to the correct service.

Dir. Path

Assigned team/event input directory.

Keeps concurrent feeds isolated.

Username

Per-camera/source username.

Authenticates and attributes the feed.

Password

Issued password.

Completes authentication.

PASV Mode

On for FTP/FTPS/FTPES behind NAT; unavailable for SFTP.

Uses passive FTP data connections.

Slot / Server

The auto-upload recording slot and Clip-FTP alias.

Defines the automatic source/destination pair.

Division

Approved HD+Web Slot-B interval based on latency and overhead needs.

Controls how quickly proxy segments become available downstream.

WHAT ACTUALLY MOVES

Transfer behavior,
without the guesswork.

TRANSFER MODES
  • Automatic post-record upload
  • Automatic during-recording proxy chunks
  • Manual this/selected/all clips
  • Browser selection
  • Background transfer
  • Resume on supported non-SFTP paths
MEDIA BEHAVIOR
  • Auto FTP watches the configured recording slot.
  • Chunk upload sends Slot-B HD+Web proxy segments while recording.
  • Manual upload handles playable completed clips.
  • The status screen reports progress and failures.
  • A smaller same-name partial can offer Resume.
LIMITS + WARNINGS
  • Recording to the selected auto-upload slot interrupts its transfer.
  • FTP does not operate during live streaming or Return over IP.
  • High-Speed mode disables FTP.
  • During-recording chunks require HD+Web proxy recording in Slot B.
  • Resume is disabled for SFTP and HTTP FTP proxy.
  • Sports overlays and scoring features do not change the FTP destination semantics; validate the actual recorded/proxy payload required by the client.
FIELD VERIFICATION

Prove the path before the green flag.

Run this checklist on the exact body, firmware, network, and media format you will use on assignment.

  1. 01The camera receives an IP on the production VLAN/hotspot.
  2. 02Its event-specific alias and directory are correct.
  3. 03Secure fingerprint is verified.
  4. 04A full test clip arrives byte-identical.
  5. 05A during-recording proxy chunk test meets the required latency if enabled.
  6. 06Slot strategy and streaming conflicts are documented for the operator.
TROUBLESHOOTING

If it will not send,
start here.

01Near-live chunks are absent

Confirm HD+Web, proxy Slot B, Division, Auto mode, selected Server, and Auto Upload On.

02Auto upload stops during play

Check whether recording reused the watched slot or live streaming/Return over IP was enabled.

03Cannot reach endpoint

Verify venue VLAN/egress, IP/DNS/gateway, host, port, and protocol.

04Authentication/path rejected

Correct the per-camera Username, Password, Dir. Path, and server permissions.

05Resume unavailable

Use a resume-capable FTP/FTPS/FTPES path without HTTP proxy and the correct partial file.

PRIMARY EVIDENCE

Official source trail.

The local archive is retained for research continuity if an official link changes. It is not redistributed through this site.

archived-local-ignored · retrieved 2026-08-26 · 268 pages
  1. 01

    JVC GY-HC500/GY-HC550 family Instructions

    Printed pp. 148-150, Upload Settings and Clip Server; pp. 189-193, upload workflows and Resume

    Open manufacturer source ↗
  2. 02

    JVC online Automatic Chunked Upload

    Automatic Chunked Upload to FTP Server

    Open manufacturer source ↗
  3. 03

    JVC online FTP Resume

    FTP Resume Feature

    Open manufacturer source ↗
BEFORE FIELD USE

Documentation gets us to the menu. Hardware earns the badge.

This guide compiles all discovered FTP-related setup evidence for this model, but it is not a promise that every firmware version and venue network will behave identically. Verification records the exact body, firmware, access point, protocol, payload, and result.

Have this camera?

Join the founding beta and help turn the documented route into a tested setup guide with original menu photography.

Test this path ↗