-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Fixed #3305: Frame reorder after the frame is read. #3319
Conversation
Could someone from the devs have a look at this? |
did not dig further, but the travis CI failed like following: |
@huili2 All versions since 1.8.0 have an issue that frames contain artifacts if multiple reference frames are in use. |
I verified with one case, and found you are correct. Could you please complement this PR to pass CI, i.e., modify corresponding SHA values in these tests? |
@xiaotianshi2 could you please verify this PR? I checked DecodeFile/DecoderOutputTest.CompareOutput/43, and found this PR could get correct 9 frames while current master could only generate 7 frames. |
@huili2 @xiaotianshi2 any update on this? |
c37a777
to
c1f98f1
Compare
@huili2 ok, did rebase this and modified the unit tests to pass |
Any news about this PR? I've just tested it and indeed solves some issues I've with WebEx and FreeRDP |
This really needs to go in, there are screen artifacts otherwise. What is the delay? |
Thank you! New release coming soon? |
This PR reverts a change that leads to screen artefacts when reading frames with multiple references for versions > 1.8.0