We were on 2018.12.3 and i upgraded our suites to the patch release 2018.12.6 and upgraded our NEXIS Client to 19.6.x from 19.2.2 and the problem has gone for us. I'll bear this reccomendation in mind to bring us up to the above, 

Job ter Burg:

Just a stab in the dark: how full is your Attic folder?

20Gb mate with 100gb free on SSD.  I've offloaded it all anyway now. Cheers

Progress of sorts - at least it is TELLING me in 2018.12.7 that it isnt actually saving:

How the hell do i fix this?

If this background save does turn out to be the problem, I think Avid should remove all the versions effected by this bug from their download servers.

This is about as severe a bug as you can have in a program and Avid should hold their hands up to this one and issue a statement to users.

Having this buried in a long list of potential issues (which many people don't bother to read until something goes wrong) is not going to win them any fans!

DIESELE:

Progress of sorts - at least it is TELLING me in 2018.12.7 that it isnt actually saving:

 

 

How the hell do i fix this?

Is this with background save switched off?

In addition to checking Background Bin Save I would look into any effects added to your sequence just before these problems begun to arise,

I hope support did not actually suggest you to update to a .8 version that hasn't been released yet. I'm also impatiently waiting for it as the  announced fixes can make a lot of the angry people in my phone more happy but there are still differences between wisful thinking and fairytales.

Two hours with support guys...

Rolled back to 2018.12.3, patched with a Beta 2018.12.8 and it seems fixed, albeit Beta (so who knows what else may crop up).  Effects saved to bins seem to work properly now when dropped back onto timeline and it carries all keyframes over.

Issue comes up randomly and ocassionally with using Resize Effect so - DONT USE THE BASIC RESIZE EFFECT.

Believe fixed in the full and imminent 2018.12.8

Sucesfully saving your work is THE absolute basic and this seismic issue has been around WAY too long from what I see. Rarely been so disheartened in this game.

Diesele.....

that is the version we will release next week.  Teeing up the mod squad soon to begin the download testing then it shoud be good to go next week.  

Marianna

If this is another issue with background save, add it to the growing flaming pile. I've long since given up on trying to get support to listen to any complaints about it, and instead, have deployed preferences to all systems to permanently disable it. 

I'd like to take this thread of topic for a moment and Marianna, am kind of hoping you can make some comments on the following.

DIESELE:

Rolled back to 2018.12.3, patched with a Beta 2018.12.8 and it seems fixed, albeit Beta (so who knows what else may crop up).  Effects saved to bins seem to work properly now when dropped back onto timeline and it carries all keyframes over.

Issue comes up randomly and ocassionally with using Resize Effect so - DONT USE THE BASIC RESIZE EFFECT.

That the beta version works is good news and let's be positive for once and also believe that it will also be fixed for the Resize Effect.

What is news for me is Avid support actually putting a beta version on a user's machine that is used for actual productions, not a testing machine of a registered beta tester. While I consider the Avid media composer user base 'involuntary beta testers' for years now, actually allowing that 'title' to be acknowledged from Avid's side might be beneficial. 

Marianna, the bugs that have made it to actual releases the last few years have negatively affected my perception of Media composer, Nexis and Mediacentral and the Avid brand as a whole and in this thread the reactions of Bruno, DIESELE and NYnutz also shows their frustration. It is my believe that allowing support to distribute beta versions to end customers and resellers and allowing their feedback and test results to be part of the development cycle is a good idea, especially if a developer is allowed to directly interact with those customers. How this practically is organized goes beyond what can be discussed here, but was this distribution of a beta version in this case an exception or is there actually some room for change?

Jeroen, I think giving me a Beta was a last resort as they had no other fixes on Resize effect killing all background saves.  I note complaints back in January about a similar issue too - ten months (just put 'avid background bin save' in Google and note the first result )

Personally I have no wish to be a Beta tester as am far too busy feeding my kids through my suite!  I try to keep a few versions back - but its tricky as you often need the fixes the new versions bring! I was specifically told not to share the patch with anyone as it was pre prod!  Fernando in support nailed it when the first guy hoped I'd go away and told me to load 2018.12.8 which was unobtaibnable .

I appreciate them fixing me up rather than allowing protocol let me wait and suffer with lost timeline anxiety!

Sad to say, but after 35+ years I've always felt I was a un-compensated beta tester for all the software I bought, except Adobe—which seems to be able to release pretty solid stuff. I'm confused as to Avid's new monthly release policy and now that's branched into 2019.X and 2018.X versions. Based on the posts I see it just seems to be bug or feature patches and sometimes create new bugs while fixing others. I would never upgrade every month, I don't see how this is of benefit to anyone and a lot of work for their team. I don't see how they could possibly QC these releases. But greater minds than mine think this is a good plan. :)  

Its not much help I know but my stock AVid teaching is to work sequences between two bins.

Duplicated from the record monitor to the alternate bin. 

That way final sequences are saved across two bins so a crash and fouled up bin leaves one intack.

But the lack of feedback on a background save is a real issues currently.

Top tip Pat and I do do that and drag stuff to an 'emergency backup' bin and immediately close it as we can all get the once in a blue moon timeline corruption.  I did in fact do this in this current context (after initial loss) but it didnt help at all as no bins actually saved.

My 2018.12.8 patch is solid so far meantime - its also great having saved effect keyframes that actually work when dropped on the timeline! Another 101 basic that should never have been corrupted in the name of progress