Same Issue,

but it works with short bin names

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.)

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

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

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

  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.

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.

Last stable version was 2018.11

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

Has this bug ever been addressed?

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

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.

Thanks Marianna, NY

I'll keep waiting to update for now.

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.

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