Eric wrote:... I will have a look when I get a chance.
Thanks Eric! This shader is particularly interesting with its built-in DSP audio filtering. It will be great if that's possible in Magic.
Eric wrote:Shouldn't your AudioToImage module have Spectrum selected, not Waveform? Maybe not, I dunno.
It's definitely AudioToImage Waveform for all oscilloscope-like shaders, although it can sometimes give interesting effects if the "wrong" setting or a combination is used.
I had it in ISF Editor and started making some code corrections to the point where there are no compiler errors.
But the ISF Editor just sits there with a black render screen.
Is there a "compile" or "start" button ?
Alternatively is there a modern way in 2025 (last post here 2019) to convert from Shadertoy ?
I've been trying to solve this for years and its always the mouse and ichannels or whatever, blah blag blah. It looks like its well understood what the problem is yet every single shadertoy importer or convertor I've used fails miserably at this task. Even A.I's fail to fix the shader code.
Do I have to join some arcane shader cult or something ?
Hi there, i came almost for the same, a little help translating, so, i have this shadertoy https://www.shadertoy.com/view/ft2SWt which i want to convert, and happens something similar to me, ISF converter just gives me a black screen, can someone plz translate this shadertoy, so i can compare and see what my mistakes are? TIA
wrote:just gives me a black screen, can someone plz translate this shadertoy, so i can compare and see what my mistakes are
I had no problems and didn't have to touch a line of code.
Zeno's_dominoes_ft2SWt.fs
Hi Sadler, thanks a lot for your quick response... But im still getting a black screen in magic, i have tried in macbook pro 2012 13" Magic demo version 2.33, Osx Catalina 10.15.7 and Macmini M1 2020 Ventura 13.4 Magic full version 2.33 as well, and in ISFEditor it says there are some synthax errors, but even if i fix them im still getting black screen.
It would be interesting to know the nature of your syntax errors though, I say again, I had none (Windows 10). It's likely down to the GL implementation on Macs? Maybe mac graphics on the various macos versions don't support certain GL features that are supported on Nvidia drivers (I see 403 gl extensions) - I don't know as I have never used macs . That shader doesn't seem to be doing anything too funky but is heavy on the gpu - I barely get 60fps in magic with it on a mobile 2080.