multiroom as server

[lifeform]

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?

I see in this forum, someone create docker for moode. However i do not check about multiroom. 
https://github.com/chourmovs/moode_tinkerboard

The multiroom system in moode right now is not meet my case. So i want to implement snapcast into it

Hope that docker meet your need

[pschellenbach]

I am brand new to Moode Audio - installed for first time yesterday - but have been using Snapcast for several years. My current Snapcast setup is a Pi3B with Hifiberry DAC+ADC Pro running both Snapcast server and Snapcast client. I feed one of my AVR zone output to the analog input on Pi, then feed analog output of Pi to another AVR zone. I select the music source on the first AVR zone (vinyl, FM, Spotify, etc), then listen to speakers on 2nd AVR zone. I have three Pi-Zero W's running Snapcast client in various rooms. Everything syncs perfectly.

I want better UI and automation of my music setup so I am exploring Moode Audio. Looks promising except for lack of Snapcast support.

I'm certainly not a Snapcast expert, but may be able to help with the integration in Moode. Snapcast communicates using TCP (proprietary protocol & websockets for control). I don't think multicast is used. 

Snapcast server accepts input from a named pipe, stdout, tcp, asla, and more. I believe MPD, librespot and shairport sync are all supported as sources to the server, so hopefully the plumbing to feed Snapcast server from Moode would not be too complicated. UI is another story.

I briefly browsed the github repos but don't really know where to start. Are there any "get started" developer documents? Any help getting started would be appreciated.

Thanks

[lifeform]

I am brand new to Moode Audio - installed for first time yesterday - but have been using Snapcast for several years. My current Snapcast setup is a Pi3B with Hifiberry DAC+ADC Pro running both Snapcast server and Snapcast client. I feed one of my AVR zone output to the analog input on Pi, then feed analog output of Pi to another AVR zone. I select the music source on the first AVR zone (vinyl, FM, Spotify, etc), then listen to speakers on 2nd AVR zone. I have three Pi-Zero W's running Snapcast client in various rooms. Everything syncs perfectly.

I want better UI and automation of my music setup so I am exploring Moode Audio. Looks promising except for lack of Snapcast support.

I'm certainly not a Snapcast expert, but may be able to help with the integration in Moode. Snapcast communicates using TCP (proprietary protocol & websockets for control). I don't think multicast is used. 

Snapcast server accepts input from a named pipe, stdout, tcp, asla, and more. I believe MPD, librespot and shairport sync are all supported as sources to the server, so hopefully the plumbing to feed Snapcast server from Moode would not be too complicated. UI is another story.

I briefly browsed the github repos but don't really know where to start. Are there any "get started" developer documents? Any help getting started would be appreciated.

Thanks

hello,
looks like what you looking for is https://github.com/moode-player

i already test moode for mpd only. i do not found configuration file yet for spotify, another source not investigate yet
like you, i also not expert but hope it can works with snapcast

[Tim Curtis]

I am brand new to Moode Audio - installed for first time yesterday - but have been using Snapcast for several years. My current Snapcast setup is a Pi3B with Hifiberry DAC+ADC Pro running both Snapcast server and Snapcast client. I feed one of my AVR zone output to the analog input on Pi, then feed analog output of Pi to another AVR zone. I select the music source on the first AVR zone (vinyl, FM, Spotify, etc), then listen to speakers on 2nd AVR zone. I have three Pi-Zero W's running Snapcast client in various rooms. Everything syncs perfectly.

I want better UI and automation of my music setup so I am exploring Moode Audio. Looks promising except for lack of Snapcast support.

I'm certainly not a Snapcast expert, but may be able to help with the integration in Moode. Snapcast communicates using TCP (proprietary protocol & websockets for control). I don't think multicast is used. 

Snapcast server accepts input from a named pipe, stdout, tcp, asla, and more. I believe MPD, librespot and shairport sync are all supported as sources to the server, so hopefully the plumbing to feed Snapcast server from Moode would not be too complicated. UI is another story.

I briefly browsed the github repos but don't really know where to start. Are there any "get started" developer documents? Any help getting started would be appreciated.

Thanks

View the Developer page at moodeaudio.org

[lifeform]

@Tim Curtis may i asked about spotify connect?
i trying search the configuration for spotify connect, could you tell me where is it? i try check file in moode github. but found nothing (i might missed it)
i still not check the sqlite3 (i just think this is for setting value)

so you might gave some clue? i want to reroute spotify connect to snapcast server.

[Tim Curtis]

I would start with /var/www/inc/renderer.php

[lifeform]

I would start with /var/www/inc/renderer.php

@Tim Curtis
sorry for distub once again. i wanna asked again
i added additional debuglog into renderer.php but looks like it never called.
i already restart the nginx and also clear nginx cache but changing directly  /var/www/inc/renderer.php nothing happened. 
what i missed? sorry for asking like this... found nothing several days

i need to test without reboot the raspberry pi. i check opcache also disabled

[Tim Curtis]

Its a function library and not a callable script.

Have a look at the function startSpotify() for information on how the librespot command string is built. You can also try searching the source tree for "startSpotify" and "stopSpotify" to see where these functions are called.

[lifeform]

Its a function library and not a callable script.

Have a look at the function startSpotify() for information on how the librespot command string is built. You can also try searching the source tree for "startSpotify" and "stopSpotify" to see where these functions are called.

i already search the startSpotify in github. i just found the function declare in www/inc/renderer.php
it called in restart-renderer.php, audio.php and worker.php

i got a little change in function startSpotify upload to system, reload nginx and php-fpm, click restart spotify connect or disable reenable from web'

but looks like my change never called. i just add line debugLog('recheck startSpotify') and check /var/log/moode.log for any log in there. but recheck never added in log.


i check nginx config and found that the root page is in the /var/www/ so /var/www/inc/renderer.php is correct path. but after update that file, restart nginx and debugLog is not there after restart spotify i just think cause of cache

[lifeform]

as far as i know (might be wrong)

submitJob will post a job that will be execute by worker.php
i can gave debug at submnitJob function but not in the worker.php (related with restart or start call function)

i still did not really understand how working.php works. is it related with watchdog? or some service?