-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snapserver protocol expansion to dynamically use source #1232
Comments
See MusicAssistant... it has everything what you want;-) |
You mean https://github.com/music-assistant/server ? That does look interesting, because of has ;) however, what is the protocol? is it snapcast compatible? where is the esp32 client? Or an openwrt client. those are the things I want :p I do see very cool that they have an integrated python simple snapserver. so that's pretty interesting. |
Yes it's a controller for different protocols. Esp32 support is also possible. See here |
Not sure if I understand your use case correctly, there are two things that might help you:
|
Yeah, but that's just snapclient using the snap protocol :p |
But that still requires you to hardcode your multiple streams in your config file, right?
I saw that! That's also what music-assistant (ab)uses, but that requires you to know from a client which port to use
I'm thinking something like too; but in the end; what you expect as a user to be able to do is to simply connect to a tcp-port, and that after connection you get your own stream. E.g. like the telnet server works (and every other tcp client/server :p). That would 'fix' that issue. No c-library or anything needed. So then I wonder what the reasoning was behind the current tcp-server 'restriction' to only a single client? |
Currently, we have to define one entry in the configuration file for each source manually. For some things that works fine (airsync, spotify) however for the pipe/tcp endpoints this is rather odd. For simple setups of course it's understandable, but once you get into a 'family style setup' things get harder. E.g. lets say you have 4 potential sources, e.g. 4 people in a household. They all have their own preferences, sources, playlists etc. Lets also say we have a few client groups. e.g. 1 per user/room, one shared for livingroom + kitchen, 1 for shared livingroom and patio.
Sometimes, people want to listen to their music just in their room. Sometimes people want to listen to their music throughout the house. Sometimes there's a different mood on the patio and in the living room.
When connecting a client to the fifo/socket, It would be nice if it would dynamically show up as a new source. If the source where to send some metadata (source-name, maybe even an UUID) that would be enough. Everything else could function as it does right now, but without the need to specify unique sources for each player.
Note, that I very much realize this also means unique instances of frontends for each of those sources, but that could be arranged if needed, e.g. a frontend could be made smarter (e.g. each 'UI' gets its own session or a 'create session' like button).
This would certainly bring snapserver to the next level :)
The text was updated successfully, but these errors were encountered: