You have 30 minutes to complete this form before the CAPTCHA will expire.

Security image * Required field
This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param=&quot;Connection Issues NGINX To Some Stream Services&quot;]277[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by lionsground<br /><br /><comcode-quote param="153"><comcode-quote param="jacobgkau">Oh, I thought that I responded to your last post, but I guess I didn&#039;t.<br />So basically, like I mentioned before, Periscope&#039;s ingest requirements are lower than most other services can handle, so you can&#039;t just duplicate the signal packet-for-packet between all the services like NGINX normally does. By using the &quot;exec&quot; solution, you&#039;re running FFmpeg on your server transcoding the input in real-time to a format that Periscope can handle. That&#039;s likely to mean your CPU requirements are a lot higher, but since you&#039;re going <i>down</i> in quality, it might not be too bad.<br />As far as the key goes, it looks like Periscope gives you a different key every time you stream, so editing the nginx.conf file is how I would do it. The new Livestream.com also has that issue, since they give each &quot;event&quot; its own stream key, rather than having one persistent key per channel. It&#039;s just a limitation of platforms to watch out for.<br />You could always make a Bash script or something to generate you a config file based on keys that you input, but you&#039;d still have to run the script every time. Maybe you could make a web app so you can paste the keys into a GUI and have the app generate the config file on the backend&hellip; but that&#039;s a lot of scripting, so you&#039;ll have to decide whether that&#039;s worth it to not have to edit the config file manually every stream.<br /><input class="cms_keep_ui_controlled" size="45" title="[snapback]276[/snapback]" type="button" value="snapback Comcode tag (dbl-click to edit/delete)" /></comcode-quote><br />Hi, no Periscope use the same key (under producer). This also solved the problem with Vaughn.<br />But I am unable to stream to Vk.<br />I tried both way the normal push and the exec ffmpeg. It&#039;s not receiving data. I&#039;m trying to figure out how to solve this maybe you are familiar with this ?<br />I also seek a solution for a combined chat.<br /></comcode-quote><br />//// PUT YOUR REPORT BELOW \\\\<br /><br /> Add: Add: Font Size Color [Font] Arial Courier Georgia Impact Times Trebuchet Verdana Tahoma Geneva Helvetica [Size] 0.8 1 1.5 2 2.5 3 4 [Color] Black Blue Gray Green Orange Purple Red White Yellow This is a reported post for a post in the topic [post param="Connection Issues NGINX To Some Stream Services"]277[/post], by lionsground [quote="153"] [quote="jacobgkau"] Oh, I thought that I responded to your last post, but I guess I didn't. So basically, like I mentioned before, Periscope's ingest requirements are lower than most other services can handle, so you can't just duplicate the signal packet-for-packet between all the services like NGINX normally does. By using the "exec" solution, you're running FFmpeg on your server transcoding the input in real-time to a format that Periscope can handle. That's likely to mean your CPU requirements are a lot higher, but since you're going [i]down[/i] in quality, it might not be too bad. As far as the key goes, it looks like Periscope gives you a different key every time you stream, so editing the nginx.conf file is how I would do it. The new Livestream.com also has that issue, since they give each "event" its own stream key, rather than having one persistent key per channel. It's just a limitation of platforms to watch out for. You could always make a Bash script or something to generate you a config file based on keys that you input, but you'd still have to run the script every time. Maybe you could make a web app so you can paste the keys into a GUI and have the app generate the config file on the backend... but that's a lot of scripting, so you'll have to decide whether that's worth it to not have to edit the config file manually every stream. [snapback]276[/snapback][/quote] Hi, no Periscope use the same key (under producer). This also solved the problem with Vaughn. But I am unable to stream to Vk. I tried both way the normal push and the exec ffmpeg. It's not receiving data. I'm trying to figure out how to solve this maybe you are familiar with this ? I also seek a solution for a combined chat. [/quote] //// PUT YOUR REPORT BELOW \\\\ Use of this website implies that you agree to the website rules and privacy policy.