“Static RTMP” feature – beta – available upon request
Tagged: static rtmp beta
- September 11, 2020 at 8:25 am #89230NanaParticipant
Hi there. Thank you so much for reporting. I have emailed you the correct link. Please check and confirm. I Apologize for any inconvenience caused.October 28, 2020 at 7:43 am #95792Charles MusisiParticipant
“message”: “Missing Authentication Token” error from my PostmanOctober 28, 2020 at 7:59 am #95798
Could you please provide more information as to when you receive this message and what actions have led up to this. If you provide a screenshot it would be more helpful to pin point the problem.March 15, 2021 at 6:23 pm #116181GabrielModerator
The feature may be unavailable or malfunctioning over the next couple of days due to platform changes related to this topic.
Please meanwhile use ‘ordinary’ rtmp addresses retrieved from the WordPress backend.
Will notify the thread when this feature is once again dependable.March 16, 2021 at 2:55 pm #116297GabrielModerator
Static RTMP (beta) is once again fully functional, it has totaled spotty downtimes of no more than 2 hours, starting yesterday.
Thank you for your understanding.March 23, 2021 at 12:02 pm #117250tom-5220Participant
Any issues with the static RTMP today? The channels wont start automatically.March 23, 2021 at 12:12 pm #117252
Sorry to hear that you are having issues with the Static RTMP. Can you please let us know any more details (including any errors) about this issue so that it can be replicated? Preferably some screenshots so we can understand the issue better. Looking forward to your response.March 24, 2021 at 8:37 am #117382tom-5220Participant
You have to push the “Start live event” and ” Go live with external broadcaster” button to start the channel and get the server and stream key to paste it in to Larix. When the static RTMP works fine the channel “wakes up” and the same key an server is used everytime. The issue is that the channel wont “wake up” to automatically for streaming. There is no errors, everything is up to date, nothing happends.March 24, 2021 at 9:53 am #117394
Thank you for reporting the issue and sending a detailed description. There was indeed an issue regarding the Static RTMP for users in Europe. This has now been rectified and it should be working. Please let us know if you face any other issues concerning the Static RTMP feature. However, bear with us since it is still a beta feature so limited support is available.
Thanks again!April 17, 2021 at 12:22 pm #121104admin-7908Participant
Is there a timeline for when this will come out of beta to be a standard, fully-supported feature?April 19, 2021 at 6:01 am #121370
Unfortunately, there isn’t a concrete timeline for when this beta feature will become a standard, fully-supported feature. Are you currently facing an issue with the Static RTMP that can be brought to our attention? Looking forward to hearing from you.May 6, 2021 at 1:26 am #124326yanrodriguez8271Participant
hi how i can get the static stmp for my streaming websiteMay 6, 2021 at 12:48 pm #124384
Please send an email to firstname.lastname@example.org with the instructed details at the beginning of this thread and one of my colleagues will get back to you ASAP. Thank you!June 11, 2021 at 5:09 pm #128972voyagerParticipant
Yesterday I was able to get everything working as I expected. This morning I fired up my OBS with the static RTMP server and key values and when I go to the streaming page on my website I get the “No playable sources found” message. Do I have to go into the WordPress site and activate the stream there every time I want to use the Static RTMP?
I thought it was supposed to start automatically “broadcasting to its corresponding ‘static rtmp’ address will start the channel if it’s inactive”.
Please let me know how to address this issue as I have programs to deliver next week and I need to have this work smoothly.
RickJune 14, 2021 at 10:01 am #129311
Sorry to hear that you are having issues. It appears that you are using the Low Latency beta feature along with the Static RTMP beta feature. Firstly, please note that these two beta features may not work together in all configurations. I would recommend attempting to use each beta feature on its own and let us know if they work well on their own, and then to observe whether this error comes about only when used together.
Secondly, the low latency beta feature is not optimized to work with caching so you may have to clear your cache each time you attempt to broadcast an event using the low latency beta feature.
Hope this helps and looking forward to hearing back.
- You must be logged in to reply to this topic.