Good evening from hot Spain.

[Nutul]

is not bad, but not too valuable either.

What do you mean? That allows you to listen to your favorite moOde player (in case you have many) from wherever you like within your LAN.
I cannot see how it could be more "valuable", maybe you can comment?

[janiversen]

Thanks a lot, for a splendid introduction to the code base.

As I start diving into the code base, I will try to make some notes, and later reformat them as documentation. However I am a "true" developer so documentation is not a strong point of mine.

THANKS for taking the time to get me started !

[janiversen]

What do you mean? That allows you to listen to your favorite moOde player (in case you have many) from wherever you like within your LAN.
I cannot see how it could be more "valuable", maybe you can comment?

You mention the nice part of the feature, being able to stream the music via http.

It lacks the possibility to switch output (local amp or http) or maybe just the possibility to silence the local amp. In my case I want to use my iPad with earbuds, while the rest of the family watches tv, which means disable the DigiAudio Amp+.

It would be more user friendly if it was integrated into the main application like e.g. Spotify have it.

Having now tried it for something like half an hour, I have run into the connection problem you mentioned. In case nothing is played http should just return an empty stream. This is not a big problem since I simply just refreshed the window.

But as I said it is a nice feature, that can be better :-)

[TheOldPresbyope]

I must be missing the point here. It feels like you are trying to make moOde be an music server when it's primary function is to be a music player. 

As it happens, a key component of moOde is the excellent MPD which is, tada, a music server and which has this odd http-server plugin, but I"d much rather use an MPD client on my phone/tablet/laptop/whatever which offers a decent user interface for this use case. Assuming, that is, that I want to take advantage of the library database already created by the MPD instance in my moOde player. I can just as easily run a music client on those separate devices which directly accesses the same underlying music sources.

As Unix/Linux cognoscenti have been saying for decades, "there's more than one way to do that!"

Regards,
Kent

[janiversen]

I must be missing the point here. It feels like you are trying to make moOde be an music server when it's primary function is to be a music player. 

As it happens, a key component of moOde is the excellent MPD which is, tada, a music server and which has this odd http-server plugin, but I"d much rather use an MPD client on my phone/tablet/laptop/whatever which offers a decent user interface for this use case. Assuming, that is, that I want to take advantage of the library database already created by the MPD instance in my moOde player. I can just as easily run a music client on those separate devices which directly accesses the same underlying music sources.

As Unix/Linux cognoscenti have been saying for decades, "there's more than one way to do that!"

Regards,
Kent

This can be a long war on words  It was not my intention to confuse things ! but I believe a music player should be able to play on different output media, like my speaker or my earbuds.

I do use the raspberry pi as a Media server as well, simply by sharing directories via SMB, but that is to me a different story.

Your idea of using a MPD client sounds like a very good alternative solution, the only problem is probably to get the same user interface but the advantage is that you can have multiple clients listening to different music. Do you have a recommendation for an iOS based mpd client ?

The expression in Denmark, the home of the Vikings, is "there's more than one way to skin a cat", but I like your quote more. And the quote is soo true.

[Tim Curtis]

What do you mean? That allows you to listen to your favorite moOde player (in case you have many) from wherever you like within your LAN.
I cannot see how it could be more "valuable", maybe you can comment?

You mention the nice part of the feature, being able to stream the music via http.

It lacks the possibility to switch output (local amp or http) or maybe just the possibility to silence the local amp. In my case I want to use my iPad with earbuds, while the rest of the family watches tv, which means disable the DigiAudio Amp+.

It would be more user friendly if it was integrated into the main application like e.g.  Spotify have it.

Having now tried it for something like half an hour, I have run into the connection problem you mentioned. In case nothing is played http should just return an empty stream. This is not a big problem since I simply just refreshed the window.

But as I said it is a nice feature, that can be better :-)

- Click the numeric level in the center of the volume knob to mute output to the local audio device. It won't affect the level of the HTTP feed. Thats always at 0dB.

- Instead of a Browser integrated player use VLC

[Tim Curtis]

I must be missing the point here. It feels like you are trying to make moOde be an music server when it's primary function is to be a music player. 

As it happens, a key component of moOde is the excellent MPD which is, tada, a music server and which has this odd http-server plugin, but I"d much rather use an MPD client on my phone/tablet/laptop/whatever which offers a decent user interface for this use case. Assuming, that is, that I want to take advantage of the library database already created by the MPD instance in my moOde player. I can just as easily run a music client on those separate devices which directly accesses the same underlying music sources.

As Unix/Linux cognoscenti have been saying for decades, "there's more than one way to do that!"

Regards,
Kent

This can be a long war on words  It was not my intention to confuse things ! but I believe a music player should be able to play on different output media, like my speaker or my earbuds.

I do use the raspberry pi as a Media server as well, simply by sharing directories via SMB, but that is to me a different story.

Your idea of using a MPD client sounds like a very good alternative solution, the only problem is probably to get the same user interface but the advantage is that you can have multiple clients listening to different music. Do you have a recommendation for an iOS based mpd client ?

The expression in Denmark, the home of the Vikings, is "there's more than one way to skin a cat", but I like your quote more. And the quote is soo true.

Playback Modes:

1. MPD
This is the core playback application.

- Play song files and Internet radio stations to a locally attached audio device.
- Concurrently but not synchronized, encode the currently playing file or station as an HTTP stream on default port 8000

2. Audio Receivers
These are 3rd party renderer (receive-only) applications integrated into moOde that receive streams sent by client applications using the protocols below.

- Bluetooth
- Airplay 1 and 2
- Spotify Connect
- SlimProto (Squeezelite)
- RAAT (RoonBridge)
- UPnP (UPnP to MPD proxy)

3. Audio Senders
These are applications and components integrated into moOde that can send output to other devices.

- Bluetooth (send MPD output to a Bluetooth speaker)
- Multiroom (send MPD, Airplay or Spotify Connect output to multiple other moOde players to-the-ear synchronized).

[janiversen]

Thanks for the very exact list. That helps me understand a couple of things.

Sorry for my lack of understanding I am still studying the docs repo, and I think you have written a lot of information, that could be used to enhance the documentation. I know "volunteers are welcome", so I let me see what I can do.

[Nutul]

Perhaps now it's time to move this thread where it belongs...

[Tim Curtis]

Thanks for the very exact list. That helps me understand a couple of things.

Sorry for my lack of understanding I am still studying the docs repo, and I think you have written a lot of information, that could be used to enhance the documentation. I know "volunteers are welcome", so I let me see what I can do.

Thanks :-)

You might want to consider creating a new, Application Architecture document in the docs repo and then link to it from the Overview section in the Master Development Guide.

There is no rush and I'll be happy to edit it.