- This topic has 17 replies, 4 voices, and was last updated 5 months, 1 week ago by scopic.
-
Posts
-
scopic
New user, going to apply for a refund if not reparable very soon:
– Generated AAF, but all clips are stamped with timeline timecode (or file duration time, not entirely sure), not the original timecode from the original bwf’s. I was unable to relink to the ISO files and lost about 4hrs of time before noticing and needing to go back to v4.
James Carrick
Hi Scopic,
Sorry to hear your having issues, you are more than welcome to ask the AppStore for a refund, we would however like to find out what is not working.
Are you able to supply the XML, and pictures or detail of where in ProTools you see a difference please, and we will investigate.
Yours Sincerely
James.
Hi James,
I’ve attached the XML out of FCPX and the original FCP file from Premiere.
I’ve also attached a photo of the exact same regions: the Green clips are exported by X2Pro v4.5.16 and preserve the appropriate timecode from the original BWF’s. The Purple are from X2Pro v5.0.34 and contain some duration code, I believe from the original start time of the BWF.
Thanks,
TTim Robson
A couple of things, firstly the xml file didn’t upload (the fcpxmld did not the xml though, I assume that this is the Premiere xml). If you zip the xml it will be OK so can you upload that please? Secondly, the xmld doesn’t crash ProTools here when converted to an AAF so it is likely to be a media problem, would it be possible to get hold of the media files?
No chance I can transfer media – NDA’d. I tested both AAF exports and crashing occurs only on the version that doesn’t reference the timecode properly, so I believe it’s due to an issue in either the AAF or because it’s referencing media that doesn’t exist. The AAF render from V5 is the only different asset.
FWIW, I have successfully linked original media via the V4 AAF and have moved past this step in the process, unless editorial sends supplemental clips / changes.
I’m rather confused by the comments about V4 and V5 AAFs, X2Pro5 produces an AAF from an XMLD, the V4 XML file from Premiere is not a supported file in the software. I am able to convert the XMLD that you sent using the current (5.0.34) version of X2Pro5, obviously it has no media embedded but the result is able to be opened in ProTools. If you are able to explain exactly what your settings are I can try to re-produce the problem that you are seeing, however, I am likely to need some media of the same nature as yours which shows the problem. Please provide as much information and media as possible.
I have both V4 and V5 installed on my system.
I used the same FCPXML file (attached above) to render AAFs from the same original media.
V5 created an AAF that opened in Pro Tools, but it had duration code embedded as original timecode on the files. Upon trying to relink the ISO files (only the mix files were in the AAF), Pro Tools crashed on every attempt.
V4 created an AAF that preserved the original timecode of the SAME original files. Upon trying to relink the ISO files, Pro Tools successfully rebuilt the ISOs to the AAF.
Hi Scopic,
To confirm X2Pro5 was written to make use of the new ARM chip set, X2Pro was written for the old Intel chip set. They are not a straight forward V4 to V5, that is why they are different products.
Am trying to test here but I cannot see the same results you are seeing, so it seems it might be media specific.
Is there any of the ISO files (just one) you have that are not under an NDA that you could forward to us please. Happy to sign any NDA that you might require for this.
Yours Sincerely
James.
Hi James,
I am attaching 2 zip files with empty audio files from the show. They can be renamed to match any of the show mix files that were used and the empty ISO files have the same time parameters as the originals.
If this doesn’t work, please let me know how one can reach out to you privately (email, phone).
Thanks,
ThomasDear Scopic,
Many thanks, will let you know how we get on, probably not till late Monday, as its now close of play in lab for the week.
Yours Sincerely
James.
Dear Scopic,
Ah, looking at all 6 Wav files, they all have a header, however after this they only have either 0’s or 20’s in them. If you pull them into FCPX you will see there is no audio on them, as there is no audio data in them.
They were all created by “Boom Recorder Pro v8.7.3+8.7.3”
We use AVFoundation from Apple and it cannot pull out any audio data only header data.
If you put any of them in FCPX do you actually see any Audio, if so then the transfer must have corrupted them, and we will forward a link to our ftp site.
Thoughts ?
Yours sincerely
James.
Not sure what’s confusing here. The metadata matches, but I cannot contractually send audio data to you; these were empty audio files intentionally. The issue at hand is that X2P v5 doesn’t pass through timecode, rather sends duration code AS timecode. The audio information it sends is fine; therefore, an empty audio file with the same header information is all you theoretically need.
Hi Scopic,
If I use GG_Show1_T01_7-M_E_Mix_L-20240216_07.wav, GG_Show1_T01_empty-empty-20240216_29.wav, GG_Show2_T01_7-M_E_Mix_L-20240216_07.wav, GG_Show2_T01_empty-empty-20240216_29.wav, GG_Show2_T02_7-M_E_Mix_L-20240216_07.wav, GG_Show2_T02_empty-empty-20240216_29.wav, generates an error in ProTools “Error reading Wave Data”. With the option to “embed media” or “reference WAV” we get the same error. Whatever you were using to strip the audio out of the WAV files is also taking the required metadata.
Am happy to sign an NDA and agree to any conditions if you can supply any single WAV or part of a WAV file with the original metadata in it.
Yours Sincerely
James
INvisibleART
Is this resolved yet?
I am experiencing the very same problem. I generated an AAF from the first episode of a show and the sound department told me the timecodes did not match the original files. Result is they were not able to do a proper confo.
I used the very same xml from FCPX to generate an AAF with the legacy version of X2Pro and that AAF worked just fine, clips retained their original timecode.regards,
Steven Sanders
- You must be logged in to reply to this topic.