| Home | News | Products | Support | Download | Sales | library | Guests | Contact | WebCam | Links | |
 |
LanBox-Talk mail archive |
| By date: Prev | Next | Index | By thread: Prev | Next | Index | ||||||
First of all thank you very much your prompt feedback. > Keep in mind that scene 5.3 (show d03 for 1.0s) will still > overwrite channel > 1 every three seconds. That is no problem. It's the motor speed for changing colors. And I like speed whe it comes to processing ;-) > > What I don't understand is that if I have some value in > channel 5 step iii) > > correctly overwrites it (engine B has higher priority) but > when it returns > > it doesn't restore the previous value. (?) I thought the > channel would just > > temporarily be overwritten.... > > The problem here is that list 5, after starting 10.1 in > engine B, ends. This > means that engine C returns to 5.0 and clears all channels. > That's why, when > engine B is done, the channel don't return to their original values. > You can fix the problem by appending "hold for ever" to cuelist 5. mmmh. I tried that but to no avail. Is it possible that values set over TCP/IP do not belong to a scene and that therefore they are not embedded in the layer's priority scheme ? But I actually set 5[255] in 5.1 I may have a workaround: script 10 calls a scene to set DMX 5 to 255 before exiting. Channel 5 ist the dimmer in the CMY lamp that I use. > > BTW, what you're doing here is quite complex.. I wonder, what > are you making? :) I'm doing the programming for an art project here in Basle, where we have to control light color in relation to the day of the year and "internet activity".... I can forward you to a describing web site when it will be online - I guess je verstaat duits... ;-) Now. A lamp array will be on a silo where sometimes worker have to enter... And when they switch the room's light on, the lamp has to shut down. That's why I trigger a scene change (DMX 5 is the dimmer which then gets set to dark) over the I/O port. When the people switch the light off - that will usually be after a while - the dimmer gets restored to his previous state. But I think it's not so tragic to set the dimmer to 255 since there has been a break in the color sequence anyway, nobody will notice. On our server I've written a few perl scripts that do the translation from proxy's statistics to HSI-Colors and again to RGB and CMY(K).... I you're interested - I've written another simple script that works as a HTML front end to Lanbox's telnet interface. I give it to you under a GNU license ;-) Ok. Thank you again. May be you know a better solution - I can live with this one. Cheers Philipp
| |||||||
| By date: Prev | Next | Index | By thread: Prev | Next | Index | ||||||