[Ben Wharton]

Hi again.

Does anyone have an explanation for the lack of communication?

In the meantime I’ve captured material with Premiere Pro and then ingested that into Avid, but it won’t work for a certain issue which is capturing material from tapes with breaking timecode (due to faulty camera mechaism). I would like to ignore the timecode as per Avid’s capture tool functionality.

Alternatively is there another system which could capture the tapes? FCP creates new clips all the time which is not ideal – even joinig them all and then re-outputting to a single file I missing a lot of stuff.

Please, any pointers greatly appreciated.

Thanks.

Ben

[Ben Wharton]

Nope, it’s one of the many ‘standards’ that are being implemented in the distribution world at present.

For FCP7 you need a plugin to play it back / edit with it.

https://hamburgpromedia.com/products/mxf4mac/codecs/avc-intra-codec.php

Ben

[Ben Wharton]

Hi Shane (or anyone else out there)

I’m struggling to find a solution. Plugins by Calibrated don’t work in FCP7.0.3, Hamburg Pro’s plugin’s don’t seem to work…

Is there really no way to open AVCIntra in FCP7? The AAF import creates QT Reference files to the original MXF files.

Think I may need to get the project delivered in a different way…

Ben

[Ben Wharton]

Hi Shane

Thanks for the reply.

When you say ‘the option’ to transcode to ProRes, do you mean on the Avid System on when importing?

To transcode on my FCP system I surely need an MXF / AVC Intra plugin. And if the Avid system is PC, which I think it is, then normally you can’t write ProRes files although I know there is a new PC ProRes codec (although it comes up as not being optimised for FCP when importing files written with it and Cinema Tools doesn’t like it – so I’m wary!)

Am I missing something?

Thanks.

Ben

[Ben Wharton]

Looking around it seems like the Hamburg Pro AVC-Intra QT codec is the way to go? I’ve requested a trial but has anyone used this codec in anger?

Thanks again.

Ben

[Ben Wharton]

As far as I’m aware CinemaTools is dead under Lion / Mountain Lion.

So if it’s a part of your workflow, you’re only hope is Snow Leopard and if that will run on your hardware. SL does not have some of the drivers for the latest Mac hardware. 10.6.8 was the only version which would run on the first run of pre-installed Lion Macs (with a few button issues on Laptops).

Good luck.

Ben

[Ben Wharton]

HI Will

Thanks for the link to the instructions – I’d found it earlier. And luckily I do have a not so old iMac which can do the re-imaging for me.

But what you don’t say is what was your Mac? Was it a new laptop that was doing all those fun (bad) things under Lion? And now it works great?!

Still searchin!

Ben

[Ben Wharton]

Hi Kevin

Thanks for your reply – so are you saying that although you got SL with your MacPro, the model you have is in fact the same model I would get if I went and ordered one right now?

Actually I just checked and so you have a 17inch laptop. I’d be getting the 2.3 15inch.

Ok, really sounding promising but STILL after one person who:

A) had a new MacBook with Lion that was behaving badly

B ) Downgraded it to SL 10.6.8 and now it works great (with FCP 7.02/3) – no wifi issues, no terrible battery life, no mega heat-up/ 6500 rpm fans.

Anyone? Been asking for 2 weeks now…:-)

Ben

[Ben Wharton]

Hi Steve

Well according to Apple forums, your assumption isn’t quite right. New MacBook Pros ship with Lion and will not boot up with older system discs. The only version which they will work with is 10.6.8 – which doesn’t exist as a retail disk. And so for that you need to make a new boot disk with one of the Apple Server utility programs which can integrate say 10.6.3 with the 10.6.8 update.

But again, this isn’t the issue for me. Getting it done – I have plenty of instructions on. Knowing that it works and works for FCP I don’t know. i.e. trying to find someone who’s done it, and their laptop works great and he or she uses FCP professionally appears to be a major task.

So, do you know or does anyone else know have this experience and can tell me?

Waiting and hoping 🙂

[Ben Wharton]

Hi Ryan

This sounds like a colour space conversion issue plus possibly a gamma playblack issue. But I can’t tell you the exact nature of where it’s happening.

Are you staying RGB all the way or are you going from YUV originated to RGB? In your sequence settings render tab what is it set to in terms of dealing with colourspace types?

Also – playback – which OS are you using? Going to Snow Leopard, Apple decided to go from 1.8 Mac standard to 2.2 PC Gamma standard (I think!) and there’s (again I think) an “FCP mode” in Quicktime which can be on or off that does/does not do gamma correction when playing back within QuickTime.

So – one or both of the above might be causing the issues you’re seeing?

Ben