Page 1 of 1

Pearl 2000 Programming error

Posted: 06 Oct 2009, 02:55
by Vfire77
Hey Folks, Im a bit of a newbie in the lighting world, I've been doing lights for a group of clubs and it's a kinda learn on your own type gig.

I have a little problem I was hoping someone could give me some tips.

I am trying to make my own page on the roller so I have taken some playbacks from another page, I pressed photocopy button before I moved them, I edited a few things in the playback and merged the memories.

The problem I am having is the when hitting the swop/Flash buttons some attributes do not get changed with the new program, ie the movement or color gets stuck from one memory to the next. Sometimes even the fixtures that I edited in the memory stay on when I pull down all the faders, I have to launch another memories from zero to get them off.

Any ideas why this might happen? I think the OS in not current.

Thanks

Adam

Posted: 06 Oct 2009, 13:40
by niclights
You need to understand HTP and LTP. As a general rule, intensities (dimmer) are HTP (highest takes precedence) and everything else (pan/tilt/colour) is LTP (latest takes precedence). Therefore for colour and positional attributes they are designed to remain until explicitly told to change.

Please have a read of the manual which will explain all this.

I also suggest you program from scratch in order to fully understand. It is more likely to confuse you trying to modify someone elses programming.

Posted: 08 Oct 2009, 23:34
by Vfire77
Ok Im not that new, I have read the quick start manual a few times already, I can't see what I described as being related to LTP and HTP, that should only make a difference with Dimming, not movements and colors. As soon as I move the next fader it should switch to new color and new movements.
Same with the swop buttons.

I program alot of my own stuff but was trying to use a few things I liked from the other guys...

I will have another read of the Section about LTP and HTP but I doubt that is the problem in it's entirety.

Posted: 09 Oct 2009, 00:41
by niclights
If it's only happening with flash/swop and not fader then it might be worth checking the cue mode (edit times). Something like mode2 could confuse matters.

Otherwise it would be useful to understand more exactly what is contained in the cues.