User Manual Archives - MediaCP https://www.mediacp.net/doc_topics/user-manual/ Media Control Panel Thu, 13 Aug 2026 03:58:32 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.7 https://www.mediacp.net/wp-content/uploads/2025/07/IconSquare-Transparent-150x150.png User Manual Archives - MediaCP https://www.mediacp.net/doc_topics/user-manual/ 32 32 AI Integration https://www.mediacp.net/doc/admin-server-manual/ai-integration/ Fri, 17 Jul 2026 04:05:01 +0000 https://www.mediacp.net/?post_type=doc&p=35073 We built AI Integration to make complex broadcasting and panel workflows faster and easier to discover. Instead of moving through several screens or learning API calls, operators can investigate audience behaviour, organize media, update playlists, monitor stations, and perform administrative work through a conversation. The quality of the result still depends on the AI model, your prompt, and the permissions you grant it. MediaCP […]

The post AI Integration appeared first on MediaCP.

]]>

We built AI Integration to make complex broadcasting and panel workflows faster and easier to discover. Instead of moving through several screens or learning API calls, operators can investigate audience behaviour, organize media, update playlists, monitor stations, and perform administrative work through a conversation. The quality of the result still depends on the AI model, your prompt, and the permissions you grant it.

MediaCP AI Integration connects your panel to AI assistants through a Model Context Protocol (MCP) server that ships with MediaCP for Unlimited subscriptions. It is compatible with Claude, Codex, the ChatGPT desktop app, LM Studio, Windsurf, and other clients that support remote MCP servers over Streamable HTTP.

System Requirements

  • An active MediaCP Unlimited subscription or Perpetual license. 
  • MediaCP 2.16 or newer
  • API Access and MCP Server enabled under System Config > Misc.
  • The MediaCP Port 80/443 Proxy service installed and enabled.
  • A panel URL that uses HTTPS and does not contain an explicit port, for example https://panel.example.com/ rather than https://panel.example.com:2020/.
  • A publicly reachable panel URL for cloud-hosted AI clients such as Claude.
  • An MCP-compatible AI client and a model with reliable tool-calling support.

Examples

The integration exposes tools for reporting, services, media, playlists, schedules, listeners and viewers, stream targets, users, announcements, DJs, jingles, events, and system statistics.

  • When do listeners spend the most time on My Hits Radio? Compare the last four weeks by day and hour.
  • Find the most popular tracks on My Hits Radio this month and propose a 25-track playlist. Show me the proposed tracks before creating it.
  • Show me what is playing now, the current listener count, and the status of every stream target for service 105.
  • Read the last 20 tracks played by service 105 and look for repetition or gaps that could explain the station complaint.
  • Draft a maintenance announcement for tomorrow at 10:00 AM. Show me the wording and audience settings before publishing it.

Connecting to your AI client

  1. Sign in to MediaCP.
  2. If you are an administrator, open System Config > Misc and confirm that API Access and MCP Server are enabled.
  3. Open Integrations from the side menu.
  4. Enable API access for your account if prompted.
  5. Copy the MCP Server URL and your Integration Key. The URL normally has this format:
    https://panel.example.com/mcp

Connect Claude

Claude custom connectors support remote MCP servers. See Claude’s custom connector guide for current plan and workspace controls.

  1. In an individual Claude account, open Customize > Connectors. For a Team or Enterprise workspace, an Owner must first open Organization settings > Connectors.

  2. Select Add custom connector. In an organization workspace, select Custom, then Web.

  3. Enter a name such as MediaCP and paste the MCP Server URL from the MediaCP Integrations page.

  4. Open Advanced settings and enter:

    SettingValue
    OAuth Client IDmediacp
    OAuth Client SecretYour MediaCP Integration Key

  5. Save the connector, select Connect, and complete the authorization flow.

  6. In a conversation, open the + menu, choose Connectors, and enable MediaCP.

If Claude asks for explicit OAuth endpoints, use:

Authorization URL: https://panel.example.com/mcp/authorize
Token URL:         https://panel.example.com/mcp/token

Claude connects from its cloud infrastructure, including when you use Claude Desktop. Your MediaCP URL must therefore be publicly reachable over HTTPS.

Connect Codex or ChatGPT desktop

Codex and the ChatGPT desktop app share MCP configuration and support Streamable HTTP with bearer-token authentication. See the official MCP configuration guide.

Option 1: Codex CLI

Set the Integration Key in an environment variable, then add MediaCP:

export MEDIACP_INTEGRATION_KEY="YOUR_INTEGRATION_KEY"
codex mcp add mediacp \
  --url "https://panel.example.com/mcp" \
  --bearer-token-env-var MEDIACP_INTEGRATION_KEY
codex mcp get mediacp

Make MEDIACP_INTEGRATION_KEY available to future Codex sessions through your operating system’s secure environment configuration. Do not commit the key to a repository.

Option 2: Codex configuration file

Add this to ~/.codex/config.toml:

[mcp_servers.mediacp]
url = "https://panel.example.com/mcp"
bearer_token_env_var = "MEDIACP_INTEGRATION_KEY"

Restart Codex or the ChatGPT desktop app after saving the configuration. In the ChatGPT desktop app, you can also open Settings > MCP servers, add a Streamable HTTP server, and enter the same URL. Use the shared configuration file when bearer-token settings are not shown in the interface.

ChatGPT web

ChatGPT web custom apps currently require an MCP-compliant OAuth 2.1 authorization flow with discovery metadata and PKCE. ChatGPT does not accept a custom static API key for this connection. The current MediaCP server provides a simpler client ID and secret exchange for Claude and does not yet implement all of ChatGPT web’s OAuth 2.1 requirements. Use Codex or the ChatGPT desktop app for the current MediaCP release. See OpenAI’s MCP authentication requirements for the web integration requirements.

Connect LM Studio

LM Studio can connect local models to remote MCP servers. Use a current LM Studio release and choose a model that is good at tool calling. See the LM Studio MCP guide for the latest interface.

  1. Open the Program tab in the right sidebar.

  2. Select Install > Edit mcp.json.

  3. Add the MediaCP server:

    {
  "mcpServers": {
    "mediacp": {
      "url": "https://panel.example.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_INTEGRATION_KEY"
      }
    }
  }
}

  4. Save the file. LM Studio should load the server and show its tools.

  5. Start a chat with a tool-capable model, enable the MediaCP tools, and approve calls when prompted.

This configuration stores the Integration Key in mcp.json. Protect the file with your operating system account permissions and never share or commit it.

Troubleshooting

The AI gives incomplete or poor answers

We have documented every MCP-exposed part of MediaCP internally so the AI receives detailed tool descriptions, parameters, natural-language usage guidance, and examples. There will always be room for improvement, and the integration is only as capable as the AI using it. Choose a model that performs well at everyday reasoning and tool-calling tasks, give it a clear goal, name the station or service, and include the time period you want analyzed.

Reporting requests are deliberately rate limited and a single reporting query covers no more than 31 days. Ask the AI to split longer comparisons into several periods instead of repeatedly retrying one large request.

The AI client cannot connect

  1. Confirm that the client is using the exact MCP Server URL shown on the MediaCP Integrations page. The URL must end in /mcp and must not include the panel’s old port number.

  2. Confirm that the header is Authorization: Bearer YOUR_INTEGRATION_KEY, with one space after Bearer.

  3. Confirm that API Access is enabled for both the system and the MediaCP user, and that MCP Server is enabled under System Config > Misc.

  4. Sign in as the root user over SSH and check all MediaCP services:

    mediacp status

    You can also check the MCP Server directly:

    mediacp status mcpserver

  5. From the MediaCP server, check the local health endpoint:

    curl http://127.0.0.1:3000/health

    A running server returns JSON with "status":"ok".

The MCP Server will not start, crashes, or has another problem

Logs are stored in:

/usr/local/mediacp/log/mcpserver/

Check the latest mcp-server-YYYY-MM-DD.log, mcp-error-YYYY-MM-DD.log, and mcp-server.out files. To restart the service in foreground debug mode and display detailed requests and errors, run as root:

mediacp restart mcpserver debug

Press Ctrl+C after collecting the error, then start the service normally:

mediacp start mcpserver

Never publish debug output without reviewing it first because requests and error details may contain private station data.

Tools are missing or an action is denied

MediaCP filters tools according to the user level associated with the Integration Key. Customer keys receive customer-level tools, while reseller and administrator tools require the corresponding account permissions. Sign in as the intended MediaCP user, copy that user’s key from Integrations, and reconnect the AI client. 

The post AI Integration appeared first on MediaCP.

]]> Audio Processing https://www.mediacp.net/doc/user-manual/audio/audio-processing/ Mon, 01 Jun 2026 23:49:42 +0000 https://www.mediacp.net/?post_type=doc&p=34617 Audio Processing allows broadcasters to enhance sound with intelligent audio processing and optimization, improving overall clarity for a polished, professional result. Two audio processors are supported master_me and stereotool. Audio Processing is available on all licenses from 2.15 onward. Note Audio processors are CPU intensive. Factor this into server resource planning. × Master_me master_me is […]

The post Audio Processing appeared first on MediaCP.

]]>

Audio Processing allows broadcasters to enhance sound with intelligent audio processing and optimization, improving overall clarity for a polished, professional result. Two audio processors are supported master_me and stereotool. Audio Processing is available on all licenses from 2.15 onward.

Master_me

master_me is an open-source audio processor. No license is required. It is configured directly within the MediaCP panel with minimal resource usage compared to Stereotool

Available processing profiles:

  • Apple Podcasts
  • EBU R128
  • Music General
  • Speech General
  • YouTube

Stereotool

StereoTool is a commercial audio processor. A valid license key is required for use. Configuration is done by uploading a .sts preset file to the station within the panel.

  • Preset File: Upload a .sts file for StereoTool configuration.
  • License Key: Enter your StereoTool commercial license key in the Audio Processor License field.

More information on StereoTool licensing is available at thimeo.com/stereo-tool/licenses.

The post Audio Processing appeared first on MediaCP.

]]> Video Stream Events https://www.mediacp.net/doc/admin-server-manual/video/video-stream-events/ Fri, 29 May 2026 01:02:41 +0000 https://www.mediacp.net/?post_type=doc&p=34503 Stream Events is a real-time event logging system for the Media Control Panel. Every action across the streaming services, from a encoder connecting live to an automated suspension, is captured, timestamped, and stored in a filterable log accessible on each service. Features Event Log Each service also shows a Stream Events item the Media Service […]

The post Video Stream Events appeared first on MediaCP.

]]>

Stream Events is a real-time event logging system for the Media Control Panel. Every action across the streaming services, from a encoder connecting live to an automated suspension, is captured, timestamped, and stored in a filterable log accessible on each service.

Features

Event Log

Each service also shows a Stream Events item the Media Service side menu, providing access to logs scoped to that service. Stream Events captures a comprehensive range of activity, including:

  • Service Events — Start, Stop, Restart, Suspend, Unsuspend, Song Title Update, Config Update, and Automated System Events along with the user or system that triggered them
  • Source Events — Connect, Disconnect, On Air (takeover), and Kicked events, including source IP, and takeover flag
  • AutoDJ Events — (TV Station) On Air at startup or when a live encoder disconnects and the system resumes control

Every logged event records the user, DJ, or system responsible for the action.

Log Filtering

Events can be filtered by category; All Events, Service Events, Source Events, and AutoDJ Events as well as by date range making it easy to monitor and find the exact events you are looking for.

CSV Export

Looking to share logs or run your own analysis? The Export CSV button lets you download the current filtered view, including service and customer information when used from the global admin panel.

30-Day Retention

To maintain performance logs are automatically retained for 30 days, after which they are cleaned up by the daily maintenance task. This keeps your database lean without sacrificing meaningful historical visibility.

API Access

Stream Events is fully accessible via the MediaCP API:

  • Global endpoint: /controller/EventLog
  • Service-specific endpoint: /controller/EventLog/{id}

Both endpoints support filtering by event type, service ID, and pagination, and return structured JSON responses including logs, total, page, and totalPages, along with formatted model attributes. Full documentation is available in our Postman API Docs.

The post Video Stream Events appeared first on MediaCP.

]]> Audio Stream Events https://www.mediacp.net/doc/user-manual/audio/audio-stream-events/ Fri, 29 May 2026 01:02:21 +0000 https://www.mediacp.net/?post_type=doc&p=34504 Stream Events is a real-time event logging system for the Media Control Panel. Every action across the streaming services, from a DJ connecting live to an automated suspension, is captured, timestamped, and stored in a filterable log accessible on each service. Features Event Log Each service also shows a Stream Events item the Media Service […]

The post Audio Stream Events appeared first on MediaCP.

]]>

Stream Events is a real-time event logging system for the Media Control Panel. Every action across the streaming services, from a DJ connecting live to an automated suspension, is captured, timestamped, and stored in a filterable log accessible on each service.

Features

Event Log

Each service also shows a Stream Events item the Media Service side menu, providing access to logs scoped to that service. Stream Events captures a comprehensive range of activity, including:

  • Service Events — Start, Stop, Restart, Suspend, Unsuspend, Song Title Update, Config Update, and Automated System Events along with the user or system that triggered them
  • DJ Account Events — Connect, Disconnect, On Air (takeover), and Kicked events, including the DJ name, source IP, and takeover flag
  • AutoDJ Events — AutoDJ On Air at startup or when a live DJ disconnects and the system resumes control
  • Mount Events (Icecast & Icecast KH) — Mount Connect and Mount Disconnect via the mount_add and mount_delete hooks

Every logged event records the user, DJ, or system responsible for the action.

Log Filtering

Events can be filtered by category; All Events, Service Events, Mount Events, DJ Events, and AutoDJ Events as well as by date range making it easy to monitor and find the exact events you are looking for.

CSV Export

Looking to share logs or run your own analysis? The Export CSV button lets you download the current filtered view, including service and customer information when used from the global admin panel.

30-Day Retention

To maintain performance logs are automatically retained for 30 days, after which they are cleaned up by the daily maintenance task. This keeps your database lean without sacrificing meaningful historical visibility.

API Access

Stream Events is fully accessible via the MediaCP API:

  • Global endpoint: /controller/EventLog
  • Service-specific endpoint: /controller/EventLog/{id}

Both endpoints support filtering by event type, service ID, and pagination, and return structured JSON responses including logs, total, page, and totalPages, along with formatted model attributes. Full documentation is available in our Postman API Docs.

The post Audio Stream Events appeared first on MediaCP.

]]> AutoDJ Crossfade https://www.mediacp.net/doc/user-manual/audio/autodj-crossfade/ Mon, 28 Oct 2024 02:47:23 +0000 https://www.mediacp.net/doc/%doc_topics%/audio/stream-proxy-copy/ Crossfading is handled by the AutoDJ provider which by default, and by our recommendation is Liquidsoap. Four options are provided with Liquidsoap AutoDJ being Fade-in, Fade-out, Smart Crossfade and Minimum Threshold.   Troubleshooting & More Information The Media Control Panel has little control over how crossfading functions besides the version of AutoDJ (Liquidsoap) provided. Should you […]

The post AutoDJ Crossfade appeared first on MediaCP.

]]>

Crossfading is handled by the AutoDJ provider which by default, and by our recommendation is Liquidsoap. Four options are provided with Liquidsoap AutoDJ being Fade-in, Fade-out, Smart Crossfade and Minimum Threshold.  

Crossfade Duration & Threshold

When not using Smart Crossfade, tracks will in sequence Fade-Out and then Fade-In without any blend or mixing. Crossfade can be disabled by setting both of these options to 0.

The Minimum Threshold setting checks the upcoming track and if the next track duration is less than the threshold, crossfading will be applied between the current and next track. The crossfade would not apply to the end of the track, unless the next track was also short.  Setting this option to 0 will ensure transitions on all tracks.

The Crossfade Cross Length setting sets the duration in seconds of the overlap between the end of the previous track and start of the next track. Note: length is only used when smart crossfade is not in use and must be at least the sum of Fade-in and Fade-out durations; it also defines the total crossfade duration.

 

Smart Crossfade

