Problem with timemapped clips
- sighter
- Offline
- Fresh Boarder
Less
More
- Posts: 7
- Thank you received: 0
8 years 9 months ago #3396
by sighter
sighter replied the topic: Problem with timemapped clips
Could look like a Patch, but when I saw this occured in my editing I didn't hesitate for a second, I've pointed in and out my clips, exported them as PRORES, and reimported it in place... Longer to fix the problem than to go around in this case... ;-)
Please Log in to join the conversation.
- jeansemeur
- Topic Author
- Offline
- Senior Boarder
Less
More
- Posts: 48
- Thank you received: 6
- Jeremy Norwood
- Visitor
8 years 10 months ago #3272
by Jeremy Norwood
Jeremy Norwood replied the topic: Problem with timemapped clips
After looking into this with Development and Product Management, we have the following statement.
There are limitations in what is possible to support in a conversion between an FCPX XML and a ProTools AAF. The most significant of these is retiming. AAF does not support the interchange of audio retiming, so instead of not supporting this, where possible we allow the transfer of the media, however it will play out without any timing effect applied to it in the AAF.
i.e. If you have a 10 second clip in the XML that has a 2x speed effect applied the clip will only play out for 5 seconds in the XML. On a transfer to AAF the start point for the clip will be the same in the XML and the clip will play for the correct duration of 5 seconds, but it will play at normal speed.
In the AAF we will have created the whole 10 second clip and will have produced a Warning in X2Pro advising that a retimed event has occurred a point X. The intention is that you can apply the retiming to the event in ProTools.
When retiming is applied to a compound clip in the XML currently we will error and consequently fail to create an AAF.
We have looked into various ways of coping with retiming in a compound clip and have been unfortunately unable to provide a solution that could work in all scenarios. As such the only way you can work with retiming in a compound clip is to mix-down any retimed compound clips before processing through X2Pro.
The current software when it errors will warn the operator of where it has failed in processing the XML and stop. This is not terribly helpful because generally you either have no retimed compound clips in a sequence or several. It can therefore be a painstaking process resubmitting the XML each time you have mixed down a retimed compound clip or finding them yourself in the XML.
We are therefore planning to ease this process by changing the way the X2Pro software works when processing an XML it is intended it will parse through the entire project and then produce a report not just listing the Warnings that it currently does and the first point where it would have failed but all points in the XML where it would have failed previously.
There are limitations in what is possible to support in a conversion between an FCPX XML and a ProTools AAF. The most significant of these is retiming. AAF does not support the interchange of audio retiming, so instead of not supporting this, where possible we allow the transfer of the media, however it will play out without any timing effect applied to it in the AAF.
i.e. If you have a 10 second clip in the XML that has a 2x speed effect applied the clip will only play out for 5 seconds in the XML. On a transfer to AAF the start point for the clip will be the same in the XML and the clip will play for the correct duration of 5 seconds, but it will play at normal speed.
In the AAF we will have created the whole 10 second clip and will have produced a Warning in X2Pro advising that a retimed event has occurred a point X. The intention is that you can apply the retiming to the event in ProTools.
When retiming is applied to a compound clip in the XML currently we will error and consequently fail to create an AAF.
We have looked into various ways of coping with retiming in a compound clip and have been unfortunately unable to provide a solution that could work in all scenarios. As such the only way you can work with retiming in a compound clip is to mix-down any retimed compound clips before processing through X2Pro.
The current software when it errors will warn the operator of where it has failed in processing the XML and stop. This is not terribly helpful because generally you either have no retimed compound clips in a sequence or several. It can therefore be a painstaking process resubmitting the XML each time you have mixed down a retimed compound clip or finding them yourself in the XML.
We are therefore planning to ease this process by changing the way the X2Pro software works when processing an XML it is intended it will parse through the entire project and then produce a report not just listing the Warnings that it currently does and the first point where it would have failed but all points in the XML where it would have failed previously.
Please Log in to join the conversation.
- Jeremy Norwood
- Visitor
9 years 3 months ago #2314
by Jeremy Norwood
Jeremy Norwood replied the topic: Problem with timemapped clips
Martin,
This seems to be a bug in our software that I have reproduced and turned into our developers.
I will update you with the news as soon as I have some.
This seems to be a bug in our software that I have reproduced and turned into our developers.
I will update you with the news as soon as I have some.
Please Log in to join the conversation.
- jeansemeur
- Topic Author
- Offline
- Senior Boarder
Less
More
- Posts: 48
- Thank you received: 6
9 years 3 months ago - 9 years 3 months ago #2308
by jeansemeur
jeansemeur created the topic: Problem with timemapped clips
Because of several problems with time mapped clips, I wanted to test what you say in the Knowledge base:
"X2Pro will create a space in the timeline which is the length of the timemapped clip (i.e. if the used part of the clip is one minute long and is slowed down by 50% there will be a 2 minute gap). X2Pro will put the original audio media at the start of this gap, with the in point aligned with the start of the gap. X2Pro will not translate the timemapping (i.e. it will not stretch or squash the media)."
I've made 3 test with each time two différents clips ( 2 second each) in the Timeline and only modify the first clip. Both clips comes from the same master clip.
TEST 01
In the First test, i've just apply a 50% speed effect
here is the XML:
and here is the a grab of ProTool after importing AAF (which is a 1,8Mo file)
But it should be that !!!
TEST 02 work well (a 3,6Mo file ... good news !!!). i've first detached audio and only apply the 50% speed effect on the video (only)
TEST 03
In the third test, i've first detached audio and apply the 50% speed effect on the connected audio (only)
here is the XML:
and here is the a grab of ProTool after importing AAF (which is a also a 1,8Mo file... bad news !!!)
it lacks the first audio !!!
What you may need to investigate: i work with FCP 10.2, export XML in 1.4 version, both clips comes from the same file and had the same ROLE (Dialogue). Clip format is 1920x1080/25p and PROJECT format is the same.
Can you help me to understand what happened ?
I can send you my AAF file but i think, regarding file sizes that it's clear. If it's a 1,8 Mo file (TEST 01 and TEST 03), it lacks the first file and when it's a 3,6Mo file (TEST 02), both file are embedded in the AAF...
Thank
Martin
"X2Pro will create a space in the timeline which is the length of the timemapped clip (i.e. if the used part of the clip is one minute long and is slowed down by 50% there will be a 2 minute gap). X2Pro will put the original audio media at the start of this gap, with the in point aligned with the start of the gap. X2Pro will not translate the timemapping (i.e. it will not stretch or squash the media)."
I've made 3 test with each time two différents clips ( 2 second each) in the Timeline and only modify the first clip. Both clips comes from the same master clip.
TEST 01
In the First test, i've just apply a 50% speed effect
here is the XML:
and here is the a grab of ProTool after importing AAF (which is a 1,8Mo file)
But it should be that !!!
TEST 02 work well (a 3,6Mo file ... good news !!!). i've first detached audio and only apply the 50% speed effect on the video (only)
TEST 03
In the third test, i've first detached audio and apply the 50% speed effect on the connected audio (only)
here is the XML:
and here is the a grab of ProTool after importing AAF (which is a also a 1,8Mo file... bad news !!!)
it lacks the first audio !!!
What you may need to investigate: i work with FCP 10.2, export XML in 1.4 version, both clips comes from the same file and had the same ROLE (Dialogue). Clip format is 1920x1080/25p and PROJECT format is the same.
Can you help me to understand what happened ?
I can send you my AAF file but i think, regarding file sizes that it's clear. If it's a 1,8 Mo file (TEST 01 and TEST 03), it lacks the first file and when it's a 3,6Mo file (TEST 02), both file are embedded in the AAF...
Thank
Martin
Last Edit: 9 years 3 months ago by jeansemeur.
Please Log in to join the conversation.
Time to create page: 0.400 seconds