> This probably requires under the hood rewrites or modification in the software to give the proper feel to the Artist color integration.
I didn't buy Artist Color with the knowledge that it worked so poorly with MC/Symphony. I bought it because Artist Color was very heavily-promoted by Avid as working "seamlessly" (and that is a quote) with MC/Symphony. It is now abundantly clear that this thesis is patently untrue.
In its current form, this product cannot be used in a professional setting. At least not without the embarrassment of constantly apologizing to one's clients for the stuttering, latency and complete lack of precision this product offers.
Avid needs to disclose whether or not this will be fixed in short order -- or if the fix requires a more substantial and time-consuming effort with an unknown "delivery date".
Simply put, I didn't buy this device so that I could begin to use it 6 months from now.
If your statement is true, and it's not simply a Driver/API issue, then *some* of us need to know that from Avid ... NOW!.
My window for returning this device is closing -- and I have no intention on paying a 33% restocking fee because Artist Color was misrepresented by the manufacturer. A manufacturer, I might add, that is responsible for both of the interconnected products -- and had complete control and knowledge of how well they worked together.
And, yes, a 33% restocking fee if the product that was purchased is not defective.
--- In Avid-L2@yahoogroups.com, Jeff Krebs <rockinjeff@...> wrote:
>
> All issues are software - it's the entire architecture of the color mode in
> the Avid design.
> Simply put - it was never designed for hardware intervention like artist
> color or tangent panels.
>
> If you know someone with Davinci (Black Magic) or Lustre with tangent - go
> check the feel and true connection of the hardware into the software.
> It is very different.
>
> This probably requires under the hood rewrites or modification in the
> software to give the proper feel to the Artist color integration.
>
>
>
> On Sat, Dec 3, 2011 at 11:32 PM, Nat Jencks <natjencks.lists@...>wrote:
>
> > **
> >
> >
> > Agreed, it's not a hardware issue. The panel works fine for me with
> > Scratch (and resolve).
> >
> > FWIW, in scratch by default all the knobs etc have "linear" response,
> > although I think you can program them to have "acceleration" sensitivity,
> > but that is certainly not determined by the hardware either.
> >
> > best-
> > -Nat
> >
> >
> > On Dec 3, 2011, at 1:36 AM, Steve Hullfish wrote:
> >
> > > I have not use this on MC yet, but the MC Color works great on Resolve.
> > Very smooth. No latency to speak of. That it works great on a 3rd party app
> > (it also works well in Color) and not on MC is ironic. (I don't know that
> > from experience, just listening to the chatter on the -L about itâˆ`)
> > >
> > > Steve Hullfish
> > > contributor: www.provideocoalition.com
> > >
> > > On Dec 2, 2011, at 10:20 PM, blafarm wrote:
> > >>
> > >> Maybe we're the only ones having problems. But I would say (with
> > absolutely no exaggeration) that this device is completely unusable in a
> > professional setting. To be fair, the other knobs and buttons work just
> > fine -- but the stuttering and latency of the three trackballs is
> > unacceptable.
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Search the official Complete Avid-L archives at:
> > http://archives.bengrosser.com/avid/
> > > Yahoo! Groups Links
> > >
> > >
> > >
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
No comments:
Post a Comment