[Andy Taplin]

Thanks Don. trashed the prefs but still saying the clips are unavailable – anything else I could try?

[Andy Taplin]

Yes, I forgot about the slow shutter setting which my camera (PMW 350) has but I tend to think of it as a bit of a gimmick – useful for effects but not really useable as a proper shutter speed. As you say I’ll need to test the actual set up as anything else will just be guess work.

I’ve seen that phasing you mention, by the way, when shooting under flos, it also seems to phase the colour as well, really noticeable in a white lab.

[Andy Taplin]

Thanks Todd

With 60P isn’t anything less than 1/60th the same as having the shutter effectively off? Which is why I though 100th (or close to it) would cancel out the flicker from the flos giving me close to a 180º shutter angle and ‘standard’ motion blur for that frame rate.

Normally here in the UK I would shoot at 25P with a 50th shutter of 50P with a 100th shutter and would probably not experience any flicker issues.

[Andy Taplin]

That’s why I want all my data on a least 2 RAIDS now…anything can fail at any time! At least HD prices make it feasible now.

[Andy Taplin]

Thanks Floh

I have a g-tech eS external RAID 5 but I’ve found that disk reliability is not the real danger (enterprise drives at least are now really reliable) but problems with the RAID hardware/firmware. With the G-tech I suddenly could not write to the RAID although I could read, so I looked for another solution like the Drobo but this is better suited to backup than editing.

I will do my backups every day promise 🙂

[Andy Taplin]

I don’t use Media 100 suite or DVC PRO HD (I’m Media 100 13 with XDCAM and ProRes) but I would try this:

Open an original Media 100 media file and the AE rendered file in QT so they are side by side. If they look the same then obviously what looks to me like a gamma change is happening as you import back into M100. If they are different then AE has mangled the gamma. Once you’ve isolated the problem you can get working on the solution.

I would also try importing the P2 to M100 as Prores and rendering out of AE in Prores, maaybe the DVC Pro HD codec has some issues round tripping.

Best of luck, I’m sure Floh will have some advice as he uses a more up to date version of M100.

[Andy Taplin]

Are you working with the native P2 files or have you transcoded them to ProRes or Media 100 HD?

I usually use Prores for HD work and find no issues going to and from After Effects.

To set the comp to the right size drag the footage to the ‘create a new composition” icon at the bottom of the Project window and a new comp at the right size with the right pixel aspect (square usually) will be created. Render as Prores and you should see no difference whatsoever to the original file back in M100.

[Andy Taplin]

I can’t remember the error message, next time it happens I’ll write down the info. In the meantime I’ll update XDCAM transfer.

Thanks, Andy

[Andy Taplin]

Thanks Floh, I guessed that was the case.

It’s a weird problem, is the XDCAM transfer software to blame most likely? I’m using version 2.11.0

[Andy Taplin]

OK so my M100 is still crashing importing XDCAM but maybe I now have a clue as to the problem.

If I look in the M100 media folder at the clip that it crashes on, it says under ‘get info’ that it’s an NTSC video media file instead of the PAL file it should be. And the file name ends with V100.1 rather than just V100. The clip icon is also different. So is this because the file is corrupted during the failed import or does M100 suddenly ‘see’ an NTSC clip and then crash?

M100 only seems to crash like this if I import more than 4 or 5 clips at a time.

MAcPro 8 core 3ghz
OSX 10.5.8
Media 100 13.0.4
AJA Kona Firmware 6.0.2
Quicktime 7.6.6

Any ideas from Floh or Wicham?

Thanks Andy