this is seriously the best wallpaper i have found in a while, any way there could be an option to seperate the wave in 3 EQ lines? like high mid and low? would love to see the 3 bands individually.

Best wallpaper! love it, take seven different awards. You deserve it

@Ambatukam Correct. This is a wallpaper :) Not an asset to make wallpapers.

oh wait its a wallpaper and not a particle i can use in the assets?

@Ambatukam Only other thing I can think of is that your view in the wallpaper browser is filtered and as a result hiding this wallpaper for whatever reason. Or maybe unsubscribe and resubscribe to the wallpaper. But I am just guessing.

I would suggest asking in the WE community forum directly as subscribing to a workshop item and the possible problems with that are beyond my knowledge. I just made the wallpaper, but I did not write WE or Steam. So I can only guess at why you might not see the wallpaper.

doesnt work man

@Ambatukam I am not sure what could do that but my guess would be to try and restart wallpaper engine and check if it shows then.

i subscribed but its not showing in my assets

It is possible though I didn't start implementing the slideshow backgrounds until newer wallpapers. However I am not longer actively working on them and just providing support. So I'm not adding new features anymore, sorry..

I only have one single request. Instead of a single background image, I'd like to set up a folder, and have it cycle through the pictures. I don't know if this is possible.

Otherwise, I love this wallpaper! :)

can you define frequency range with value in hertz for your low mid and high colors.
your wallpapers are amazing
9mn safety always off

@DexterRiley I would suggest using the wallpaper browser. If you select this wallpaper and scroll down in the settings on the right, at the bottom you will find a bunch of buttons, one is "Browse Presets". You can find 16 examples of presets that way. Hope that helps.

Anybody have a good group of settings for how it looks best?

@Milez5858 The reason is very simple. I don't have any compatible hardware to test/develop with.

Dude.. you have many nice visualizations, but none of them have LED integration. Is it much work to add?

好看(～o￣3￣)～

What do you mean? You subscribe and then select it in wallpaper engine.. Thats the normal way to set this as your background.

So how do I set this as my background?
what file is it under?

nice！！！！

Nice!

Thank you mate!
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=849094640

@qwe14789cn .. fixed :) was left it by accident

我就看看。。。。

I think clean up the fps on the top-left is much more better

Sounds easy enough, and would be a nice option for the VU meter wallpaper too. But it wont be in the next update. Gotta take some time to update some wallpapers and want to finish the features I wanted first for this one first. But it should be easy enough to add. In due time.

ong suggest,use a folder for background.image so that image auto change after a predetermined time.

so great.thanks for creating

@Bioharard, where can I find this file? I'll also create a dicussion thread on this to prevent further cluttering here.

I'm still subscribed here since I replied earlier (btw, Workshop items also have a discussions section but I think people usually miss it - mentioning it since there was talk about removing comments due to clutter before).

I think WebGL issues should output errors to debug.log, so maybe you could check that for something useful?

Right now it really suggests WebGL context could not be created for whatever reason. It is exactly the line in threejs that is trying to create the webgl context from the canvas thats failing. If it didnt find the canvas element we would get a different error. It if was related to the settings/options I've giving it, it should also give a different error.

But I will search more in the weekend, as it is weird that others would work and this one fails. As you are the first to mention it, and the function the code fails on, it seems chromium is failing for some reason and would be something outside of my powers. But I will see if I can find anything that can help figure out what it is before bugging Bio with a bug report.

Yeah, it stops the initialisation and further execution at the moment, no reason to continue if it fails anyway. But that is why those elements are not hidden, most for my testing/debugging purposes. But great. I will look into it :) I have an idea where to look now.

If I had to guess I'm missing a dependency somewhere, but it doesn't seem to be WebGL since other pages using WebGL load just fine. Perhaps there is a more specific component missing?

Update: There is a new error now. It also shows three coloured boxes with FPS, MS and MB (but with nothing in the boxes though) and a white/greyish box in the top-right. The new error is as follows:
Object.wallpaper (wallpaper.js:68:11): TypeError: Cannot read property 'getExtension' of null
at Object.get (three.js:19292:21)
at new WebGLRenderer (three.js:19725:14)
at Object.init (waveRenderer.js:42:19)
at Object.waveRenderer (waveRenderer.js:16:7)
at Object.init (index.html:982:26)
at Object.onInit (index.html:1413:30)
at Object.init (wallpaper.js:111:10)
at Object.wallpaper (wallpaper.js:64:8)
at window.onload (index.html:1406:11)
new WebGLRenderer (three.js:19719:12): THREE.WebGLRenderer: Error creating WebGL context.
new WebGLRenderer (three.js:19502:11): 82
new WebGLRenderer (three.js:19502): Three.WebGlRenderer
log.js:131:14: log started

Sure thing, no rush :) Just hope it shows an error. Will look more during the weekend. I must of overlooked something but dont see what so fast.

@Squee I'll check once it updates. As of right now it still shows the old error, I'll check if I notice WE updating its workshop content.

@Chairman Meow . I just uploaded an update that will stop if initialization failed and hopefully report an error. Changed one line that I could see that might cause a problem. Could you check if it help or maybe if it generates a new error? Will take steam a bit before it updates.

Thnx for reporting it. It sounds like the initialization failed for some reason, which would explain why the object was not created. Will see if I can reproduce it or see what might be causing the failure.

Crashes for me with the following error:
Object.animationLoop (wallpaper.js:335:13): TypeError: Cannot read property 'wave1' of null
at Object.render (index.html:1050:55)
at Object.onRender (index.html:1405:52)
at Object.animationLoop (wallpaper.js:332:10)
at wallpaper.js:296:51

Restarting wallpaper engine or the PC does not fix it.

I'd say just leave them, then they know what I am replying too or they might think I'm crazy ..

Thanks, i'll try it when I'm free, comment back when I'm done. Also shall I delete previous comments or allow them to be visible for others as reference?

Answer Part 2:

The swing ( the up/down movement of the wave shaped in the last one ) controlled by the "stereo oscillation" option, but is very dependent on your audiosource as its determined by if sound is more on the left channel or right channel. Raise it a bit if you want. More audio on the left channel, wave goes down, more audio on the right channel, wave goes up.

The stereo options are very dependent on your audio source, as that waveshape will not happen if the source is mono and it will remain flat.

Hope that explains some thing to get your desired effect. I think those are the settings you are looking for. Let me know if ya manage.

Answer Part 1:
The last has a very short time span. Bring down the display history values to a very low setting.. If you do that, you might also want to set the Height option fairly low.

If you will notice that on the last one the 3 colored bars are about the same height. You can do this by changing the normalization to "per channel". If you set that to "Normalize" then one channel might peak out above the others.

Also if you notice that the last one ( compared to the 3rd screenshot ) doesn't have the 3 waves mixed together ( not overlapping like the 3rd screenshot ) but follow their own path. You can do that by changing the stereo seperation to "per channel".

1,3,last? mine just seems like the normal wave pattern from soundcloud? am i doing anything wrong ? cuz i think mine is almost identical to the default preset

Which screenshot did you want it too look like?

could u tell me ur settings?
doesnt at all look like the screenshots on my end;(

Hell yeah! Great work again!

Already noticed some improvements with settings while testing, had a lot less resetting to do when sorting items. And presets would be awesome.

Cheers, seems fixed. I did some testing with your options before and nothing seemed to have made refreshing/vsync perfect. Maybe this will get better the next time I update CEF, but it doesn't seem to be perfect yet in Chrome itself.

I also have some small property improvements coming up, e.g. resetting won't be necessary anymore. I will probably look into presets some time after the next patch since they'd be pretty useful for your wallpapers for sure, being able to distribute some stock ones and users being able to save their own presets too.

Fixed the cutoff. Also removed my setTimeout solution ( still using requestAnimationFrame for the main loop ) as after further testing I have no proof it fixed the microstuttering. No need to make it more complex I guess, but as worth a try :)

First one used setTimeout to maintain the most stable update times, as with the frame limiter the frame intervals were a lot less stable. But after removing the frame limiting code, i noticed it didnt matter anymore in that situation, so using requestAnimationFrame now in the hopes its better.

My last trick of last night was to directly return from the rendering loop, and delay the actual updating of the canvas with a setTimeout, in the hopes of having the browser render the canvas and update the dom behind the scenes between frames so when the next requestAnimationFrame even is triggered, the html and canvas are hopefully already updated. Felt like it helped a bit on my end, but have no hard evidence its better, or thats how webkit works.