| 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 | ||||||
MisterJ wrote: I'll toy a bit with the idea with some more realistic examples (I have a show currently which I can "refactor") to see what it gives. Allright.. I'm refactoring my show a bit and I like this way of doing it.. I am taking (sometimes) a bit a different approach, which leaves me with a final question. In stead of doing (201.1 = some channels, 201.2 = zero values for those channels) -- cue 2 show 201.1 for ever, crossfading for 3s -- cue3 show 201.2 for 0.05s, crossfading for 3s (fade out channels of 201.1) show 202.1 for ever, crossfading for 3s (fade in some new channels) I sometimes do this -- cue 2 show 201.1 for ever, crossfading for 3s -- cue3 show 300.1 for 0.05s, crossfading for 3s (fade out all channels) show 202.1 for ever, crossfading for 3s (fade in some new channels) Here "300.1" is a total blackout. Thus not just the channels that were active in 201.1, but all the channels. I currently have no dimmers attached to my lanbox, so I can only look at the scene window and the dmx-output window to see the effect. The above approach could sometimes mean that I fade out some channel (during 0.05 seconds) and then fade it back in to its previous value. So this means there is a dip for that channel during 0.05 seconds. Two questions on this matter: - will this dip be noticable by the audience? I assume not, but I'm asking to be sure. I'm just using normal PC spots and other halogeen lamps.. - sometimes a "show for 0.00s" also seems to do the trick, but not always. What is the exact reason for using 0.05 and not 0.00? It seams like a "0.00" is sometimes ignored, and sometimes not... thanks again, Jan
| |||||||
| By date: Prev | Next | Index | By thread: Prev | Next | Index | ||||||