matkeane Posted September 14, 2015 Report Share Posted September 14, 2015 Hi, I've been experimenting with external control of Watchout cues using setInput. Setting the tween time with the third parameter works fine, except that the movement is linear, with no easing, which looks a bit harsh. I don't suppose there's a hidden 4th parameter that enables ease-in-out? I have been playing with sending position data from an external app to try and achieve a smoother move with easing. First by trying to update the generic input used for position at 60fps. This works pretty well with one layer but, as predicted by Mike Fahl in this post - http://forum.dataton.com/topic/1262-interactive-inputs-are-freezing-up-watchout/ -once you start sending updates to a few more layers, things slow down and eventually crash. My next approach was to split the move into segments, and send setInput commands every few frames with a tween time, to try and approximate an easing curve while sending fewer network commands. This works a bit better, in that things don't lag as badly, but the change in speed between segments is noticeable. Even using this approach, and staggering the network commands, once I had 10 layers moving around, things got pretty slow again. So a couple of questions: Is the slow-down when moving multiple layers due to overhead in the network protocol? If I use a midi controller and link the sliders and knobs to Watchout cues, I don't notice the same slowdown. Rather than using a generic input, would I be able to achieve smooth changes without bogging down Watchout by sending Midi updates through a virtual midi interface? Thanks for any ideas... Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.