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

Instance index ignored? #5

Open
arokhsar opened this issue Apr 4, 2023 · 3 comments
Open

Instance index ignored? #5

arokhsar opened this issue Apr 4, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@arokhsar
Copy link

arokhsar commented Apr 4, 2023

In the example project with the QuantizedBuffers plug-in, if you go to the DrumKitTrack and change the Instance Index to any value other than 1, even though the DrumKit script is hard-coded with an instanceIndex value of 1, the script still seems to be communicating with the same QuantizedBuffers instance.

For example, I would expect that if I change the Instance Index on the plug-in to 2, but still do QuantizedBuffersHelper.FindById(1), I would no longer hear any drum samples when I press the input keys. Instead, it behaves as if it the indices match.

Similarly, if I keep the QuantizedBuffers index at 1, but change the instanceIndex in the DrumKit script to any other value, QuantizedBuffersHelper.FindById still seems to return that same QuantizedBuffers plug-in.

@x37v x37v self-assigned this Apr 11, 2023
@x37v
Copy link
Contributor

x37v commented Apr 11, 2023

@arokhsar This is interesting.. I'll have to look into it.

The key element seems to be that you have to have an index that corresponds in your script and plugin on first run, then after that, you can change either and run again and you can still trigger the drums.

It is an odd behavior and not ideal for development but it doesn't seem to be critical at least.. if you restart your editor the behavior should go away if you keep your indexes aligned?

@x37v x37v added the bug Something isn't working label Apr 11, 2023
@arokhsar
Copy link
Author

Thanks! I agree that it doesn't seem critical, and you are right -- if you restart the editor the behavior goes away.

@x37v
Copy link
Contributor

x37v commented Apr 14, 2023

I'll hunt this down and fix it at some point but I'm happy it isn't making things unusable in the mean time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants