Forum Replies Created

  • Jussi Lohijoki

    February 12, 2009 at 10:47 am in reply to: Capturing to Media Composer via firewire problems

    Your deck is JVC … hmm if I remember correctly there is at least couple of JVC decks which has had huge problems with avid. One was BR something. Have tried find is there any matching one’s in deck templates or even bit similar. If you open the deck templates you can see that those files are simple txt files. Try Open one existing JVC-temple which close enough and do modifications there. Some times if you use just generic dv device Avid can’t find/or do not know how to act with the deck.

    In PC workstations you can register dvbuffers again to make sure that CPU and firewire device can communicate. I don not know is there similar method in Mac. Can you Mac see in CPU level the deck?

    Other thing to do is to install DIO RUNTIME from MC installers again – I believe that In Mac platform that means reinstalling the whole software again.

    You can also find from avid sites list of supported devices. Sometimes there is limitations or orders how to proceed with a certain deck.

    And one thing more are using firewire drives at the same time? Both FW 400 connctors are basiccally the same they both are connected to motherboard so if you have one please remove the fw-drive and try again.

    cheers
    -Jussi

  • Jussi Lohijoki

    February 12, 2009 at 7:21 am in reply to: buffer overrun detected

    Hello

    First when you are posting an error message the systemm config would be great. It just makes things easier and defenetly you get more answers. I mean which software ( Xpress/MC)and version and also is there any I/O’s connected to the CPU which kind drives you are using?

    But buffer overrun error can be caused by overloading the system’s playback capabilities. Normally this kind of error happens when you have too many streams in your timeline but according the picture in your case that’s not the issue. You may have bad RAM in the CPU. You can try replace/reseat the RAM and the error should go away.

  • Jussi Lohijoki

    February 11, 2009 at 11:17 am in reply to: old OMF files not recognized by new MC

    Hello

    Is there any change to transcode those clips in your older Avid?
    That might help to transcode those omf-clips to mxf. I have once done in interplay environment where we needed old omf-files from Xpress. All orthodox methods gave us very similar situation what you have now, so I switched edit to standalone mode and just copy pasted material to unitys workspace omf mediafiles folder and the I forced Avid scan media again ( remove media datbase files) and then I got my old omf-files fully working.

    -jussi

  • Jussi Lohijoki

    February 11, 2009 at 10:11 am in reply to: old OMF files not recognized by new MC

    Hello

    Do you have opportunity to transcode in your older avid? That might make the clips work. I have faced similar problem with interplay and old Xpress OMF-files and what I did was just copy paste in standalone mode ( no interplay connection) and then I removed mediadatabase files ans allowed Avid rescan the omf mediafiles folders. When avid creating mediadatabase files again it eats more easily “old material”

    _jussi

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy