rtmp server destination as streaming output about botamusique

[Fr6jDJF]

Mumble stays pure VOIP with this, but still controlling the music.

There is some disappointment in the quality that the Opus codec is producing for music streaming output. Not only expressed in range but also in bending audio.

Therefore, user owned hour+ mixes, and user mix livestreams (if not video gameplays) are generally streamed directly to the rtmp service on a few output paths by some of the users here.
This currently with simple VLC/one-liner ffmpeg commands/OBS, where Mumble with it's connected users being the binding factor for providing sources.
Fine for long tracks and live sessions, less for short and separate songs by diverse/current listeners interest.

In this, I would like to add botamusique to the general rtmp service route, for the yt-dl song requests, to get the 3rd party sourced playlist compose factor in there (bot simply taking over the sourcing task for non live media/lower that threshold for content input with diversity)

*The rtmp service method allows routing Mumble VOIP towards center speaker, so voice won't reach sub audio range and music dB output levels during playback, still being sourced through it by commands.
clean voice/clean music

[azlux]

If I understand well, you modify the bot to send flux to rtmp radio instead of the mumble channel.
Mumble is useless in this case. Can you explain me the use case ?

[TerryGeng]

I think botamusique is designed to focus on transmitting music into mumble server, so the kernel of this bot is pymumble.

Since stereo support has been added in mumble 1.4.0 and has now been incorporated into botamusique, I don't see any reason that the music this bot delivers is not matched with the music wrapped in other protocols.

I shall close this issue now. If you'd like to continue this discussion, I'll reopen this issue.