So I've come across something weird now that I'm starting to us MXF on a consistant basis as opposed to OMF.  I wonder if anyone has any insight into this.

So I'm capturing MXF media to a unity.  I usually keep my max capture time to 65 minutes.  Now I've come across the problem that when I try to capture to the unity without creating in and out marks, I get an error message stating "MVL_insufficient space".  I made sure that I had enough space to capture up to 65 minutes, as I first thought that maybe that's why it wouldn't let me (even though OMFs would).  But I did have enough to capture at least 65 minutes worth, and then some.  If I created in and out marks, I could capture fine.  If I changed to OMF, I could capture fine.  I had to capture to my local drive, and then consolidate over to the unity to be able to get it to work with MXF.

I recently did some testing, and I found out that if I want to keep my max captur to MXF at 65 minutes, I had to make sure that my unity workspace had enough room to capture at least 85 minutes.  So I thought, maybe you always need 20 minutes more than your max capture is set for.  So I set my unity workspace to have only enough space to capture 37 minutes.  So I figured the maximum amount of my MXF could be 17 minutes...but it actually let me set it up to 29 minutes without giving me a problem.  If I set it to capture 30 minutes, it would give me the insufficient space error.  So in that case, I only needed 8 minutes extra then what my max capture was set for.

So long story short, is there some specific percentage or anything between how much space you have available on your drives and what your maximum capture time for MXF is (the one found in the Capture settings) that allows you to capture on the fly (without ins and outs) without giving you that insufficient space error?  Anybody else ever come across this?

BUMP