Sara Burke
Forum Replies Created
-
Neil,
You can send them to sburke@borisfx.com, along with descriptions of what you are seeing, what the desired result is, and I’ll try my best to find a solution.
—————–
Sara M Burke
BorisFX
sburke@borisfx.com -
If possible, could you send me the FCP XML of the sequence you are trying to export to AAF? It would help me confirm these issues.
—————–
Sara M Burke
BorisFX
sburke@borisfx.com -
Sara Burke
June 13, 2011 at 3:19 pm in reply to: Boris AAF Transfer problem with relink after AMA locatingMake sure the media start timecodes of the clips you are trying to relink are equivalent to what they appear to be in the Avid bin. If they are not the same, the clips cannot relink. If you are still having a problem, please contact our support team at support@borisfx.com.
—————–
Sara M Burke
BorisFX
sburke@borisfx.com -
Neil,
1) Freeze Frames are supported only for video at this time. However, they should be replaced by a filler, which sounds like this is not happening for you.
2) Motion Effects are supported only for video at this time. Unfortunately, sounds like the duration of those motion audio clips is incorrect.Thanks for your input! These are issues we will definitely address for a future release.
—————–
Sara M Burke
BorisFX
sburke@borisfx.com -
Sara Burke
June 13, 2011 at 3:10 pm in reply to: Boris XML Transfer import issue FCP to AE (file cannot be found)The file paths given to AE by XML Transfer are the paths of the files as they appear in FCP. Renaming master clips in FCP should not be a problem. However, are you stating that after the XML was exported from FCP, the original files themselves were renamed? If this is true, at this time, you would have to reconnect them in AE. Normally if your files are offline, AE will not show this message unless AE has a potential problem with file playback. You could try natively importing those files in AE and see if you get the same result.
Our very next release of this plugin will contain a Reconnect Media button on the XML import side, which will allow you to reconnect all your media at the time of import instead of having to do it via AE.
—————–
Sara M Burke
BorisFX
sburke@borisfx.com -
Sara Burke
May 24, 2011 at 6:45 pm in reply to: Exception: Sequence refers to non-existent track in clipHello,
I have had some experience with this message. How were the MXFs created? That is, are you importing the MXF and then getting the message when you click on the master clip or sequence? Usually this means the file specification states it has a certain number of tracks with IDs..but if the file’s tracks do not actually match the specification, Avid might try to reference one of the supposed tracks that don’t actually exist. The fact that the message says A1 is a bit suspicious. Do your audio MXFs originate from a clip with video?
Sara M Burke
BorisFX -
Freddie,
I would really like to help figure out the issues you are seeing with Boris AAF Transfer. I realize that it is very frustrating to get unexpected results. If you would be willing to send me some examples with explanations, I could try to see what’s going on and might be able to help. You can send me an email at sburke@borisfx.com – I would need either the FCP project file, or FCP exported XMLs of the sequence(s) you are trying to export to AAF.
Sara M Burke
BorisFX -
In the HTML log where you are seeing errors related to the Text, what does one of them say? The standard FCP Text Generator is translated to MC’s Title Tool – However, you must recreate the title media in MC as Jeremy replied, i.e. opening the effect editor on the clip, clicking on the ‘Edit Title’ button, and re-saving the title. This must be done for each Title Tool clip transferred to MC.
However, sounds like this isn’t your case. If you have FCP Text Generators such as Crawl or Lower Third, these are not supported when transferred to MC via AAF Transfer. Unfortunately, it is an Avid MC limitation for us at the time being. We hope to support these Generators in a future release. If you have an unsupported Text Generator, it will be listed as Not Supported in the HTML log and you would also get an alert at the end of the AAF export stating that some features are unsupported.
Sara M Burke
BorisFX