[Tig] dv 2k+ possible bugs?

[Rob Lingelbach]

Quoting Rob Lingelbach <rob at colorist.org>:

> 1900 subscribers as of June 2008
> Andy Lichstein supports the TIG
> recommended reading: http://tools.ietf.org/html/rfc1855
> ====
>
>
> I've been wondering some unexplained behavior on the part of a DaVinci
> 2k+ that someone else may also have experienced.  I can get the s/w
> version tomorrow if that's relevant.
>
> 1)In scroll mode, when "Exiting as is" is applied, the mona lista does
> not return to the current event in the list until the film is moved.
> "Exit as Was" does return to the current event, as expected.    This
> behavior of the list remaining on the event to which you're scrolled
> back when you "Exit as is"  doesn't seem to make sense, and indeed
> concerns me that perhaps if I were to recall a scratchpad memory,
> while the list is in not showing the current event (where the film is
> parked) that it might be plugged into that scrolled-to event (behavior
> that is rarely wanted, though sometimes I do that on purpose- scroll
> back and bang in a correction from a memory to a previous event - a  
> so-
> called "undocumented feature" that Bruce Graham showed me many moons
> ago).

We're running version 4.0.3 on a regular 2k, and we get this too.  I  
agree it
doesn't make sense, but I've gotten into the habit of playing the film  
after
hitting "Exit as is" to see how the grade works on the shot, so it's  
rarely an
issue.

>
> 2)Also often in Scroll Mode I find I can't scroll past a certain
> event; scroll jumps back to where I started - I suspect that there is
> something in the events I'm scrolling past that Scroll Mode doesn't
> like-  I can use the Jam event # to go directly to an event that
> otherwise I can't get to by scrolling with the joyball, but often of
> course I don't know what event it is until i move around with scroll,
> so Jam event # is not that useful in many cases.
>

You're driving a Spirit, right?  On the GCP, go to 'TK Config' and  
check to see
if 'Auto Re-scan' is enabled. (It's in the lower left of the screen)   
If it is
enabled, disable it.  About a month or so ago, we started experiencing  
some odd
behavior from our Spirit, such as the same scroll issue you described  
as well as
the the film deck stepping back and forth on it's own when setting the  
count on
a roll of film.  Turned out that 'Auto Re-scan' had been turned on at  
some
point.  Turning it off fixed it.

> 3)Regarding secondaries: often, and I don't know if this is always
> true, when I define a kilovector by the put-cursor-on-color/grab-
> saturation-knob-and-turn method, the very definition of the vector
> makes it jump in phase or saturation as if I were turning the knob
> quite a lot more than i am.   I believe this also happens in 6-vector
> mode but I'll test it tomorrow ..  there could be some interacting
> conditions that cause the secondary vector 'jump.'   (now I'm
> wondering if it happens when defining a single vector or only when I
> have multiple, which could mean there's an overlap condition.)

Dumb question, but did you try quitting and relaunching the 2k  
software?  We
occasionally get some kilovector weirdness, and relaunching the software
generally fixes it.  I've haven't experienced the specific problem you
described, but it's worth a shot.


Hope this helps, and good luck.


Ken Wald
Colorist
Optimus - Chicago

>
> thanks in advance for any help.
>
> --
> Rob Lingelbach
> rob at colorist.org    http://www.colorist.org/robhome.html
>
>
>
>
> _______________________________________________
> No product marketing on the main TIG mailinglist.
> Emergency contact: rob (at) nccom.com
> Tig mailing list
> Tig at tig.colorist.org
> http://tig.colorist.org/mailman/listinfo/tig
>