Dedicated Volumio Database and Play Queue?

[Gitaarwerk]

Very insightful Jotak thanks!

[Hooch]

@jotak

Hi,
I also agree with the abstraction layers, and Volumio having its own json-talking layer as the default one.
About DB: I talked with a mongo “evangelist” some weeks ago, because I also thought some NoSQL DB would be more interesting than SQLite. He advised me not to do it, because SQLite is as far as I know the only kind of DB that doesn’t take any resident memory for daemon. So it’s best fitted for small platforms such as pi, especially when there’s no very frequent DB requests , which is the case with volumio. Mongo uses a daemon. So does elastic search, which is suited for big data, it’s not our scheme. So except if some of you guys know some nosql version of a sqlite-like executable, I think the best is to stuck on that.

Thank you Jotak, I think that keep it light IS the way. So I totally agree to sticking with SQLite.

[volumio]

@jotak

Hi,
I also agree with the abstraction layers, and Volumio having its own json-talking layer as the default one.
About DB: I talked with a mongo “evangelist” some weeks ago, because I also thought some NoSQL DB would be more interesting than SQLite. He advised me not to do it, because SQLite is as far as I know the only kind of DB that doesn’t take any resident memory for daemon. So it’s best fitted for small platforms such as pi, especially when there’s no very frequent DB requests , which is the case with volumio. Mongo uses a daemon. So does elastic search, which is suited for big data, it’s not our scheme. So except if some of you guys know some nosql version of a sqlite-like executable, I think the best is to stuck on that.

Very sensible joel. Let’s stick with that. It will also allow us to reuse your code, with some slightly changes.

[jomo]

Hey everyone, I’ll use this to introduce myself. I was just added to the GitHub repo and this forum.
I have some experience with js and node, plus some other things. I’m also jomo on GitHub.
I’m currently running Volumio Beta 1.4 on a Raspberry Pi B+.

Anyway, if I understand the current architecture plan correctly, all audio is sent to SOX and then goes out via ALSA.
Would it be possible to support different output devices/services? I’m thinking of sending audio to speakers via AirPlay as requested here. This would allow to later add more options such as similar streaming protocols, or an HTTP stream.

PS: michelangelo mentioned a meeting that would start soon - where and what kind of meeting is this? Couldn’t find anything on the forums.

[volumio]

Dear Jomo! Yes, definetely a multi output setting would be ideal. I was thinking on something like this as well. What we need to do is just create multiple outputs with mpd, or create some sort of abstraction layers.
We’ll have a meeting on skype at 9pm, GMT +2 , I’ll send you my skype id via pm!

[jomo]

I don’t use Skype. I actually deleted it a long time ago because I really hated it, sorry guys.
You don’t happen to use IRC as well?

There is airplay and airplay2 for node, not sure what the difference is but they both sound promising to me.

[ning-yu]

One solution to multiple output might be to use PulseAudio as an interface layer to ALSA. It is possible to configure it for bit perfect audio playback (no resampling).

I think I have PulseAudio on the architecture diagram, but it is in the wrong place since I did not know what it was at the time!

Edit: Looks like it’s non trivial to configure PulseAudio to not resample!

[volumio]

I personally hate Pulse: soundwise is just a disaster, and its configuration is a pain in the ass…But we can see what we can achieve with alsa… We could use for non critical quality things, a loopback device or a FIFO

[volumio]

@jomo

I don’t use Skype. I actually deleted it a long time ago because I really hated it, sorry guys.
You don’t happen to use IRC as well?

There is airplay and airplay2 for node, not sure what the difference is but they both sound promising to me.

Sorry but we’re about to begin and everyone is on skype… You can use the skype web client without need to install anything
blogs.skype.com/2014/11/14/pleas … -web-beta/