Pearl 2008 jerky motion occasionally

[Tumbleweed]

Sometimes, the console acts like it's not sending the pan/tilt fine commands... The file I'm using is at about 50% capacity, with 90% of the playbacks used. It's not doing this on individual fixtures (Mac 700 set to regular mode), it does this on all 8 of my spots (I haven't checked to see if it does it on our Mac 700 Washes)

Plus, it doesn't do it all the time, just when transitioning between certain playbacks. (specifically, Ia 4 and Ia 5) (Ia 5 is a 3 second fade to an audience blinder ov various heights with a gobo change, and the magenta flag goes it)


also, one weird thing... When transitioning to Ia 5 from most playbacks on that page, the fixtures will bump themselves down, then correct their position at the end of the 3 second fade. I deleted that playback, rewrote it, yet it does the same thing.

anyone have any ideas? (other than go fishing... the fish will throw it back, and I guess upgrading to Titan isn't in the cards for a 2008)

[niclights]

I doubt this has anything to do with 16bit or specific playbacks, unless it is a manual fade and therefore a faulty fader.

I find your description very confusing, but perhaps this is due to the amount of information in the console causing slowdown? 50% sounds very high, even with all playbacks used etc.

If you have a consistently repeatable example then try performing a wipeall, patch only the necessary fixtures and recreate the relevant cues.


Otherwise maybe you can try and give more details? Exactly what is patched/manual fading or not/are any of the affected cues in mode2/if you make linked copies of the repeatable playbacks does it still occur on the copies etc?

[Tumbleweed]

ok.. let's see...
Ia 4 is a mode 0 cue
Ia 5 is a Mode 1 cue

there's no linked copies of either cue (or of anything else on that page)


I might have to split this show into a few files, as i use this console at the house gig i have (I use another UK based console manufacturer's stuff for my road gigs). I may have found the memory limitation in this console....


Quick question- can a Titan running in classic mode run a 2008 file?

[niclights]

Did you try the wipeall test as suggested?

Making linked copies was also something for you to test to eliminate the specific playbacks.

You did not answer about what is patched. It is possible that the memory usage is due to a long history of fixtures being patched and then deleted.


Titan is the name of the new software. Classic is the name of the old.
A Pearl Expert running Classic will be compatible with your file.

[Tumbleweed]

the file I'm using does have a long history of having stuff patched and unpatched- mainly, extra LED stuff people bring, plus, there's a lot of conventional crap on universe A that I've been going through and deleting.

Currently, there are 48 channels of dimmers and one hazer on universe A, 8 Mac 700 profiles, 8 mac 700 washes, and 4 Atomic strobes on universe B.


I may totally redo everything- start with a fresh patch


About 1/3 of the playbacks are mode 2, another 2-3% are mode 1.


Fortunately, i don't have to deal with this for a while- nothing at the house gig needs my attention until mid February... lol

[niclights]

The reason for mentioning mode2 was only to determine if you were performing a manual fade on LTP values where the cue also contained timed fade information. This can result in erratic results.

The patch you describe is relatively small. I'm not sure how you could end up with such high memory usage except perhaps if all cues were record by fixture with all photocopies/long chases etc. Not sure.
Still instinct says old fixtures. I think you can see these on a VDU when in the patch menu. I don't really know why they remain or if there's any way to get rid of them.

Try the wipeall test. If this proves it is memory usage then in the future I recommend saving during your shows and reloading these after a touring LD. This is what I always do, if not just to restore everything to how it should be and is easy now with Usb.