Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Rework Song::processNextBuffer #5723
Rework Song::processNextBuffer #5723
Changes from all commits
6877575
e0f50e8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will be explained in the comment below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This adds
m_playPos[m_playMode] < timeline->loopBegin()
condition for jumping back which is undesired in casem_loopRenderRemaining > 1
, and make the area before the loop point be skipped or play wrongly. A relevant bug was reported on Discord.Also, the
startCycle()
call should be checked bym_playPos[m_playMode] >= timeline->loopBegin()
, though it was already wrong before this PR.The proposed fix is in the comment above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix looks good to me and seems to work properly; PR open at #5814.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
frameOffsetInTick
might be invalid at this point ifenforceLoop()
changed the play position.Edit: It's not a regression can even be wrong, so you can ignore it at this moment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A situation where it matters is:
As I mentioned above, it's not a regression, but an old bug. You can ignore this.
If it's considered as a bug, I can open a new bug report.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
frameOffsetInTick
is correct, in that it still corresponds to the ticks of the currentPlayPos
. The ticks of thePlayPos
should be reset to zero/fmod'd with one though (can't decide which is correct). The issue is #3028. (Zonkmachine mentioned this here: #5723 (comment).)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I see. Thanks for mentioning the relevant issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the same reason, this check might go wrong. This can result in skipping some TCOs.
Edit: It's not a regression and can even be wrong, so you can ignore it at this moment.