Well I think I have resolved this issue. Super Bowl my tush!!! This turned into a Super Brawl.
I uninstalled and reinstalled the Video Desktop. Still had the problem. For giggle I trashed mc state and voila it started working correctly on the work system, just like it does on my home system.
Then I switched back to our NitrisDX circa 2009 and it still worked but when I then went back to the DNxIO the problem reappeared. Another trashing of MC state and it worked again.
So my conclusion so far is that when the system runs on the older NitrisDX it changes something in MC state in a way that messes with the DNxIO protocol/communications when it is switched back to. I'm pretty sure I don't see this behavior on my home system as I would have probably noticed it but I will double check when back at home. My theory based on what I've done so far is that my home system with a circa 2012 NitrisDX that came with an HIB that is compatible with the DNxIO somehow doesn't alter the MC state code the way an older NitrisDX does. Perhaps this has to do with the "Passive" vs. "Active" change in the HIB cards and that given my newer NitrisDX is probably built with the Active HIB protocol chip set or whatever it is that doesn't alter the mc state code in a manner that doesn't work with the DNxIO. This is just speculation but sounds like it could be the root of the problem.
Bottom line it appears switching between an older NitrisDX and a DNxIO requires a trashing of MC State file. Going from DNxIO back to the older NitrisDX seems to work without issue from what I can tell.
What's that old saying, "Once you've gone older NitrisDX you can never go back!!!" ;-)
Hope this helps somebody else down the line. Now I can actually start working.
Posted by: bigfish@pacbell.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (4) |
No comments:
Post a Comment