Hi Everyone,
Im Using OBS with NMS and NPM on Ubuntu Mint on a own Dedicadet Server (i7 7700k 32 GB, 1 Gbit Down and Upload)
The program works perfectly in the Prism app / Streamlabs App. I think it just doesn't work with the GoPro on Connection lost and i really dont know why
I testet Larix App Also... and it doesnt work too like gopro
I just can do this step after connection lost:
I have to closed the running NPM Terminal, and Restart NPM START in Terminal - and it works again and i can connect with my gopro.
What I have already tested:
In Prism App - Start Livestreaming- closed prism app. Scene Switched From Live to BRB - WORKS PERFEKT
In Prism App - Start Livestreaming again- OBS Switched from BRB to Live. Shut down mobile internet. scene switched to BRB. - WORKS PERFEKT
But one Big Problem...
When I disconnect the GoPro from the power in live mode (simulating an LTE dead zone) - it takes a long time for NMS to notice this. The GoPro is Offline 10 Minutes, but !bitrate shows me a current connection... (maybe a dead publisher? )
The Problem is, when I simulate a LTE dead zone, I cannot reconnect to the Server with my GoPro, because there is an error with the URL.... It hangs up with recognizing the bit rate.
[28 Apr 23:06:04] @irrB0T: Aktuelle Bitrate: Offline
The !bitrate shows me after 15 Minutes - the Stream is Offline
Why does the bitrate take so long to drop to 0?
I just can do this step after connection lost:
I have to closed the running NPM Terminal, and Restart NPM START in Terminal - and it works again and i can connect with my gopro again
Hi Everyone, Im Using OBS with NMS and NPM on Ubuntu Mint on a own Dedicadet Server (i7 7700k 32 GB, 1 Gbit Down and Upload)
The program works perfectly in the Prism app / Streamlabs App. I think it just doesn't work with the GoPro on Connection lost and i really dont know why
I testet Larix App Also... and it doesnt work too like gopro
I just can do this step after connection lost: I have to closed the running NPM Terminal, and Restart NPM START in Terminal - and it works again and i can connect with my gopro.
What I have already tested: In Prism App - Start Livestreaming- closed prism app. Scene Switched From Live to BRB - WORKS PERFEKT In Prism App - Start Livestreaming again- OBS Switched from BRB to Live. Shut down mobile internet. scene switched to BRB. - WORKS PERFEKT
But one Big Problem...
When I disconnect the GoPro from the power in live mode (simulating an LTE dead zone) - it takes a long time for NMS to notice this. The GoPro is Offline 10 Minutes, but !bitrate shows me a current connection... (maybe a dead publisher? )
[28 Apr 22:49:26] @irrB0T: Aktuelle Bitrate: 3666 Kbps // Where I unplugged my GoPro [28 Apr 22:49:43] @irrB0T: Aktuelle Bitrate: 2876 Kbps [28 Apr 22:49:56] @irrB0T: Aktuelle Bitrate: 2055 Kbps // Low Bitrate Detection switched to LOW in this time (works) [28 Apr 22:50:32] @irrB0T: Aktuelle Bitrate: 1185 Kbps [28 Apr 22:50:53] @irrB0T: Aktuelle Bitrate: 959 Kbps [28 Apr 22:51:45] @irrB0T: Aktuelle Bitrate: 642 Kbps [28 Apr 22:53:53] @irrB0T: Aktuelle Bitrate: 354 Kbps [28 Apr 22:56:45] @irrB0T: Aktuelle Bitrate: 221 Kbps [28 Apr 22:58:39] @irrB0T: Aktuelle Bitrate: 177 Kbps [28 Apr 23:02:23] @irrB0T: Aktuelle Bitrate: 127 Kbps
The Problem is, when I simulate a LTE dead zone, I cannot reconnect to the Server with my GoPro, because there is an error with the URL.... It hangs up with recognizing the bit rate.
[28 Apr 23:06:04] @irrB0T: Aktuelle Bitrate: Offline The !bitrate shows me after 15 Minutes - the Stream is Offline
Why does the bitrate take so long to drop to 0?
I just can do this step after connection lost: I have to closed the running NPM Terminal, and Restart NPM START in Terminal - and it works again and i can connect with my gopro again