You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed some log entries complaining about files not found, which seem to be related to the audio track selection in my push settings.
14:09:07 [FAIL] Opening file '/aac' failed: No such file or directory
14:09:07 [FAIL] Opening file '/|stereo' failed: No such file or directory
My push configuration for the steam is a follows. Where I would like to pick the stereo aac track of my stream and push it to Youtube together with the video feed.
The message is luckily harmless, but it shows a namespace collision between a RMTP feature to replace audio tracks on outgoing pushes and the generic audio track selector. It first tries to replace the audio track with a file listed as the audio parameter, if that fails it assumes it is a track selector instead and continues as normal. So I would say this is a bit of a mistake on our end. I think we'll be changing the audio overwrite RTMP function to another parameter, probably audioreplace makes more sense...
The custom url parameters is known and luckily fixed in current development builds! We're working on releasing the development as a new version, but we've put in probalby too many features/changes into a build and it's taking us a while (as is tradition at this point).
You can check at that build if you'd like, but the RTMP namespace collision would still be in there at the moment.
I noticed some log entries complaining about files not found, which seem to be related to the audio track selection in my push settings.
My push configuration for the steam is a follows. Where I would like to pick the stereo aac track of my stream and push it to Youtube together with the video feed.
And the stream metadata, if that helps.
As a side-note, I also noticed that when you edit the push and save it, another set of 'Custom url parameters' will be attached to the end.
The text was updated successfully, but these errors were encountered: