Magic Music Visuals

Using an ISF module for that is a waste of processing and memory. Even if the image isn’t being modified, it’s still being copied. Hmmm, seen several of these over time, trying to collect all the info. Is this as opposed to the RotateVector module? When seen previously I took away the processing wo...

Another thing you can do is make an ISF module called Annotation (or some such) that just passes through the input. The cool thing is you can disable the Show Param For both Bypass and Power, and just have a block with some text: annotationblock.png I've made a file called : Annotation.fx and added ...

You can also make an ISF that does nothing at all to achieve this, then it's named appropriately as well. In my case, I've created a file called StayConnected.fs with the following "code" /*{ "INPUTS": [ { "NAME": "inputImage", "TYPE": "image&qu...

Hello, Appears to be a bug in renaming globals in a specific situation - If there are 2 globals named such that one is a subset of the other, then a name change will incorrectly rename the longer one in expressions, e.g. global: "clock" global: "clockLength" an expression somewhe...

I remembered something in passing on the ISF.video site, here's a link for lightning items:

https://editor.isf.video/shaders?q=ligt ... vate=false

If an ISF module is connected, it does create at least one image buffer even if the Bypass parameter is selected (which is different than if the Bypass button is on). The module which uses the least resources is the InputSelector, because it does nothing except route the chain. good to know, thanks.

I think I found a solution for this. Eric just sent me in this direction for something else that I'm trying to solve and that got me thinking about some interesting approaches. TL;DR See attached diagram and follow steps * Duplicate the effect module you want to apply. Ensure effect settings are the...

I wanted this same thing. While it's being developed, a couple ideas that helped me achieve this effect. Use a simple module with no options like Antialias or Depth Test. You can then check Bypass and hide Power checkbox by unchecking Show Param For -> Power. You can't hide Bypass because the module...

First of all, thank you for the notes, I understand the need to reinforce using globals in expressions as this is very powerful. :D I am using expressions with globals extensively, I don't think it solves this problem. Hold will hold for a specific period of time, according to the number in the box....

If you read the User's Guide, you'll see that Globals can be used in Expressions It is quite the expansive document and in general help information in both the guide and the interface is TOP NOTCH, and for that I am very very grateful. :) I reference it often, and I use globals in expressions all t...

As it appears, modifiers like Hold, Average, Smooth, that take in a value from the previous modifier and apply change over time can have their value modified by midi or osc (Learn Param...), but have no way to be modified by a global value. Is that possible?

ok, good question - this actually takes me to several larger problem. I would really like to kick off a sequence based on an event. i.e. a button push starts a ramp from 0 and something happens on that movement. I know we can ctrl-e, but can't make that happen with MIDI, and I don't want to force it...

thank you.

My goal is not to scale something with translate, I am moving things around the camera in 3d space, and was just wondering. New to this sort of thing, so I'm gathering the clip plane is set at that Z value? Or in my thought process, 0,0,0 in 3d space is centered and 2.3142 away from the camera?

It appears that Magic MIDI and OSC inputs to scene modules and globals can detect a current value of a parameter, but I cannot find a way to detect that the same value was sent again. e.g. a continuous controller for a knob sending 0x01 over and over as it continues to be turned in one direction. Or...

When translating on the Z axis, with no other transformations, 2.3142 -> 2.3143 is the magic number that puts the input "behind" the camera (assuming it is a 2d input). Does that number represent something interesting about the camera or Magic settings? I considered it might be related to ...