Michael Phillips
1
COW Coin
Forum Replies Created
-
As far as not linking, are there any special characters in the folder/file names? I have to admit to not having a whole lot of GoPro footage to test with, so I’m making assumptions. If it were possible for you to share a small sample, I could take a look at it. Send to michael[at]24p[dot]com via WeTransfer/dropbox or similar services.
Michael
-
You should be AMA linking, and not importing – but that does not mean the issue goes away but worth trying. I don’t know how much of this footage you have, but I would consider making new sources as was the attempt with MPEG Streamclip. In Media Composer – if you are on v8.3 or later:
1. AMA link to 23.976 source in your 24.000 project type
2. Right click on all selected clips and choose “source settings”
3. On frame rate tab, select project rate (which should indicate 24.000)
4. Click OK and back in bin do a transcode to a high enough quality you would use in final finish – at least DNxHD 115 or consider 175 or 175x.
5. This will now create frame for frame speed up for best quality and will now be true 24.000 clips.The next steps depend on how you will work with Resolve for final finish – you can color correct the DNxHD media directly or you might want to create a new source by exporting the newly created master clips and bringing them back again treating these as though there were the camera masters.
For that I have been use MXF OPAtom 1a from the AMA export as I prefer the MXF wrapper to QuickTime .mov which has the chance of messing with gamma and such depending on application. MXFOPAtom 1a works great with Resolve, Premiere, and other applications.
Michael
-
I just tried my one test XAVC-S file and it did not work either and I could swear this worked before. I emailed my test file to my contacts at Drastic to see if they can let us know what the issue might be as Avid points to this plug-in as the solution for XAVC-S.
Stay tuned.
Michael
-
Sony Alpga series like the A7 are very popular cameras but they record XAVC-S which Avid does not support the codec type, and Sony does not create the AMA plug-in for. You will find plenty of bitching and moaning on this in a variety of forums.
Your choices are to rewrap using something like ClipWrap before AMA linking, or using Sony’s tools to export out in a format that Avid supports, transode in something like Resolve or Adobe Media Encoder to Avid supported codec, or pay $99 for the Drastic Technology XAVC-S AMA plug-in for Avid.
Michael
-
I suspect the “NTSC” is an indicator that in NTSC countries, the 23.976/24 source needs to have pulldown applied to meet television standards as you can see from the Adobe Media Encoder settings below (which I prefer using for these types of encodes). Also, the Adobe Media Encoder actually shows me what controls I have. I just launched Compressor, first time in a long time, and it has been reduced to presets only from what I can tell.
Adobe Media Encoder Presets:
User controllable parameters within the preset. In this case it is 1080p/23.976 High Quality. Notice the NTSC button to indicate the type of pulldown flag to include in the encode for DVD BlurRay playback.
Michael
-
Isn’t there a high quality BluRay setting in Compressor that you can use and make the file ready to go for BluRay playback?
Michael
-
So I think we are saying the same thing – the original 24.000 Blackmagic shots are conforming, but the 23.976 GoPro stuff is not. Then the GoPro 23.976 material was frame rate converted using MPEG Streamclip which sort of surprises me I guess as I do not think it does a frame for frame pullup type frame rate conversion meaning it will have blended or dropped frames every 1000 frames (00:00:42:16). I’m also going to assume that the original GoPro had not timecode in it (or started at 00:00:00:00) as I think MPEG Streamclip does not support timecode it its encoding which may point to the issue as well.
Michael
-
Assuming it is the converted 23.976->24.000 clips that are conforming, how did the editor do the conversion?
Michael
-
At first blush, those do look like Sony XDCAM folder structures. AMA linking is pretty particular about file/folder naming conventions as well as which level you select the folder using AMA (folder) versus AMA (file). what you can do is try the XDCAM AMA plug-in (file) and drill down all the way to the .mxf file itself. If you can see it, and it links, then you know you have the right AMA plug-in. Swith to the folder version of that plug-in and start at the Content folder level or the one above and see if you can access the all the files within.
Make sure folder names do not have special characters in it like /*# etc.
Michael
-
when looking at the user manuals, I saw no way of turning them off either. And while is correct that they are not taking up room, there are still two issue in post he/she may not be aware of:
1. It is a pain in the ass to keep turning them off during editorial
2. If you do transcode with audio channels, it will create channels of silence that will take up 48kHz/16 bit space.Michael
