replace MusicControl repo with new one

[martinpl]

Transfer Music Control from OMGDuke to martinpl

Update restores functionality lost in (not) recent changes.

Reasons for Changing Ownership

Current maintainer step down, plugin don't work for a while. Maintainer agreed to forking / basing code on his work.

mirobouma/MusicControl#17 (comment)
https://discord.com/channels/960281551428522045/1020218094293106729/1415707759084834856

Task Checklist

Developer

• The original author or authorized maintainer of this plugin has either agreed to the transfer or has been unresponsive for an extended period as described above.
• I am accept the responsibility of becoming the authorized maintainer of this plugin.
• I have abided by the licenses of the libraries I am utilizing, including attaching license notices where appropriate.

Plugin

• I have verified that my plugin works properly on the Stable and Beta update channels of SteamOS.
• I have verified my plugin is unique or provides more/alternative functionality to a plugin already on the store.

Backend

• No: I am using a custom backend other than Python.
• No: I am using a tool or software from a 3rd party FOSS project that does not have it's dependencies statically linked.
• No: I am using a custom binary that has all of it's dependencies statically linked.

Testing

• Tested by a third party on SteamOS Stable or Beta update channel.

[martinpl]

#859 but without additional ci/cd actions (hopefully)

[github-actions]

This pull request is stale as no updates or testing reports have been posted within the last 7 days. Please ensure you are actively recruiting testers or resolving the issues discussed. If you do not remove the stale label or comment, this will be closed in 7 days. Please close this pull request if you need more time to resolve issues so we can keep our repo healthy.

[EMERALD0874]

@martinpl Your repo should share the same name as the previous one for our actions to succeed. Can you please rename the repo to its original name so the plugin is built correctly as a replacement for the original?

[martinpl]

@EMERALD0874 done

[EMERALD0874]

LGTM for testing

[mboaisha]

Bit late to the party but here are my testing notes

Plugin Testing Report

Installed Plugins

• Music Control - 1.7.1-96106b0
  • Current version in the testing branch
• TabMaster - 2.11.0
• DeckyFileServer - 1.1.0
• NonSteamLaunchers - 1.2.33
• ProtonDB Badges - 1.1.0
• PowerTools - 2.0.3
• CSS Loader - 2.1.2
• Battery Tracker - 0.2.0
• SteamGridDB - 1.6.0
• Storage Cleaner - 1.4.0
• HLTB for Deck - 2.0.4
• Free Loader - 1.4.1
• Animation Changer - 1.3.2
• EmuDecky - 1.0.2-1
• AutoFlatpaks - 1.6.8
• IsThereAnyDeal for Deck - 1.0.4
• Junk-Store - 1.1.9
• Wine Cellar - 0.1.6
• Audio Loader - 1.6.1
• MusicControl - 1.1.6
  • The stable channel one that should be unlisted
• PlayTime - 3.0.6
• Deck Settings - 1.2.5

Specifications

• SteamOS 3.7.15 (Stable)
• Steam 1759461205 (Stable)
• Decky 3.1.11 (Stable)
• Steam Deck OLED 1 TB with 1 TB Micro SD card attached.

Issues

Has the following major blocking issue(s): N / A
Has the following minor non-blocking issue(s):
- Would be nice to be able to display the plugin's version somewhere in the Info page.
- Link to the GitHub page mentioned in Info > Troubleshooting page suggested

Summary

Spotify was already installed via Discover. Switched the Store Channel to Testing in Decky Loader. Installed plugin. Music Control was able to detect Spotify with no issues.

Connected bluetooh headphones and played more music while playing a game in Steam. Modified audio codec earlier to minimize latency with my Bluetooth headset.

Audio while playing a Steam game was working as expected with no issues.

Tried playing Non-Steam games while audio running. No issues. (EmuDecky, PS2 emulation)

No issues found while docked on official docking station. I am able to control the music and output them through bluetooth headphones and TV speakers.

Instructions found in plugin are accurate and informative.

[martinpl]

@EMERALD0874 old plugin is still in the story, could be because of plugin name mismatch?