Latest post Mon, Jul 15 2019 3:30 PM by Jeroen van Eekeres. 73 replies.
Page 3 of 5 (74 items) < Previous 1 2 3 4 5 Next >
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 25

    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 371
    • Points 4,385

    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,520
    • Points 222,175
    • 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 371
    • Points 4,385

    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,610
    • Points 65,805

    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 52
    • Points 715

    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.

    Doing regular manual saves are still the only way to be sure your work is secure and its a trick old school editors won't drop. [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,610
    • Points 65,805

    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 52
    • Points 715

    Re: Background Bin Save is a disaster

    Last stable version was 2018.11

    Doing regular manual saves are still the only way to be sure your work is secure and its a trick old school editors won't drop. [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 35

    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

  • Wed, Jun 12 2019 6:15 PM In reply to

    • ManChicken
    • Top 500 Contributor
    • Joined on Mon, Feb 4 2008
    • Denver, CO
    • Posts 261
    • Points 3,310
    • Moderator: MetaFuze

    Re: Background Bin Save is a disaster

    Has this bug ever been addressed?

  • Wed, Jun 12 2019 7:42 PM In reply to

    • Marianna
    • Top 10 Contributor
    • Joined on Thu, Oct 13 2005
    • Avid
    • Posts 10,520
    • Points 222,175
    • Avid Beta Moderators
      Avid Customer Advocate
      Avid Developer Moderator
      BlogAuthor
      SystemAdministrator

    Re: Background Bin Save is a disaster

    Manchick....

    2 bugs associated with this..... 

    MCCET-2927 Intermittently, saving bin result to an Exception and can cause corruption - this was fixed in 2018.12.4

    MCDEV-10123  Background bin save: Bins remain marked as dirty after re-opening the project - still working on it.

    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

  • Wed, Jun 12 2019 9:09 PM In reply to

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

    Re: Background Bin Save is a disaster

    can confirm that in MC 2018.12.5 (on macos 10.13.6 or 10.14.3/4), background bin save still results in bins disappearing from the project window and not reappearing until after the bin is closed. Have not seen repeats of 0kb/corrupt bins or 0KB attic files.

    Dave

    Post Production Infrastructure Engineer

    "A very big network"

     

  • Mon, Jun 17 2019 4:38 PM In reply to

    • ManChicken
    • Top 500 Contributor
    • Joined on Mon, Feb 4 2008
    • Denver, CO
    • Posts 261
    • Points 3,310
    • Moderator: MetaFuze

    Re: Background Bin Save is a disaster

    Thanks Marianna, NY

    I'll keep waiting to update for now.

  • Mon, Jun 17 2019 11:53 PM In reply to

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

    Re: Background Bin Save is a disaster

    have now seen reoccurrance of 0KB bins. going back to enforcing all editors enter a console command every time they launch media composer...

     

    I would have back-revved to 2018.11, but apple disallows us from downgrading newly purchased machines to 10.13.6 from 10.14.3. yay security.

    Dave

    Post Production Infrastructure Engineer

    "A very big network"

     

  • Wed, Jun 26 2019 11:20 PM In reply to

    Re: Background Bin Save is a disaster

    We also confirm experiencing this issue on MC 2018.12.3. Running 2013 Mac Pro on Mac OS 10.12.6. Shortening Bin names is a reliable workaround.

     

    -EB

Page 3 of 5 (74 items) < Previous 1 2 3 4 5 Next >

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