Michael Phillips
1
COW Coin
Forum Replies Created
-
Not to mention that Quicktime (the wrapper) plays havoc with codec color space and will always try to modify it to make sure “it looks good” which is not what we want all the time.
Michael
-
The timecode of the new transcoded clips (.new) from the sequence should be the same timecode as the original clips. They may not have the same START as the sequence will only transcode what’s in the cut plus whatever handles were set at time of transcode.
If you want to try an AAF of an AMA linked sequence without a transcode, then be sure to check “edit protocol” in the AAF settings when exporting. Also should be set to “link to”.
Michael
-
If you AMA to the QUickTime sources, right-click on the clip and select “source settings” you will find a menu with three settings of create video level, expand to graphics levels or, do not modify. Try one of those to see if you get what you expect. Video, analog or digital works in a 16-235 (black and/levels in 8 bit terms) and Avid being a video editing system by nature like working that way. That being said, one can certainly work full swing with levels 0-255 with the settings above if they desire. Just be sure to check the proper settings on export to not expand levels again crushing blacks, etc.
Here is a document by Job on import/export thst will give you a better sense of how it all comes together.
https://www.jobterburg.nl/Publications/601_709_RGB.pdf
Michael
-
Have you tried it in a custom column, then doing a “duplicate column” into the TapeID column once imported?
Michael
-
Well…. I made it work. I need to redo it a few times and take careful notes, but I was able to get a 1080i/50 transcoded sequence from 23.976 to relink back to the original media in a 1080p/23.976 project and cuts are right on or off by 1 frame.
Stay tuned.
I will write something up and it to my blog at https://24p.com/wordpress/
Michael
-
There is a difference between no support, end of life, and no further development. Manufactures tend to “support” apps for many years beyond the end of life cycle. They usually mean no new development. for example, Avid recently released a new 5.5.x and 6.5.x to support bins from the new v7. Nothing new, just supported. I suspect the same for Adobe and Encore.
Michael
-
Shane is right on with his advice. Once you hit “transcode” and you get that rather draconian message that this is now a new clip and will lose all relationship to it’s camera original – that’s what you got. Don’t get me started that it could be designed to deal with that, but what are you gonna do?!?!?
So what Shane advises is the best way to go. Something to try, and no guarantees, is to transcode back in a 1080p/23.976 project, and then do a relink to selected to the correctly managed clips. There’s a chance it will work and you may only have to reword ins and outs that may have shifted due to the 23/976/25 timecode rate. In theory, it might just work. I will give it a try myself on a few clips when I get the time. Perhaps Job has tried something like this coming from the PAL world.
Michael
-
If I remember correctly, 5.5.x only supported the AJA i/O Express and it was v6 that opened it up to many more. But as Job states, the upgrade to v7 is a good deal.
Michael
-
No – go to the master clip from the original import. Delete the media, NOT THE CLIP!. Highlight the clip and go to Clip – Batch Import. Find original clip, resolution, etc. I’m hoping you were working in NTSC 16:9 for the moves…
Michael
-
You should be able to re-batch import the files into the clips. Try it on a few clips, but you can do a bunch at a time.
Michael