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

get traction_engine working #11

Closed
atsushieno opened this issue Nov 27, 2019 · 4 comments
Closed

get traction_engine working #11

atsushieno opened this issue Nov 27, 2019 · 4 comments
Labels

Comments

@atsushieno
Copy link
Owner

tracktion_engine builds on Android, and it is most likely that it can handle audio plugin related bits in JUCE.

Then, if we implement juce_audio_processor for AAP it is likely to work. augene project can be used as a reference player. It is very simple auduo plugin based music player based on tracktion_engine.

Problem: even if we get this working, there is no "instrumental" sample yet.

@atsushieno
Copy link
Owner Author

Current problem: JUCE Android backend holds its own JavaVM and attach to JNIEnv by its own current thread. Call to JavaVM->AttachCurrentThread() twice does not work ("Calling AttachCurrentThread() on an already-attached thread is a no-op."). There needs to be some workarounds that makes it possible to unify those two frameworks.

@atsushieno
Copy link
Owner Author

atsushieno commented Jan 11, 2020

So far everything avoids dynamic JNIEnv instancing from JavaVM.

bd74234 has some JUCEy treat:
image

@atsushieno
Copy link
Owner Author

@atsushieno atsushieno changed the title implement JUCE audio processors and get traction_engine working get traction_engine working Mar 8, 2020
@atsushieno
Copy link
Owner Author

JUCE integration has moved to aap-juce repo. Closing.

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

No branches or pull requests

1 participant