Latest post Tue, Apr 17 2018 9:28 AM by Ian Withnall. 12 replies.
Page 1 of 1 (13 items)
Sort Posts: Previous Next
  • Mon, Apr 9 2018 6:58 AM

    • Ian Withnall
    • Not Ranked
    • Joined on Wed, Jul 22 2015
    • Brisbane Australia
    • Posts 24
    • Points 265

    Small 18.4.0 Issue with scary drive behaviour.

    I just updated my MC to 18.4.0 and when I open the program, it seems to be constantly refreshing the media drive that has the active bin loaded in the viewer window. 

    Every few seconds the drive activity light flickers, and the viewer pane seems to refresh.

    It's stopping work just now so very perpplexing. 

    Seems to do everything else OK except you need to do it in three seconds or it will re-activate the viewer window. 

    Also affects other mac windows when MC is open. 

    I'm running Sierra 10.12.6 on a 12 core 2010 mac pro 3.3ghz with as mentioned, MC 18.4.0 Symphony. 

    Suggestions? 

    Apple Mac Pro 2010 Sierra 12 Core 3.3 64GB RAM 1TB SSD BMD Studio Card. Esata 4 Port running G-Raid external drives USB 3 [view my complete system specs]
  • Tue, Apr 10 2018 9:56 AM In reply to

    • Ian Withnall
    • Not Ranked
    • Joined on Wed, Jul 22 2015
    • Brisbane Australia
    • Posts 24
    • Points 265

    Re: Small 18.4.0 Issue with scary drive behaviour.

    AAAAAANNNNNEEEEEEEBOOOOODDDDEEEEEEEEEE???????????

    Apple Mac Pro 2010 Sierra 12 Core 3.3 64GB RAM 1TB SSD BMD Studio Card. Esata 4 Port running G-Raid external drives USB 3 [view my complete system specs]
  • Thu, Apr 12 2018 7:10 AM In reply to

    • Ian Withnall
    • Not Ranked
    • Joined on Wed, Jul 22 2015
    • Brisbane Australia
    • Posts 24
    • Points 265

    Re: Small 18.4.0 Issue with scary drive behaviour.

    Hi,

    Thanks for all the replies........

    Anyway... moving on. 

    Seems that when I try to AMA link, at the bottom of the link window a small message is flashing that says 

    AvidOPFrameGeneratorApp is not responding.

     

    Then it says restarting and so it goes. 

    I have re-instslled blackmagic decklink software, force quit Avid and now I'm out of ideas. 

    When I searched finder for AvidOPFrameGeneratorApp all that shows up is a folder with some fatal error logs! 

    So I'm out of ideas!

    Apple Mac Pro 2010 Sierra 12 Core 3.3 64GB RAM 1TB SSD BMD Studio Card. Esata 4 Port running G-Raid external drives USB 3 [view my complete system specs]
  • Fri, Apr 13 2018 1:43 AM In reply to

    • Ian Withnall
    • Not Ranked
    • Joined on Wed, Jul 22 2015
    • Brisbane Australia
    • Posts 24
    • Points 265

    Re: Small 18.4.0 Issue with scary drive behaviour.

    Hi,

    I have now uninstalled and reinstalled MC and the problem still exists.

    I. 

     

    Apple Mac Pro 2010 Sierra 12 Core 3.3 64GB RAM 1TB SSD BMD Studio Card. Esata 4 Port running G-Raid external drives USB 3 [view my complete system specs]
  • Fri, Apr 13 2018 3:26 AM In reply to

    Re: Small 18.4.0 Issue with scary drive behaviour.

    Ian Withnall:
    Seems that when I try to AMA link, at the bottom of the link window a small message is flashing that says 

    AvidOPFrameGeneratorApp is not responding.

    My only thought wold be have you tried deleting your AvidSouceBrowser cache?  here is the Windows path to it C:\Users\Public\Documents\Avid Media Composer\AvidSourceBrowserCache.  The Mac path should be fairly similar. 

    There is a risk involved I have not needed to do this so do not KNOW how safe this process is. If I were in your position I would assume that this Cache would be auto recreating similar to the way we deal with corrupt Avid Media database files. 

    Good luck

     

  • Fri, Apr 13 2018 3:44 AM In reply to

    • Ian Withnall
    • Not Ranked
    • Joined on Wed, Jul 22 2015
    • Brisbane Australia
    • Posts 24
    • Points 265

    Re: Small 18.4.0 Issue with scary drive behaviour.

    Hi,

    Thanks for getting back. 

    What exactly are those "Risks" you refer to. 

    Edit.. Tried this and no joy!

    I was also tempted to trash those media database files too? 

    Thoughts?

    Ian. 

    Apple Mac Pro 2010 Sierra 12 Core 3.3 64GB RAM 1TB SSD BMD Studio Card. Esata 4 Port running G-Raid external drives USB 3 [view my complete system specs]
  • Fri, Apr 13 2018 4:22 AM In reply to

    Re: Small 18.4.0 Issue with scary drive behaviour.

    Ian Withnall:
    I was also tempted to trash those media database files too?
    I would.  For years deleting the media databases was first step in problem solving for all Avids.

  • Fri, Apr 13 2018 4:33 AM In reply to

    Re: Small 18.4.0 Issue with scary drive behaviour.

    A couple of other thoughts 

    1: Hold down the ALT key as you open the project.  This will prompt MC to keep all the bins closed during start-up.  You can then isolate which bin is causing MC to freeze.

    2: Free up memory:
    1.Click the Info tab of the Project window.
    2.Click the Clear Memory button.
    A dialog box opens asking if you want to close and save all opened bins.
    3.Click OK.
    This operation deletes cached data for the online master clips only. Memory might also be used by other parts of your Avid editing application and will not be reduced by using the Clear Memory button.

  • Fri, Apr 13 2018 4:48 AM In reply to

    • Ian Withnall
    • Not Ranked
    • Joined on Wed, Jul 22 2015
    • Brisbane Australia
    • Posts 24
    • Points 265

    Re: Small 18.4.0 Issue with scary drive behaviour.

    HI

    yep I'm doing it next. 

    And thanks for advice. 

    Regards

    ian

     

    Apple Mac Pro 2010 Sierra 12 Core 3.3 64GB RAM 1TB SSD BMD Studio Card. Esata 4 Port running G-Raid external drives USB 3 [view my complete system specs]
  • Fri, Apr 13 2018 6:44 AM In reply to

    • Ian Withnall
    • Not Ranked
    • Joined on Wed, Jul 22 2015
    • Brisbane Australia
    • Posts 24
    • Points 265

    Re: Small 18.4.0 Issue with scary drive behaviour.

    Hi,

    So I have deleted the Media Databases and cleared memory. Still doing it.

    I also disconnected the keybards in case there was a stuck buttoin. Nope. Still doing it. 

    Have opened projects that have their own drives and still does it there too. 

    Have started a new project with a new user and still does it. 

    Any ideas on what this AvidOPFrameGeneratorApp thing is?

    I have only been able to deduce that it is somethign to do with Matrox, but I may be wrong on that.

    I have deleted the Matrox driver and also deleted the folder that contains the AvidOPFrameGeneratorApp app, and still does it. 

    The folder only has fatal eror logs that I can't read. 

    I have also deleted and reinstalled the latest firmware for the Blackmagic card, did another uninstall and reinstall after reinstalled the MC software. 

    See below for the crash report that is contained in the AvidOPFrameGeneratorApp folder. 

    This log file is current with the last time I opened Avid.

     

    2018/04/04 07:56:57.022453 AMALogger pid=5890 tid=0x7fffa15893c0 LogLevel_Info: AMALogger 2.1.0.0 (Built May 13 2017 09:25:37) NOTE: log times are in UTC!

    2018/04/04 07:56:57.022682 AMAUtilLib pid=5890 tid=0x7fffa15893c0 LogLevel_Info: AMAUtilLib initialized

    2018/04/04 07:56:57.031896 Avid Generic Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info:  2.4.2.10028

    2018/04/04 07:56:57.050644 AVCHD MSP Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info:  1.3.15.64

    2018/04/04 07:56:57.067812 AMASampleProviderSupport pid=5890 tid=0x7fffa15893c0 LogLevel_Info: AMASampleProviderSupport 2.1.0.0

    2018/04/04 07:56:57.068706 Avid MediaProcessor Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info:  0.1.2.17

    2018/04/04 07:56:57.077688 AVCHD MVP Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info:  1.3.15.64

    2018/04/04 07:56:57.085793 MediaCollector MVP Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info:  2.1.2.10036

    2018/04/04 07:56:57.102369 QuickTime Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info:  1.8.11.10052

    2018/04/04 07:56:57.238767 MSP_MXF Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info: Feature Toggle /GenericMXFContainer/MXFPartitionOptimization = ON

    2018/04/04 07:56:57.238808 MSP_MXF Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info: Feature Toggle /GenericMXFContainer/MXFExportEssenceOrderPerSMPTEST436 = ON

    2018/04/04 07:56:57.238818 MSP_MXF Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info: Feature Toggle /GenericMXFContainer/MXFBackgroundIndexing = ON

    2018/04/04 07:56:57.239026 MSP_MXF Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info:  1.20.7.66

    2018/04/04 07:56:57.261098 WaveAiff Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info: WaveAiff loaded

    2018/04/04 07:56:57.387488 AS-02 Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info:  1.10.7.66

    2018/04/04 07:56:57.399389 Avid Image Sequencer Plug-In pid=5890 tid=0x7fffa15893c0 LogLevel_Info: MSP_DPX loaded

    2018/04/04 07:56:57.411432 nablet XAVC XDCAM Plug-in pid=5890 tid=0x7fffa15893c0 LogLevel_Info: nablet XAVC XDCAM MVP MSP loaded

    2018/04/04 07:56:57.420494 nablet XDCAM EX Plug-in pid=5890 tid=0x7fffa15893c0 LogLevel_Info: nablet XDCAM EX MVP MSP loaded

    2018/04/04 07:56:57.437889 AMAUtilLib pid=5890 tid=0x7fffa15893c0 LogLevel_Warning: Unable to open disk (/dev/rdisk4s1), errno = 13, /Snapshots/relengmaverick1_1494681634/xplat/ama/source/utils/AMAUtilLib/AMAVolume.cpp(1023)

    2018/04/04 07:56:57.439746 AMADeviceMonitor pid=5890 tid=0x7fffa15893c0 LogLevel_Info: CAMADeviceMonitor::GetVolumeStatus() returned volume /

    2018/04/04 07:56:57.441256 AMADeviceMonitor pid=5890 tid=0x7fffa15893c0 LogLevel_Info: CAMADeviceMonitor::GetVolumeStatus() returned volume /Volumes/Avid Projects

    2018/04/04 07:56:57.441882 AMAUtilLib pid=5890 tid=0x7fffa15893c0 LogLevel_Warning: Unable to open disk (/dev/rdisk4s1), errno = 13, /Snapshots/relengmaverick1_1494681634/xplat/ama/source/utils/AMAUtilLib/AMAVolume.cpp(1023)

    2018/04/04 07:56:57.441906 AMADeviceMonitor pid=5890 tid=0x7fffa15893c0 LogLevel_Info: CAMADeviceMonitor::GetVolumeStatus() returned volume /Volumes/PROJECTS

    2018/04/04 07:56:57.442138 AMAUtilLib pid=5890 tid=0x7fffa15893c0 LogLevel_Warning: Unable to open disk (/dev/rdisk4s1), errno = 13, /Snapshots/relengmaverick1_1494681634/xplat/ama/source/utils/AMAUtilLib/AMAVolume.cpp(1023)

    2018/04/04 07:56:57.442471 AMAUtilLib pid=5890 tid=0x7fffa15893c0 LogLevel_Warning: Unable to open disk (/dev/rdisk4s1), errno = 13, /Snapshots/relengmaverick1_1494681634/xplat/ama/source/utils/AMAUtilLib/AMAVolume.cpp(1023)

    2018/04/04 07:56:57.442680 AMADeviceMonitor pid=5890 tid=0x7fffa15893c0 LogLevel_Info: CAMADeviceMonitor::GetVolumeStatus() returned volume /Volumes/Lacie Porta

    2018/04/04 07:56:57.443484 AMADeviceMonitor pid=5890 tid=0x7fffa15893c0 LogLevel_Info: CAMADeviceMonitor::GetVolumeStatus() returned volume /Volumes/G-RAID C 4TB

    2018/04/04 07:56:57.444017 AMADeviceMonitor pid=5890 tid=0x7fffa15893c0 LogLevel_Info: CAMADeviceMonitor::GetVolumeStatus() returned volume /Volumes/Time Machine 1

    2018/04/04 07:56:57.444818 AMADeviceMonitor pid=5890 tid=0x7fffa15893c0 LogLevel_Info: CAMADeviceMonitor::GetVolumeStatus() returned volume /Volumes/G-RAID B 4TB

    2018/04/04 07:56:57.445388 AMADeviceMonitor pid=5890 tid=0x7fffa15893c0 LogLevel_Info: CAMADeviceMonitor::GetVolumeStatus() returned volume /

    Apple Mac Pro 2010 Sierra 12 Core 3.3 64GB RAM 1TB SSD BMD Studio Card. Esata 4 Port running G-Raid external drives USB 3 [view my complete system specs]
  • Fri, Apr 13 2018 7:13 AM In reply to

    Re: Small 18.4.0 Issue with scary drive behaviour.

    Just checking did you delete the folderin bold below that contains the OPFrameGenerator.db  (database)?
    C:\Users\Public\Documents\Avid Media Composer\AvidSourceBrowserCache\OPFrameGenerator.db

    Ian Withnall:
    Unable to open disk (/dev/rdisk4s1), errno = 13
    Coding and log files are beyond me but the repeated line  "Unable to open disk (/dev/rdisk4s1)" in the log would suggest to me a starting pont to investigate.

    Can you easily disconnect the G-RAID and try again? (Preferably with the OpFrameGenerator.db file deleted after you have disconnected the G-RAID)

  • Fri, Apr 13 2018 9:12 AM In reply to

    • Ian Withnall
    • Not Ranked
    • Joined on Wed, Jul 22 2015
    • Brisbane Australia
    • Posts 24
    • Points 265

    Re: Small 18.4.0 Issue with scary drive behaviour.

    Hi,

    Yes, I ran it with that .db file deleted. Which was a good lead but sadly no. .

    I also tried it with NO Drives attached apart from the actual Avid Projects Drive, just on a small blacnk project. Also did it with the Blackmagic Drivers uninstalled. 

    Just waiting now for Avid to call me back.

    I feel like it is somethig simple, but maybe not.

    I

    Apple Mac Pro 2010 Sierra 12 Core 3.3 64GB RAM 1TB SSD BMD Studio Card. Esata 4 Port running G-Raid external drives USB 3 [view my complete system specs]
  • Tue, Apr 17 2018 9:28 AM In reply to

    • Ian Withnall
    • Not Ranked
    • Joined on Wed, Jul 22 2015
    • Brisbane Australia
    • Posts 24
    • Points 265

    Re: Small 18.4.0 Issue with scary drive behaviour.

    Hi, Well I dumped out of 2018.4 and went back to 8.8.1 and happy days.

    Working perfectly again.

    So, maybe I'll just stay put for a while and see what happens next. 

    Thanks very much to all who helped.

    regards,

    Ian. 

    Apple Mac Pro 2010 Sierra 12 Core 3.3 64GB RAM 1TB SSD BMD Studio Card. Esata 4 Port running G-Raid external drives USB 3 [view my complete system specs]
Page 1 of 1 (13 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller