Same ol', same ol'
3 messages in this thread
Gregory: Once again, thanks for such swift response. Have performed multitudes
of both cold & warm re-boots. Have field-order =1. Have initialized the
BCD5000. I'm thinking it's something internal to Release2.000. Talked (phone)
w/ a guy in Georgia who remembers having such a problem, that seemed to fix
itself contemporaneously w/ his upgrading to ver. 2.01a. Sometime next week
should be receiving ver.3xx. and, with fingers rigidly crossed, HOPE its the
fix. Simply can't imagine any other parameters/tweaks/combos to try. As I
mentioned in our first message, no onne on the hardware side seems to have a
clue (read: "unfamiliar w/ the problem, so it can't be ours..". Will keep you
posted. Thanks, and have a very happy New Year!
Theo.,
>>field order stuff….
There was a long thread back in March about field-order gremlins that could
jump into the Vista (due to it's programmable nature) but I searched and
couldn't find any specific reference to problems with 3DS version 2.00 or 2.01a
(2.01 died an early death). If so, then by extrapolation r3 alone may not
solve your problem.
I assume you have controlled your startup as the Good Greg recommened as to
eliminate the possibility of ANY other software messing with the Vista?
Video moron that _I_ am, I've had video stuttering twice before (using
Vista+DQ50P+AG7750). Both times were unrelated to field rendering and totally
due to my inexperience: once I had my snyc set up improperly, and once I forgot
to reblack the tape after changing something. Begging your pardon if I'm way
off base here, but one simple but looming question: Can you put an animation
cleanly to tape with your hardware WITHOUT rendering to fields?
JKJ (familiar with crossed-fingered animating)
PS: and one tiny unrelated suggestion – if you were to use Reply instead of
starting a new thread, forum continuity would reign! <g>
Theo- I had the same problem with 2.0. 2.01 or 2.01a fixed it. I was using
the 5000 with a BVW75. I remember because it was completly unexplained. I
laid part of an animation down, and then restored more rendered frames and
began laying the remainder of the animation down. The field orders were
reversed (at least thats how they were laying to tape). Seems like rebooting
cured it for me, but after the upgrade to 2.01a, I've never seen the problem
again. I'm using 3 now and don't have the problem, so I think you'll be safe.
-Mark