See the track without finding its window
Keep the title, artist and available artwork beside your game tools. When several players are open, the displayed source helps you choose the right one before pausing or skipping.
Music controls, beside your game
Gaming media controls. Keep your next track within reach.
Pause the music, find the next track and get back to your session. SysCubes brings supported Windows player controls into your dashboard, compact game overlay and paired phone, with direct local-file playback on the desktop.
Free Windows AppNo Account Needed100% Virus-Free (Overwolf Verified)
- Windows media sessions
- Dashboard + supported Overlay
- Local files on dashboard
Explore the interactive preview
A player within reachSilent example
Night Drive
Example Windows media session
3:00
Try Play to change the example state. This demo is not connected to a player.
Switch example surfaces and sources, then try the playback controls. Tracks are fictional and the demo is silent; it does not connect to players or load files.
Quick answer
Your player, controlled from your workspace.
Choose a Windows session to see its track and use supported play, pause, skip and seek commands. Put the controls on the desktop or over a supported game, and share them with a paired phone on your trusted LAN. For direct local audio, use the dashboard's Local files source.
The useful actions, close by
See the current track and control the player without searching for its window.
Pause, skip and keep the music moving
Use the commands your player exposes from one compact widget. Play/Pause, Previous and Next follow its capabilities; seeking adds a position control when the session supplies a usable timeline.
Fit playback around your session
Choose a Windows player or local audio on the desktop. Keep a compact session control over a supported game, or reach it from your paired phone. Direct file selection belongs to the full dashboard.
Keep using the player and music service you already know. SysCubes reads its Windows session and brings the available controls into your workspace, while the source app continues to handle its catalog, account and playback.
Put the controls where they fit
Dashboard, compact Overlay and phone offer different access.
| Surface | What it exposes | Boundary |
|---|---|---|
| Desktop / second-screen dashboard | System-session selector, Auto, supported playback controls and a Local files source. | Available sessions and supported local formats determine what can play. |
| Compact game Overlay | Current system-session metadata, supported playback buttons and seekable progress when available. | Requires a supported running game and this profile's media placement; no direct local-file picker. |
| Phone Companion | Selected system-session title/artist, status and supported fixed playback commands. | Pairing, enabled Media module and reachable trusted local network; no phone-side local playlist picker. |
Use a second-screen dashboard when you want a broader source selector visible beside the game. Use the compact Overlay when a small exposed-player control fits your HUD. For phone access, check the pairing and module requirements first.
Confirm which player will receive the action
Choose a preferred session or let Auto find an available player.
Start playback in the original app
A player must expose a Windows media session before the native controller can see it. Start a track or video, then check the dashboard. A running executable or open browser alone does not guarantee an exposed media session.
Select the session you want
Choose the displayed system player in the dashboard source list, or use Auto. The current selection prefers the saved session when present, then a playing session, a paused session and another available session. If a source disappears, confirm the new displayed title before sending an action.
Try the commands you use most
Pause once and confirm the intended player responds. Try skip or seek where offered, then place the widget where you want it. With several players open, keep the displayed title in view so each action reaches the right source.
Music playback and app playback volume are separate controls. The dashboard's system volume affects the current Windows output, while the per-app volume mixer provides a more specific live mix. Use the mixer when your question is how loud music should be beside the game, rather than which track should play.
Capability comes from the source
Play, skip and seek only when the current session permits them.
| Action | What must be available | Practical check |
|---|---|---|
| Play / Pause | The current session must permit the action appropriate to its playback state. | Verify the original player changes state. |
| Previous / Next | The session must expose the relevant skip command. | A live source or limited player may not offer a playlist action. |
| Seek | An exposed seek capability and a valid duration/timeline. | A duration label alone does not prove the player permits changing position. |
| Local playlist navigation | A loaded dashboard playlist and an available previous/next item. | At the start or end of the list, navigation is naturally limited. |
Microsoft documents separate media-session control flags for playing, pausing, moving between items and changing playback position. SysCubes uses those capabilities to determine available actions. If a player stops exposing a session or rejects a command, verify its state instead of assuming all media applications implement the same controls.
Audio files you choose on the PC
Use the dashboard Local files source for direct playback.
The dashboard can open one or several local audio files and play the selected list with track navigation, playback position and its own local playback volume. Actual playback depends on the format and decoding support of the app host. Start with a known working file and check that duration and sound appear.
Give your chosen audio files a place beside your notes, timer and volume controls. The local source stays in the full dashboard. For compact overlay or phone control, choose an external player with a supported Windows session instead.
Select the files you want on the PC and use the local playlist controls to move between them. Supported formats depend on the app host's decoder. The fictional tracks in this page's illustration are only examples and load no audio.
Start with one player and one surface
Verify the media workflow before an important session.
Choose the current Windows build
This workflow uses SysCubes on Windows through Overwolf. SysCubes is available to download via Overwolf; use the download page to get the official release and start managing your media.
Play a source and choose it on the dashboard
Start playback in the original player, inspect the exposed sessions and select the intended one. Test Play/Pause, then skip or seek only where offered. For direct local playback, choose a known audio file in the dashboard.
Place media in the intended game profile
Choose dashboard and compact Overlay visibility separately. A selected desktop widget does not automatically appear over the game. Keep the compact widget clear of useful game information, and verify actual game support.
Check the phone only after the desktop works
Pair on a trusted local network and enable the Media module. Confirm the displayed track matches the intended system session before testing a command. If it fails, separate the network/pairing question from the player's exposed-command question.
Get playback working
Find the next useful check for your player.
| Symptom | Useful next check |
|---|---|
| Nothing playing | Start the source app's playback and check whether Windows sees a system session. |
| Wrong title or player | Select the intended dashboard session; inspect fallback when the preferred source has closed. |
| Play works, Next does not | Check the session's exposed skip capability and whether another item is available. |
| Progress is shown but seeking is disabled | A valid timeline and seek permission are both required. |
| Direct local playlist is missing in Overlay | Use the dashboard Local files source; the compact surface controls system sessions. |
| Desktop works, phone does not | Check trusted LAN reachability, pairing and the enabled Media module before changing the player. |
Use the media controller troubleshooting guide for a source-first check. For general overlay availability, follow the startup and overlay steps. The missing mixer app guide covers audio playback sessions, which are separate from the media sessions used for transport commands.
Your questions, answered
Music controls, beside your game FAQ
What is the SysCubes media controller?
It is a widget for viewing and controlling supported Windows media sessions, with Play/Pause, Previous, Next and seeking where the player exposes those commands. Use it on the dashboard or in a supported compact game Overlay. The dashboard also has a Local files source for choosing and playing supported audio files.
Which music apps and browser players can I control?
SysCubes works with players that expose a supported Windows media session. Start a track or video, then choose its session on the dashboard. Track details and available commands follow that player, so check the actions you use most. App or browser playback alone does not establish support for every command.
Why are Next or the progress slider disabled?
A session can expose Play/Pause without supporting skipping or seeking. SysCubes reads the player's available controls and a valid timeline before enabling those actions. A live source, unavailable duration or disappearing session can therefore have fewer controls. Test in the original player before assuming the widget has lost a feature.
Can I choose which player the widget controls?
The dashboard source selector can prefer a particular currently exposed system session or use Auto. The current selection logic prefers a saved session when present, then a playing session, a paused session and another available session. A source that has closed may therefore fall back to an available player; verify the displayed title before sending a command.
Where can I play local audio files?
Use Local files on the full desktop dashboard to choose audio, navigate your playlist and adjust its player volume. The compact overlay and phone control Windows media sessions instead. For those surfaces, use an external player that publishes a supported session; the dashboard's direct local playlist stays on the desktop.
Can my phone control the selected music player?
With Phone Companion active, paired and its Media module enabled, the phone receives selected system-session metadata and supported fixed playback commands. It uses the preferred or available system session rather than a phone-side file picker. Both devices must reach the same trusted local network; the companion connection is local HTTP, not an internet remote service.
How do media controls relate to recorded audio?
Media controls choose what plays; your recorder's sources decide what enters the clip. Music included in captured system audio can still be recorded. Listen to a saved test clip and choose source separation when you need it. The volume mixer balances live playback levels rather than creating independently editable recording tracks.
Your PC. In your hands.
Keep the soundtrack close. Keep your session moving.
Bring media, app volume and your game tools into one Windows workspace. Download SysCubes for Windows free to control your music in-game today.
Download SysCubes for Windows
Free • No credit card or account needed • Instant 1-minute setup • Windows 10/11