Latest post Thu, Feb 21 2008 1:46 AM by jdw. 6 replies.
Page 1 of 1 (7 items)
Sort Posts: Previous Next
  • Wed, Jan 23 2008 8:19 PM

    • jdw
    • Top 500 Contributor
    • Joined on Thu, Oct 13 2005
    • Posts 363
    • Points 4,435

    2.8 save bug?

    Just wondering if anyone out there is experiencing this...

    2.8 on 10.4.11

    when hitting command s to save, everthing saves properly. Don't change anything and hit command s again and it saves everything again. In the past, if there was nothng to save, it wouldn't rifle through all the open bins...
    MC 2018.9 OS 10.13.6 ISIS 7000 (2018.6.1) [view my complete system specs]
  • Wed, Jan 23 2008 8:43 PM In reply to

    Re: 2.8 save bug?

    Pretty sure it's always done that to me jdw.  My Avid has always been an equal opportuniy saver.
    Blackmagic UltraStudio 4K, 12-Core MacPro, 64 GB RAM, 24 TB Thunderbolt Storage [view my complete system specs]

    Conformity is the jailer of freedom and the enemy of growth. Motion Inc

  • Tue, Feb 19 2008 2:34 AM In reply to

    • double-g
    • Not Ranked
    • Joined on Thu, Feb 2 2006
    • Posts 15
    • Points 195

    Re: 2.8 save bug?

    I'm pretty sure this is new behavior. Immediately after upgrading from 2.7.3 to 2.8, we saw every bin opened with the diamond icon in the bin's title bar. Figured it might be some change to the bin structure between 2.7 and 2.8, but even after everything has been saved over in 2.8, the behavior continues...
  • Tue, Feb 19 2008 2:56 PM In reply to

    Re: 2.8 save bug?

    Wanted to double-check this myself, running 2.8.

    If the project window is active, command+S will force an autosave of all bins, even if nothing has changed.

    If a bin is active, hitting command+S will ONLY save the bin if something changed.  (The diamond is not in the bin name if nothing has changed.)

    I don't know when this changed, but our Meridien systems don't act this way.  The only save when something changes, regardless of the active window.

    It's important to note because if you don't have enough bins setup for your Attic, you can very quickly only have a few minutes worth of changes if you actively save.





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

    -- Kevin

  • Tue, Feb 19 2008 3:49 PM In reply to

    Re: 2.8 save bug?

    My MC 2.7.5 system at home exhibits this exact behavior... I think it's been this way for awhile.
    Blackmagic UltraStudio 4K, 12-Core MacPro, 64 GB RAM, 24 TB Thunderbolt Storage [view my complete system specs]

    Conformity is the jailer of freedom and the enemy of growth. Motion Inc

  • Tue, Feb 19 2008 3:55 PM In reply to

    • BLKDOG
    • Top 10 Contributor
    • Joined on Thu, Oct 13 2005
    • Lansing, MI
    • Posts 17,731
    • Points 226,405
    • Avid Employee
      Moderator: MCA Mac
      Moderator: MCA PC

    Re: 2.8 save bug?

    It SHOULD behave exactly as Kevin Describes above. The only time that currently saved bins should force-save again is when you select to save with the Project window active.
    Project Manager, Avid Professional Services - Americas [view my complete system specs]

    In agreement, Unity. In Disagreement, Discussion. In all things, Charity.


  • Thu, Feb 21 2008 1:46 AM In reply to

    • jdw
    • Top 500 Contributor
    • Joined on Thu, Oct 13 2005
    • Posts 363
    • Points 4,435

    Re: 2.8 save bug?

    Select a bin in 2.8, make a change and save. It will save. Don't change anything. With that same bin selected, hit save again...it will save again. This is new.
    MC 2018.9 OS 10.13.6 ISIS 7000 (2018.6.1) [view my complete system specs]
Page 1 of 1 (7 items)

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