-
[quote user="RalphFoster"]We found that the OMF databases did not get updated or scanned if you were in HD mode. So all of this had to be done whilst we were in SD mode. Hope this helps anyone else who encounters this. [/quote] I've found this to be the case as well. Try changing the format of your project to either SD or HD and then back
-
I've got a handful of classic nitris on Vista 64's that I haven't received any calls with problems like that. Doesn't mean the problem didn't happen and the operator figured it out (yeah, right...they're not gonna call?) but it's nothing I've heard of. All of our systems are gonna be in the 3.0-3.1 realm, though. Not
-
We currently have 2 out now that seem to be stable at this point--and by stable, I mean as bad as any other 3.5 Mac composer system, but at least not worse. Both Nitris DX bobs. Both on 4.1.6 running 5.1 clents. But these have only been out for about 1-2 weeks, so I hardly feel that's an appropriate amount of time to bless the thing. But that's
-
My mistake--I misunderstood Mike_Fitchie as saying the problem was "Media Net 3.5.x". I have seen sluggishness in Mac>Unity connectivity since OSX came out, at least as compared to PC's or OS9. Mike is probably referring to Media Composer 3.5.x, not Media Net 3.5.x. I have definitely heard woes of this type with composer 3.5+. Avid's
-
[quote user="Mike_Fitchie"] has it started on the macs sinse installing 3.5.x have seen v bad performance on macs on unity in 3.5.x during project opening/saving/closing....had to back rev to resolve..... [/quote] That's interesting, I've always equated the mac/unity sluggishness with OSX. OS9 was always superfine on unity, but OSX
-
Here is what I have found with my testing/troubleshooting: I can not recreate the problem with a non-group clip. Master clips/subclips play fine. In fact, grouped clips play fine so long as they're not in quad/nine-split. I have found this to be a problem ever since version 3 came out...from version 3 - 3.1.2. PC or Mac it makes no difference. I
-
Thanks for the suggestion. I have tried that, and the weird thing is that in this situation, Windows doesn't want to find the drivers. I've always just left it to find them, and it always does. But with this computer, it says that it's unable to find suitable drivers. ...but if I manually go in and (in any way) set the drivers--be it, navigating
-
So far no good. I did uninstall composer and deleted all traces of flamethrower. I then reinstalled composer. Plugging in the mojo does make it show up in device manager, but with an exclaimation point. I can force it to the flamethrower driver, which loads fine, but composer doesn't see the thing. I'm going to uninstall 2.6.8 and roll back
-
Actually, I did. I performed a brand-new clean format. It's pretty strange, I've also uninstalled/reinstalled media composer (but I didn't delete all the flamethrowers then--I'll do that now) twice, I've also tried using flamethrower drivers from different versions of composer (crazy, I know...I'm just reaching for anything now
-
I'm sorry for such a cheesy, basic question...but for some reason my brain is fried and I'd love a shot in the arm if anyone's got one out there. SDI mojo connecting to an XW 8000 running 2.6.8. QT 7.1 and NVidia 84.26, (not that it matters for this problem) SDI mojo, firewire 400 going into either on-board port (front or back) is seen by