FCPX export BUG!

Just to chip in here.

1) No swearing on the Forum please.

2) There is an export error within FCPX adding one frame to an interlaced 1080 25 FPS project.
I've had it on different projects on different machines with different media.

I have filed a bug report.

So please do not question if it happens or not, as I have wasted many hours in suites trying to work out why it is happens and then fixing it. I still cannot pin it down.

Peter

yes, peter, in fact, 29.97 interlaced also has the BUG. I can upload video and prove it.
you are right, I have no way to fix this.
I did test of my post on the first page, unfortunately, it sometimes ok, but sometimes failed.

so, the efficiency solution I think for now is:

install 10.0.9 to the same mac pro, find the added frame in the 10.1.1, and delete it in 10.0.9
then export!
10.0.9 has not that BUG.
the mac pro's export time is good if you've rendered all the timeline, 0.25 times timeline duration on mac pro2013 (6cores D500)

so, that will cause you about 0.5++times of timeline duration.

peteramwiggins wrote: Just to chip in here.

1) No swearing on the Forum please.

2) There is an export error within FCPX adding one frame to an interlaced 1080 25 FPS project.
I've had it on different projects on different machines with different media.

I have filed a bug report.

So please do not question if it happens or not, as I have wasted many hours in suites trying to work out why it is happens and then fixing it. I still cannot pin it down.

Peter

.

your codec is H.264, we won't use that for broadcasting.
I've said prores422 all the time.

Tom Wolsky wrote: .

I said I did the same test in ProRes with the same result. I'm done. Wiggins wants this closed.

ok, Wiggins's test prove the BUG.
and apple support told me there's bug.
and I will upload a video to prove it.

Tom Wolsky wrote: I said I did the same test in ProRes with the same result. I'm done. Wiggins wants this closed.

hi, peter, I also find the audio is not exactly the same.
when the frame duplicating happens, the audio begins to shift.
the shifting amount is very small ( less than 1 frame )from beginning and gradually increase.

So, strictly speaking, even use 10.0.9 to delete the duplicated frame, we cannot fix the BUG 100 percent!
Cause we can not align the audio frame by frame.

peteramwiggins wrote: Just to chip in here.

1) No swearing on the Forum please.

2) There is an export error within FCPX adding one frame to an interlaced 1080 25 FPS project.
I've had it on different projects on different machines with different media.

I have filed a bug report.

So please do not question if it happens or not, as I have wasted many hours in suites trying to work out why it is happens and then fixing it. I still cannot pin it down.

Peter

Tom,

I don't want it closed, I want to find out why it is happening!

Rather than arguing about if it happens or not (as it does) we could try to use our combined efforts to find a fix.

Peter

Well this had me very worried as I've just output a Television show for broadcast.
Resolution in 1280 x 720 25p ProRes HQ. Duration just shy of 57 minutes.

Thankfully the master file is exactly the same length. Whew!

Very weird thread, and I think a language barrier has something to do with it.

Artofoe, why don't you just try putting an adjustment layer on top and add a broadcast-safe filter on it as Ronny says? I think a few people have said that fixed it. Your work-around seems way too complicated.

All I'm saying is that of course it should be fixed, but like everything, you have to find a workaround until it's fixed.

For the record, I still have not seen this bug, but I only work in 24p and 29.97i/p. I have not seen it in 29.97 as you say, but it could be because the timeline is rarely if ever 29.97i. We usually add pulldown to 24p, or add interlacing to a 30p project after export.

I pointed out that method
and then I tested 10 times
sometimes ok sometimes failed

ronny just followed my method, but done no tests.

there's no ways to fix it 100% cause of the audio gradually shifting.

haysoos123 wrote: Very weird thread, and I think a language barrier has something to do with it.

Artofoe, why don't you just try putting an adjustment layer on top and add a broadcast-safe filter on it as Ronny says? I think a few people have said that fixed it. Your work-around seems way too complicated.

All I'm saying is that of course it should be fixed, but like everything, you have to find a workaround until it's fixed.

For the record, I still have not seen this bug, but I only work in 24p and 29.97i/p. I have not seen it in 29.97 as you say, but it could be because the timeline is rarely if ever 29.97i. We usually add pulldown to 24p, or add interlacing to a 30p project after export.

Putting an adjustment layer with & without a broadcast safe filter doesn't help
(plus having the clip connection on the first frame or not)

Trashing all the renders before exporting doesn't help

hi, peter, that's right!
Even sending to compressor doesn't help.

peteramwiggins wrote: Putting an adjustment layer with & without a broadcast safe filter doesn't help
(plus having the clip connection on the first frame or not)

Trashing all the renders before exporting doesn't help

hi,tom, I uploaded a video here:
vimeo.com/96675474

1 test, no cutting video, you can see clearly the BUG with prores422.

vimeo.com/m/96691257

My 23td test. Apologies for the one handed iPhone video.

Tom, BUG means OK doesn't make sense, but Failing makes sense.
If there's failing, there's BUG.
My understanding is right?
Yesterday, we've done a TV project, with this BUG.
38mins15s, we found the added frame, and imported the Pores422 mov to 10.0.9, deleted the frame,
then exported using 10.0.9.
It took only about 4mins for 10.0.9 to exporting the 38min15s Prores422 mov.