Release notes
Videorc 0.9.115 Beta 1
Going live on Kick works now. In 0.9.113 and 0.9.114, Videorc sent Kick streams to the wrong address and Kick refused every one. Stream keys also stay out of the logs, and signing in to a platform ends on a proper Videorc page.
Kick streams go live
- Kick streams connect again; 0.9.113 and 0.9.114 could not go live on Kick.
- Stream keys no longer appear in logs or support bundles when a stream fails.
- Signing in to a platform ends on a Videorc page that says you're connected.
Kick
Going live on Kick failed straight away in 0.9.113 and 0.9.114, with an "Input/output error" and nothing reaching your channel. Kick hands out its ingest address without the part its servers expect, and Videorc used it as it was. Videorc now builds the full address from what Kick returns, so a connected Kick account goes live again. Nothing needs to be reconnected: Videorc reads your Kick stream key each time you go live.
Stream keys stay private
When a stream could not connect, the error Videorc logged included the full destination address, and for RTMP that address contains your stream key. Stream keys and any password in a server address are now masked in the log, in the in-app log and in support bundles. If you shared a support bundle after a failed stream, consider resetting that platform's stream key.
Connected
After you sign in to YouTube, Twitch, Kick or X, the browser tab now shows a Videorc page that says you're connected and names the platform, instead of a bare line of text. If sign-in failed, it says why and what to try next.
