Snapcast: Is this still being developed? as i love it

[palitu]

I have noticed that development has stopped for the last 6 months. Is that the end of snapcast?

I use it at home and i was looking at using it as a PA system for a 3rd world hospital, but if it is not being developed further i will have to look at a commercial solution.

i hope it isn't dead! as this is great.

[renearts]

As far as I know this is still quite actively developed. Have a look at the development branch, last commit was 5 days ago. Also the issue tracker shows a lot of activity. So I guess you shouldn't worry.

[badaix]

No worries, I'm just busy with other stuff.
Snapcast is still running 24/7 @ home (I'm one of the biggest fans :wink:) and there are already some small fixes in develop branch, which I should turn into a release soon.

[synth3tk]

That's a relief. I'm looking to eventually get Snapcast setup and integrated with Home-Assistant, but the lack of a recent release gave me pause. I never thought to check the development branch.

[palitu]

yeah - didnt check the dev branch either.

@badaix - i have it running at home, though i am currently in Kiribati. There hospital needs a PA system and im thinking that snapcast will work a treat for them to be able to use a push-to-talk microphone and pipe that to all the remote clients.

Is there a web based control client that i could set them up with?

Thanks, and looking forward to the next release!

[badaix]

@palitu There are some web controls mentioned here: #116. I don't know if they will fit your needs.

[palitu]

So i am one step closer to having a Hospital PA run off snapcast.

I have had a good meeting with the hospital director, and looking to get a system with 20 nodes installed, over both WiFi and Ethernet.

I will create a thread here when i get further into it, to show what i have done for it, and for others to use if they want.

I really need to figure out what version to use though, is v0.12 stable?

[badaix]

Well, I'm using the v0.12 at home and it's released now since 16 days without any bug related to it (except #294, which I was not able to reproduce yet). So I would consider it stable.

[slackline]

Hi @palitu ,

I was wondering how you've fared with implementing Snapcast for hospital PA systems?

My father-in-law wishes to synchronise audio to additional rooms in a few churches he's involved with and has asked my advice as he was impressed with my deployment of Snapcast on Pi's at home for syncing audio in multiple rooms (and thank you @badaix for writing and maintaining Snapcast, its brilliant and everyone who I show the system to is impressed).

The main challenge I think will be getting things to fit in with the existing systems which I suspect places will be reluctant to ditch (would be great if I could say "Get a Pi + iQaudio DAC+ as master for each center and Pi-Zero W + iQaudio DAC+ for each additional room at each church). Thus I was curious if or how you've integrated Snapcast into existing PA systems.

Thanks in advance and no worries if you've not done anything but I thought I'd ask.

Cheers,

slackline

[palitu]

@slackline, thanks for your interest

Unfortunately I am not integrating into an existing PA system.

What i have so far:

1. RPi as snapserver
2. a USB microphone with Push-to-talk
3. pulse audio loop-back device to send the microphone to the snapcast sink
4. cpiped to mute and unmute individual devices (cpiped tends to cause a number of breaks due to the way it is architected. I am just using it currently to mute/unmute)

for each client, they are pretty straight forward

1. OPi Zero with case and Anologue output board
2. Speaker
3. power supply
4. wired ethernet

One thing that i am noticing is that data transfer per client is starting to creep up - and with 20+ nodes, that may start to cause issues on their network.

So far - i have tested up to 5 clients.

There are a number of things that you could do - inpout from existing system into server.

My biggest issue is the lack of webUI to control and discover Nodes.

Good luck!

[slackline]

@palitu thanks for the write-up thats all useful information.

The biggest challenge I can see so far is where a Raspberry Pi slots into the existing system. Useful to know that you can loop-back pulse-audio into snapserver, and as you say the rest (clients) are pretty straight forward.

Challenge will be that there are multiple heterogenous setups and my father-in-law is at the other end of the country. I'm sure that can be overcome though one system at a time.

[SymanK83]

@palitu My first take of a web UI based on Node and angular is mostly done. If you are interested I could share the approach.

[palitu]

I'd Love it!

cheers

On Sun, Feb 18, 2018 at 6:35 PM, SymanK83 [e-mail] wrote:

@palitu https://github.com/palitu My first take of a web UI based on
Node and angular is mostly done. If you are interested I could share the
approach.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/badaix/snapcast/issues/278#issuecomment-366506690,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGU9IIMd8CzOWVyGr3jKapZ_u2e26ozlks5tV_0EgaJpZM4PiHY6
.

[SymanK83]

I‘ll get back to you in the next few days.
It‘s still a very rough cut and pretty ugly, but operational ;-)

[palitu]

ta

On Tue, Feb 20, 2018 at 5:52 PM, SymanK83 [e-mail] wrote:

I‘ll get back to you in the next few days.
It‘s still a very rough cut and pretty ugly, but operational ;-)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/badaix/snapcast/issues/278#issuecomment-366924776,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGU9IB0j4exFaAN8QR0jqB2hb1mMpscoks5tWpXrgaJpZM4PiHY6
.

[SymanK83]

Hi @palitu, sorry, this took much longer than anticipated.
I had some issues with the telnet connection. This interface is pretty ugly, but it works for me until I have time for it. Basically the server prepares the snapserver data for the web ui and vice versa. The UI displays the different elements available in the snapcast environment in rows (streams, groups, clients). You can drag streams to groups to make the group play that stream. And you can drag and drop clients to groups (splitting groups does not yet work). The upper row is meant to link to a static list of players (e.g. Mopidy Iris frontends).

https://github.com/SymanK83/simos

[palitu]

I like how you are thinking of the interface - not sure on the pink, but that is another topic ;)

Thanks, i will try and find some time to have a play.

[SymanK83]

I can relate to the color topic. I was hoping for my wife to be more inclined to use it. that worked ;-)
It‘s a heavy work in progress, and I‘m optimistic to make something worthwhile for daily use. Snapcast is a great platform for that. Maybe in a few weeks it will be worth showing to a wider audience using Snapcast and getting some feedback.
I‘m highly anticipating yours.