Reactive Volume
See original GitHub issueReactive Playback-Rate works perfectly fine.
The reactive volume should work too, since it uses the same watcher and is updated/set the same way as the playbackRate, I do however get following error
Uncaught (in promise) TypeError: AudioParam.setValueAtTime: Argument 1 is not a finite floating-point value.
The error occurs right on load, I can’t even update the volume ref.
const volume = ref(0.5);
const [press] = useSound(buttonPress, {volume})
I don’t see what’s the difference between the playbackRate value and the volume value, and I haven’t looked into this further yet, so I don’t know what’s causing this error.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Reactivate a mirrored volume - Veritas SORT
In most cases, Reactivate Disk will bring the disk online and all of the volumes will be healthy. Note: Dynamic disks belonging to...
Read more >Troubleshooting Disk Management | Microsoft Learn
Disk shown as online with a healthy volume ... Solution: If the I/O errors are temporary, reactivate the disk to return it to...
Read more >the reactive field volume model vs. the - apparent size model1
the reactive field volume model (RFVM) and the apparent size model (ASM), have been found to yield similar dietary predictions in many situations....
Read more >Reactivate the source volume - Product documentation - NetApp
Navigate to the source volume in the volumes page, and verify that the SnapMirror relationship you created is listed and the relationship state ......
Read more >Reactive and Functional Polymers Volume Four - Springer Link
This book presents an analysis on reactive and functional polymers which are manufactured with the aim of improving the performance of unmodified polymers ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah yes, the 1.1.1 fixes the problem! Awesome and thanks for the quick fix!
Hey @ericwaetke ;
I just added the example I told you about on my demo page.
https://vue-use-sound.netlify.app
It’s at the very bottom of the page, I hope you can fix your problem with my latest updates.
Don’t forget to update the vue-use-sound package, as I pushed 2 new versions today.
Can’t wait to see what you’ll build with it. 🤗