User Details

Username: spasmoid
Website: None provided
Facebook: None provided
Twitter: None provided
Soundcloud: None provided
Account Status: enabled
Member since: Jul 18 2013
About spasmoid:
(report this profile)

Devices by spasmoid

No devices have been posted by this user.


Comments by spasmoid

Comments

You might want to consider greatly increasing your top speed :)

Can you imagine a dance song with a riser that exponentially increases the speed of an animated sound element until it becomes perceived OMNIPRESENT ;)

Might even have an interesting phasing effect for the given listening environment.

Yes I know. This could be the beginning of something awful :P

AWESOME PLUGIN. Just what I needed!

I was achiveing circular animation with this setup.
http://wwhub.s3.amazonaws.com/Ableton_surround_template_XY-Send-Nodes.png

And you can animate interesting chapes by setting different rates between the two LFOs and altering the Phase.

However it does suffer from sharing the "Knob" POSITION variables in global space. This means that if you have two instances of the device, they both fight to update the same coordinates as the knob position is animated. Effectively limiting you to one XY Send Nodes device per set.

Someone needs to find a way to move the X and Y position variables into the scope of the device instance. Whilst I have experience as a programmer, I am a straight up n00b with Max so I have no idea. I need to start learning this thing.

anyway, there it is. We're limited to only using 1 per set if we want to animate.

Krisloop. This is fantastic. 5 stars. I really have to learn how to make my own devices. I just started looking at this stuff today.

Up until your mod, I was achiveing circular animation with this setup.
http://wwhub.s3.amazonaws.com/Ableton_surround_template_XY-Send-Nodes.png

And you can animate interesting chapes by setting different rates between the two LFOs and altering the Phase.

You mod is a lot simpler.

Both versions suffer from sharing the "Knob" POSITION variables in global space. This means that if you have two instances of the device, they both fight to update the same coordinates as the knob position is animated. Effectively limiting you to one XY Send Nodes device per set.

Someone needs to find a way to move the X and Y position variables into the scope of the device instance. Whilst I have experience as a programmer, I am a straight up n00b with Max so I have no idea. I need to start learning this thing.

anyway, there it is. We're limited to only using 1 per set if we want to animate.