InfoAudio User Manual

Operational guide for radio and broadcast teams using the InfoAudio platform. Source baseline: docs/InfoAudio_Referencia_Aplicativos.md Language: American English

1. Purpose

InfoAudio is a broadcast automation platform for radio stations and media operations. It supports live playout, studio recording, music scheduling, voice tracking, media ingest, transcription, reporting, and integration with third-party broadcast systems.

This manual is intended for:

• On-air operators
• Producers and programming staff
• Music scheduling teams
• Traffic and compliance users
• Broadcast engineering and technical operations

This document focuses on how to use the platform in day-to-day station workflows. Installation, deployment, and infrastructure setup are covered in the installation and configuration guide.

2. Platform Overview

InfoAudio combines desktop applications, Windows services, and support tools.

In a typical station workflow:

• Player Desktop drives the on-air log in real time.
• Gravador records studio or production audio.
• VoiceTracker records announcer breaks against scheduled content.
• MusicMaster Suite synchronizes music metadata and schedule changes.
• ProgAuto Suite imports external logs and playlists.
• Services.Manager controls the service layer.
• Utility applications support cueing, waveform editing, reporting, ingest, backup, and troubleshooting.

Core platform capabilities include:

• Live playout and execution log control
• Audio routing and device switching
• Instant playback of short-form audio elements
• Music and schedule synchronization
• Voice tracking production
• Media ingest and catalog support
• Export, reporting, and compliance workflows
• Broadcast-video and cloud integration

3. User Roles

3.1 On-Air Operator

Primary responsibilities:

• Monitor the live log
• Trigger or supervise event execution
• Run InstantPlay elements
• Watch timing, segues, and stopsets
• Escalate device or service failures quickly

3.2 Producer or Imaging Operator

Primary responsibilities:

• Record production audio
• Edit waveform markers and fades
• Prepare assets for air
• Validate cue timing

3.3 Music and Programming Staff

Primary responsibilities:

• Confirm schedule imports
• Review music and metadata sync status
• Validate schedule updates before airtime

3.4 Traffic, Logs, and Compliance Staff

Primary responsibilities:

• Review log exports
• Run rights-management and airplay reports
• Confirm planned versus as-run output

3.5 Engineering and Technical Operations

Primary responsibilities:

• Maintain workstation and service health
• Validate integrations
• Supervise failover, routing, and monitored folders
• Troubleshoot service and infrastructure issues

4. Main Applications

4.1 Player Desktop

Informa.Player.Desktop is the primary on-air playout application.

Primary functions:

• Execute the broadcast log in real time
• Display current, next, and upcoming events
• Route audio through configured devices
• Trigger InstantPlay elements such as sweepers, promos, IDs, and jingles
• Exchange status with Gravador
• Receive music and schedule updates from MusicMaster
• Support RDS text generation and selected integration workflows

Operational highlights:

• The workspace layout can be restored between sessions.
• Audio output may use ASIO or WASAPI, depending on hardware and license.
• The application can integrate with vMix, TriCaster, NDI, VLC, satellite workflows, BreakMonitor, Spotify, and cloud services.

4.2 Gravador

Informa.Gravador is the studio recording application used alongside the player.

Primary functions:

• Record from ASIO or WASAPI devices
• Capture live, production, or announcer audio
• Save files as MP3, FLAC, or WAV
• Exchange status with Player Desktop

4.3 VoiceTracker

Informa.VoiceTracker supports voice tracking workflows for announcers and producers.

Primary functions:

• Load scheduled blocks
• Preview and stack content
• Record voice inserts against music flow
• Review waveforms and timing
• Adjust event-related audio before final save

4.4 MusicMaster Suite

The MusicMaster integration layer keeps InfoAudio synchronized with the external music scheduling environment.

Components:

• MusicMaster Plugin
• IntegradorMusicMaster service
• MusicMaster CLI

Primary functions:

• Synchronize metadata
• Synchronize schedule changes
• Notify Player Desktop in real time
• Support field mapping and sync monitoring

4.5 ProgAuto Suite

ProgAuto automates playlist and schedule import from external files.

Supported formats:

• XML
• TXT
• CML

Primary functions:

• Monitor hot folders
• Interpret incoming files
• Create, update, or merge blocks and events
• Support test and satellite-oriented workflows

4.6 Services Manager

Informa.Services.Manager is the central control console for InfoAudio Windows services.

Primary functions:

• Discover installed services
• Start, stop, restart, install, and uninstall services
• Edit service parameters
• Manage multi-company and multi-instance configurations
• Open service logs

5. Using Player Desktop

5.1 Start a Shift

Recommended startup sequence:

1. Log in to Windows with the authorized station account.
2. Launch Player Desktop.
3. Confirm the correct station, database, and user profile are loaded.
4. Review the current hour and the next hour in the execution log.
5. Confirm the application is communicating with required services.
6. Check audio routing before going live.
7. Confirm the clock and system time are correct.

Before opening the mic or sending content to air, verify:

• The active log is the correct broadcast day and hour
• The studio output device is available
• InstantPlay elements are visible and ready
• No sync or reconnect warnings are active

5.2 Read the Execution Log

The execution grid is the operator's primary reference during live operation.

Use it to:

• Follow the active event
• Review what is next in the segment or hour
• Track stopsets, program elements, and music flow
• Identify items that may require operator attention

Operator guidance:

• Keep the current event line visible at all times.
• Review upcoming transitions before the current item ends.
• Pay special attention to short-form elements such as IDs, sweepers, and sponsor tags.
• If schedule updates arrive close to airtime, confirm the refreshed log before allowing the next sequence to roll.

5.3 Use InstantPlay

InstantPlay is intended for fast access to high-frequency elements.

Typical uses:

• Station IDs
• Sweepers
• Promos
• Liners
• Emergency inserts

Recommended operator workflow:

1. Confirm the element is assigned to the correct hot area or panel.
2. Preview the label or category before triggering.
3. Trigger the element only when the program clock and segue timing allow it.
4. Watch the execution response and confirm the expected playback behavior.

Best practices:

• Reserve critical InstantPlay banks for approved elements only.
• Do not use InstantPlay to bypass scheduled commercial content unless authorized.
• If a hot element does not respond, verify device routing and asset availability before retrying repeatedly.

5.4 Manage Audio Routing and Device Changes

Player Desktop supports dynamic device workflows through the audio engine and device utilities.

Use this feature when:

• A studio interface changes state
• A backup output path must be selected
• Engineering requests a route change
• A device disappears and must be revalidated

Operational guidance:

1. Confirm whether the station uses ASIO or WASAPI.
2. Validate the selected output path before changing devices during a live segment.
3. Coordinate any route change during a safe timing window.
4. If needed, use SoundDevices to confirm device visibility.
5. Recheck meters and confidence monitoring after any change.

5.5 Respond to Schedule and Metadata Refresh

When MusicMaster integration is enabled, Player Desktop may receive:

• Schedule change notices
• Metadata refresh notices

Operator workflow:

1. Review whether the visible log has updated.
2. Confirm the update applies to the correct daypart or hour.
3. Check that no manual operator action is about to conflict with the refreshed sequence.
4. Inform programming if a late schedule revision impacts a live segment.

5.6 Monitor RDS and Broadcast Metadata

Where enabled, Player Desktop may generate RDS text or related metadata outputs.

Operational guidance:

• Confirm metadata appears correct for the current song or event.
• Escalate repeated mismatches between on-air content and metadata.
• Treat metadata errors during sponsored or regulated content as higher priority.

6. Using Gravador

6.1 Choose the Right Recording Mode

Use ASIO when:

• The workstation is connected to a professional studio interface
• Low latency and direct hardware access are required
• The ASIO feature is licensed and validated

Use WASAPI when:

• Standard Windows audio devices are in use
• A fallback mode is needed
• Loopback capture is required

6.2 Configure a Recording Session

Before recording:

1. Launch Gravador.
2. Confirm the correct input device is selected.
3. Select the target format: MP3, FLAC, or WAV.
4. Select the required bitrate or bit depth.
5. Confirm the recording path and session purpose.
6. Check that meters are active and expected signal is present.

6.3 Record Audio

Recommended workflow:

1. Confirm studio silence or source readiness.
2. Start recording.
3. Monitor the VU meter and elapsed state during capture.
4. If the session is tied to live operation, keep Player communication active.
5. Stop recording only after confirming the full segment has completed.
6. Review the output file before releasing it for production or archive use.

6.4 Use Cases

Typical broadcast use cases:

• Voice-over recording
• Promos and imaging
• Aircheck capture
• Backup capture
• Segment production

6.5 Recording Best Practices

• Use WAV or FLAC for production masters when post-editing is expected.
• Use MP3 when compact delivery files are acceptable.
• Avoid changing input devices while a recording is active.
• If the recorder loses the device, stop and validate the hardware before restarting the session.

7. Using VoiceTracker

7.1 Prepare the Session

Before recording a tracked break:

1. Open the required scheduled block.
2. Review the event stack and the order of songs, breaks, and inserts.
3. Confirm the playback and recording devices.
4. Check that waveform and stack views are visible.

7.2 Record Against the Log

VoiceTracker is intended to preserve music flow and segue timing.

Recommended workflow:

1. Preview the surrounding events.
2. Identify the correct insertion point.
3. Record the voice track.
4. Review waveform placement and playback timing.
5. Adjust as needed to maintain a clean segue.
6. Save only after the break is editorially and technically approved.

7.3 Review the Stack and Waveform

Use the stack and waveform tools to:

• Inspect content order
• Review intro and out timing
• Check spoken break placement
• Validate that the insert does not collide with scheduled audio

7.4 Common Voice Tracking Practices

• Record to the scheduled tone and pacing of the show.
• Keep the segue clean into the next song or imaging element.
• Review every break in context, not in isolation.
• If a block fails to load, confirm the schedule exists before opening a support ticket.

8. Using EditorMixagem, InfoCue, and Audio Utilities

8.1 EditorMixagem

Use EditorMixagem for file-level and event-level audio preparation.

Typical tasks:

• Set CUE points
• Adjust fade in
• Adjust fade out
• Insert or review jingles and short elements
• Save event audio changes back to the system

Recommended workflow:

1. Open the target event or file.
2. Review the waveform from the beginning to the first audible transient.
3. Place or correct the start cue.
4. Review outro timing and fade shape.
5. Save the event only after confirming the edit in context.

8.2 InfoCue

Use InfoCue when cue resolution must be validated for a specific audio event.

Typical use cases:

• Validate event cue behavior before air
• Process a specific event code
• Confirm cue-related settings during troubleshooting

8.3 SoundDevices

Use SoundDevices to verify audio device visibility and routing state.

Recommended checks:

• Confirm the expected device is present
• Confirm the device remains visible after opening Player Desktop
• Confirm the route change requested by engineering is reflected in the device list

9. Using MusicMaster and ProgAuto Workflows

9.1 MusicMaster User Workflow

Use the MusicMaster plugin and service workflow when programming changes must flow into InfoAudio.

Typical operator or programming tasks:

• Review synchronization status
• Confirm metadata updates are reflected in the platform
• Confirm schedule updates have reached the live log
• Review field mapping only when authorized

When a sync occurs:

1. Watch for the schedule or metadata update notice.
2. Confirm the affected content appears correctly.
3. Report repeated sync failures or stale data to engineering.

9.2 ProgAuto User Workflow

Use ProgAuto when schedules are imported from external systems or network feeds.

Typical workflow:

1. Confirm the inbound file was delivered to the correct monitored folder.
2. Confirm the file format matches the expected import type.
3. Verify that the imported blocks and events appear in the system.
4. Review merged or updated content before airtime when policy requires it.

Operational note:

• ProgAuto can create, update, or merge content, so users should confirm whether the station wants additive updates or a replacement-style import behavior for the affected workflow.

9.3 InfoXML Workflow

When XML-based imports are enabled:

1. Confirm the XML file reaches the expected inbound path.
2. Confirm processing completes after the service polling cycle.
3. Review the resulting schedule data in the appropriate operational screen.

10. Using Services and Background Workflows

10.1 Services Manager

Use Services.Manager to supervise the background services required by the station.

Common user actions:

• Review service health
• Start a stopped service
• Restart a stalled service
• Open logs for a service instance

Recommended workflow:

1. Open the dashboard.
2. Review service state for the local station or company.
3. If a service is down, confirm whether it is safe to restart it.
4. Restart the service and review its logs.
5. Escalate recurring failures instead of repeatedly cycling the service.

10.2 MidiaIngest

Use the media ingest workflow to process new assets automatically.

Typical user checks:

• Confirm the source file reached the ingest folder
• Confirm the service processed the file
• Confirm metadata such as duration and codec was extracted
• Confirm the asset is available for catalog or scheduling workflows

10.3 ExportaLog

Use log export workflows when scheduled file delivery is required for traffic, affiliates, clients, or compliance.

Typical user checks:

• Confirm the export job exists
• Confirm the output path is valid
• Confirm the job executed on time
• Confirm the output file matches the expected layout

10.4 Transcription

Use the transcription workflow when audio-to-text output is required.

Typical user checks:

• Confirm the source audio is available
• Confirm the transcription status progresses correctly
• Review text output quality where operationally required
• Escalate repeated timeout or error status

10.5 Backup

Use Backup.Config and backup processes to support environment continuity.

Typical user checks:

• Confirm backup schedules exist
• Confirm the last run completed
• Escalate failed or skipped backup cycles immediately

11. Reporting and Compliance

11.1 ReportEdit

Use ReportEdit to run or design broadcast operation reports.

Common report categories include:

• Programming and operation reports
• Music aired reports
• Rights-related reports
• Planned versus actual reports
• Uncataloged audio reports

Typical workflow:

1. Select the report type.
2. Apply the correct filters, company, or date range.
3. Preview the output.
4. Export or print as required by the business workflow.

11.2 Ecad

Use Ecad for copyright and rights-management workflows.

Typical user tasks:

• Manage company-related ECAD files
• Filter records by company
• Review output before submission or archive

11.3 Compliance Best Practices

• Confirm the reporting period before generating official output.
• Do not overwrite prior period exports without approval.
• Review planned versus actual discrepancies before delivery to stakeholders.

12. Integrations in Daily Operation

12.1 vMix, TriCaster, NDI, and VLC

These integrations are typically used in visual radio and video-assisted workflows.

User-facing expectations:

• The integration should reflect the active on-air or studio state
• Overlay or source control should respond on time
• Loss of connection should be escalated to engineering

12.2 Spotify Search

Where enabled, Spotify integration may be used to search external catalog information.

User guidance:

• Treat Spotify results as a search aid, not a substitute for approved catalog policy.
• Confirm any mapped item matches the station's internal metadata standards.

12.3 Cloud and Remote Workflows

Where cloud workflows are enabled:

• Schedule and voice-track transfers should be monitored
• Repeated delivery failures should be escalated
• Remote workflow changes should be coordinated with technical operations

13. Daily Checklists

13.1 Start-of-Shift Checklist

1. Log in with the correct station account.
2. Launch Player Desktop.
3. Confirm the current log and upcoming hour.
4. Validate output routing and confidence audio.
5. Confirm service health.
6. Test critical InstantPlay elements.
7. Confirm clocks and metadata behavior.

13.2 Production Session Checklist

1. Confirm the correct source or event.
2. Validate record devices.
3. Confirm format and target quality.
4. Record or edit.
5. Review playback.
6. Save and route the asset according to station policy.

13.3 End-of-Shift Checklist

1. Confirm the next operator or automation path is ready.
2. Review unresolved warnings or device issues.
3. Confirm critical exports or scheduled workflows completed.
4. Escalate any issue that could affect the next airshift.

14. Troubleshooting for Users

14.1 Common Checks

If an application is not behaving as expected:

1. Confirm only one instance is running if the application is single-instance.
2. Check the service state in Services.Manager.
3. Review the relevant log or status message.
4. Confirm the workstation still has network and database access.
5. Confirm the expected audio device is still available.
6. Confirm inbound folders, output folders, and credentials are still valid.

14.2 Typical Symptoms

Player Desktop:

• No audio output: verify device routing, ASIO or WASAPI selection, and monitor path.
• Log not refreshing: verify MusicMaster or ProgAuto workflow status.
• InstantPlay not firing: verify asset availability and application responsiveness.

Gravador:

• Record cannot start: verify the selected input device is available.
• Poor capture quality: review input mode, level, and format choice.

VoiceTracker:

• Block not loading: verify the block exists in the schedule.
• Device missing: confirm the playback and recording devices are visible to Windows.

Services:

• Service stopped: restart only if safe, then review logs.
• Import stalled: confirm the file arrived and matches the expected format.

14.3 When to Escalate

Escalate to engineering, IT, or technical operations when:

• A service fails repeatedly after restart
• Database access is lost
• License validation fails
• Audio hardware disappears or becomes unstable
• Scheduled content is clearly out of sync with the source system
• Reporting, export, or backup workflows stop completing

15. Operational Best Practices

• Use ASIO with approved studio hardware when available.
• Keep workstation and service clocks synchronized.
• Validate last-minute schedule changes before high-value dayparts.
• Restrict manual live-log edits to authorized staff.
• Review exported logs and compliance reports on schedule.
• Treat failover, device swaps, and route changes as controlled technical actions.
• Review voice tracks and edited assets in context before approval for air.

16. Quick Reference

17. Scope Note

This manual covers platform-level operation based on the current technical reference. Station-specific log policies, rights workflows, naming standards, folder mappings, security permissions, and escalation rules should be documented in the broadcaster's local standard operating procedures.