Latest post Fri, Jul 4 2008 11:39 AM by TerryO. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • Mon, Apr 14 2008 2:23 PM

    • Julian L
    • Not Ranked
    • Joined on Thu, Feb 21 2008
    • Posts 4
    • Points 55

    Trouble getting firewire drives to be seen by the media indexer

     We are running with Interplay version 1.2.1 and Avid adrenalines 2.8.1

    When we point our client machine indexer to the MXF media files folder on the firewire drive the media indexer either states 'storage not found' or states 'normal' but in both cases is not scanning and will not see the media.

    Has anyone had  any similar experiences or problems not neing able to see firewire media on an Interplay system?

    Thanks

     

  • Mon, Apr 14 2008 4:50 PM In reply to

    Re: Trouble getting firewire drives to be seen by the media indexer

    Julian: did you added the option to scan local drives in the editor?


    Regards

    Felipe Gonzalez

    ACSR Interplay

    Avid Latin America

    El cerebro es como un paracaídas, trabaja mejor cuando se abre / Brain is like a parachute, it works better when it is open

     

  • Mon, Apr 14 2008 6:46 PM In reply to

    • Highnoon
    • Not Ranked
    • Joined on Tue, Jul 11 2006
    • Denver, CO USA
    • Posts 60
    • Points 700

    Re: Trouble getting firewire drives to be seen by the media indexer

    i have inconsistent problems with this.

    when you go into service config and set the MI Service path to the drive, do you disconnect the 1394 connection to the Adrenaline?

    i have better luck getting MI Service to scan drives via USB2 than Firewire for whatever reason, but i've only used them to relink then consolidate media from remote locations onto our ISIS system, not to edit from.

    try tapping the drive to the Avid MediaFiles folder, and letting avid find the MXF>1 folder by itself, instead of driving all the way to it. and yes, check your media creation settings and make sure you've selected "automatically scan local drives as they come online", which typically (but not always, i've found) will create that path in the MI Service Config.

    also, if it sees the drive and returns a [Normal], copy in or delete something random from the MXF folder and see if that drives a rescan or database creation.




    39 MCsoft 2.7.7 w/Mojo HP XW8000-8200 Avid ISIS 1.4 64TB Avid Interplay 1.1.6 60 Avid Interplay Assist 1.6 2 Dual Boot Symphony Nitris/DS v8.0 HPXW9300... [view my complete system specs]
    Eli Hensley | High Noon Entertainment Technical Services Manager & Morale Officer the race for quality has no finish line...so technically it's more like a death march.
  • Thu, May 1 2008 8:36 AM In reply to

    • Julian L
    • Not Ranked
    • Joined on Thu, Feb 21 2008
    • Posts 4
    • Points 55

    Re: Trouble getting firewire drives to be seen by the media indexer

    Thanks for your reply. Glad you are having inconsistant problems with this also.

    Tried you ideas but with no success. Avid have a system that they are experiencing similar problems on another of their own systems.

    Apparently the next version 1.2.3 does not fix this problem yet.

    Will get back to you if I here any more.

  • Fri, Jul 4 2008 11:39 AM In reply to

    • TerryO
    • Not Ranked
    • Joined on Mon, Oct 24 2005
    • Oslo, Norway
    • Posts 72
    • Points 810

    Re: Trouble getting firewire drives to be seen by the media indexer

     We have the same problem here at TV 2 Norway.

    Avid Norway is investigating the problem for us.

    In the mean time, as a workaround, we use a special .bat file to make the Avid temporarily "Standalone" .

    This way we can access/import files. Then an other .bat file makes it "Interplay" again so we can Check in the clips.

     

    Work machines: 5 Avid Media Composer Adrenaline version 2.8.3 / 3.0 Avid built HP machines 3 GB RAM, Dual Xeon processor 3,2 GB 1 Avid Symphony Nitris... [view my complete system specs]

     

Page 1 of 1 (5 items)