Skip to content
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

markrange waveformrenderer using rendergraph #14189

Merged
merged 1 commit into from
Feb 3, 2025

Conversation

m0dB
Copy link
Contributor

@m0dB m0dB commented Jan 18, 2025

Ports the markrange waveformrenderer to a rendergraph node. This can be reviewed and merged independently from the PRs for the other waveformrenderers.

Copy link
Member

@acolombier acolombier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like there is an issue with range. For example with an active loop here, the play position is going beyond the end marker

image

@m0dB
Copy link
Contributor Author

m0dB commented Jan 21, 2025

I can't reproduce this, @acolombier , but it also don't see how this could be caused by this PR.

If you set loop points, the range is drawn exactly where you set it, right? And if you close the track and re-open it, the range is where you expect it?

If this is the case, the range code is working. The fact that your play position goes beyond. the end marker must be something else. Is it only visual or also audible?

@JoergAtGithub
Copy link
Member

It could also be that the visual playposition is wrong. The related code to determine it is here: VisualPlayPosition::determinePlayPosInLoopBoundries

@m0dB
Copy link
Contributor Author

m0dB commented Feb 2, 2025

Ping @acolombier . Can you provide more info?

@acolombier
Copy link
Member

acolombier commented Feb 3, 2025

If you set loop points, the range is drawn exactly where you set it, right? And if you close the track and re-open it, the range is where you expect it?

No, it seems to have a slightly offset. But it could be the play position which is now quite where it should be!

Is it only visual or also audible?

Only visual.
I'll try to provide a recording asap to help with debugging!

@acolombier
Copy link
Member

I tried again and I couldn't reproduce neither on legacy nor QML UI! No idea why this was a problem previously.

Copy link
Member

@acolombier acolombier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, Thanks!

@acolombier acolombier merged commit 1d25302 into mixxxdj:main Feb 3, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants