Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'No such file or directory' warnings when using audio track selectors in push settings #223

Open
m4rcu5 opened this issue Jan 3, 2025 · 1 comment

Comments

@m4rcu5
Copy link

m4rcu5 commented Jan 3, 2025

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.

rtmp://a.rtmp.youtube.com/live2/<redacted>?audio=aac,|stereo&subtitle=none&video=all

And the stream metadata, if that helps.
image

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.

@Rokamun
Copy link
Contributor

Rokamun commented Jan 6, 2025

Heya!

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants