I restream using ReStream.io - I broadcast via OBS (my broadcast machine is MacOS, so therefore I cannot use the cool StreamLabs alternative app, unfortunately). My signal goes to ReStream.io, which sends it to both Slipmat.io and Periscope; I have a small-but-devoted Periscope audience whom I do not want to abandon, but they are solidly sworn to that platform.
I was granted a spot in the alpha testing group for the native streaming platform - thank you @uninen for this and for all of Slipmat.io! - and I did not experience any problems transmitting a signal from ReStream.io to Slipmat.io using the RTMP URL I was assigned during the alpha testing of the native streaming platform within Slipmat.io.
When I tried to transmit from ReStream.io to Slipmat.io this past Friday night/Saturday morning, however, I could not get my signal through from ReStream.io. @uninen came to my rescue - thank you again! - and discovered that the RTMP URL I was attempting to broadcast using had a “/” added to the end of it.
I opened up ReStream.io, saw that “/” added, deleted it, and saved my settings. However, when I still couldn’t get a signal through, I opened the settings back up in ReStream.io and saw that the “/” had returned. It is not possible to save an RTMP URL in ReStream.io, it appears, without ReStream.io appending a “/” to the URL.
I do not know if this is a new thing that ReStream.io has instituted, or if a “/” had always been appended to the RTMP URL I had been using previously; because things were working, I didn’t have occasion to check the RTMP URL in ReStream.io to observe whether or not it had been changed.
Has anyone else encountered this problem under similar circumstances?
Has anyone discovered a solution or workaround?
Is it possible to enable Slipmat.io to accept an ingest RTMP URL with a “/” appended?
I value your help and time more than I can express - thank you kindly!