What problem would this solve?
I usually use a music overlay when streaming, in order to show attribution on screen (like required by NCS). This requires using a third-party YTM client in the first place, but the only supported clients are web wrappers.
Given YTubic's low resource utilization, it's extremely attractive for background music.
What would you like to see?
A standard web-socket server, emitting events whenever the following events happen:
- Playback Start
- Playback Stop
- Playback Time Update
Potential data fields for the events:
- Song Name
- Artist Name
- Album
- Current Play Time
- Album Image (either encoded, or the URL)
Alternatives you've considered
Currently, the existing solution is to either not show the song information, or to use another third-party client with support.
What problem would this solve?
I usually use a music overlay when streaming, in order to show attribution on screen (like required by NCS). This requires using a third-party YTM client in the first place, but the only supported clients are web wrappers.
Given YTubic's low resource utilization, it's extremely attractive for background music.
What would you like to see?
A standard web-socket server, emitting events whenever the following events happen:
Potential data fields for the events:
Alternatives you've considered
Currently, the existing solution is to either not show the song information, or to use another third-party client with support.