movement of pos. pallette lost.

[Haytech]

Hi,

I normally program pallettes 1-6 with static positions and another six with movement.

 

Now there seemed to be a problem creating a movement from a static position pallette and storing it into a new pallette ... the new stored pallette shows the static pos data after calling it.

 

Our desk runs desk os rel. 9.6

[K-Nine]

Not heard of that one before, but then again, I've probably never tried that particular operation

 

When I get some time I will investigate on one of the desks.

 

Just a thought - do you output one of the 'static' position palettes first, adjust the movement effect parameters as necessary, and then save to another position palette ?

 

I was wondering if the wheel LCD was showing pan/tilt parameters as a palette reference rather than actual DMX values may be a factor here.

[Haytech]

Just a thought - do you output one of the 'static' position palettes first, adjust the movement effect parameters as necessary, and then save to another position palette ?

 

Hi, K-Nine

that is exactly my point. Be prepared to get :? by the desk.

Sometimes it plays back the generated and stored movement and sometimes not.

 

Display shows indeed the P1 for all position data on the wheels display.

but it can be altered.

 

Cheers

[K-Nine]

Does the wheel still show P1 even if you add a movement effect and then save as a different position palette ?

[Haytech]

I don´t know exactly but i don´t think so. - this must have arise my attention .

 

Sorry for clumsy words

Cheers

[Pipo]

You have to 'change' every parameter so that P1 isn't on the display anymore.

 

With change i mean: scroll the wheel so that the P1 disappears, change the parameter to the required value or put it back to the original value and then program your pallet. It works for me.

[Haytech]

Thanks Pipo,

I will try it tomorrow, when desk is unpacked from our lorry

 

Thanks again

with regards

 

 

Sebastian

[K-Nine]

If you change all the movement effect parameters such that they no longer reference the original position palette, this appears to work

 

It would also appear that you don't need to adjust the pan and tilt parameters (unless you want to of course) - when you save the position and movement effect as a new position palette, it should take the actual pan/tilt DMX values from the original palette and store them in the new one.

[Haytech]

Hi there,

I tried it once again under testing conditions -

I cleared every pallette first then I made some position pallettes.

In this case I spotted one point in the room then I altered every value on position Pallette P/T / MovSp / Offset / Rota / Speed / Effect / Dim X / Dim Y etc.

 

This is now a movement pallet i.e. P6

 

But ( there is a big but ) If know other pallettes i.e. color / beamshape will be stored then the movementpallettes seem to be static ones ...

[K-Nine]

Erm, still a little confused here Haytech.

 

Can I just clarify what you did, so I can try it here and see if I can reproduce the problem...

 

Program a static position palette, say P1.

 

Select fixtures and output position palette P1.

 

Wheel LCD shows 'P1' for all the position parameters, including the six movement effect parameters.

 

Adjust all the position parameters, including all the movement effect parameters such that the fixtures now have a movement effect (eg circle).

 

Save fixture position data as a new position palette, say P6.

 

When you output position palette P6 later, it appears static, ie it has lost it's movement effect ?

 

Not quite sure where the last paragraph about colour/beam palettes comes into this :?

[Pipo]

I think what Haytech means is that after he has stored his movements into the palet, they all work fine, BUT when he starts programming the color and beamshape-pallettes, the position-pallettes lose their movement and become static.

 

Never had that problem before.

[Haytech]

Erm, still a little confused here Haytech.

Can I just clarify what you did, so I can try it here and see if I can reproduce the problem...

Program a static position palette, say P1.

Select fixtures and output position palette P1.

Wheel LCD shows 'P1' for all the position parameters, including the six movement effect parameters.

Adjust all the position parameters, including all the movement effect parameters such that the fixtures now have a movement effect (eg circle).

Save fixture position data as a new position palette, say P6.

When you output position palette P6 later, it appears static, ie it has lost it's movement effect ?

Not quite sure where the last paragraph about colour/beam palettes comes into this

 

think what Haytech means is that after he has stored his movements into the palet, they all work fine, BUT when he starts programming the color and beamshape-pallettes, the position-pallettes lose their movement and become static.

 

Pipo is right -

All movements are working fine until I program some other pallettes like colour / beamshape

I tried this on a Fat and a Leap it can be reproduced.

[Haytech]

Any new experiences on this tricky thing ??

[K-Nine]

Any new experiences on this tricky thing ??

 

Not yet - I will try and investigate as soon as I have the time - obviously better if I can try and reproduce the fault in our demo room with real fixtures

[Haytech]

I tried

Mac500 buckets

Mac600

Elation Servospot 250 ( same as Robe Spot 250+)

some other´s like HES Cyberlight

HES Trackspot

etc...

[Haytech]

Here are my latetest experiences of my problem...

 

Leap Frog, 6x Servospot, 8x MAC 500 ...

I blanked all pallettes before I began to program new ones ...

I began the programming with the position pallettes ... like I usually do, because they are the most used ones.

 

I programmed 6 Movements to pallettes. then I programmed 6 Beamshape pallettes then the desk shows the massage 'Saving desk data' on main display - know the movement pallettes seem to be static.

PS I never used a existing pallette to create a moving one I setup a new position / movement for each.

 

Please help - this error is wacky (to be gentle)

[K-Nine]

Hi Haytech,

 

After further investigation, testing and discussion with our software guru (aka Simon) it appears we have discovered the source of the bug ...

 

It appears that programming the corresponding colour or beamshape palette is affecting the movement effect data on the programmed position palette 8O

 

For example - if position palette 7 has been programmed with a movement effect, then programming colour palette 7 or beamshape palette 7 is clearing out some of the "extended data" area of the base memory. This "extended data" is where the movement effect parameters are stored. This should only happen when you are programming a position palette.

 

There are two possible work-arounds to avoid this problem ..

 

1. Use different palette numbers for your position palettes with movement effects to those used for colour and beamshape palettes (eg program colour/beam numbers 1-12 and pos palettes with movement 13+

 

2. Program your colour and beam palettes first and then your position palettes.

[Haytech]

Hi K-Nine and other Zero guys,

 

knowing this - keeps the desk on the road for know.

 

Thank you for investigating time on this one first I thought you didn´t believe me.

 

Thanks again

[K-Nine]

It wasn't a case of not believing you - it was just trying to set up the correct situation and specific sequence of events to reproduce the problem

 

As soon as Simon suggested it might be the corresponding number thing, I tried it .. and voila .. reproduced the fault simply by programming TWO palettes - in previous tests I had programmed lots of palettes with no problem at all 8O

 

Weird stuff .. software :wink:

 

Frog Reference No 5490 - Programming corresponding colour/beam palettes clears movement effect data from position palette - Bug to be fixed in next release.

[Haytech]

Hi Zero88 folks,

HAPPY NEW YEAR 2005 all the best luck for Frog 2 launch.

It would be great when this bug is solved asap.

Many thanks

 

Sebastian

[ice]

Yeah, how about OS version 9.7 or something?