Ignore sampleRate
See original GitHub issueWhen I use methods captureException
and captureMessage
, I don’t have the ability to ignore the sampleRate
option. Is it possible to implement this?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Javascript: sample rate ignored on constructing an AudioContext
gives a sample rate of 48000 samples, while I want it to be running at 44 Khz? Chrome 71.0.3578.98, mac os 10.14.2. Reference: ......
Read more >MediaTrackConstraints.sampleRate - Web APIs | MDN
The MediaTrackConstraints dictionary's sampleRate property is a ConstrainULong describing the requested or mandatory constraints placed upon ...
Read more >Sampling for JavaScript - Sentry Documentation
It can choose to keep or ignore any parent sampling decision, or use the sampling context data to make its own decision or...
Read more >sampleRate | Apple Developer Documentation
Instance Property. sampleRate. The current audio sample rate, in hertz. iOS 6.0+ iPadOS 6.0+ Mac Catalyst 13.1+ tvOS 9.0+ watchOS 2.0+. Declaration.
Read more >Input sampling rate does not match the output? - scsynth
ERROR: Input sample rate is 88200, but output is 44100. Mismatched sample rates are not supported. To disable input, set the number of...
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
There is no alternative solution to what Daniel already mentioned above:
On the other side, I can definitely see a scenario, where global handlers should be set to let’s say 20% sample rate, as one may have a pretty crowded site, but they’d want to make sure that
captureException
from on their payment component will always reach our servers. Right now there’s no way to achieve that.