JSE - Sound Stress Test

-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0\|52\|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Off Topic -> JSE - Sound Stress Test
Mon, 30 Dec 2024, 06:41
Jayenkai	JSE - Sound Stress Test Been fiddling with "Sound" functionality for the past few days. Vague explanation of the functionality > Reveal 🔎 It's not exact yet, so though you can happily play with it, don't lock down anything, because I might tweak how it sounds/works in the next short while. Currently the commands work like so.. NewSound "Sound Name" SoundTone "Sound Name","wave type",Start Frequency, End Frequency, length of event, "event parameters" where "wave type" = sine, sawtooth, square, triangle, noise, or brown and "event type" = Step : Makes the sound step from Start to End Ramp : Makes the sound ramp smoothly Loop : Causes the sound to loop between Start and End Repeat : Takes the distance between Start and End and repeatedly adds (or subtracts) it until the sound ends. Jump : Ramps from Start to End, then Steps back down. Drop : Jumps from Start to End, then Steps back down. (I think.. Or are those two the other way round?!) and also Time : Changes the length of event to being in seconds (otherwise it's 0.0-1.0 based on the length of the sound .. I couldn't think of a snappy name for that. Suggestions welcome) You should \| those together, eg "step\|loop\|time" or "ramp\|repeat" Next up is the SoundEnv command, which currently only does ADSR values. SoundEnv "Sound Name", Attack, Decay, Sustain, Release Attack = time in seconds that the sound should take to ramp from 0 to full Decay = time in seconds that it then takes to reach the Sustain volume Sustain = 0.0-1.0 volume Release = time in seconds that it then takes until the volume reaches 0 And then, of course, there's a Sound command. Sound "Sound Name", pitch (0.5 to about 4'ish), volume (0 to 1), pan (-1 to 1) ... That sound complicated enough for ya?! Stress Test I've written a quick stress tester. The engine "should" be pretty OK with it, but I'd like everyone to give it a whirl and let me know how it does. On my MacBook, the FPS is fine, and I'm getting the %age value up as high as 12%. On the Quest 3, the FPS is still fine, but the %age is hitting about 30%. > Reveal 🔎 Of course, that's with it doing 21 sounds per frame, and in real gameplay situations that "should" probably be a little less! It's also "blowing out" the audio buffer a bit, due to there being so many sounds being played simultaneously, all over the top of each other, so I need to find a way to avoid that. I really do need to do a lot of tweaks to this engine!! But ... For sanity's sake, can we all give it a go, and let me know how your system copes with it. Hold K for a bit, (maybe hold your ears, too!) and watch the lower of the two values. (and the FPS, if that drops!) Gimme a nice average for the lower number. Maybe even a peak value if you can catch it. If you can, you can test the sound function here Ta all -=-=- ''Load, Next List!''
Mon, 30 Dec 2024, 08:05
Dan	All test ran fine but one: Holding the V button (gamepad.x) on the keyboard, the sound starts, but then it stops abruptly. It takes a while before the other sounds can be played again (after it stops), and it can be fastened by switching the (chrome) tabs Here is the audial representation of what is happening: File.io file sharing the link expires in 2~3 days.
Mon, 30 Dec 2024, 08:12
Jayenkai	Yeah, that's the audio buffer being overloaded. I need to find a way to avoid that. But the code's still slaving away in the background, so it's good to know it's running full speed -=-=- ''Load, Next List!''
Mon, 30 Dec 2024, 09:50
Krakatomato	Pretty much always 63 / 0 on the M4Pro. It blips up to 6 and I think I may have seen a 12? Not sure. Top number never changes
Tue, 31 Dec 2024, 05:36
Jayenkai	Had to faff about with extra audio "nodes". It was the constant creation+deletion of the nodes that was causing the audio-glitches. I thought I'd blown out the audiobuffer, but that wasn't the case. So, instead I've made some permanent nodes for output, and hopefully that should help alleviate the "cut out" issue. Here's the Newer Version of the Sound Stress Test. It now plays an MP3, and a JMTrackr file in the background, as well as adding panning and mixing in some "normal" audio, too. Honestly, turn your volume down before starting this one!!! (but loud enough that you can still hear it) Importantly I'm after that "blackout" thing. If you see that, let me know. The FPS and Stress%age should be pretty stable, I think. -=-=- ''Load, Next List!''
Tue, 31 Dec 2024, 08:07
Dan	So far it is running ok on my windows (chromealike) web browser.