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

Fail to achieve loop playback using B_LOOP #1809

Closed
dsyrock opened this issue Dec 1, 2023 · 1 comment · Fixed by #1808
Closed

Fail to achieve loop playback using B_LOOP #1809

dsyrock opened this issue Dec 1, 2023 · 1 comment · Fixed by #1808
Assignees
Labels

Comments

@dsyrock
Copy link

dsyrock commented Dec 1, 2023

Following the behavier in REAPER, B_LOOP=1 should mean that looping is enabled. I attempted to apply this to CF_Preview_SetValue, but the results were unstable. Occasionally, successful continuous looping was achieved with B_LOOP=1, but more often, it would stop on its own after a short period. With B_LOOP=-1, the success rate of loop playback is higher, but interruptions have also been experienced. Could you please advise on factors that may lead to interruptions in loop playback?

@cfillion
Copy link
Collaborator

cfillion commented Dec 2, 2023

It's a boolean so setting anything not 0 is considered a 1 and behaves the same. (This can be observed using CF_Preview_GetValue)

Got more details on the issue you're having with it and how to duplicate? I used B_LOOP yesterday while troubleshooting your section issue and it was working fine then.

EDIT: Is the REAPER window focused (or transport active) the whole time the preview is playing? By default REAPER closes the audio device when inactive (Preferences > Audio > Close audio device when stopped and an application is inactive).

EDIT2: Found a condition where the preview can sometimes be incorrectly destroyed at the loop point. Fixing that...

EDIT3: Builds for testing will be at #1808.

@cfillion cfillion self-assigned this Dec 2, 2023
@cfillion cfillion added bug and removed bug labels Dec 2, 2023
@cfillion cfillion linked a pull request Dec 2, 2023 that will close this issue
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 a pull request may close this issue.

2 participants