In a long video, only a few position values ​​are displayed and the rest are not displayed.

[snbspd7]

There seems to be a problem in Metaburner where the position value is not displayed when the duration is 100 minutes.

I wonder if there is a solution.

[latenitefilms]

Apologies for the delayed response.

Are you able to share a FCPXML to reproduce this?

Most people using Metaburner are using it on feature length timelines - and we haven't had any issues so far about length causing problems.

[snbspd7]

Thank you for your reply. I will compress and deliver the XML I edited.

…

-----Original Message----- From: "Chris ***@***.***> To: ***@***.***>; Cc: ***@***.***>; ***@***.***>; Sent: 2024-12-23 (월) 10:51:38 (GMT+09:00) Subject: Re: [latenitefilms/Metaburner] In a long video, only a few position values ​​are displayed and the rest are not displayed. (Issue #72) Apologies for the delayed response. Are you able to share a FCPXML to reproduce this? Most people using Metaburner are using it on feature length timelines - and we haven't had any issues so far about length causing problems. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[snbspd7]

Could it be that the XML I sent wasn't delivered?

[snbspd7]

Sisterhood_MAIN_EDIT.fcpxmld.zip

If it doesn't go, I'll send it back to you.

[latenitefilms]

Thank you! I've downloaded the above FCPXML, so I'll see if I can reproduce.

[snbspd7]

Happy new year! You haven't found the cause yet, right? I am so curious so I am leaving a message.

[latenitefilms]

Thanks for chasing up @snbspd7!

I'm actually having trouble getting Metaburner to process your FCPXML at all - it's just crashing when attempting to process.

I'm still trying to work out exactly where and why it's failing.

There's a few weird things in the FCPXML when importing into a fresh Library on my side. For example, if you search for 34-14-T01 in the Timeline Index, there seems to be a clip that doesn't seem visible in the timeline. I can see the same thing with one of the 45-1-T02, 62-6-T02, 67-1-T01, 77-8-T01, 78-4-T04, 79-1-T02, 79-4-T01, 79-6-T03, 79-2-T02 and 60-2-T05 instances. Do you see the same weirdness on your side?

Also, if you go into the Clips section of the Timeline Index, and sort by Position, there's quite a few clips that have a negative position.

I'll keep digging and see what I can uncover.

[latenitefilms]

After deleting the following "ghost clips" in the Final Cut Pro Timeline Index:

• 23-5-T02
• 34-14-T01
• 35-4-T05
• 45-1-T02
• 60-2-T05
• 62-6-T02
• 67-1-T01
• 75-2-T05
• 75-3-T02
• 75-4-T01
• 77-8-T01
• 78-4-T04
• 79-1-T02
• 79-2-T02
• 79-4-T01
• 79-6-T03
• 80-20-T02

...everything seemed to work as intended with Metaburner.

So I think in this case, SOMETHING has happened to the Final Cut Pro project, that's corrupted/confused things.

If you check the above clips in the Final Cut Pro Timeline Index, can you also see these "ghost clips"? Does removing them fix the issue?

To be honest, I'm not really sure what the best solution to fix this is - as it SEEMS like it's a bug in Final Cut Pro.

[snbspd7]

Thanks for your reply. I will test it and get back to you. -----Original Message----- From: "Chris ***@***.***> To: ***@***.***>; Cc: ***@***.***>; ***@***.***>; Sent: 2025-01-06 (월) 15:40:19 (GMT+09:00) Subject: Re: [latenitefilms/Metaburner] In a long video, only a few position values ​​are displayed and the rest are not displayed. (Issue #72) After deleting the following "ghost clips" in the Final Cut Pro Timeline Index: 23-5-T02 34-14-T01 35-4-T05 45-1-T02 60-2-T05 62-6-T02 67-1-T01 75-2-T05 75-3-T02 75-4-T01 77-8-T01 78-4-T04 79-1-T02 79-2-T02 79-4-T01 79-6-T03 80-20-T02 ...everything seemed to work as intended with Metaburner. So I think in this case, SOMETHING has happened to the Final Cut Pro project, that's corrupted/confused things. If you check the above clips in the Final Cut Pro Timeline Index, can you also see these "ghost clips"? Does removing them fix the issue? To be honest, I'm not really sure what the best solution to fix this is - as it SEEMS like it's a bug in Final Cut Pro. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[snbspd7]

Thank you for sharing the update. If the same issue persists even after deleting the ghost clips, it does seem likely that the problem originates within Final Cut Pro. As you mentioned, proceeding with the additional methods provided earlier is a good idea. Here are some further tips that might help:

[latenitefilms]

I think maybe your last message was incomplete?