Latest post Mon, Oct 18 2010 10:34 PM by cosmopost. 7 replies.
Page 1 of 1 (8 items)
Sort Posts: Previous Next
  • Thu, Sep 30 2010 3:57 AM

    ScriptSync License Bug

    We're having problems with the Scriptsync (SS) license in MC5032. Every now and then when activating SS to recognize our script, an error message indicates the system cannot locate the license and crashes the program. After rebooting, SS will properly function for 30 mins or so but then the license bug appears and crashes it again. SS worked fine initially after the SS license and dongles were updated, but the frequency of the crashes has increased dramatically over time. All four of our Nitris DX systems are hardware identical and Nexidia licensed, but the two stations on which SS is used the most have crashed the most. The other two stations which use SS less frequently are fine for the time being. Any thoughts?

     

    Intel Mac Pro 8-core, 8 gb RAM, MC 5032, Dongle License, Nitris DX, OS 10.6.3

    Mac Pro 8-core 2.8GHz Intel Xeon, 22GB RAM, 8800GT, Matrox Mini, Startech 3port Firewire pci express card, Atto Celerity FC-41ES, Keyspan usb twin serial... [view my complete system specs]

    Mac Pro 8-core 2.8GHz Intel Xeon, 10GB RAM, 8800GT, Mojo-SDI, Startech 3port Firewire pci express card, Atto Celerity FC-41ES, Keyspan usb twin serial adapter

  • Wed, Oct 6 2010 8:29 PM In reply to

    • cosmopost
    • Not Ranked
    • Joined on Wed, Oct 6 2010
    • Posts 5
    • Points 45

    Re: ScriptSync License Bug

    We're having precisely the same license issue along with some other bugs.  One error message says Disks_Too_Many and shows an mxf file name after.  Our assistant editor can work for about 20 minutes and gets one of these two errors.  Once he got both errors at the same time. 

    We've tried doing this with or with out scriptsync activated.   When the assistant is trying to program a script manually we can get the crash and also when we have the script scync license activated we get the same error.

    Please let us know if you can find any solution.  

    We've tried replacing computers entirely.  This seems to be a software bug in 5.0.   

    Next step is to use a dual boot and program the script in 4.0 software prior to giving it to the editor to work on.

     

  • Wed, Oct 6 2010 8:36 PM In reply to

    • cosmopost
    • Not Ranked
    • Joined on Wed, Oct 6 2010
    • Posts 5
    • Points 45

    Re: ScriptSync License Bug

    Here's our system config

     

    Unity 16 TB - fiber connections

    v5.2 Unity Clients

    3 systems with Nitris DX

    1 system software only

    MC v 5.0.3.4

    XDCAM HD format dialies edited natively

    8 gig ram 8-core Macs

     

  • Wed, Oct 6 2010 9:01 PM In reply to

    • mschneider
    • Not Ranked
    • Joined on Thu, Oct 13 2005
    • PostWorks, New York
    • Posts 38
    • Points 470

    Re: ScriptSync License Bug

     

    We too have a client with the same problem. Same error and frequence, similar or identical setup.

     

    Does anyone have further information on this?

    Matt

    Matthew Schneider Director of Technology PostWorks, New York 100 Avenue of the Americas, 10th Floor New York, NY 10013 212.894.4000 (work) 347.672.4192 (cell) mscheider@postworks.com

  • Wed, Oct 13 2010 3:45 AM In reply to

    • cosmopost
    • Not Ranked
    • Joined on Wed, Oct 6 2010
    • Posts 5
    • Points 45

    Re: ScriptSync License Bug

    So far today we seem to have a temporary fix.  We unlicensed the software on the first assistant's system.  Pulled out the dongle and the folks at AVID gave us a software only (node based - non-dongle) license to try. 

    For most of the day we were able to use scriptsync without crashing.  After about 5 hours of uptime, we had a kernel panic crash while scripting.  It's unclear what the cause of the crash was.  We've gone back to using version 4 in that room since we have a tight schedule to keep.

    We took the same approach mid-day on a different system with a different assistant editor and had a few hours of solid scripting using version 5 and no problems.  We'll see what the day brings tomorrow, but it's possible that avoiding the dongle solves the problem.

    Here's the procedure we used.

    With AVID V5 Running and a script open, we unlicensed the Scriptsync without checking the box to remove it from the computer.    We then quit and pulled out the dongle.  We then restart the computer and license MC using the internet and plugged in a software (non-dongle) license serial number.

    Run AVID V5, open the script and re-license the Scriptsync software (If necessary. I don't remember if we had to do this or if it found the previous license.).  

    Then, back to work in AVID 5.  Wish us luck!

     

  • Mon, Oct 18 2010 9:10 PM In reply to

    Re: ScriptSync License Bug

    We came up with a similar workaround. We've unplugged the hardware dongle and let MC5 operate under the 30-day trial software license. Several days of no crashing thus far. Hopefully Avid can figure thgis out before our trial period expires. Incidentally, our one system that ScriptSyncs less often continues to work perfectly well with the hardware dongle. Jus' lucky I guess (insert sarcastic emoticon here).

    cosmopost:

    So far today we seem to have a temporary fix.  We unlicensed the software on the first assistant's system.  Pulled out the dongle and the folks at AVID gave us a software only (node based - non-dongle) license to try. 

    For most of the day we were able to use scriptsync without crashing.  After about 5 hours of uptime, we had a kernel panic crash while scripting.  It's unclear what the cause of the crash was.  We've gone back to using version 4 in that room since we have a tight schedule to keep.

    We took the same approach mid-day on a different system with a different assistant editor and had a few hours of solid scripting using version 5 and no problems.  We'll see what the day brings tomorrow, but it's possible that avoiding the dongle solves the problem.

    Here's the procedure we used.

    With AVID V5 Running and a script open, we unlicensed the Scriptsync without checking the box to remove it from the computer.    We then quit and pulled out the dongle.  We then restart the computer and license MC using the internet and plugged in a software (non-dongle) license serial number.

    Run AVID V5, open the script and re-license the Scriptsync software (If necessary. I don't remember if we had to do this or if it found the previous license.).  

    Then, back to work in AVID 5.  Wish us luck!

     

     

    Mac Pro 8-core 2.8GHz Intel Xeon, 22GB RAM, 8800GT, Matrox Mini, Startech 3port Firewire pci express card, Atto Celerity FC-41ES, Keyspan usb twin serial... [view my complete system specs]

    Mac Pro 8-core 2.8GHz Intel Xeon, 10GB RAM, 8800GT, Mojo-SDI, Startech 3port Firewire pci express card, Atto Celerity FC-41ES, Keyspan usb twin serial adapter

  • Mon, Oct 18 2010 9:49 PM In reply to

    Re: ScriptSync License Bug

    There is a bug regarding ScriptSync licensing that Avid is working on.  I'm not sure this is related to your issue, but it might be worth trying.

    First, delete the following folders (Mac only):

    HD\Library\Application Support\Avid\SWL

    HD\Library\Application Support\Avid\Pixie

    Then, indirectly activate the ScriptSync license:

    1.       In the ScriptSync Activation Dialog box, select the option to Activate from another computer
    2.       Go to http://activate.avid.com  (You can do this on the editing system or on another computer.)
    3.       Enter in the Machine ID, System ID, and ScriptSync serial number
    4.       Take the Activation code that is generated back to the editing system

    Does this solve your issues?

    Symphony v8.8 | OS 10.11.6 • Nitris DX • 12-core MacPro (Mid 2012) • 36 GB RAM • Facilis Terrablock 24EX [view my complete system specs]

    -- Kevin

  • Mon, Oct 18 2010 10:34 PM In reply to

    • cosmopost
    • Not Ranked
    • Joined on Wed, Oct 6 2010
    • Posts 5
    • Points 45

    Re: ScriptSync License Bug

     

    I think we're basically taking the same approach.  Since the bug seems to be related to the dongle, we un-license the scriptsync and then pull the dongle.  We then get AVID to provide an actual software license serial numbers for MC and authenticate using it so we have no dongle at all.  We then activate scripsync with its serial number.  Thus far, this seems to be the solution.  No dongle=no problems.

Page 1 of 1 (8 items)

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