XY x 4 Pad Project

[Neptune]

This is kinda cool. Comes out like the supermodulation in HGFs AlioNoctis.

[aliasant]

It is cool. I know =)

Here is my latest version. Its getting there.
Much nicer now but still some small things that needs fixing.

Have a look and test it properly.

Andrews Recable XY Pad 4.osm

(20.45 KiB) Downloaded 172 times

[aliasant]

OK. Version 6.

Getting better and better.

The Random works better now and only for dots that has P enabled ( are in Play mode)
If you want a dot or all of them to be affected by random, put them in Play mode and reset them some were.
The random is dependent on how many "steps" the dot had and if a dot is resetted it only has one step so a random
will give that step a new value. This also means that if a dot had a path built up by say 5 steps a click on the random will randomize those 5 steps and not add any more. This way you can control the random for each dot.


Also implemented Rate and Smooth controls for each dot. Both use a input value ranged 0-1


I still want to create the trail when recording moves and I still need to restrict / shrink the are for the dots a bit.

Andrews Recable XY Pad 6.osm

(19.36 KiB) Downloaded 154 times

[Andrew J]

EDIT - this was based on v5, will look at v6 in a tick...


Nice! A couple of comments:

- It's hard to tell which P icon to press when they're greyed out, you might need a colour cue to make it easier
- Do you really need to convert to sample rate for smoothing? Seeing as you're immediately going back to float, you can probably just do some sort of moving average. With a tick time of 25ms, the 40ms de-zip equates to (n+(n-1)*0.6)/1.6. Try out the module below...
- I didn't know that trick for array size (using an Int component to convert it), that's cool!
- I also hadn't checked the virtual key codes out, so I didn't know about 02 for RMouseDown (I was wondering how you got that to work)

-Andrew

Smoother.zip

(1.86 KiB) Downloaded 165 times

[aliasant]

[quote="Andrew J"]EDIT - this was based on v5, will look at v6 in a tick...


Nice! A couple of comments:

- It's hard to tell which P icon to press when they're greyed out, you might need a colour cue to make it easier
- Do you really need to convert to sample rate for smoothing? Seeing as you're immediately going back to float, you can probably just do some sort of moving average. With a tick time of 25ms, the 40ms de-zip equates to (n+(n-1)*0.6)/1.6. Try out the module below...
- I didn't know that trick for array size (using an Int component to convert it), that's cool!
- I also hadn't checked the virtual key codes out, so I didn't know about 02 for RMouseDown (I was wondering how you got that to work)

-Andrew

Nice to be able to teach someone like at least one thing hehehehe

About the smooth thing. I think using a float smooth gives a different result. At least the one I tested before.
I think the as soon as the input stops changing the smoothed output stops before it reached the same value as the input stopped at. What might be possible though is to use a simple lopass filter hopped?

About the P's. Yeah I know. I am not sure if they are any good. Maybe there is another way to do it.
Ideal would be for all the knobs and buttons to stay in their position when resizing the entire window.
Im not so good at that stuff so if someone else wants to fix that it would be great.

Was also thinking about having a R button. That would be Randomize individually for each dot.

BTW. I was just testing this in my vocoder and it is quite the bomb. So easy to use. However there are still stuff to do and bugs to fix but not that many I think.

[aliasant]

There is a serious bug that needs a fix.

If you turn down the Smooth to its minimum and start dragging you can see that the dot aint going from a to b but it is constantly fighting between 2 different values. This is why the more smoothing the less of this is seen or heard but it really needs a fix. I guess it is the "Last Changed" float that is getting new values into both inputs.

[Andrew J]

There is a serious bug that needs a fix.

If you turn down the Smooth to its minimum and start dragging you can see that the dot aint going from a to b but it is constantly fighting between 2 different values. This is why the more smoothing the less of this is seen or heard but it really needs a fix. I guess it is the "Last Changed" float that is getting new values into both inputs.

Your minimum smooth time has to be greater than the time between ticks, so set it to >=40msec

[aliasant]

There is a serious bug that needs a fix.

If you turn down the Smooth to its minimum and start dragging you can see that the dot aint going from a to b but it is constantly fighting between 2 different values. This is why the more smoothing the less of this is seen or heard but it really needs a fix. I guess it is the "Last Changed" float that is getting new values into both inputs.

You're minimum smooth time has to be greater than the time between ticks, so set it to >=40msec

OK. In my test version I changed the minimum from 20 to 40. Seems to work

Now. How do I make the area that the dots use a bit smaller so I get a frame around them for the buttons and stuff?

[Andrew J]

No - take a look at this version and see how I've added an inset which is used to reduce the span parameters and also as an offset which gets applied to the x/y coordinates in the transform module. Problem with this is that your dots are offcenter so it doesn't look quite right. I've put a white square behind each dot to show you the area you should stay within (you will need to tune your shifts and possibly the size parameter).

I've also put the float smoother in here, but hardwired to 2 samples (equivalent to 50msec with the dezippers). This means the smooth controls are redundant, so I removed them.

Lastly, I realised the redraws were very inefficient. So I've taken all the co-ordinate outputs and grouped them up, put them through one limiter and then sent that back to each of the dot RedrawAreas. This seems much smoother to me now.

Andrews Recable XY Pad 6 - AJ.osm

(18.55 KiB) Downloaded 163 times

[aliasant]

Superb. That works much better. And yes. ok. Ill give up the smoothers. This seems to work quite well.
And now I can fit in a R (random) button for each dot.
I also love this one because its so easy to put in more then the 4 dots.
Just copy and paste. Very sweet.
O btw. I was thinking about a Lock button for each dot. Everything is already in there. Just need to place the button and hook it up. What do you think? Overkill?

Now I need some rest from this.
A movie and some food.

[Andrew J]

O btw. I was thinking about a Lock button for each dot. Everything is already in there. Just need to place the button and hook it up. What do you think? Overkill?

I don't know, I don't need the record/playback for my stuff yet - I just wanted a surround panner. Still, this is working really nicely now, so I might have to dream up some other uses for it

EDIT: Only just had a play with the rate control, that resampling idea is pretty nifty!

[aliasant]

EDIT: Only just had a play with the rate control, that resampling idea is pretty nifty!

Lol. Was that you saying: Hey Martin.... Sometimes you actually produce some good shit!




I just tried to add a 5th dot and then realized the a square only has 4 corners. Never realized that before................

LOL
So to place each dot in a corner isnt very practical with more then 4 dots..

Maybe the controls could be on the side or above/under the XY instead?

[Andrew J]

EDIT: Only just had a play with the rate control, that resampling idea is pretty nifty!

Lol. Was that you saying: Hey Martin.... Sometimes you actually produce some good shit!

What? I can't believe I haven't told you that before - sometimes you produce some good shit Martin!

I just tried to add a 5th dot and then realized the a square only has 4 corners. Never realized that before................

Oh dear, I take back every nice thing I ever said about you

Enjoy your movie, I'm going back to bed :yawn:

[MyCo]

Isn't it better to implement the movement directly in streams? And then use Mono2Float or Poly2Graph to display the dots? For me it doesn't make sense to use this, when your automations are not accurate.

[aliasant]

Isn't it better to implement the movement directly in streams? And then use Mono2Float or Poly2Graph to display the dots? For me it doesn't make sense to use this, when your automations are not accurate.

I dunno?
Show us?