Multi-Display and PiP with Ales Player: Installation, Performance and Networking Tips
How to set up Picture-in-Picture (PiP) and parallel tracking in Ales Player, which platforms are supported, how to manage bandwidth and hardware limits — step by step, with sample settings.
Introduction
Multi-screen (Picture-in-Picture or parallel playback) features in Ales Player strengthen the user experience in scenarios where you need to watch multiple broadcasts at the same time. In this guide, you will find how to install on which platforms, network and hardware requirements, practical settings and real usage examples. The content is intended solely for users' OWN legal sources.
What are multi-screen and PiP, when are they used?
- PiP (Picture-in-Picture): Simultaneous display of a second content (e.g. live score, camera view) in a small window of the main screen.
- Parallel viewing / multi-window: Two or more playback sections side by side on the screen.
Use examples: simultaneous match + analysis monitoring, live sports tracking with news feed, main broadcast with security camera feed. These features combined with Ales Player's Multi-source Support provide a powerful and flexible experience.
Which platforms are supported? (Restrictions and notes)
- Android TV (/platforms/android-tv): Full PiP experience provided if Android PiP APIs are supported. Performance increases with hardware acceleration; Parallel 4K playback may be limited on low-power TV boxes.
- webOS (/platforms/webos-tv): mini‑player/overlay support on webOS devices varies by manufacturer; Windowed viewing may be limited on the webOS version of Ales Player, so check your device's webOS version and model.
- Mobile (iOS/Android) (/platforms/mobile): In mobile applications, PiP usually works as the platform allows (supports iOS 14+ and Android 8+). Background noise and energy consumption are particularly important for mobile.
- Windows (/platforms/windows): The Windows application has “mini player” or multi-window support; It is possible to run multiple Ales Player instances or use the built-in multiplay mode.
Note: Platform's own PiP/overlay restrictions (codec, DRM, hardware acceleration) affect the experience.
Setup and quick settings (step by step)
Below are critical settings, both in-app and platform-specific.
- Install the current version of Ales Player. Updates bring performance and PiP compatibility.
- Add your resources to Ales Player; If you are going to use multiple sources, follow the configuration examples on the Multisource Support page.
- For Android TV
- Settings → Playback → Hardware acceleration: On (default). Without hardware acceleration, CPU load increases.
- Settings → Multi window / PiP: Enable PiP.
- Suggestion: Fix the resolution for the PiP window to the 480–720p range.
- Mobile (iOS/Android)
- Give Ales Player PiP and background playback permissions in device settings.
- Set a maximum resolution limit from within the app to control mobile data usage.
- Prefer a short pre-buffer value; Having a very large buffer in mobile networks increases data usage.
- Windows
- Settings → Window mode → Activate Mini player or Multi window mode.
- Use hardware acceleration; If GPU is supported, choose NVDEC/Intel Quick Sync.
- Sound and focus
- Determine which sound will be played in the PiP window (main window or PiP). Pin one via Settings → Sound → PiP audio.
- Automatic restart / Sync Where You Left Off
- If you log out while watching with PiP, enable the Continue Where You Left Off feature to maintain the viewing position.
Bandwidth and storage: practical calculation table
The table below is for example purposes; actual values vary depending on codec, GOP structure and ABR profile.
| Stream type | Typical bitrate (Mbps) | 2 windows (same resolution) | Recommendation PiP resolution |
|---|---|---|---|
| 720p SDR (H.264) | 2.5–4 | 5–8 Mbps | 480p–720p |
| 1080p SDR (H.264/HEVC) | 4–8 | 8–16 Mbps | 480p–720p |
| 4K HDR (HEVC) | 15–30 | 30–60 Mbps | 720p or 1080p (transcode) |
Practical notes:
- If there is a server that can deliver the same source at two different resolutions, choose the lower profile for PiP. This saves both network and CPU.
- If the server uses ABR, the application may reduce overall traffic by forcing lower profiles during parallel playback.
CPU, GPU and battery: performance optimization
- Hardware acceleration: Enable on every platform if possible. Software decoding increases multi-core CPU consumption.
- Number of decoders: Decoding multiple streams at the same time strains GPU/ASIC resources; Avoid more than 2 live windows on low power devices.
- FPS and chroma: In PiP windows, using 30 fps and 4:2:0 chroma may be sufficient; 60 fps and 4:2:2 require high resources.
- Thermal limits: Prolonged multiplayback may cause heat build-up, which may lead to throttling. Consider device cooling for long broadcasts.
- Mobile battery: Optimize background in PiP mode; If video decoding is left on in the background, the battery will drain quickly.
Use scenarios and sample settings
- Main screen: 1080p@30fps (H.264), PiP: 480p@30fps.
- Settings: PiP sound off (main sound on), hardware acceleration active.
- Expected traffic: 8–12 Mbps.
- News + Camera (Mobile)
- Main: 720p ABR, PiP: 360p. If there is a mobile data limitation, allow PiP only Wi‑Fi.
- Your location synchronization enabled, fast logout recovery.
- Security + TV (Windows kiosk)
- Main: 1080p, PiP: IP camera 720p (RTSP). Use the mini player mode of the Windows application.
- CPU: Decode camera directly with GPU acceleration; Increase buffer during action scenes.
Best practices: network and resource management
- Reduces the load on the network if you can use multicast / LAN resources for the same in-network devices. However, it requires multicast configuration and device compatibility.
- Serving different bitrate manifests of the same broadcast on the server side allows the client to choose a lower profile for PiP.
- User interface: Add controls such as quick close, resize and add to favorites in the PiP window; Keeping the viewer in control improves UX (integration with Favorites & Recommendations is recommended).
- PiP automation at live events: You can develop PiP triggering (e.g. show small window when score changes) strategies for key moments by pairing it with Live TV and EPG
Security, privacy and legal use
Ales Player does not provide the content; It is important that users only add their own legitimate subscriptions and sources. Be aware of content providers' DRM and terms of use when using multi-screen features; some DRM profiles may restrict PiP or second window. Also implement monitoring controls using profiles and parental control (Profiles and Kids Mode).
Summary and recommendations
- To get started: Limit the PiP window to low resolution (480p) and turn on hardware acceleration.
- Network planning: Calculate the number of parallel traces and the total bandwidth required with the table above; 4K parallel playback requires serious networking and hardware.
- Server side: If possible, make the client choose the lower resolution by providing a different profile.
- Platform differences: Android TV and Windows offer the most flexible experience; It may vary depending on the webOS model.
Practical step: Define multiple sources in Ales Player, enable PiP mode on one device, try a sample live match + news scenario and adjust PiP resolution based on bandwidth observations. For more resources and platform guides, you can check out Ales Player's Mobile Application (iOS/Android) and Windows Application pages.
Frequently Asked Questions
How many PiP windows can I open in Ales Player?
The number of PiPs that can be unlocked depends on the hardware power of the device and platform constraints. As a general rule, 1–2 windows are suitable for low-power devices, and 2–4 windows are suitable for powerful TVs/PCs.
How do I reduce total bandwidth when using PiP?
Use a lower resolution profile for PiP, if the server side offers different bitrates, match PiP to a lower profile and enable ABR to allow the client to make adaptive selection.
From which window does the sound come from in PiP?
Ales Player has audio focus adjustment; By default, the main window audio is played, but you can enable PiP audio from the settings. This may vary by platform.
Is PiP auto-triggering possible at live events?
Yes. For example, using EPG data and event triggers, PiP opening strategies can be implemented for a specific moment; For this, integration with [Live TV and EPG](/features/canli-tv-epg) is useful.
What should I do if PiP has performance problems?
First, enable hardware acceleration, lower the PiP resolution, close background applications and, if necessary, transcode a single stream and serve it in a lower profile.