Michael Phillips
1
COW Coin
Forum Replies Created
-
29.97 to 23.976 gets frames dropped or blended in order to reduce the number of frames for each given second of footage.
23.976 to 29.97 adds fields in a 29.97i (not p also called 1080i/59.94.
Michael
-
Have you tried the Sony AMA Plug-in?
Michael
-
Title Tool, and most likely Marquee legalize levels into video specs when saving – so what would be full white 255 RGB is now 235 RGB.
Media Composer is a Rec/601/709 system. You can cheat it and work full wing with imports, and now LUTs to go full scale, but there are still operations like titles and some VFX renders that will make legal video.
In your case, create the white frame outside of Media Composer and import with 601/709 levels so that Media Composer leaves it alone.
Michael
-
Did you happen to turn off the monitor on V1 track? It’s where you activate the tracks (or not) when editing.
Michael
-
I don’t know if you’ve looked into it, and they have a demo version available, is BeaTunes (https://www.beatunes.com) that is originally designed for DJ’s and the like, but the ability to insert tags, mood, description and BPM is also very handy to have on the library assets when later searching in Media Composer. We are looking into supporting the color and span based sectioning of the songs that is now part of their v4 release.
And on OS X, I use GetLyrical, a free app for inserting lyrics by selection. This also gets parsed to the extent of what the bin allows to be loaded (128 characters).
If the FIND feature ever gets updated for range finding, then BPM and other numerically based metadata becomes even easier to find.
Michael
-
Do a mixdown to ProRes, then export same as source.
Michael
-
Certainly something can be done as a full-on reporting application, but that is a lot more work addressing the smaller end of the market “seat count wise” and one needs to look at ROI. I am sure you’ve already noticed that not all plug-ins are available for MC as for other NLE’s… 🙂
One could consider an easy XSLT file from the XML generated by FilmScribe, but that is not well maintained by Avid, does not work with AMA clips that have any kind of transform as they are considered an “optical” and can no longer be tracked.
The mus.ID works based on the fact that the clip is tagged as a music file when AMA linked so parsing the AAF is fairly easy. I could also let it see all .mov type extensions to flag whatever, but would be compromising the AMA agreement. But a full on, generic reporting app is a lot more work as AAF is not the easiest format to deal with. Also not a long term business seeing as Wes no longer develops Automatic Duck, and that was two resources for several years.
As I mentioned, getting an AMA license from Avid does not give you the freedom to do whatever you like – I could easily do a stock footage tagging app using the same model, but I am not allowed to as I had to be very specific as to what my AMA plug-in was going to do. If Avid is planning on developing a similar solution, you will not get the license, or under very defined (limited) use.
Now AAF for the most part is open, and I have thought about recreating a combined EDL Manager/FilmScribe/reporting application and even had one designed for Avid when I was there. To me, right now, it is not worth the effort. There’s always the “rumors”about Avid updating what they have. But I have some ideas on how the reporting app might be able to do something, but the price would change.
This plug-in was quick to make, and useful, and if it generates some money, great. Avid does not do a whole lot to promote it, it has been very difficult to get Avid to add it their AMA page despite multiple requests. Kinda funny since Avid used it as part of their NAB main stage demo this year. Maybe once they get Marketplace 2.0 in place there will be additional value in developing. But for small one/two person shops, an Avid only plug-in is not going to feed you. Adobe reached out to me when they saw it and am looking into a version for them.
Michael
-
WAVE does not store ID3 metadata- there is an ID3 blob in AIFF files that we are looking into. Also, Avid has a BWF/iXML AMA plug-in that in theory would parse that for those file formats.
The workaorund for these files types is extracting the metadata from the AME linked file, consolidate, and reimport higher quality file as a batch import. I will be testing this and writing something up.
I don’t really have a twitter account… I know, I know, I should.
Michael
-
I can only do what the AMA license from Avid allows me to do. Avid has a marketplace for stock footage already so they want/will be handling that as part of their Avid Everywhere vision.
Also, I have to use AMA as it is one of the few methods by which third parties can intercept/parse, inject metadata when linking to media that works at the Media Composer only level.
Michael
-
Please buy it NOW, baby needs shoes!
🙂
Michael