Smart Crossfade will automatically attempt to calculate the volume between tracks to produce an optimal transition. For example, should Track A include a soft fade at the end and Track B a loud start, Smart Crossfade would not fade-out and only fade-in. Read more about Smart Crossfade. Often tracks may already include a fade-out built into the media file, and in this case Smart Crossfade will be useful to avoid double ups in the crossfading transition.

Replay Gain Adjustment

The Replay Gain Adjustment feature works by checking the metadata on uploaded audio files for REPLAYGAIN_* metadata and adjusting playback using this metadata to normalize the volume of the audio stream. Enabling the feature will apply it across the entire service for AutoDJ tracks and will use more CPU.

You can read about the ReplayGain standard on the Hydrogenaudio Wiki.

The post AutoDJ Crossfade appeared first on MediaCP.

]]> Fallback, Backup and Intro Files https://www.mediacp.net/doc/user-manual/audio/fallback-backup-and-intro-files/ Wed, 24 Apr 2024 04:16:05 +0000 https://www.mediacp.net/doc/%doc_topics%/audio/media-library-copy/ MediaCP Audio Services have an intro folder by default that is useful for a variety of features. Files uploaded into this folder can be selected as Intro or Backup files and can also be selected as fallback mountpoints. This page will go through these features and how to use them. Uploading Intro, backup and fallback […]

The post Fallback, Backup and Intro Files appeared first on MediaCP.

]]>

MediaCP Audio Services have an intro folder by default that is useful for a variety of features. Files uploaded into this folder can be selected as Intro or Backup files and can also be selected as fallback mountpoints. This page will go through these features and how to use them.

Uploading

Intro, backup and fallback files can be uploaded into the Media Manager /intro folder. These files should be the same samplerate/bitrate as the stream. Once uploaded, they can be selected from the service configuration interface or mountpoint configuration. More information on uploading media can be found on the Media Library page.

Intro File

On Icecast and Shoutcast services there is the option to setup an intro file.  You can access this selction by selecting Configure, then navigating to the service type tab ie “Icecast 2 KH” or “Shoutcast 2” etc.

From there you can select and Intro file. This will configure an intro file for your radio station.

IMPORTANT: Note that the intro file MUST be the same samplerate/channels as the live stream in order for this to work properly.

Backup File

Shoutcast services have the additional option of a Backup File. This again will need to be uploaded to the /intro folder. 

You can access the selection for this by selecting Configure, then navigating to the Shoutcast 2 tab.

The Backup File selection specifies a MP3 file that will be streamed to connections over and over again when the source stream disconnects.

Fallback Mountpoint

In the Mount Points section, you you will need to select Manage Mount Points on the intended mountpoint.

From there you can select Media Tracks from the /intro folder or other mountpoints as a fallback should the stream go offline on the mountpoint.

A fallback mountpoint is configured with a parent mountpoint. In the event of the parent mountpoint losing connection it will then move all clients currently connected to the now defunct mountpoint to it’s fallback mountpoint or in this case the fallback track.

The post Fallback, Backup and Intro Files appeared first on MediaCP.

]]> Reporting https://www.mediacp.net/doc/user-manual/video/reporting/ Mon, 22 Apr 2024 00:22:02 +0000 https://www.mediacp.net/doc/%doc_topics%/audio/reporting-copy/ The Reporting page provides historical information for the last 6 months of broadcasting by default. This can be expanded to a maximum of 2 years. Information is updated nightly and available in several presets or custom periods. This section page a walkthrough and explanation for the sections of the reporting page for you to better understand […]

The post Reporting appeared first on MediaCP.

]]>

The Reporting page provides historical information for the last 6 months of broadcasting by default. This can be expanded to a maximum of 2 years. Information is updated nightly and available in several presets or custom periods.

This section page a walkthrough and explanation for the sections of the reporting page for you to better understand and make use of the information provided.

Reporting Period

On the top right of every page is the reporting period selection. By Default, this will show yesterday’s data but can be set to a custom range or the following presets; Yesterday, Last 7 Days, This Month, or Last Month

Summary

Viewers
  • Peak Viewers – The highest number of connections at one time over the period
  • Unique Viewers – Refers to the individual viewers connections including from the same IP address.
  • Total Viewers Hours (TVH) – The number of minutes or hours collectively viewed by all viewers. For example, 2 Viewers over 30 minutes would be 1 Total Viewer Hour.
  • Data Transfer – Total – The total data transferred in the selected reporting period.
  • Total Tracks Played – The total number of files played in the selected period.
  • Unique Tracks Played – The total number of unique files played in the selected period.
  • Peak Track – This will show the file with the highest peak viewers. It takes three lines to show the track metadata, peak viewer count, and the time/date.
  • Viewers over period – This Graph shows the viewers from the selected reporting period sorted by date/time and viewer count.
Export

Several reports are available for downloading providing more detailed information into CSV format:

  • Track Timeline Play by play report of performances and TVH
  • Track Performance Session information grouped by track
  • Region Performance Session information grouped by region
  • User Agents Session information grouped by User Agent
  • Top Viewers Session information from top 10 viewers
  • Daily Traffic Daily summary of data consumed by station

Other data can be directly downloaded with the Export buttons shown throughout. For example you can export the Sessions by Length data.

Sessions

Summary
  • Unique Viewers – Refers to the individual viewer connections including from the same IP address.
  • Unique Countries – The total unique countries from the viewers that have connected.
  • Unique Cities – The total unique cities from the viewers that have connected.
  • Unique User Agents – The total unique User Agents from the viewers that have connected.
  • Total Viewer Minutes (TVM) – The number of minutes collectively viewed by all viewers. For example, 2 viewers over 30 minutes would be 1 Total Viewer Hour.
  • Total Viewer Hours (LVH) – The number of hours collectively viewed by all viewers. For example, 2 viewers over 30 minutes would be 1 Total Viewer Hour.
Sessions
  • Total Sessions – The number of total sessions from the selected reporting period.
  • Average Session Length – The calculated average length of session from the reporting period.
  • Average Sessions Per Day – The calculated average daily sessions the reporting period.
  • Average Sessions Per Hour – The calculated average hourly sessions from the reporting period.
  • Data Transfer – Total – The total data transferred in the selected reporting period.
  • Data Transfer – Session Avg. – The calculated average data transfer per session from the reporting period.
Sessions by Length

This section shows a pie chart of the length of sessions.

GeoIP Map

The GeoIP map shows the color intensity of each country based on how many  viewers come from this region.

Popular Regions

Shows a sortable table of popular regions with information on the session count, TVH, and Data Transfer.

Top Viewers

Shows a sortable table of the Top Viewers with the IP Address, Country, City, Session count, and TVH.

Top User Agents

Shows a sortable table of the Top User Agents with the Country, City, Session count, and TVH.

Sessions by Time Period

Peak Sessions by Hour

This Graph shows the viewers from the selected reporting period sorted by date/time and viewer  count.

Sessions by Day of Week
This section shows a pie chart of the quantity of sessions based on day of week.

Tracks

The Tracks tab shows the services popular tracks comprehensive and sortable data table that is dynamically loaded and is exportable. 

Traffic

The traffic table provides a daily breakdown of data transfer relating to the service over the time period.

The post Reporting appeared first on MediaCP.

]]> Public Page https://www.mediacp.net/doc/user-manual/video/public-page/ Mon, 15 Apr 2024 23:38:09 +0000 https://www.mediacp.net/doc/%doc_topics%/audio/public-page-copy/ The Public Page feature is available on Video services and provides your station with a publicly accessible page with your media player. Enabling Public Page Public Page must be enabled by your server administrator from the Service -> Configure -> Features tab. Once enabled, it will be instantly available on the service from the new […]

The post Public Page appeared first on MediaCP.

]]>

The Public Page feature is available on Video services and provides your station with a publicly accessible page with your media player.

Enabling Public Page

Public Page must be enabled by your server administrator from the Service -> Configure -> Features tab. Once enabled, it will be instantly available on the service from the new Public Page page.

 

Customisation

