| 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 | ||||||
Hi there I noticed a behavior of the Lanbox which is not consistent with my understanding of the priority of the engines. Let's explain it in a simple way ;-) i) I start to show a scene in engine C with some channels set to some values. ii) From now on I continuously set channel values in the same engine via TCP/IP with *C9 03 ch# val [..] # (I hope 03 means engine C) iii) If I get a specified value on the I/O port, I jump to another cuelist in engine B which sets DMX channel 5 to 000 until the trigger on the I/O disappears iv) As soon as the script returns to engine C (go s#.st# in engine C), step ii) is valid again, that is, the values are set via TCP/IP 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.... Here the full scripts: ENGINE C (list 5) ======== show d01 for 1.0s 002: hold for 2.0s show d03 for 1.0s go 001 if input 8 within 0-512 go 002 001: go 10.1 in engine B :d01 1[255] 2[000] 3[000] 4[000] 5[255] 7[000] :d03 1[255] ENGINE B (list 10) ======== show d01 for 2.0s 002: go 001 if input 8 within 1000-1024 go 002 001: go 5.2 in engine C :d01 5[000] Any clue what it could be ? Thank you very much for your help Philipp
| |||||||
| By date: Prev | Next | Index | By thread: Prev | Next | Index | ||||||