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

Initial feedback for (virtual) controller mappings sometimes not sent right after project load #172

Closed
helgoboss opened this issue Feb 23, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@helgoboss
Copy link
Owner

No description provided.

@helgoboss helgoboss added bug Something isn't working enhancement New feature or request and removed bug Something isn't working labels Feb 23, 2021
@helgoboss
Copy link
Owner Author

This is related to REAPER itself. ReaLearn properly sends the feedback to the device output provided by REAPER but REAPER doesn't send it yet, looks like it has a buffer that doesn't get flushed. But Audio_IsRunning() returns true.

Pressing play is one of the events that eventually send the data. Another way is to call Audio_Quit() followed by Audio_Init().

@helgoboss helgoboss changed the title Initial feedback sometimes not sent right after project load Initial feedback for (virtual) controller mappings sometimes not sent right after project load Feb 25, 2021
@helgoboss
Copy link
Owner Author

Wrong. It's ReaLearn's fault. It only seems to affect virtual controller mappings. The real-time processor receives the feedback instructions but at a time when it doesn't have all virtual mappings yet.

helgoboss added a commit that referenced this issue Feb 25, 2021
by resolving feedback for virtual controller mappings always in main processor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant