Well, I guess it's a good thing that there's no interest in this. It doesn't look like Vixen 3 is well suited for this. Apparently at the end of every sequence all zeros are sent to the channels. This could end up wreaking havoc on servo's. If this implementation changes I'll look into it again but until then I don't see the need.
There's a bit of a gap in that logic. Content comes from the sequence. But hardware control and interfacing comes from patching and display setup. If you want to limit the range of the values being output on a channel, you'd do that by placing a dimming curve on that channel.
Is the problem here the value of zero, or that there's an idle state that it goes to when not explicitly sent something else? In either case, a new filter could be created to define a different idle state.
I'm not yet familiar with 3D object suite. What would such a module have to offer and how would it apply to sequencing in vixen?
You're missing my point. You should be defining the idle position in display setup and not by expecting your last sequence command to be the last. (the appropriate filter doesn't exist yet, but it could) This is a function of the output section, not the sequence. So whenever vixen is not telling to do otherwise, it should do this. whatever values would make Eyes forward, brows relaxed, mouth closed would be this value.There are 2 cases that I see where this would be desirable. 1 animatronic and one regular lights...
1. Animatronic. On my porch I had a talking skull using a RenServo controller(and Vixen 2 at the time). If a 0 was sent at the end of each sequence it would have sent the head looking way to 'his' right instead of nicely looking forward.
This concept doesn't work within the vixen paradigm. You're making a very limiting assumption that only one sequence is working at a time, and only a sequence can cause an output to respond. That's simply not the case. Many things can feed into the elements at once. If you want the lights to be on, you need to tell them you want them to be on and what it means to be on. Maybe this is by looping a sequence in a schedule, maybe it's by using the web API to set channels on, but in any case, it doesn't assume. You need to tell it what you want it to be doing at all times.2. Lights. There are some times when people like to make their displays static for a period on time. My brother, for example, likes to leave the Christmas lights on overnight Christmas eve. At about 11:00 he changes them all white. In Vixen 2 he simply needs to run a couple second sequence and not have it end on a 0 so they stay in their last position. It's just a nice option to have.
XmasinVancouver
Re: Any interest? 3d object suite
3d object suite? Ported from where? Sorry, curious about this functionality
Unfortunately I haven't checked out Vixen 3 in awhile but I do remember that there were plans on handling servo controllers, etc. Having said that, as of the last time I did look at Vixen 3, it would give a graphical representation of your animatronics, allow you to manipulate that in real time and record the movements. Instead of dealing with a grid(I'm not sure what it's called in Vixen 3) to manipulate your object you can manipulate a 3d representation of it instead. It was a huge time saver in Vixen 2.xI'm not yet familiar with 3D object suite. What would such a module have to offer and how would it apply to sequencing in vixen?