Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


multiroom as server
#11
Correct. The sender cannot also run the receiver. This is built into the design of the multiroom feature including its audio configuration and network protocol (IP multicast).

To have sender also be a receiver you would prolly need to use something based on multi-unicast network protocol and that supports clock sync between sender and receivers for example I think SnapCast uses this approach.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#12
(07-24-2024, 02:49 PM)Tim Curtis Wrote: Correct. The sender cannot also run the receiver. This is built into the design of the multiroom feature including its audio configuration and network protocol (IP multicast).

To have sender also be a receiver you would prolly need to use something based on multi-unicast network protocol and that supports clock sync between sender and receivers for example I think SnapCast uses this approach.

so this means that 9.0.4 still not using snapcast for multiroom?
i remember you said snapcast intergration still in development. and then you gave some solution with multicast. so snapcast not integrated yet, right? 

for snapcast as sender also as client it is already implemented by raudio-1. i read some discussion about it in diyaudio forum.
Reply
#13
The existing TRX solution has always used IP multicast. A simple enhancement was made in 9.0.4 to allow multiple senders. This was done to support a usage scenario posted by a user.

Snapcast is on my TODO list to investigate but priority is low relative to other items on the list. If another dev wants to look into it I can help out a bit but be forewarned that integrating something like Snapcast will be a significant work effort.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#14
(07-25-2024, 10:45 AM)Tim Curtis Wrote: The existing TRX solution has always used IP multicast. A simple enhancement was made in 9.0.4 to allow multiple senders. This was done to support a usage scenario posted by a user.

Snapcast is on my TODO list to investigate but priority is low relative to other items on the list. If another dev wants to look into it I can help out a bit but be forewarned that integrating something like Snapcast will be a significant work effort.

can you might gave some clue what must to do with integrated moode and snapcast. i want to make it works. but my knowledge is limited. 

i have already trying snapcast multiroom with raudio. it is really awesome. cause the sender as receiver and my phone as receiver can listen same audio without some latency in client. 
it is really what i need Big Grin

based on your multiroom config, there is web snapcast that already included.
the main problem come to my mind is, what path of audio we want to works in moode. 

i will try to integrate it if you waant to help with it
Reply
#15
It would require more or less expert-level knowledge of moode code and its existing multiroom feature plus a strong desire to understand Snapcast code and how it works.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#16
(07-26-2024, 12:01 PM)Tim Curtis Wrote: It would require more or less expert-level knowledge of moode code and its existing multiroom feature plus a strong desire to understand Snapcast code and how it works.

ha ha ha

looks like you already declined my good deed.
however i understand with that.

if you have time please consider snapcast further.
Reply
#17
(07-26-2024, 12:01 PM)Tim Curtis Wrote: It would require more or less expert-level knowledge of moode code and its existing multiroom feature plus a strong desire to understand Snapcast code and how it works.

hello,
may i ask some clue for installing this.
i trying to install snapserver. and i already running it. the snapserver is already cast the sound to my phone (as client) i did not install snapclient in the moode yet

there is some problem i face it right now. when i added some mpd config to make snapserver receive song it keep vanish after i reboot the system. so looks like it is will be generate everytime setting is changing? am i right?

another problem how i route 
moode --> snapserver - - - network - - - snapclient --> speaker or something connected to moode hardware

this cause if i do not use snapclient as source of sound, sound in the server will be not sync with sound in my phone. there is latency that i cannot config

any clue or help? 


disclaimer : i know it is not yours responsibility to answer or to gave me some clue. but if you can help i really thank for that






UPDATED: 
snapclient can run after call with parameter "snapclient --player alsa:buffer_time=300 -s default:CARD=BR21"
after snapclient run. i add latency to 500ms to make sound in the moode hardware and in my phone sync right

cause i use usb dac so it needs to state. i still not found any  best solving method for this
Reply
#18
Quote:there is some problem i face it right now. when i added some mpd config to make snapserver receive song it keep vanish after i reboot the system. so looks like it is will be generate everytime setting is changing? am i right?



https://moodeaudio.org/forum/showthread....3#pid47753
----------
bob
Reply
#19
(08-04-2024, 05:28 AM)DRONE7 Wrote:
Quote:there is some problem i face it right now. when i added some mpd config to make snapserver receive song it keep vanish after i reboot the system. so looks like it is will be generate everytime setting is changing? am i right?



https://moodeaudio.org/forum/showthread....3#pid47753

noted. thankyou

could you tell me where spotify connect configuration location?
Reply
#20
I'm just wondering. I run 3 moOde players at home, but I also run OMV on another RPi and that contains a few dockers. Would it be possible to run moOde in Docker so it can serve as a server for a multiroom setup?
Reply


Forum Jump: