Michael Phillips
1
COW Coin
Forum Replies Created
-
You can mix resolutions, frame rates, codecs, etc. but for signal based capture, you need to be in a project that matches the format.
Michael
-
https://www.sonycreativesoftware.com/pdzk-ma2
And is the camera model listed on the Sony AMA page, and is the one you downloaded?
Michael
-
Hmmmm…. You can try moving up and down the folder hierarchy to see if one works or not, but the one I mentioned is the one that works for me when using files from the Sony F55. Have you confirmed these are from a Sony camera? If so, which model? My files are wrapped in .mxf and not .mp4. Just to see if anything imports, you can try the QuickTime AMA and click directly on the .mp4 file to see what happens.
Michael
-
Assuming you have the most recent AMA plug-ins for XDCAM, use the XDCAM (folder) and select the one right above BPAV. In your example, it would be “Inappropriate CAM A 1” That should do it.
Michael
-
Maybe I wasn’t that clear, but in the ALE that you downloaded, it will still crash because I wanted you to see that the last even in the ALE had a comments field that way too long and that is what is crashing MC upon import. You can open the ALE file in a text editor (I like TextWrangler on OS X) and either delete the last event or shorten the comments column to match the other events. Then it will import.
In all cases, it will not relink to any of the media because ALE merge and relink is based on an EXACT match of:
1. Either Tape or Source File metadata fields. This is the file name of the source file being recorded of which there as no record in the original ALE file.
2. Start and End timecode must also be an exact match. There is no fuzzy merging based on ranges and such with ALE merge.And if it did work, some events may be limited or truncated to the limitation of characters as witnessed with this sample file.
Michael
-
You imported first, cut it into the timeline, added the pan & zoom effect, then from within the effect you tried accessing the higher resolution file and from there get the error?
Michael
-
Can’t you just do a mixdown and work from there? Sounds like an awful lot of work.
Michael
-
Does changing its position in the group window when loaded in the source change that?
Michael
-
The header had a double TAB. I corrected that and it imports fine. The other issue the file has is the COMMENTS column has too many characters. In the corrected file below, I shortened the ALE to just the first 7 events where event 7 has a really long value in comments. It crashed the application. If you shorten that to be the length of other events’ comments, it imports fine. Go ahead and edit that in this file and you will see that it imports.
https://dl.dropboxusercontent.com/u/1226998/test.ale.zip
And because of the need to give it a SOURCE that will not match the camera originals, it will not merge or link.
Michael
-
Select your source clips and try AutoSequence from the BIN menu.
Michael