From the Public Page you can access the station configuration. Here you can manage the Public Page and HTML5 Player.  

  • Address – Provides a link to access the public page.
  • Name – Title shown on the public page. This defaults to the services name.
  • Description – Brief description of your service, that is shown below the name.
  • Header color – Sets the color of the player header on the public page. Options of Green, Blue, Purple, Orange, and Red.
  • Public Page Background – Choose between the seven preset backgrounds or upload a custom background.

The post Public Page appeared first on MediaCP.

]]> HTML5 Player https://www.mediacp.net/doc/user-manual/audio/html5-player/ Wed, 27 Mar 2024 04:34:54 +0000 https://www.mediacp.net/doc/%doc_topics%/audio/public-page-copy/ The HTML5 Player is available on Icecast and Shoutcast services and allows you to have an embeddable player to easily share your radio station with. Managing HTML5 Player The HTML5 Player can be managed on the Public Page if that is enabled on your service. See Public Page If you do not have Public Page […]

The post HTML5 Player appeared first on MediaCP.

]]>

The HTML5 Player is available on Icecast and Shoutcast services and allows you to have an embeddable player to easily share your radio station with.

Managing HTML5 Player

The HTML5 Player can be managed on the Public Page if that is enabled on your service. See Public Page

If you do not have Public Page enabled, you can manage the HTML5 Player from the Widgets & Links page by selecting the settings icon (COG) in the top right corner of the player. 

You can also get your Embed Code from the Widgets & Links page.

Customisation

Here you can manage the  HTML5 Player from the station configuration page

  • Primary Color – Sets the color of the player header on the public page. Options of Dark, Green, Blue, Purple, Orange, and Red.
  • Permitted Domains – Restrict HTML5 player to this list of comma-separated list of domain names or leave empty to allow player on any website. 
  • AutoPlay – Automatically attempts to play the broadcast on load of the player at 50% volume. Autoplay requires visitor prior interaction (click, tap, previous visit with play, etc).
  • Display Options – Enable or disable displaying Connections, Direct Links, Mount Points, and Covers
  • Player Background – Player background is used when a cover is not found for the currently playing track, or the covers are not enabled. JPG file only.
  • Album Cover Provider – Allows you to use the default provider for the panel or choose between iTunes and Last FM to get album covers.

Permitted Domains

The Permitted domains feature can cause issues if not setup appropriately. It functions by restricting HTML5 player to the provided domains. If the panels domain is not permitted, then the player will not be available on the panel.

It is important to note that there should not be a trailing comma at the end of the final domain as that may cause the domain to not function. 

You should always include the subdomain for the websites you want to be permitted. For example, if your website uses the common www subdomain you will need to include this. 

The post HTML5 Player appeared first on MediaCP.

]]> Public Page https://www.mediacp.net/doc/user-manual/audio/public-page/ Thu, 21 Mar 2024 06:21:05 +0000 https://www.mediacp.net/doc/%doc_topics%/audio/stream-authentication-copy/ The Public Page feature is available on Icecast and Shoutcast services and provides your station with a publicly accessible page with a media player, listener count and track history. Enabling Public Page Public Page must be enabled by your server administrator from the Service -> Configure -> Features tab. Once enabled, it will be instantly […]

The post Public Page appeared first on MediaCP.

]]>

The Public Page feature is available on Icecast and Shoutcast services and provides your station with a publicly accessible page with a media player, listener count and track history.

Enabling Public Page

Public Page must be enabled by your server administrator from the Service -> Configure -> Features tab. Once enabled, it will be instantly available on the service from the new Public Page page.

 

Customisation

From the Public Page you can access the station configuration. Here you can manage the Public Page and HTML5 Player.  

  • Address – Provides a link to access the public page.
  • Name – Title shown on the public page. This defaults to the services name.
  • Description – Brief description of your radio, that is shown below the name.
  • Header color – Sets the color of the player header on the public page. Options of Green, Blue, Purple, Orange, and Red.
  • Display Options – Enable or disable displaying Track History and Connections 
  • Public Page Background – Choose between the seven preset backgrounds or upload a custom background.

HTML 5 Player

We have a dedicated page for the HTML5 Player and it’s features here: HTML5 Player

The post Public Page appeared first on MediaCP.

]]>