Cinema Tools won't conform P2 footage-Temporal Compression Error

S

Strangepork

New member
Hello all,
I am using FCP 6 with latest updates, on a MBP importing my P2 cards as usual. I am conforming my 720p60 footage to 25fps for delivery through Cinema Tools. worked fine last week, now I cannot conform my footage. all my QT files are moved to the "skipped" folder, the log shows that they have "temporal Compression" and cannot be processed to 25fps.

the QT clip info shows 50mb/s while
cinema tools analysis shows 5 mb/s

When I export a clip from QT using "same settings" the clip will then conform fine.

My question: is there a P2 driver update I need to get my workflow working again?

I have searched over all online, and cannot find a solution.

Thanks.
Anthony
 
Hi, the same problem for me.
I think that it's happened from new "application support" upgrade.
If you export from QT to Pro res, then Cinema Tools works fine.
But the workflow becomes complicated.
If you have any answers, please contact me.
Thanks
Ale Beltrame
 
me too

me too

same issue: getting a 'temporal compression' issue with DVCPRO-HD files from my firestore that I'm trying to conform from 60 to 24 fps.

But i'm not completely sure it's not a firestore operator error.

Has anyone else experienced this as well - DVCPRO-HD imported thru 'log and capture' into FCP, being flagged as "normal quality with temporal compression" instead of "maximum quality"?

The "Normal quality w/Temp comp" doesn't make sense, does it? I mean DVCPRO-HD doesn't have a variable quality setting, does it?
 
An update:

The problems described in my previous post were experienced on a Mac Pro, with all software fully current (FCP 6.0.3, OSX 10.5.2, etc).

I hooked up the Firestore to my older PowerBook, also sys 10.5.2, but with an older FCP (5.1.4). After importing the files thru FCP, I copied them to the Mac Pro, where the files were able to be conformed normally in Cinema Tools. In other words the same files had been imported without any 'temporal compression' flag.

So something appears to be broken in the recent update (6.0.3 and associated support files), because the Mac Pro worked normally for this process about six weeks ago before I upgraded everything.
 
Evening Films said:
An update:

The problems described in my previous post were experienced on a Mac Pro, with all software fully current (FCP 6.0.3, OSX 10.5.2, etc).

I hooked up the Firestore to my older PowerBook, also sys 10.5.2, but with an older FCP (5.1.4). After importing the files thru FCP, I copied them to the Mac Pro, where the files were able to be conformed normally in Cinema Tools. In other words the same files had been imported without any 'temporal compression' flag.

So something appears to be broken in the recent update (6.0.3 and associated support files), because the Mac Pro worked normally for this process about six weeks ago before I upgraded everything.
Click to expand...


You might also look at Raylight MXFX for Mac, which can batch process add/remove pulldown, change from 25 to 24 fps, and some other useful things. It read and writes MXF files and preserves the metadata. http://dvfilm.com/MXFX
 
mvb said:
You might also look at Raylight MXFX for Mac, which can batch process add/remove pulldown, change from 25 to 24 fps, and some other useful things. It read and writes MXF files and preserves the metadata. http://dvfilm.com/MXFX
Click to expand...

Thanks for the tip, Marcus. I've used DV Film Maker for years. I didn't realize that Raylight was available for Mac - is that a fairly recent addition?

--Hans
 
Evening, I am suffering this error since a couple of months, while my FCP was still 6.02.
in a Mac Pro.

I tried the same in my old powerbook and it didnt work. Also in a G5. Its final cut for sure, or firestore. I will try to extract the mxfs in other way than fcp, and see what happens.
jaa
 
Bump -- any new insights on this thread? Anyone else having (or not having) this problem?

I've upgraded to QT 7.5 and OSX 10.5.3 with no fix for this issue.
 
Bump again. Still getting the "temporal compression" futz on DVCPROHD 720/60 files transferred in FCP 6.0.4.

Anyone else -- confirm, refute, anything?

Pain in the a** to have to load my files using my old PBook, FCP 5.1.4 -- about three times slower, have to copy the files, and... I shouldn't have to jump thru this hoop anyway!
 
Yes! I just had this issue and it's actually my first time shooting in HDV and I'm really freaking out.

My friend said all I had to do was use Cinema Tools for the batch conform from the 60fps stuff we shot to 24fps. This is now not working, and although the clips play perfectly in my timeline when I just drag them down with the rest of the 23.976 frames, when I export to something like the AppleProRes422 codec, it will stop at like 18% (what I assume is where my first 60 frame clip is) and tell me there's a "General Error".

PLEASE HELP! I do not have an older Mac that I can transfer from. I need to use my brand new Macbook Pro and I need to get this done by Sunday as I really didn't expect CONFORMING to be my biggest drawback. Any help is greatly appreciated.
 
You must log in or register to reply here.
Back
Top