-
Notifications
You must be signed in to change notification settings - Fork 132
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
[Multiple Threading] getCurrentPeriod not correct after period changes #1525
Comments
BTW: Same asset works fine without multiple-threading. |
Hello, We have some issue reproducing for now, but it seems similar to the issue fixed by #1502 (though that one was generally an issue for the initial Period, not the next ones). Can you check with our last development build? You can put If it also has the issue, we may have the need to reproduce it. |
Hi @peaBerberian , Thanks for reply, I'll check with latest dev branch and see if the issue still there. Another comment for this issue is, the period switches between encrypted one to unencrypted. I'll try get a test stream for you if the issue still there. |
Scratch that we reproduced it! |
Thanks for reporting the issue, |
Sorry closed that one by mistake |
We just made the dev build including the fix: It's planned for the next official release, we plan it for next month for now. |
The latest dev branch dose fix the issue above. Thanks @peaBerberian . |
Thanks! That's @Florent-Bouisset quick investigation and fixing work, I'm only a messenger and version-releaser in that issue! |
Hi there,
Seems that we're not get the correct currentPeriod when play multi-period stream with multiple-threading feature enabled.
user agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36
Details as below logs:
One more thing is eventListener
periodChange
is not been triggeredCould someone help check this issue?
Thanks in advance.
The text was updated successfully, but these errors were encountered: