It's definitely not a matter of intelligence or lack thereof, most people naturally tend to over complicatethings they don't immediately understand. This makes things unnecessarily difficult so they give up quickly.Really, the only thing you need is a strong interest, keep at it and give your brain time to make sense of it.Because thats all it is, you are failing to see that this is not so different from what you already know.People often perceive too great of a distance between light and sound, when in fact theyare nearly identical. Especially when it comes to describing them mathematically.

Its no accident that using a DAW to create music is very similar to using a video editor to create a film.

Well it is a long way from anything I've ever tried to do before and I'm time poor. But based on what you said I reinstalled the demo and will keep tinkering. Code for me is like my cat looking at a calculator. Hopefully I'm smarter than my cat but I'm not betting on it.

Is there a way to get audio into the standalone and if not what is the purpose of it?

This thing is the tits!! Is anybody else experiencing the following behavior:

Set up a region to loop while you teach yourself rudimentary GLSL, then when the loop starts over the step sequencers stop and won't move again until you rest the transport?

Especially since I'm teaching myself the coding, it would be ideal to just have a loop going while trying everything out.

Also is there a manual, with some very basics about the coding language and the way the plugin handles it? There are some potentially really cool things that I'd like to try out but I don't even know if they are possible in the context of the plugin. Also a simple list of the names "in the code" of all the buttons sliders and sequencer stuff. I've figured out most by trial and error, but that would seem like a handy reference for folks starting out with GLSL. Maybe pop up tips on each bit of the interface that say what it does, output range, proper way to reference in code etc.

Anyway. Love this thing. Can anybody point me toward the official bug reporting place for it? Is it on their website somewhere?

I don't think there is a manual as yet, I haven't seen one anyway. And yeah, the sequencer will not reset with a loop in your DAW, unless you set it to onset. Not sure if thats intendedor not. No specific, bug report avenue in place that I've noticed.

Anyway, here is one of the shaders from the GLSL Sandbox, hacked for Viz. Maybe interesting tosee what I very quickly changed. E.g. not much thought in the changes, nor have I explained them heh.I will when I got some time to think about making more meaningful changes, or just write a new one.It uses the parameters, slider 1 and seq1 so you can play with them. The audio amplitude changessome stuff as well. Its kinda neat.

plexuss wrote:Well here is my first attempt without knowing anything about what I was doing.

This is amazing plexuss! We're so happy to see users actually creating full videos with this thing. That's exactly what we intended. And great track by the way. We'll definitely post this on our channels.

There's currently not a great way to get audio into the standalone version. We're working on that feature- need to add proper routing. Personally I like to do everything in the DAW so the plugin probably got a bit more attention. We'll fix that. Adding Syphon/Spout support is also high on the list.

dreamvoid wrote:Questions - can't find answers about this on the Echobit web site: - are video export functions included? or streaming to disk?- if yes, are exports in 720p, 1080p possible? and in which formats?

Video export isn't currently supported. We usually use third party software to capture everything. We plan to add proper recording in the future, although personally I'd almost rather add Unity/Unreal Viz plugins first- speaking of, since the audio metrics and all interface parameters are output via OSC you could already theoretically build hooks into Jitter/Unity/Whatever and control that through Viz. I plan to make it so that even the shader programs are broadcast through OSC though that might not be useful considering you'd still need to pass uniforms and whatnot on the other end... Syphon might be the way to go for now. We're still considering what's possible and useful for the user so feedback is also welcome as we decide on these features. Thanks for all of the notes so far.

lnikj wrote:Any chance of this making it to VCVRack?

Ha! Possibly. I was actually planning to release a video where I'm playing with VCV and Viz. Through Unfiltered Audio we've released three VCV modules and have a few more in the pipeline (one rhymes with Joko) so I'm familiar with the format and believe Viz could work in that format.

Anyway, I just commented the code rather than explain it witha wall of text. ...-Cheers

Awesome shader! This thing looks great. Really happy to see that you guys are getting the workflow and what makes it unique- I'd also love to make a portal on our site so that it's fast to share presets and shader code. Ironically we could really use a web version exactly like shadertoy but with our variables and whatnot so that you could just demo these things in action... hopefully we'll get to that sooner than later.

Does the plugin pass on any clock information to the code? If the tempo and song position can be plugged into the code there are worlds of cool things that can be done. Also some definitions of what exactly variables like "time" actually mean so they can be properly utilized would be handy. I'm getting my head around lots of the simpler GLSL stuff and mangling my own pictures.

What is the deal with the step sequencers not resetting? Is this something that can be fixed or perhaps coded? Also this plugin is not saving its settings with a project in any of my hosts? Some simple "getting started" style documentation would be useful if they would explain how the file structure is meant to work and so forth. The coolest thing I've made is saved, but I can't figure out at all how to reload it and as I say the settings aren't properly recalled with the session. This is true in cubase 5, 8, 8 and Bitwig as well.

Yeah there seems to be some issues under windows at least. You have to place the frag files in the factory directory with the rest for them to work. Maybe try making a User directory, as I assume it’s supposed to make one but doesn’t. Anyway, the factory directory thing works, I haven’t tried making a user directory yet.