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
interaction when running multiple instances #184
Comments
Yes, that is how it is. There is a common audio backend (audioplus) used by all the audio_render components (used by omxplayer). audio_render does pause audioplus when paused. This unfortunately stops other clients. |
Noticed this today. Glad I'm not the only one :) |
How do you get different dbus names for each instance? I got it working for one instance by reading /tmp/omxplayerdbus.pi but it's always the same, even after restarting the script. I have launched another instance by Popen... |
start omxplayer with |
When I run multiple instances of omxplayer (in --win mode), I'm getting a strange interaction from the play/pause command (via stdin or dbus). For dbus commands I'm using different dbus names for each instance.
When I pause one video, the other videos play on but are muted. If I resume the first video again, I'm getting sound back immediately on other videos, but their video display freezes for a moment.
If I have paused one video and lost sound on all others, I can get sound back on them, when I pause them and start them again (each one). If I then resume the first video, the other videos are not disturbed in any way.
The text was updated successfully, but these errors were encountered: