-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
autoplay no longer working #156
Comments
I'm not sure if English is your second language, but the way you phrase "if according to..." here comes across as rude. :) Please understand I am the sole maintainer here and do this in my spare time.
Autoplay breaks Chrome and Firefox playback on desktop, as Firefox recently made a move to block all autoplay, and I expect Chrome and OBS Studio's Chromium to follow. It puts the underlying
This is what the instructions encourage on our Twitch widget page - the Twitch widget itself does not play audio for this reason. I will update the Twitch widget documentation as the best way to do this now, rather than media playing in the background, is the VLC source in OBS Studio, using one of our stream URLs as the playlist contents: http://allstream.rainwave.cc/all.ogg |
No rudeness was intended and I apologize if I came off as such. |
No worries, if I had a dollar for every time I was unintentionally rude on Github I'd be up there with Bezos by now. :D If you have any remaining questions or issues, you can ask here or on the Rainwave Discord. Will be more than happy to get you setup. :) https://discord.gg/rNCBhSz I'll be keeping this issue open until I've updated the Twitch widget help to mention the VLC source. |
A glance over the repo implies that this was intentional, as a commit 15 days ago specifically disabled the autoplay feature. Why is this, if according to the site's widget page, "We highly encourage you use Rainwave as background music for your streams"
To do so now means that the page needs to be loaded and interacted with every time the music is to start.
The text was updated successfully, but these errors were encountered: