ABHA79 wrote:Gary Adams wrote:Hello Jamie. There are two possible methods to do this. You would put this in the URL field. It is up to the service to allow one or both of these methods. Some do not. I would test this on OBS first to see if it works in the same way. I hope this helps. Stay safe.
rtmp:\\user_name:password@service_or_IP_address:port/publish_point
or
rtmp:\\service_or_IP_address:port/publish_point?rtmpauth=user_name:password
Regards, Gary
Thank you Gary for responding. I sincerely appreciate it. I feel like I'm close but nothing has worked yet as if I'm missing just one bit of information, or I've written the URL wrong somehow. Is there someone there at BMD that specializes in this sort of thing, using the encoder with a service that requires authentication?
Also, in your response did you mean to make it "rtmp:\\user_name...." or should it be "rtmp://user_name...."?
Here's some additional info that might help. DaCast gives me the following info (I've taken out the numbers and replaced it with # just to be safe in this post)...
Stream URL: rtmp://p.ep######.i.akamaientrypoint.net/EntryPoint
Stream Name: dclive_1_150@######
Backup URL: rtmp://b.ep######.i.akamaientrypoint.net/EntryPoint
Login Details (I've replaced the numbers in this post with XXXXXX for the login and YYYYYY for the password to be safe):
Login: XXXXXX
Password: YYYYYY
So with that information, I feel like I've tried numerous combinations within the Streaming.XML file but it's still not letting the stream go through. Maybe I've entered it wrong. But does this info help YOU in helping me figure out how exactly to enter this into the XML? When I used a Teradek encoder before with DaCast, there was a box in their software for the Stream URL, Stream Key, and then an Authentication Login box and a Password Box. BMD doesn't have the authentication login box and password box.
Hopefully this info helps you in helping me find the correct way to do this. As for OBS, I've never used it before. Again, DaCast says their service works with all RTMP encoders, but they just require authentication. I'm hoping we can find a resolution with the info above.
I don't know how helpful this would be, but this part of a page from a link that one of the agents from DaCast(requires username and password to stream) sent to me. I tried to paste the URL but that was blocked so I had to copy and paste a section I think is relevant.
****
Setting Up the Video Encoder Application
Following is some setup guidelines shared by Akamai in order to help you if you are still encountering issues while streaming after following to the word our encoder setup walkthrough or need to have more informations on the setup you desire.
In This Chapter:
A) Prerequisites
B) Supported Codecs
C) Stream Redundancy
D) Encoding Guidelines
After you complete your live stream setup, you will have the information to configure your video encoder to capture and push your stream to the entry points. Several third-party live video encoders are qualified for Media Services Live: Stream Packaging.
A) Prerequisites
Streaming technology allows ingest of the RTMP protocol while outputting Apple Live Streaming segments (full compatibility with RTMP in/HLS out) requires support of video in H.264 format and audio in AAC-LE format.
If you use an encoder other than those listed in the Dacast platform you must ensure that it issues the onMetaData packet as part of its broadcast, and that the packet includes the following information, or you will experience errors:
• description
• keywords
• rating
• title
• presetname
• creationdate
• videodevice
• framerate
• width
• height
• videocodecid
• videodatarate
• videokeyframe_frequency
• audiodevice
• audiosamplerate
• audiochannels
• audioinputvolume
• audiocodecid
• audiodatarate -->If your stream is audio-only, the encoder should remove the video-related entries:
• description
• keywords
• rating
• title
• presetname
• creationdate
• audiodevice
• audiosamplerate
• audiochannels
• audioinputvolume
• audiocodecid
• audiodatarate -->Similarly, if the stream is video-only, the encoder should remove the audio-related properties:
• description
• keywords
• rating
• title
• presetname
• creationdate
• videodevice
• framerate
• width
• height
• videocodecid
• videodatarate
• videokeyframe_frequency
****
Maybe this can help with identifying the requirements/sequence of the code etc to enable streaming?