jesterjosh
New Member
Nevermind, I figured it out. There error is misleading. I was actually missing semicolons at the end of the push commands.
Last edited:
Nevermind, I figured it out. There error is misleading. I was actually missing semicolons at the end of the push commands.
Thank you for your reply. Much appreciated. Is there anyone here that knows who I can hire to make such server.
And will this server be multi device usable.
Regards
worker_processes 1;
events {
worker_connections 1024;
}
http {
include mime.types;
default_type application/octet-stream;
sendfile on;
keepalive_timeout 65;
server {
listen 80;
server_name mydomain.org;
location / {
root html;
index index.html index.htm;
}
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root html;
}
}
}
rtmp {
server {
listen 8080;
chunk_size 4096;
application live {
live on;
record off;
#on_publish http://myip/auth.php;
#notify_method get;
#these two are for authentication, disabled to test this issue.
}
}
}
exec ffmpeg -re -i rtmp://localhost:1935/transcode/test -Some good Quality-settings who i can find in this forum... rtmp://other-plattform:1935/live/test;
If I stream at 1080@60 to my NGINX server and want to encode it but let it stay at 1080@60, what would the best ffmpeg command be? Do avoid it doing unnecesary downscale command or something? :P
Not same quality. Streaming using NVENC with 50mbit to the encoding pc, over there it's gonna get encoded to bitrates for twitch/hitbox. Aka 3500-4500.I'm not sure why you would want to re-encode the stream to the same quality?
Not same quality. Streaming using NVENC with 50mbit to the encoding pc, over there it's gonna get encoded to bitrates for twitch/hitbox. Aka 3500-4500.
But it isin't. You can stream usng more than 3,5k. It just limits your potential veiwers. So for my question, what would the ffmpeg line be for not doing unnecesary lines that scales it? just re-encodes the incoming stream to lower bitrates without modifying scale and such? I use the -s 1920x1080 line, but I'm not sure if its needed or not as it's already in 1920x1080@601080p 60fps isn't really possible at those bitrates. Twitch's max is 3500, and that's barely enough to make 720p 30fps look decent.
Thank you mate. So no need for the -s flag and -r flag? And how about the filter flag? lanczos/BillneaerFenrir is certainly correct: Official maximum bitrate you should use communicated by Twitch.tv is 3500. Of course you are free to use your own values, we cannot stop you from doing that, but twitch has the right to close down your stream if they want to.
Now to your question, if your input res/fps is the same as the output, you just have to tell ffmpeg which bitrate, encoder and preset to use.
Thank you mate. So no need for the -s flag and -r flag? And how about the filter flag? lanczos/Billneaer
hello! is it somehow possible if a streamer have a short disconnect (~2min) to show an alternative stream?
if yes can you show me an example? rmtp server is a remote dedicated server
E: or a video, its because if stream goes offline on twitch there is a huge viewer loss, i would pay for any help
Has anyone got a setup like this to work with the new Periscope Producer? It is just an RTMP server address and key, but when I put in the 'push' nothing appears in Periscope Producer's settings page. I've actually tried streaming to both Youtube and Periscope and the Youtube functions fine, but the Periscope goes into a black hole.
Streaming direct from OBS to Periscope works, or from the App Cameleon to both Youtube and Periscope, but can't make the NGINX solution outlined above work. Wondering if anyone else has had some success.
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()