hi, i would like to make task about bugs which i found.
Console software 1.1.3.2
1. At my opinion AutoFix doesn't work correctly
2. another bug will be easier explain step by step:
- make seq at fader
- make another pole (upper button with some function)
- move seq at another page
- move seq at another place
- seq is separates and i can't move it or delete anymore
I will suggest to move to mode 2, but with Ma3 Light a lot of hardware is not used like it should!
Come On MA!
I know that a lot of funcionality still is not implemented. but I am just passing elearning, and trying make it step by step. but it supprising me that functionality of official guid doesn't work correctly
Hmm this is a little bit interesting, not sure if this is exactly what you are seeing but I also see something odd when moving a fixed fader to another page.
It does not always seem consistent, but here are the steps I took to cause it to happen:
Steps 7, 8 or 9 will cause the 200 executor to either split from it's 300 or the 300 goes missing. when this happens you can't move the 200 executor. However, if in AutoFix mode this seems to be cosmetic since turning the executor off and back restores the fader to its proper height and can be moved again. If you did a Fix On Page 1.215 then you have to turn the fix off and go+ the fader before it will rejoin and can be moved.
Other Width/Height issues still exist so my guess it just hasn't been looked at yet.
readout PHYSICAL in using command AT doesn't make it correctly
at MA2 was readout NATURAL and it was really natural. overthere is ...
function "+" doesn't work
ex.
fixture 1
please
+2
please
// illegal object: +2
I expect this same shortcut from MA2. If there is DEFAULT command FIXTURE, I don't have to mark it always. For me it is bug
Don’t have an account yet? Register yourself now and be a part of our community!
