Viewing a single comment thread. View all comments

elrugmunchero t1_ir9g3qr wrote

Chrome seems to handle my webAudio stuff better than Firefox, last time I checked Firefox wouldn't handle detune more than 100 cents, I'm not actually sure what the correct behaviour is, but it was annoying to calculate the playbackrate myself, and it works in Chrome

1

ImDrewpy OP t1_ir9iygg wrote

yeah the WebAudioAPI has been a pain for me no matter where its used. but the performance issues are certainly worse on Chrome (or atleast, for me, more reproducable)

2

elrugmunchero t1_ir9jkuk wrote

I'm making a midi-powered FM synth, On firefox it works for a while, but starts to use more and more cpu over time until the fan's running full tilt and it starts missing notes. Thing is, you can stop the synth, javascript debugger thing shows nothing is running, but I cant even watch youtube cause my cpu's getting chewed to fuck by nothing. I wanna use the synth for megadrive sounding game audio, so this obviously can't fly. Chrome handles it just fine, alongside my half-built asteroids clone

1