Conversation
User-configured settings are lost when values are hardcoded, save them to restore after streaming so avoid errors on app restart
This reverts commit 948b6f3.
|
looks like there's a linter failure here |
When I try to check the error it says "Build not found" and re-running the test doesn't seem to be working. |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sorry about that didn't realize! our builds expire after i think a week so i just manually triggered a new one with the above command, i think you can do that in the future as well if you encounter missing builds again |
Thanks! The linter test is passing. |
When a user configures YouTube as a custom ingest, the stream type is
rtmp_common. When the stream starts, the stream type is changed tortmp_custombut the encoder remains as-is and works correctly.rtmp_commonhas specific encoders marked as available which are unavailable when usingrtmp_custom. In this case, when the app restarts after streaming and the stream type has changed, the encoder is marked as invalid because it is checkingrtmp_custom.Save the original settings when the stream is started so they can be restored when the stream stops to avoid this (incorrect) error.