Latest post Fri, Apr 5 2019 1:58 PM by Timo B.. 38 replies.
Page 3 of 3 (39 items) < Previous 1 2 3
Sort Posts: Previous Next
  • Mon, Apr 1 2019 9:27 AM In reply to

    • balke
    • Not Ranked
    • Joined on Thu, Mar 6 2014
    • Posts 1
    • Points 15

    Re: Background Bin Save is a disaster

    Same Issue,

    but it works with short bin names

  • Tue, Apr 2 2019 2:02 PM In reply to

    • NYnutz
    • Top 500 Contributor
    • Joined on Wed, Nov 25 2009
    • New York City
    • Posts 356
    • Points 4,210

    Re: Background Bin Save is a disaster

    balke:

    Same Issue,

    but it works with short bin names

     

     

    Balke, great call on long bin names. For the first time, i have been able to replicate this behavior in a new project by creating bins with very long names and triggering a background save operation by modifying the contents (in my case, updating the assets from production management.)

     

     

    Dave

    Post Production Infrastructure Engineer

    "A very big network"

     

  • Tue, Apr 2 2019 2:27 PM In reply to

    • Marianna
    • Top 10 Contributor
    • Joined on Thu, Oct 13 2005
    • Avid
    • Posts 10,284
    • Points 219,195
    • Avid Beta Moderators
      Avid Customer Advocate
      Avid Developer Moderator
      BlogAuthor
      SystemAdministrator

    Re: Background Bin Save is a disaster

    NYnutz:

    balke:

    Same Issue,

    but it works with short bin names

    Balke, great call on long bin names. For the first time, i have been able to replicate this behavior in a new project by creating bins with very long names and triggering a background save operation by modifying the contents (in my case, updating the assets from production management.)

    Anyone know how many characters in a bin name causes it to crap out?

    Marianna

    Director of Online Communities and Forums/Customer Advocate [view my complete system specs]

    marianna.montague@avid.com

    mobile 813-493-6800

    Twitter:  avidmarianna

    Facebook: Marianna Montague

    www.avidcustomerassociation.com   |  Connect 2019 | April 6-7 | Aria, Las Vegas, NV

    WWLD

  • Tue, Apr 2 2019 9:49 PM In reply to

    • NYnutz
    • Top 500 Contributor
    • Joined on Wed, Nov 25 2009
    • New York City
    • Posts 356
    • Points 4,210

    Re: Background Bin Save is a disaster

    Haven't had a chance to test scientifically yet. will try to get some results back tomorrow. 

    Dave

    Post Production Infrastructure Engineer

    "A very big network"

     

  • Thu, Apr 4 2019 9:00 PM In reply to

    • luca.mg
    • Top 25 Contributor
    • Joined on Thu, Oct 13 2005
    • Roma - Italy
    • Posts 5,582
    • Points 65,470

    Re: Background Bin Save is a disaster

    Sorry for asking: do You think it's safe to upgrade to 2018.12.3, keeping the bin names short? Stick out tongue

    Symphony 2018.12.3, BM Intensity Pro 4k, Windows 10, i7-5930K, 32 GB ram, Quadro K620 [view my complete system specs]

    peace luca

  • Thu, Apr 4 2019 9:47 PM In reply to

    • Thomas
    • Not Ranked
    • Joined on Sun, Feb 23 2014
    • Cologne
    • Posts 49
    • Points 670

    Re: Background Bin Save is a disaster

    Big Smile  Not really. We are all Beta-Testers. Feel free and help Avid develop their products or stay more safely with older versions...

     

    Fixed in Media Composer v2018.12.3

    The following have been fixed:

    • ➤  Bug Number: MCCET-2919. The editing application would crash intermittently when trimming with Motion Effects in the Timeline.

    • ➤  Bug Number: MCCET-2916. In some instances, you would receive an exception error when working with keyframes in the Motion Effect Editor.

    • ➤  Bug Number: MCCET-2892. In some instances, playback would stop after adding an Audio Mark IN/OUT.

    • ➤  Bug Number: MCDEV-10686. Clicking on the checkbox for “Enable Mask Margin” or “Include Inactive Audio Tracks” in the AAF export dialog did not enable the options.

    • ➤  Bug Number: MCCET-2772. Clips may not have updated properly if you batch imported with Dynamic Relink enabled.

    • ➤  Bug Number: MCCET-2895. On some systems, the memory usage would increase until the editing application became sluggish.

    several Avid Workstations, Baselight One [view my complete system specs]

    Thomas Poerschke, Editor & Colorist

    ColorGrading.TV @ MMC Studios Köln, Am Coloneum 1, 50829 Cologne, Germany
    web: www.colorgrading.tv

  • Fri, Apr 5 2019 8:54 AM In reply to

    • luca.mg
    • Top 25 Contributor
    • Joined on Thu, Oct 13 2005
    • Roma - Italy
    • Posts 5,582
    • Points 65,470

    Re: Background Bin Save is a disaster

    I know beta testing is not like it used to be... In the middle of a gig right now, not taking this step at the moment. Thank You for the feedback.

    Symphony 2018.12.3, BM Intensity Pro 4k, Windows 10, i7-5930K, 32 GB ram, Quadro K620 [view my complete system specs]

    peace luca

  • Fri, Apr 5 2019 10:06 AM In reply to

    • Thomas
    • Not Ranked
    • Joined on Sun, Feb 23 2014
    • Cologne
    • Posts 49
    • Points 670

    Re: Background Bin Save is a disaster

    Last stable version was 2018.11

    several Avid Workstations, Baselight One [view my complete system specs]

    Thomas Poerschke, Editor & Colorist

    ColorGrading.TV @ MMC Studios Köln, Am Coloneum 1, 50829 Cologne, Germany
    web: www.colorgrading.tv

  • Fri, Apr 5 2019 1:58 PM In reply to

    • Timo B.
    • Not Ranked
    • Joined on Fri, Dec 9 2011
    • Posts 3
    • Points 25

    Re: Background Bin Save is a disaster

    Hi Marianna,

    I keep the bin-names-character-count less then 27 ... since then I am able to work again.

    Regards,

    Timo

     

    PS. reminds me of the Apple Ad: C:\ONGRTLNS.W95

Page 3 of 3 (39 items) < Previous 1 2 3

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