Hi All, this is my first post to the forum so fingers crossed!
I have a new XHG1 which has just been released in PAL-land and have had some weird problems relating to the 'print to video' back to HDV tape from FCP 5.1.2. with 25p (which Canon calls 25F) footage. The PAL version of the XHG1/A1 has 50i and 25F modes rather than 60i/30F/24F.
The latest FCP does have a codec for native HDV 1080 25p which captures fine from the XHG1, then edits fine in a HDV 25p sequence - but when it comes to 'print to video' the 25p sequence the resulting output on tape drops out or freezes at every CUT point. It doesn't dropout during the print to video process, but does when playing back the tape in the camcorder.
If i set the sequence codec setting as 50i instead of 25p then it outputs fine to tape - BUT any 25p material has to be RENDERED when dropped in to that sequence. (that was my workaround but hardly desirable)
Anyone else experienced this? Neither Apple or Canon seem to be aware of the problem which is odd since the PAL XLH1 has been around for awhile and when i tested that camera it did the same thing.
cheers
I have a new XHG1 which has just been released in PAL-land and have had some weird problems relating to the 'print to video' back to HDV tape from FCP 5.1.2. with 25p (which Canon calls 25F) footage. The PAL version of the XHG1/A1 has 50i and 25F modes rather than 60i/30F/24F.
The latest FCP does have a codec for native HDV 1080 25p which captures fine from the XHG1, then edits fine in a HDV 25p sequence - but when it comes to 'print to video' the 25p sequence the resulting output on tape drops out or freezes at every CUT point. It doesn't dropout during the print to video process, but does when playing back the tape in the camcorder.
If i set the sequence codec setting as 50i instead of 25p then it outputs fine to tape - BUT any 25p material has to be RENDERED when dropped in to that sequence. (that was my workaround but hardly desirable)
Anyone else experienced this? Neither Apple or Canon seem to be aware of the problem which is odd since the PAL XLH1 has been around for awhile and when i tested that camera it did the same thing.
cheers
