Releases: jprjr/multistreamer
11.0.3
11.0.2
11.0.0
New release! I'll be honest, there's no new features, just breaking changes. This version can be installed with Luarocks which should hopefully make deployment easier. Additionally, Multistreamer no longer uses config.lua
, it uses a YAML config file, and all database migrations will be automatic in the future.
If you're running a previous release, I put instructions in the README on how to upgrade - https://github.com/jprjr/multistreamer#migrating-from-multistreamer-10---11 - basically, you can export a YAML version of the config file, and prep the database for the automigrations.
Lastly, this new version specifically requires OpenResty 1.13+, which includes the Lua Stream module.
10.2.4
10.2.3
10.2.2
10.2.1
10.2.0
New Features! No config changes are required
Chat Widget Generator
Instead of manually crafting a chat widget URL, the user now has a page for configuring the URL with a small form. There's a Copy-to-clipboard button, and a preview of the chat on the right.
Chat Profile Pictures
The chat webpage/widget will show user profile pictures, if available. This is enabled by default on the widget, it's set with the "show_picture" query parameter
Chat Fadeout
You can set fadeout=(time in seconds)
as a query parameter, and messages in the chat will fade away and be removed after that period of time.
Compact Chat
The default chat interface is good for viewing chat on a nice, big monitor, but if you only have a small area for embedding, it's not so great.
If you add compact
as a query parameter, the chat will use an alternate layout (vertical instead of horizontal) and a smaller icon. This should work well in narrow spaces
10.1.1
10.1.0
New feature (changes only required if you want to disable transcoding/pullers).
config.lua
has two new options:
allow_transcoding
(default: true) -- if false, hide all transcoding settings from the userallow_custom_puller
(default: true) -- if false, hide custom puller settings from the user
Note: this will not remove previously-defined transcoding/puller arguments. If they're already set, they will remain active, but the user won't be able to disable them.
You can remove all previous transcoding arguments with the following SQL queries:
update accounts set ffmpeg_args = NULL;
update streams_accounts set ffmpeg_args = NULL;
To remove puller arguments:
update streams set ffmpeg_pull_args = NULL;