-
Notifications
You must be signed in to change notification settings - Fork 57
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
AudioContext started to soon #11
Comments
I can confirm the issue, it's related to this package we use that is actually archived and I guess outdated.. I will find a possible substitution. Edit: @lidio601 can you help me with this? i'm not familiar with tonejs |
this package can be used instead, to reduce the amount of code and make it work on all browsers |
DescriptionI am using this Component in Nuxt.js.It working Perfectly.But it will gives autoplay warning always, Steps to reproduceTone.js Autoplay Policy issue ResultsExpectedRecord Audoi from web through Nuxt.js Actualfunctionally working but it rise warnings exponentially Error outputAdditional Informationpls fix this issue or other wise give the alternate solution for that versionsvue-record"@codekraft-studio/vue-record": "0.0.3" Tone.jsTone.js v13.8.25 browsersChrome Version 81.0.4044.122 (Official Build) (64-bit) |
version - 0.0.3 |
Hello Everyone, facing the same issue here. When do you think you guys can fix it? Is there a workaround in place? I found this StacKOverflow article which might be useful in resolving the issue. |
I have the solution in a fork with this proyect. |
Was anyone able to solve this its running and I think consuming memory too ? @LuisDavidPadron @SergejSi |
did you find anything on this ? |
any solution guys? |
#30 duplicate issue |
Tonejs/Tone.js#341 also it might help you |
@derakhshanfar i have started to live this issue thanks for letting me know can you pinpoint which was the thing that solved it there are too much stuff in the thread you shared would appreciated if you can just post the snippet or process that solved it |
Any change we can only run connection to the audio context during mount of the component?
The text was updated successfully, but these errors were encountered: