Future scaling suggestion

May I suggest an option for a future release of Catalyst ?

I, for one, would find it unbelievably handy to be able to specify something like a "global scale" as a user preference. Let me clarify what I mean and why I would need such a feature. When working with content that is, say, 720x576, and is being displayed at, or very near "native resolution" or full screen, I find that the majority of the scaling & translation range (X & Y positioning) is unusable, and often results in having live scaling & translation cues being so steppy as to also be unusable.

For example, if I wanted to scale a piece of content from "0%" (just small enough to not be seen) to full screen, the 16-bit DMX values are 32911 > 36345, which is an incredibly small slice of the DMX spectrum...and if I wanted to perform this scale change over, say, 10 seconds, the transition is incredibly steppy...whereas, if the range was from 0 > 36345, that would be a *much* greater step resolution and, I surmise, would allow for a much smoother transition from imperceptably small to full screen.

Does that make any kind of sense ?

Thanks.
Parents
  • [QUOTE=hillaryknox]Yeah, I know about the mspeed channel...unfortunately it doesn't really help smooth things out enough for what I need...I mean, there is a slight difference, but for what I really need, it's not quite the answer. Plus, there's that age-old pain-in-the-ass-ness of having to use the mspeed channel at all, and if you need different parameters to have different timings, etc.

    mspeed channel - is nothing like the 'mspeed' on a light.
    a computer has no physical inertia - it will instantly do what you tell it.

    you need to check the output and update rate of dmx from your console.
Reply
  • [QUOTE=hillaryknox]Yeah, I know about the mspeed channel...unfortunately it doesn't really help smooth things out enough for what I need...I mean, there is a slight difference, but for what I really need, it's not quite the answer. Plus, there's that age-old pain-in-the-ass-ness of having to use the mspeed channel at all, and if you need different parameters to have different timings, etc.

    mspeed channel - is nothing like the 'mspeed' on a light.
    a computer has no physical inertia - it will instantly do what you tell it.

    you need to check the output and update rate of dmx from your console.
Children
No Data