Latest post Wed, Jun 26 2019 3:33 AM by Jared. 9 replies.
Page 1 of 1 (10 items)
Sort Posts: Previous Next
  • Tue, Jan 8 2019 8:32 PM

    • chuckkahn
    • Top 500 Contributor
    • Joined on Thu, Oct 13 2005
    • Toronto
    • Posts 363
    • Points 3,995

    shared storage considerations re: Background Bin Auto-Save?

    Are there any special considerations for the new AMC v2018.12 Background Bin Auto-Save feature with regards to ISIS 5500 shared storage environments?   I Bin Settings I changed Auto-Save interval, Inactivity period and Force Auto-Save to 1, 1 and 2 seconds.

     

    I notice this new notification comes up after installing 2018.12:

     

    "creating bin snapshot for background save"

     

     

    Avid Media Composer 2018.11 / MacOS High Sierra / iMac (Retina 5K, 27-inch, 2017) / 4.2 GHz Intel Core i7 / 64 GB 2400 MHz DDR4 [view my complete system specs]
  • Sat, Jan 12 2019 10:48 PM In reply to

    • Thomas
    • Not Ranked
    • Joined on Sun, Feb 23 2014
    • Cologne
    • Posts 52
    • Points 715

    Re: shared storage considerations re: Background Bin Auto-Save?

    Please don not use it. 

    This feature saves our Bins with 0kb! Also in the Attic-Folder! Already the second workstation has got infacted by that problem. So we deactivated BackgroundBinSave in the Console. But hey what a disaster is this? It is not a real Background save. It is saving in an temporal bin and when it wants to write the original bin it can´t because the "lck" (Bin-lock) File! So this is not working at Windows. With Mac we had another Issue: When we rendered Sequences and saved them via Background BinSave and closed the Bin and opened the Bin on another Windows workstation, then always the last ca. 50 effects of the sequence which has been rendered are not rendered / or the renderfiles have not been saved.
    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

  • Sat, Jan 12 2019 10:52 PM In reply to

    • chuckkahn
    • Top 500 Contributor
    • Joined on Thu, Oct 13 2005
    • Toronto
    • Posts 363
    • Points 3,995

    Re: shared storage considerations re: Background Bin Auto-Save?

    All our Avids are on Mac here and I'm the only one running 2012.12 with background save and I haven't seen these issues your describe.   So that's a Windows only issue?

    Avid Media Composer 2018.11 / MacOS High Sierra / iMac (Retina 5K, 27-inch, 2017) / 4.2 GHz Intel Core i7 / 64 GB 2400 MHz DDR4 [view my complete system specs]
  • Sat, Jan 12 2019 11:12 PM In reply to

    • Thomas
    • Not Ranked
    • Joined on Sun, Feb 23 2014
    • Cologne
    • Posts 52
    • Points 715

    Re: shared storage considerations re: Background Bin Auto-Save?

    Yes it is a windows issue.

    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

  • Sat, Jan 12 2019 11:32 PM In reply to

    • Thomas
    • Not Ranked
    • Joined on Sun, Feb 23 2014
    • Cologne
    • Posts 52
    • Points 715

    Re: shared storage considerations re: Background Bin Auto-Save?

    Do you use Mac Mini late 2018 with MC2018.12?

    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

  • Sat, Jan 12 2019 11:37 PM In reply to

    • chuckkahn
    • Top 500 Contributor
    • Joined on Thu, Oct 13 2005
    • Toronto
    • Posts 363
    • Points 3,995

    Re: shared storage considerations re: Background Bin Auto-Save?

    No, I use a MacPro5,1.

    Avid Media Composer 2018.11 / MacOS High Sierra / iMac (Retina 5K, 27-inch, 2017) / 4.2 GHz Intel Core i7 / 64 GB 2400 MHz DDR4 [view my complete system specs]
  • Sat, Jan 12 2019 11:51 PM In reply to

    • Thomas
    • Not Ranked
    • Joined on Sun, Feb 23 2014
    • Cologne
    • Posts 52
    • Points 715

    Re: shared storage considerations re: Background Bin Auto-Save?

    MacPro 5.1 really? How about realtime performance and rendertimes?  I think MacPro 6 is allready very slow. But if it works - fine.

    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, Feb 8 2019 9:48 AM In reply to

    • Freddy
    • Top 500 Contributor
    • Joined on Sun, Nov 5 2006
    • Sweden
    • Posts 255
    • Points 3,050
    • Avid Employee

    Re: shared storage considerations re: Background Bin Auto-Save?

    I would suggest using the latest Nexis Client, instead of the old ISIS Client.

    The newer more optimized Nexis Client is compatible with ISIS 5000, and ISIS 5500. (Make sure your ISIS 5K is updated to the latest 4.7.11).

    You can get it from: http://esd.avid.com

     

    http://www.freddylinks.com <-- Find EVERYTHING Avid and Tutorials there. Probably the most comprehensive Avid only webpage with over 2000+ Links to Avid Video Tutorials and Avid Information for Media Composer, NewsCutter, Symphony, Interplay, ISIS, Unity MediaNetwork, ProTools, Avid Artist Series. Completely free of fees, registrations, and ads.

  • Sun, Feb 10 2019 8:46 PM In reply to

    • chuckkahn
    • Top 500 Contributor
    • Joined on Thu, Oct 13 2005
    • Toronto
    • Posts 363
    • Points 3,995

    Re: shared storage considerations re: Background Bin Auto-Save?

    Who are you responding to? I'm on Nexis Client 7.11.0.

     

    Freddy:

    I would suggest using the latest Nexis Client, instead of the old ISIS Client.

    The newer more optimized Nexis Client is compatible with ISIS 5000, and ISIS 5500. (Make sure your ISIS 5K is updated to the latest 4.7.11).

    You can get it from: http://esd.avid.com

     

     

    Avid Media Composer 2018.11 / MacOS High Sierra / iMac (Retina 5K, 27-inch, 2017) / 4.2 GHz Intel Core i7 / 64 GB 2400 MHz DDR4 [view my complete system specs]
  • Wed, Jun 26 2019 3:33 AM In reply to

    • Jared
    • Not Ranked
    • Joined on Tue, Aug 15 2017
    • Posts 10
    • Points 100

    Re: shared storage considerations re: Background Bin Auto-Save?

    I'm on Nexis shared storage and background bin save seems to be working as expected, except with a script. When I have one script open (48,000K) I get interrupted with a save progress bar in the foreground while I'm working. I've broken that script into two parts so they are smaller in file size and the same issue persists, although it seems to be less frequent.

    I've also noticed that as the day goes on, after a certain amount of time, background bin saving seems to stop happening in the background. Again, the bins are saving to the attic, just not in the background.

    Is there any correlation between bin/script size and the issues I've described above? Is there a cache of some sort that might be filling up and preventing bins from saving in the background, related to bin size or how long Media Composer has been running? Has anyone else run into a similar issue?

    Thanks.

Page 1 of 1 (10 items)

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