Hello,
In front I would apologise for my English. I'm living in the Netherlands and my English was often not so good. So for that I would apologise.
Here's my problem,
I'm working for a sound and light compagny in the netherlands and we have 2 pearl 2008 lightconsoles.
1 works fine and I don't have any problems with it.
I'm very statisfied the way it works.
But the other on has a problem, and I can't solve it out.
The problem is that I can start a chase by pulling up the fader.
But when I start a second chase, both chases stop working and the stop led blinks on.
Well at first I thougt that the pearl might be in theare stack programming modus.
So I started up the theatre stack programming and closed it.
Unfortunately the problem wasn't solved.
I've read the manual and saw there was a button called snap back.
I didn't understoot the meaning of it, but when I started 1 chase and hit the button twice, it started. but then I started the second chase and suddenly al the chases stopped working again and the stop button blinked on.
After testing in the program mode, i turned the key into run mode.
But then the chase wouldn't start at all in the normal mode, and in the take over mode it started after connecting it.
I looked inside edit times, but all parameters were normal.
Link = 0 fade in 1.0 fade out 1.0 etcetera.
At this moment I don't know what this problem could be.
We're thinking of a setting that is set wrong.
I've set the user settings to default several times but it didn't work neighter.
So if anybody knows what this problem might be, please react.
The software I'm currently running is v3.0.2 and the date is 1 jun 2006
Best regards,
Tymen Abels
Problem on a pearl 2008 desk
Moderator: Moderators
Hmm. Strange.
Firstly I would say that the software version sounds wrong. I could be mistaken but I don't know of any version (2008 or other) that would be v3.x. Latest software for 2008 is v1.1 available here: http://www.avolitesdownload.com/Downloads/Pearl2008.stm
You could compare this with the working console perhaps?
Similarly I would perform a hard wipeall (see manual) on the bad console and then save show from good console and load into bad. This will eliminate any programming issues. If the problem exists on only one console then it is either software version or faulty hardware.
If it looks like hardware or you want help installing new software then email service with serial no.
As an aside, 'snap back' is used to quickly return to previous chase step without timing. The main purpose for this is in a theatre stack situation (either theatre mode or unlinked chase) where you may have accidentally fired a cue too early and need to return to previous state.
Firstly I would say that the software version sounds wrong. I could be mistaken but I don't know of any version (2008 or other) that would be v3.x. Latest software for 2008 is v1.1 available here: http://www.avolitesdownload.com/Downloads/Pearl2008.stm
You could compare this with the working console perhaps?
Similarly I would perform a hard wipeall (see manual) on the bad console and then save show from good console and load into bad. This will eliminate any programming issues. If the problem exists on only one console then it is either software version or faulty hardware.
If it looks like hardware or you want help installing new software then email service with serial no.
As an aside, 'snap back' is used to quickly return to previous chase step without timing. The main purpose for this is in a theatre stack situation (either theatre mode or unlinked chase) where you may have accidentally fired a cue too early and need to return to previous state.
Well at first I made an mistake, because the versionnumber was from an other program I'm using on my laptop.
Per accident I wrote the wrong number, it was V1.0.
My apologise !
You're thinking that it might be an hardware failure?
Or is this an error that can occure by the software?
I couldn't sorted that out of your reaction.
It's probably that it can be a hardwarefailure.
Maybe per accident a short circuit on the mainprint.
I can try to do a hard wipeall and load a show from the good pearl.
Also I have to update the personallities but that wouldn't be a problem.
But I'm not in the oppurtunity to do that in a few days because of other appointments.
I would thank you for your reaction and I hope this wil solve this problem.
Best regards
Tymen Abels
Per accident I wrote the wrong number, it was V1.0.
My apologise !
You're thinking that it might be an hardware failure?
Or is this an error that can occure by the software?
I couldn't sorted that out of your reaction.
It's probably that it can be a hardwarefailure.
Maybe per accident a short circuit on the mainprint.
I can try to do a hard wipeall and load a show from the good pearl.
Also I have to update the personallities but that wouldn't be a problem.
But I'm not in the oppurtunity to do that in a few days because of other appointments.
I would thank you for your reaction and I hope this wil solve this problem.
Best regards
Tymen Abels
Personalities are stored in the showfiles, so you don't need to worry about updating unless that was a separate matter.
Using the same showfiles eliminates programming error. If the two consoles have the same software version and only one causes an issue then I would have to consider hardware fault or, perhaps, a problematic software install. If the two consoles have different versions then it is possible it is software related. It is always worth having the latest version in any case.
The problems you mention are certainly unusual. A chase not running when fired would just suggest it is unlinked and waits for [go]. But I can't think of a reason why it would make another chase stop. You can have linked copies of the same chase but then I'm fairly sure that if you alter the timing on one it will change on the other, so I would not think this was the reason. Using the same showfile removes these questions anyway. For sure, if there is a fault where running one chase stops another, then I think it is unique to yourself since it would be very obvious and everyone would have noticed!
Using the same showfiles eliminates programming error. If the two consoles have the same software version and only one causes an issue then I would have to consider hardware fault or, perhaps, a problematic software install. If the two consoles have different versions then it is possible it is software related. It is always worth having the latest version in any case.
The problems you mention are certainly unusual. A chase not running when fired would just suggest it is unlinked and waits for [go]. But I can't think of a reason why it would make another chase stop. You can have linked copies of the same chase but then I'm fairly sure that if you alter the timing on one it will change on the other, so I would not think this was the reason. Using the same showfile removes these questions anyway. For sure, if there is a fault where running one chase stops another, then I think it is unique to yourself since it would be very obvious and everyone would have noticed!
Who is online
Users browsing this forum: No registered users and 27 guests