Answers for
station teams.

BroadcastPilot imports television schedules, manages program metadata, generates production ATSC 1.0 PSIP tables, and creates ATSC 3.0 laboratory packages for engineering review.

Not yet. v2.0.0 creates an engineering candidate containing A/331 service-list signaling, a readable service-guide review file, a manifest, and a validation report. It does not generate a complete ROUTE/MMT emission. Use the export with an ATSC 3.0 gateway, scheduler, exciter, or analyzer vendor and send us their validation results.

No. BroadcastPilot runs on a supported 64-bit Windows or Ubuntu computer. Your station still needs a compatible multiplexer, encoder, or transport system that accepts the selected IP output.

The guided workflow walks you through the station identity, schedule, receiving equipment, validation, and Go Live controls. After the engineering values and destination are confirmed, daily start-and-stop operation takes only a few clicks.

BroadcastPilot supports 64-bit Windows and 64-bit Ubuntu Linux. Download the `.exe` for Windows or the `.deb` for Ubuntu.

No. BroadcastPilot is software and uses your station’s existing IP-capable multiplexer, transport equipment, and transmitter chain.

Excel weekly grids, CSV event lists, JSON event lists, and XMLTV are supported. BroadcastPilot also includes a downloadable Excel schedule template.

No third-party listings subscription is included. You can import supported schedule files supplied by your station or provider. Direct provider connectors require a separately configured service.

Every license includes one primary FCC station call sign, one activated computer, all virtual subchannels under that station, software updates, portal access, and standard support.

Each additional FCC-licensed station call sign is $100 per year for the same complete term as the primary license. A one-year add-on is $100, three years is $300, and five years is $500.

No. Virtual subchannels operating under the licensed parent station are included. A separately licensed FCC facility or call sign counts as an additional station.

The product key activates the application. The portal login lets you retrieve that key, view licensed stations and expiration dates, see the activated computer, download releases, and change your password.

BroadcastPilot may issue a time-limited demo account and product key for evaluation. Demo access expires automatically on the date displayed in the customer portal.

Internet access is required for activation and periodic license verification. A temporary connection problem uses the license’s connection-grace period so a brief outage does not immediately interrupt an already validated installation.

BroadcastPilot generates STT, MGT, TVCT, EIT, and ETT. The selected profile determines which tables it sends to the downstream system.

Yes. Every station output has its own station profile, imported guide-schedule selection, call sign, virtual channel, program and source identifiers, TSID, PSIP ownership profile, PIDs, and network destination. Add only the number of station outputs you need.

Import the schedules first, then open Station Outputs. Use Guide schedule to send on each route and confirm that a nonzero event count appears beside the selection.

BroadcastPilot and the multiplexer must not generate the same PSIP table simultaneously. Decide which device owns each table before starting production output.

The application displays a green ACTIVE status and increasing packet and byte counters. That confirms local transmission; verify receipt separately at the multiplexer and off air.

BroadcastPilot checks for updates automatically but asks the operator to approve or postpone installation. It does not intentionally stop active output until the operator chooses to update.

Confirm the complete key was copied without extra spaces, the computer has internet access, the subscription is active, and the application call sign exactly matches a station included on the license.

The account may not yet be connected to a license, or you may have signed in using a different email address. Contact the BroadcastPilot administrator who issued the account.

Check the route’s Guide schedule to send selection and event count, validate the imported schedule, confirm titles and times, and verify that the multiplexer passes BroadcastPilot’s assigned PSIP PIDs without regenerating the same tables.

Common causes include packet loss, insufficient transport bandwidth, duplicated PSIP sources, remultiplexer configuration, or downstream RF problems. Compare a local analyzer test with the multiplexer input and off-air result to locate the affected stage.

Export a BroadcastPilot configuration backup and have the previous activation released. Install on the replacement computer, activate it, restore the backup, and validate output before returning it to service.