4 ms·
I checked out the solution on github, but my results were not like advertised in the video. On my laptop it sounded like a dying cat of some sort.
by cessor 12y ago
I checked out the solution on github, but my results were not like advertised in the video. On my laptop it sounded like a dying cat of some sort.
- zulko 12y agoStrange. Even with headphones ?
- exDM69 12y agoIt would be more helpful if you could describe the results more accurately. The most common reasons in audio problems I've found are mismatching sample rates and a failure to meet the deadline of the audio interrupt, causing choppy or distorted audio. A mismatched audio format (ie. number of channels or bits per sample) might also cause problems. Also, knowing what OS/Audio api backend is being used is vital information for debugging.
- cessor 12y agoYou are right, feedback should contain constructive comments, but I couldn't be bothered to go into further details when I wrote my response. Here is a short video that I made showing what it really sounds like on my machine: https://vimeo.com/97857232 https://vimeo.com/97857232 I can't affort to "nerd into" the actual problem right now. Hence the whitty and non constructive comment. Apologies.
- exDM69 12y agoThat's either wrong sample rate or missing the deadline for the audio callback. My guess is the former.
- Marazan 12y agoI get exactly the same effect EDIT: Looking into it further, I get that effect just loading up the provided .wav (which sounds fine in any media play) and not doing any processing on it, just trying to play it straight up. EDIT AGAIN: Got it, the very low buffer size of 100 is casuing the problem. Using the default size and everything is working like a charm