InfoAudio Installation and Configuration Guide

Deployment, setup, and validation guide for InfoAudio environments. Source baseline: docs/InfoAudio_Referencia_Aplicativos.md Language: American English

1. Purpose

This guide describes how to install, configure, and validate an InfoAudio environment for radio and broadcast operations. It is written for broadcast engineering, IT infrastructure, systems administration, and technical support teams.

The guide covers:

• Platform prerequisites
• Database and application setup
• Licensing
• Windows services
• Audio and studio device configuration
• Integration setup
• Operational validation after deployment

2. Platform Summary

InfoAudio is a Windows-based broadcast automation platform built on:

• .NET Framework 4.5.2 for most applications
• .NET Framework 4.7.2 for selected modules such as InfoCue and Integrador
• SQL Server for the operational, log, and reporting databases
• WPF and WinForms desktop applications
• Topshelf-hosted Windows services
• BASS.NET for audio playback, recording, and device control

Primary database contexts:

• Informa: core operational database
• InformaLog: audit and execution history

3. System Requirements

3.1 Operating System

• Windows 10 or Windows 11
• Windows Server 2016 or later

3.2 Application Frameworks

• .NET Framework 4.5.2
• .NET Framework 4.7.2 for modules that require it
• Visual C++ Redistributable required by BASS.NET components

3.3 Database

• SQL Server 2014 or later

3.4 Optional or Scenario-Based Components

• IIS for web-related setup steps handled by the installer
• ASIO drivers for professional low-latency studio audio
• Whisper CLI and model files for transcription workflows

4. Pre-Installation Checklist

Before installation, confirm the following:

1. The target server or workstation matches the required Windows version.
2. SQL Server is installed, reachable, and backed up.
3. Required service accounts and Windows permissions are available.
4. Audio interface drivers are installed for on-air and production workstations.
5. Firewall rules are planned for any HTTP listeners, TCP sockets, or cloud traffic.
6. Station naming, company ID, and database credentials are approved.
7. Licensing and activation workflow are available.
8. Required third-party integrations have their IP addresses, ports, and credentials documented.

Recommended planning items:

• Define which machine hosts Player Desktop, core services, and utility tools.
• Define watched folders for ingest, XML import, log export, and transcription.
• Define failover expectations for ShadowConfig or multi-station deployments.

5. Installation Order

Use the following sequence for a clean deployment:

1. Prepare Windows, frameworks, and drivers.
2. Prepare SQL Server connectivity.
3. Install the InfoAudio application package.
4. Create or initialize the database.
5. Apply schema updates.
6. Activate licensing.
7. Configure core services.
8. Configure audio devices and workstation-specific options.
9. Configure integrations.
10. Validate end-to-end operation.

6. Database Setup

6.1 Initial Database Creation

Use Informa.CreateTool for new environments.

This tool initializes:

• Core schema
• Default user records
• Menu structure
• Permissions and groups
• System events
• Company data
• Holiday data
• Accessory themes
• Default player layout

Recommended practice:

• Run initial creation only once per new environment.
• Capture the final database names and credentials in deployment records.

6.2 Schema Updates

Use Informa.DataBase.SQL.exe <config-file> to apply schema migrations.

The migration engine:

• Compares current and target database versions
• Applies sequential SQL scripts
• Uses atomic execution through transactions
• Manages version state for the main and log databases

Recommended practice:

• Back up databases before every schema update.
• Validate the target configuration file before running migrations.
• Review migration logs as part of deployment sign-off.

7. Application Installation

7.1 Interactive Installer

Use Informa.Instalador for guided environment setup.

Installer capabilities include:

• SQL Server configuration
• IIS application creation when needed
• Application pool creation
• Connection pooling setup
• INI generation
• Configuration encryption through ServicoCriptografia

Key internal processes include:

• ColetarConfiguracoesBanco
• ConectarBanco
• CriarAplicacao
• CriarPool
• ManipularArquivoConfig

7.2 Update Mechanism

Use Informa.Atualizador for update workflows.

Supported operations:

• -z: create ZIP from a folder
• -dz: extract ZIP
• -iv: write version data to BackOffice
• -a: execute update with process wait and relaunch

Update log:

• LogAtualizador.txt

Recommended practice:

• Run updates during approved maintenance windows.
• Confirm no live playout or active ingest session depends on the target binaries.
• Validate the relaunch path after the update finishes.

8. Licensing

8.1 Activation

Use Informa.Licenca.Ativacao to activate the installation against the central licensing service.

8.2 Validation

Use Informa.Validador.Ativacao to confirm installed license status and validity.

Licensing characteristics:

• Hardware fingerprint binding
• Validation against a central server
• Limited offline contingency mode
• System clock tamper detection
• Company-based licensing using EmpresaId

Recommended practice:

• Perform activation after the final hardware image is stable.
• Avoid hardware changes after activation unless revalidation is planned.

9. Core Workstation Configuration

9.1 Player Desktop

Configure the on-air workstation for Informa.Player.Desktop.

Key configuration areas:

• Station database connectivity
• Language file in %ProgramData%\Informa\Idioma
• Audio output routing
• ASIO enablement when licensed
• Integration endpoints for MusicMaster, vMix, TriCaster, NDI, VLC, satellite, and cloud

Operational dependencies:

• Named pipe ConexaoInfoAudioGravador
• Named pipe InfoAudioMusicMasterSync

9.2 Gravador

Configure Informa.Gravador on studio or production workstations.

Key configuration areas:

• Record input device
• ASIO or WASAPI mode
• Output format: MP3, FLAC, or WAV
• Visual customization through GravadorCores.txt

Supporting files:

• Delta.mp3
• Silencio.wav

Required native audio DLLs:

• bass.dll
• bassenc.dll
• bassenc_flac.dll
• bassenc_mp3.dll
• bassmix.dll
• basswasapi.dll
• bassasio.dll

9.3 VoiceTracker

Configure Informa.VoiceTracker with:

• Playback devices
• Recording devices
• Access to the target schedule data
• User and station configuration

9.4 SoundDevices

Use SoundDevices to validate the workstation audio device inventory and visibility from the player stack.

10. Windows Services Configuration

10.1 Service Framework

Modern services run on the shared service framework in Informa.Services.Shared and are commonly hosted through Topshelf.

Default service directories:

• Configuration: %ProgramData%\Informa\Services\Config\
• Logs: %ProgramData%\Informa\Services\Logs\
• Language: %ProgramData%\Informa\Idioma

Batch operations supported by the framework:

• start-all
• stop-all
• install-all
• uninstall-all

10.2 Services Manager

Use Informa.Services.Manager as the preferred control plane for:

• Service discovery
• Start, stop, and restart
• Install and uninstall
• Service parameter editing
• Company and instance configuration
• Log access

This is the recommended operational console for multi-service deployments.

10.3 Primary Services

IntegradorMusicMaster

• Configure two HTTP listener ports:
• PortaPublishChangedHours
• PortaPublishMetaData
• Validate named pipe communication to InfoAudioMusicMasterSync.
• Confirm NexusServer endpoint settings.

ProgAuto

• Configure watched folders and import formats.
• Validate XML, TXT, or CML file handling.
• Confirm merge and update behavior with the station schedule policy.

Integrador

• Configure cloud authentication through Shared Access Key.
• Confirm queue processing and webhook communication.

InfoXML

• Configure XML input folders.
• Validate startup delay and timer-based processing.

ExportaLog

• Configure export jobs, output templates, intervals, machine naming, and path variables.

MidiaIngest

• Configure ingest folders and metadata processing workflow.
• Validate catalog insertion after ingest.

Transcription

• Deploy whisper-cli.exe.
• Deploy the model file such as ggml-tiny.bin.
• Validate command execution and timeout behavior.

