Timing Problems

Hi all, I am having some timing issues in grasshopper.

Right now I am streaming data out of Grasshopper using UDP Sender - Ghowl.

The problem seems to be that the rate of any component that has a timer influences the rate that the data is sent via UDP Sender.

I am able to deal with this issue in most cases, but I am using the Firefly - Leap component and the Expire Timer (T) input does not seem to be working. It always pulses as fast as possible, even if I plug in a number.

I am not sure if there is a way to get the Leap component to respond to the time input better, or if there is a way to cut the time/pulse out of the data stream. I just want to control the rate that the UDP Sender sends data.

Any advice would be greatly appreciated. I am always trying to control time throughout my data stream and it would be great to find a way to modify the pulse downstream.

Kind Regards,

Jake

Replies to This Discussion

Permalink Reply by Luis Fraguada on March 26, 2014 at 3:25pm

You have more than one timer in your definition? the udp sender just sends when it gets new data. Without an example file it would be damn tough to help you.

Permalink Reply by Jake Newsum on March 26, 2014 at 4:16pm

I realize that the UDP sends when it gets new data.

What I am needing is something between the timed component and the UDP Sender. Ideally, I need a data dam that can be toggled by a parameter. This would allow me to 'time' the data dam to control the rate at which data is sent to and through the UDP Sender.

At a basic level, without the need for the timed data dam, I just need the Firefly Leap component to use the time interval that I am specifying.

Here is a basic example that shows the refresh rate of the Firefly Leap component. As I plug in different Expire Times, the refresh rate always appears to be the same.

Attachments:

leapTime.gh, 7 KB

Permalink Reply by Luis Fraguada on March 26, 2014 at 4:48pm

May i suggest you post to the Firefly group if you have not done so yet as it seems something that requires a Leap controller to work and unfortunately I do not have one. Is there any better operation with the Firefly UDP component (thought it does not seem the issue is in sending the data)?

Permalink Reply by Jake Newsum on March 26, 2014 at 5:06pm

The Ghowl and Firefly UDP Senders seem to work the same for my purposes. It would be great if one of them had a time interval input to regulate when it sends.

: )

I might try to write something in python to modulate time for me downstream. With the way python works in grasshopper, I haven't figured out a way to control the pulse. Even if I made the component only output data that was sampled every second, that data would still be pulsed repeatedly until the next second, thus sending repeated data at the speed of the leap... tricky.

The leap is just a stand in device to testing. I am really using the kinect which has similar pulsing issues. The kinect responds to its time input better than the leap, but I would still like to be able to control the rate that data is send through the UDP downstream.

Permalink Reply by Jake Newsum on March 26, 2014 at 5:31pm

"I might try to write something in python to modulate time for me downstream. With the way python works in grasshopper, I haven't figured out a way to control the pulse. Even if I made the component only output data that was sampled every second, that data would still be pulsed repeatedly until the next second, thus sending repeated data at the speed of the leap... tricky."

If anyone has ideas, advice, or knows of previous discussions that might help, please let me know. If I get anything working, I will post it back on here.

Kind Regards,

Jake

Permalink Reply by Jake Newsum on March 26, 2014 at 5:42pm

Well... I had not noticed that you can right click the data dam and set a timer. That is nifty. This will have to work for right now.

RSS