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

Looping a 4 bar clip skips the last bar #337

Open
alex-cherg opened this issue Sep 13, 2024 · 2 comments
Open

Looping a 4 bar clip skips the last bar #337

alex-cherg opened this issue Sep 13, 2024 · 2 comments

Comments

@alex-cherg
Copy link

alex-cherg commented Sep 13, 2024

Steps to reproduce:

  • compile Luppp from 9986ec2
  • record a clip lasting for 4 bars
  • after the 4 bars the clip starts looping
  • it goes successfully through 4 bars
  • however, on the second "loop" after bar 3 it goes directly to bar 1
  • the ultimate loop is 7 bars: b1 -> b2 -> b3 -> b4 -> b1 -> b2 -> b3 -> and repeat (b4 is skipped) -> b1 -> ...

Interestingly, when I save the session and then load it, the bug gets fixed and the full 4 bars loop correctly, however in a live performance scenario this is unfeasible.

I really like Luppp so far and would love to use it for live performances, however the above is a blocker.

Help is very much appreciated!

@harryhaaren

@alex-cherg
Copy link
Author

I compiled from https://github.com/openAVproductions/openAV-Luppp/releases/tag/release-1.2.1 and the issue doesn't seem present. So this seems to be broken in one of the following commits: release-1.2.1...master

@harryhaaren
Copy link
Member

Hmmm thanks for the breakdown into which range of commits are culprit, that is very helpful. I reviewed the commit messages, and didn't find an obvious culprit. Honestly, the fact there's no unit/integration tests built in Luppp (totally my lacking on doing this during development) allows this type of regression. As other comment I'm not really active on OpenAV projects anymore, so unless somebody picks up the issue & investigates, I'm not sure if/when it'll be fixed, sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants