Catalyst can't draw perfect squares/rectangles?

I'm having a problem with getting straight lines out of Catalyst. This seems like it should be a no brainer but I can't make it work.

If I take a video source (via Phoenix input) or any piece of content and bring the dimmer up & scale it smaller than the mix (so that the edges of the layer are visible) there is usually a one pixel tear on at least one side of the rendered layer.
I thought this would be an easy fix by adjusting the default fine rotation value at the console but that didn't work, which I find astonishing.
The rotation channel on grandMA is defaulted to a 16-bit value of 32768. If I adjust it to 32767, the tear simply moves to another part of the edge.

I find it unbelievable that out of 64,000 possible steps on a 16-bit channel, I can't get a layer with a straight vertical edge on the sides!

And no, the problem is not caused by the wall processor or anything else in the food chain. The problem is visible right on the local LCD monitor, as well as a separate MAC MINI system I use at FOH for preview only.

What's the trick to getting a perfectly square layer in Catalyst?

Thanks


4.30/build 297

I have noticed this too. I have always seen it on the right side, about 1/3 from the bottom right edge. Never a massive issue with that, but just thought it was interesting..

can't seem to make it do this....
however, Im using manual controls not DMX to test

Are the X, Y, and Z rotation values at 0 on the HUD?
Have you tried replicating this using manual control rather than DMX?

(16 bit = 65536, not 64000... maybe this is the problem?)

Is there any reason you are running m297? This is a custom version.

try running the release version m257 - available here:

http://homepage.mac.com/goatee/.Public/m257.dmg

password peru-

Simon

Quote:

---

Originally Posted by Mr_P

can't seem to make it do this....
however, Im using manual controls not DMX to test

Are the X, Y, and Z rotation values at 0 on the HUD?
Have you tried replicating this using manual control rather than DMX?

(16 bit = 65536, not 64000... maybe this is the problem?)

Is there any reason you are running m297? This is a custom version.

try running the release version m257 - available here:

http://homepage.mac.com/goatee/.Public/m257.dmg

password peru-

Simon

---

HUD controls are indeed at 0.
I'm aware that 16bit is more than 65k steps. I was just making a point. :)
And no, I haven't tried to replicate with manual controls. But I will take a screen shot and upload it so you can see what is happening.

I'm running m297 because Richard sent me that version this spring... As I understand it, the public release that followed m297 had significant changes to the FX designer, and as I had already programmed my show it didn't make sense to change versions.

The current public release version is m257.
Anything Richard gives you privately is custom and not for public distribution...
If you have specific issues with that particular version you must contact him directly.

To eliminate DMX, set up the same configuration in m257 and see if it does the same thing...
Also try to replicate it manually.

S

Quote:

---

Originally Posted by Mr_P

The current public release version is m257.
Anything Richard gives you privately is custom and not for public distribution...
If you have specific issues with that particular version you must contact him directly.


S

---

Of course. But I'm assuming that a few other people must have been using the same build at some point and was hoping that someone had a solution.

i think its a dmx issue -

please check in DMX input HUD for exact dmx values being sent and send me screen capture of DMX values

its not a software version thing

Quote:

---

Originally Posted by Leif

Of course. But I'm assuming that a few other people must have been using the same build at some point and was hoping that someone had a solution.

---

i dont think its me - i think its a dmx/programming thing -

please look in DMX input/artnet HUD at exact values being sent from lighting console

and send me screen capture

one of the rotation parameters is not zero - x or y or z - can be any one of them is not exactly at the zero position-

i believe the exact zero value is 32768 in 16bit dmx which is 128,0 as 2 8 bit values