-
Notifications
You must be signed in to change notification settings - Fork 27
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
SoundEffect
fx value doesn't have an effect
#155
Comments
I had a play around with this. The Do we need to expose these "fx steps" and "fx param" parameters to Python? Or maybe give better defaults? (Or both). |
We can use the default values used by MakeCode, but if these are going to be the "unofficial defaults" and are not exposing them to the user, we should probably include them in CODAL instead. |
Reported in support ticket https://support.microbit.org/helpdesk/tickets/70448 (private) |
@dpgeorge because these settings are different depending on the type of CODAL doesn't have a way to set the same values as MakeCode without changing something in the CODAL API. We could either update CODAL to have something like an "effect factory", or maybe we could set up these fx-steps and fx-param values as macros defined in CODAL? |
Having simply a set of Then I guess we will not expose these fx-steps/fx-param values to the (Python) user, at least for now. They will be set automatically when the fx is set. |
Fixes issue #155. Signed-off-by: Damien George <[email protected]>
In 8d9067d I made it so that when the |
Once the PR #213 is merged, the macros can be included from lancaster-university/codal-microbit-v2@9a03c69 |
The above PR is merged and I think this issue can now be closed. |
No matter what the
fx
value is, it doesn't change the sound.We can see in this example code (also runnable in the Python Editor simulator), that the sound is the same in all cases.
fx_test.hex.zip
The text was updated successfully, but these errors were encountered: