-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Selecting Tracks for Recording to File #778
Comments
I tested your new commit with 2, and 6 audio tracks streamed from the live source, and trying 2, 4, and 6 selected audio tracks for recording. My tests show that the behaviour has changed so that the number of audio tracks selected is respected rather than ignored. However, the recorded audio tracks are all duplicates of the first live source audio track. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I tested this on v0.14.4 and the issue that all recorded audio tracks are duplicates of the first track remains. |
I've been working on other important things in the meantime, so I've only now solved this problem. I applied it to the master, so test it Thanks. |
I tested your changes and the issue is resolved for my configuration, thanks for your great work! |
Describe the bug
Recording to files does not write the selected audio tracks. Instead, it ignores the tracks selection and duplicates the first audio track for each live source audio track (6 duplicates in my case).
To Reproduce
Steps to reproduce the behavior:
curl -d '{ "id" : "vod", "stream": { "name": "quat", "tracks":[0,3,6] } }' -H 'Authorization: Basic '"${OME_AUTH_KEY}" -H 'Content-Type: application/json' http://192.168.1.8:8081/v1/vhosts/default/apps/hw60:startRecord
Expected behavior
Selected audio tracks are written to the output file.
Logs
ovenmediaengine.log
Server (please complete the following information):
Additional context
As far as I am aware this issue is similar to the issue I had with #685, but for the Recording publisher instead of RTMP Push.
The text was updated successfully, but these errors were encountered: