← Camera index

Manufacturer-documented path

Panasonic
AG-CX370

AG-CX370 can initiate FTP transfer of P2 MXF clips, MOV clips, P2 proxy clips over wireless LAN; wired LAN; USB tethering/mobile route as supported. The documented route accepts a user-configured server; it is suitable for a destination-neutral ingest gateway after protocol, firmware, and payload testing.

2025FTP

Accessory-assisted camera client

TRANSPORT

wireless LAN + wired LAN + USB tethering/mobile route as supported

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

PAYLOAD

P2 MXF clips · MOV clips · P2 proxy clips

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

TRIGGER

manual and automatic transfer; proxy-only can be selected for P2 recordings

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

STATUS

Documented.
Not lab-verified.

FTP was added in firmware 1.24 AVCHD is excluded Physical Camera to Anywhere interoperability is not yet lab-verified.

MANUAL EVIDENCE

2 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

    Establish a supported route: wireless LAN; wired LAN; USB tethering/mobile route as supported.

  2. 02

    Have the required hardware or provisioning ready: network connection; no vendor storage subscription is stated for the FTP destination.

  3. 03

    Prepare a reachable FTP server, login, writable directory, and enough server capacity for P2 MXF clips, MOV clips, P2 proxy clips.

  4. 04

    Firmware qualification: FTP was added in firmware 1.24.

  5. 05

    Firmware qualification: AVCHD is excluded.

  6. 06

    Firmware qualification: file transfer is unavailable during 4K streaming or NDI HX2 output.

CONNECTION FIELDS

Destination host/folder

The designated reachable network server and folder issued for the job.

Firmware 1.24 sends files to a configured network folder.

FTP credential

A least-privilege camera/event login.

Authenticates the transfer and supports isolation.

Transfer mode

Manual or automatic; for P2 choose full material or proxy-only as required.

Determines trigger and bandwidth.

Network route

Wired LAN, wireless LAN, or supported mobile route; do not enable incompatible simultaneous IP output modes.

The file-transfer service requires a working IP path.

WHAT ACTUALLY MOVES

Transfer behavior,
without the guesswork.

TRANSFER MODES
  • Documented operation: manual and automatic transfer; proxy-only can be selected for P2 recordings.
  • Begin with a manually selected short clip; enable automatic/record-during-upload only after end-to-end verification.
MEDIA BEHAVIOR
  • Documented payload classes: P2 MXF clips, MOV clips, P2 proxy clips.
  • Main material and proxy are separate transfer targets where documented; confirm the active recording format creates the chosen payload.
  • Do not remove or format the recording card while an upload is pending or active.
LIMITS + WARNINGS
  • Required equipment/provisioning: network connection; no vendor storage subscription is stated for the FTP destination.
  • FTP was added in firmware 1.24
  • AVCHD is excluded
  • file transfer is unavailable during 4K streaming or NDI HX2 output
  • Test large files and the selected recording format before production; older P2 manuals document format- or size-specific transfer restrictions.
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. 01Confirm the camera has an IP address and can resolve/reach the server.
  2. 02Transfer one short eligible clip and confirm it appears in the assigned folder.
  3. 03Open the received file and compare size/duration with the source.
  4. 04Confirm whether the received object is main material or proxy.
  5. 05If automatic upload is enabled, record another short clip and verify the queue and completion state without removing the card.
TROUBLESHOOTING

If it will not send,
start here.

01FTP CLIENT SERVICE or UPLOAD is unavailable.

Verify firmware, network device selection, adapter recognition, recording/playback state, and any profile or license prerequisite.

02The server cannot be reached.

Confirm DHCP/static address, gateway, DNS, server URL, port, route, and venue firewall/NAT behavior.

03Authentication succeeds but copying fails.

Check destination syntax, write permission, free space, card state, file-size limits, and whether the format is eligible.

04Automatic upload pauses or never queues.

Check upload enablement, profile state, recording format, card access load, shot-mark/proxy filters, and incompatible streaming/NDI modes.

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-official-pdf · retrieved 2026-08-26T04:40:28Z · 234 pages
  1. 01

    Official model or firmware evidence

    Firmware Ver. 1.24: FTP file transfer; manual/automatic transfer

    Open manufacturer source ↗
  2. 02

    Official manufacturer PDF

    Operating Instructions, base network setup chapters; this May 2025 manual predates the separately documented firmware 1.24 FTP addition

    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