[Feature Request]: Support for 6K Labs' Amuse Plugin

[AsuToki360]

Preflight Checklist

• I use the latest version of YouTube Music (Application).
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description

I usually put some music on my streams, and I really like this app, it's just missing a feature that has the other YT Music Desktop client to make it work with the Amuse plugin which shows the title and artist info, etc.
It's the "Remote Control" option, when that is enabled in the other client it does work with the Amuse plugin, however I would like to hear my music with no ads, and that client doesn't have an ad-blocker.

At the moment I'm writing this I haven't even found a similar option in this client, making the Amuse page a bit useless for my streams.

Proposed Solution

Add a similar option in this client or add a similar option, if possible.

Alternatives Considered

I'm thinking of something similar could happen if I tried the Tuna OBS plugin, although I haven't tested it yet.

Additional Information

No response

[ArjixWasTaken]

I'd assume OBS plugins like that would support mpris metadata (on unix) and whatever alternative windows has.
It is information provided to the OS.

[h-banii]

Apparently, despite Amuse saying they have "youtube music support", they actually mean ytmdesktop specifically

amuse: https://docs.6klabs.com/docs/accounts-apps/youtube-music
ytmdesktop API: https://github.com/ytmdesktop/ytmdesktop/wiki/Remote-Control-API

Amuse seems to be closed source and requires login to use, so I couldn't find much

[ArjixWasTaken]

They do give an option of connecting specifically to "th-ch/youtube-music", they have a drop-down when customizing the "connection" settings.

The issue is that they are asking for an IP and port, which doesn't make sense, and the guide they have is for ytmdesktop

[ArjixWasTaken]

I didn't test if they supported our new http api, but I highly doubt that.

[ArjixWasTaken]

As a former maintainer and current contributor, thankfully I can say "fuck it" and not work on this.

If a proprietary service does not give good documentation, and they would make profit from us supporting them...there is no motivation to actually support them.

They could make a PR to fix this, it honestly would be a 30 minute job if given the proper knowledge of how their API works.

(this is my personal opinion and doesn't necessarily reflect the opinion of the maintainers and other contributors)