ShadowConfig

• Configure network paths and sync intervals for failover scenarios.

RemoteVoiceTracker

• Configure according to the remote voice-tracking topology used by the broadcaster.

11. Integration Configuration

11.1 MusicMaster

Configure:

• Sync intervals
• Field mapping
• NexusServer endpoint
• Service listener ports

Validation points:

• Metadata changes reach InfoAudio
• Schedule changes trigger player refresh
• Service logs show successful bidirectional exchange

11.2 vMix

Configure:

• Target IP address
• HTTP port 8088
• Overlay and input naming conventions

Validation points:

• API calls succeed
• Overlays update correctly
• Connected state is reported

11.3 TriCaster

Configure:

• Target IP address
• HTTP port 5952

Validation points:

• /version responds
• JSON API control succeeds

11.4 NDI

Configure:

• TCP socket port
• NDI source naming

Validation points:

• The source InfoAudio NDI is published correctly
• The target workflow receives the stream

11.5 VLC

Configure either TCP or HTTP control, including the expected HTTP port 9000 when applicable.

Validation points:

• VLC launches with the required arguments
• Command channel is reachable
• Initial video or NDI warm-up works as designed

11.6 Spotify

Configure:

• Client ID
• Client Secret
• OAuth listener on local port 60403

Validation points:

• Track search succeeds
• Token refresh completes

11.7 InformaCloud

Configure:

• API key
• Company activation
• Schedule upload
• Voice-track upload

Validation points:

• Authentication succeeds
• REST calls reach https://voicetracker.informa.solutions/

11.8 Satellite

Configure:

• TCP and UDP communication
• Default port 15000, unless changed
• Station role as hub, source, or receiver

Validation points:

• Command transport succeeds
• Multi-client behavior matches the network design

12. Validation and Go-Live Checklist

Perform these checks before release to operations:

1. Launch Player Desktop and confirm the live log loads correctly.
2. Validate audio playback on the air chain and monitor path.
3. Launch Gravador and confirm successful test capture.
4. Validate VoiceTracker record and playback.
5. Confirm required services are installed and running.
6. Confirm service logs are being written.
7. Validate database read and write activity.
8. Test at least one schedule sync or import path.
9. Validate at least one log export or report workflow.
10. Confirm license activation and validation status.
11. Verify backup scheduling if enabled.
12. Record the final installed versions and service topology.

13. Troubleshooting

13.1 Installation Failures

Check:

• SQL connectivity
• Windows permissions
• IIS prerequisites when applicable
• Missing runtime components
• Encrypted or malformed configuration files

13.2 Service Start Failures

Check:

• Service account permissions
• Missing configuration in %ProgramData%\Informa\Services\Config\
• Port conflicts on HTTP listeners
• Missing watched folders or network shares
• Missing third-party binaries such as Whisper CLI

13.3 Audio Issues

Check:

• Driver installation
• ASIO availability and license status
• Device visibility in Windows
• Presence of required BASS native DLLs

13.4 Integration Failures

Check:

• IP address and port accuracy
• Firewall rules
• API credentials
• Named pipe availability between local applications
• Remote endpoint availability

13.5 Database and Versioning Issues

Check:

• Connection strings
• Migration status
• Database version alignment
• Version registration in BackOffice

14. Recommended Deployment Practices

• Separate on-air workstations from heavy background-processing roles when possible.
• Keep a documented inventory of service names, ports, and watched folders.
• Standardize %ProgramData% paths across stations.
• Back up all three databases before upgrades.
• Freeze updates during critical dayparts and live specials.
• Validate failover and sync workflows before using them in production.
• Keep an installation log for each station or company instance.

15. Scope Note

This guide is based on the current technical reference of the InfoAudio codebase. Exact installer screens, database names, watched folders, service credentials, and integration endpoints may vary by broadcaster, cluster, or station engineering standard, and should be documented in the local deployment runbook.