Not sure if this question belongs here or in Music Assistant but wondering if Sendspin spec and players could support "zones" or is it up to each and every Sendspin client to expose itself as multiple players if the client player capable of multi-room audio via multichannel audio? That is, how can the Sendspin specification best support "single source, multiple zone" when client is in practice a single reciever that has multiple outputs connected to stereo-speaker sets located in different rooms.
Is the longterm plan that the Sendspin protocol will natively expose such multi-room zones too someday if a single client have multiple zones?
FYI, it does sound like the "MusicCast" player provider in Music Assistant offer such zone handeling features to support multiple zones, (but it does have known limitatiom that if a device has multiple zones (i.e. main + max 3 others) only one of these zones can be streamed to. However, if streaming to main, the other zones can be joined to that player, however this is a limitation of the Yamaha devices and not in Music Assistant).
For reference; someone in the Home Assistant forum asked if Music Assistant server had a Denon AVR player provider and if that has "zone" supported, and the back-story there is that some AVRs (Audio Video Receivers, a.k.a. AV receiver, also known as a home theater receiver) can be used to as a multi-room audio system to provide multichannel audio to different zones as an alternative to using them for home cinema surround sound.
Another multi-room audio use case is that there are stereo receivers that are known as "Multi-Zone Amplifier" (a.k.a. "Multi-room Amplifier") which are designed to act as a multizone amplifier with built-in support for multi-room audio that can output stereo to multiple rooms, such as example MusicCast (Yamaha), [HEOS(https://www.denon.com/en-us/inside-denon/how-to/what-is-multi-room-audio-everything-you-need-to-know.html) (Denon), and the Sonos Amp Multi (that is usually rack-mounted and made for professional installations)
Meaning that while some stereo receiver(s) are designed to only multi-room audio for playing music in different zones, he in this case he had his home AVR in a similar setup as many of those is similarly also capable of outputting 2-channel audio to different rooms, and what he wanted is a player provider in Music Assistant that is capable of seeing that his AVR setup offers different zones and offer the ability to select which zone(s) to play to directly from Music Assistant.
PS: I also know that Music Assistant also has an HEOS player provider but the webpage for it specifically mention that a known issue (limitation) is that while playback to additional zones is supported they cannot be turned on/source selected from Music Assistant (and instead it needs to be controlled externally, maybe via Home Assistant).

Not sure if this question belongs here or in Music Assistant but wondering if Sendspin spec and players could support "zones" or is it up to each and every Sendspin client to expose itself as multiple players if the client player capable of multi-room audio via multichannel audio? That is, how can the Sendspin specification best support "single source, multiple zone" when client is in practice a single reciever that has multiple outputs connected to stereo-speaker sets located in different rooms.
Is the longterm plan that the Sendspin protocol will natively expose such multi-room zones too someday if a single client have multiple zones?
FYI, it does sound like the "MusicCast" player provider in Music Assistant offer such zone handeling features to support multiple zones, (but it does have known limitatiom that if a device has multiple zones (i.e. main + max 3 others) only one of these zones can be streamed to. However, if streaming to main, the other zones can be joined to that player, however this is a limitation of the Yamaha devices and not in Music Assistant).
For reference; someone in the Home Assistant forum asked if Music Assistant server had a Denon AVR player provider and if that has "zone" supported, and the back-story there is that some AVRs (Audio Video Receivers, a.k.a. AV receiver, also known as a home theater receiver) can be used to as a multi-room audio system to provide multichannel audio to different zones as an alternative to using them for home cinema surround sound.
Another multi-room audio use case is that there are stereo receivers that are known as "Multi-Zone Amplifier" (a.k.a. "Multi-room Amplifier") which are designed to act as a multizone amplifier with built-in support for multi-room audio that can output stereo to multiple rooms, such as example MusicCast (Yamaha), [HEOS(https://www.denon.com/en-us/inside-denon/how-to/what-is-multi-room-audio-everything-you-need-to-know.html) (Denon), and the Sonos Amp Multi (that is usually rack-mounted and made for professional installations)
Meaning that while some stereo receiver(s) are designed to only multi-room audio for playing music in different zones, he in this case he had his home AVR in a similar setup as many of those is similarly also capable of outputting 2-channel audio to different rooms, and what he wanted is a player provider in Music Assistant that is capable of seeing that his AVR setup offers different zones and offer the ability to select which zone(s) to play to directly from Music Assistant.
PS: I also know that Music Assistant also has an HEOS player provider but the webpage for it specifically mention that a known issue (limitation) is that while playback to additional zones is supported they cannot be turned on/source selected from Music Assistant (and instead it needs to be controlled externally, maybe via Home Assistant).