The Avolites Discussion Forum

Hi there,

I'm having a problem with the Titan Expert.

When I set times for a cue or a memory to 2 sec. The times go automaticly to 60 sec. We've been resetting the table a few times and programming the memorys and cues a few times.

Am I forgetting something? or is it something in the software?

I've never seen this. Can you give exact steps to repeat? Also can you confirm this is v2.0?

niclights wrote:I've never seen this. Can you give exact steps to repeat? Also can you confirm this is v2.0?

yes it's V2.0

when we make a cue list and we set the times for 2 sec each step, then after a while (sometimes after 4 minutes sometimes after an hour) the fadetimes go automaticly to 60 sec.

so if we make some cues with a fadetimes of 0sec, then the effects a lost because it's fading in in 60 secs.

I hope that you understand what I mean because my english is not that good

I understand what you mean, but I don't understand why! I cannot repeat this.

It might be useful if you can give more exact details. Such as how you create the Cuelist and what you are doing when you see it change.

For an example this is a test I did:

Program Mode,
Clear,
Press Chase button twice (for create cuelist),
Press Playback Swop key five times (creates four step cuelist),
[Edit Times],
Scroll to step 3 with wheel,
[Fade In],
4 <enter>,
Exit,
Raise Playback,
Press Go repeatedly.

Observe fade times in connected view. I expect to see default time 2s for all steps except step 3 which should be 4s. I look for some times changing to 60s.
I also tried enabling link on every step so that the cuelist was able to continuously run on its own. I could see no problems.

Perhaps you do something different? Like use in run mode/user setting 'connected view sets temporary speed'/etc?

niclights wrote:I understand what you mean, but I don't understand why! I cannot repeat this.

It might be useful if you can give more exact details. Such as how you create the Cuelist and what you are doing when you see it change.

For an example this is a test I did:

Program Mode,
Clear,
Press Chase button twice (for create cuelist),
Press Playback Swop key five times (creates four step cuelist),
[Edit Times],
Scroll to step 3 with wheel,
[Fade In],
4 <enter>,
Exit,
Raise Playback,
Press Go repeatedly.

Observe fade times in connected view. I expect to see default time 2s for all steps except step 3 which should be 4s. I look for some times changing to 60s.
I also tried enabling link on every step so that the cuelist was able to continuously run on its own. I could see no problems.

Perhaps you do something different? Like use in run mode/user setting 'connected view sets temporary speed'/etc?

okay, this is how we did.

program mode
tap chase
select "create a cue list" ("B" button in the blue lcd screen)
make a few cues
then exit, exit, clear.
set all fade times to 0.1sec.
make the "flashbutton" a "Go-button"
then exit, exit, clear.
test it a few times (no problem)
a few minutes later we test it again
seeing no difference in cues
looking what it could be
then we look to the fade-times
and they're all set to 60sec.

weird isn't it?

This is strange. I have tried with your method but still I do not see any problem.

Can you think of anything else? Does it matter what is in the cues - fixture types/attributes etc? What are your user settings? Is auto-save enabled?

niclights wrote:This is strange. I have tried with your method but still I do not see any problem.

Can you think of anything else? Does it matter what is in the cues - fixture types/attributes etc? What are your user settings? Is auto-save enabled?

hmm I have no idea, the fixtures we use are almost only moving heads. and some times we record it in fixture mode and stage mode but I don't think that this may be a problem.

but from a colleague of mine, there's another question: When we start up the expert titan, when it's completely started up. some lights turn on. And they go out when we put one fader up and down.

Why is this?

I agree, I don't think it is related to that either. However, if you can constantly repeat this problem then there must be something different you are doing. I can't imagine that this could be caused by faulty hardware. Keep thinking about it and see if there's anything you have forgotten to mention.

The lights turning on problem occurs on all universes apart from 1. I do not know what causes it. The only solution at the moment is to activate something relating to each of the affected universes before plugging in the DMX.

Ok that's clear now to us

but the main problem stays strange...
I think that we just have to live with te risc that this can happen during a show:(

If you email me your showfile with an example I am happy to see if I can repeat it here.

niclights wrote:If you email me your showfile with an example I am happy to see if I can repeat it here.

Do you meen the .D4Z file?

Yes

Hi i am new to the Expert with Titan V2 and in order to help me come to terms with the differences between the old Pearl software (2000-8 ) and the new release i have been reading others issues they may have with the updates.
In your post you mention that you have recorded in fixture and in stage mode, where does this facility exist as i cannot find it in the new owners/instruction manual.
In the old software the option to change between record by fixture or by channel was in the AVO key user settings menu.

In the record cue menu - ie. after you press the memory function key.