MetaCheater Utility

[Terry Wester]

Hi tab32,

Could you please confirm that this worked on the PC version of AVID ? I was under the understanding that the Red QT component was required, which is mac only ?

/confused ..

Thanks,
Seth.

Yes It will, you can not see the pointer files in quicktime, but MetaCheater will read the time code and reel names on a pc for the pointer files.

1. Using the pc version of red cine output quicktimes that avid can read, I used the Avid NTSC DV codec.

2. Then create your ALE file with MetaCheater

3. Load the ALE into the avid

4. Link your media to the Red Cine output files.

The only gotcha I found was if the quicktime proxys are older, they might not have the reel numbers. You can recreate form Red Alert and all is well, but you need a mac for that of course.

-- Terry

[Terry Wester]

Only RedAlert! is putting the source TC into the QT file. RedAlert! only works on Mac. The RED QT codec component is only avaialble for Mac.

MetaCheater runs on either Mac or PC.

Michael,

I don't have access to a camera right now. Do you know if the quicktime pointer files produced by the camera have proper time code and reel names in them that MetaCheater can read?

Thanks

-- Terry

[MichaelP]

Well...... it has the proper source timecode (time of day...) but it is open to debate what should/could be considered the REEL ID to make it unique. Currently it is using the "Axx" portion of the filename as the Tape name. I don't believe that over the course of a multi-day shoot this will hold up as being unique.

But... Jabez very nicely allows for the user to override the Tape ID in the Metacheater application by whatever you want to call it. So that will help create a unique ID on a daily basis. Then the application does allow the full filename to be tracked as frames as in <filename>-<000000> where <000000> is a total frame count which can be tracked in Avid.

Michael

[M Most]

Well...... it has the proper source timecode (time of day...) but it is open to debate what should/could be considered the REEL ID to make it unique. Currently it is using the "Axx" portion of the filename as the Tape name. I don't believe that over the course of a multi-day shoot this will hold up as being unique.

Well, until you hit 999 rolls from either the A or B camera, I don't see how this is any different than the film roll ID's we've been using for years (or at least those of us who have shot film for years). The camera dept. has to do its job and enter these numbers correctly, however.

If you're doing a conform you really don't want to be changing those numbers, because they will no longer match those in the r3d file - thus causing problems for anyone going back to those files for either new exports or direct usage (say, a conform in Scratch, which will read them directly from the R3d file). Right now, I don't know of any available tools for editing that information in the R3d files themselves. But as with all things Red, that could change at any time (and, at least in this case, I hope it does - it's a bit dangerous to only be able to create information once, and even more dangerous if the only time to do it is during production).

[Brenton]

You are a beautiful, beautiful man!!

I had an instant NerdGasm when it produced that ALE

Now to complete my rapturous experience is to load this in Avid and see the media playing :)

You have made my day!

Ciao for now

B

[MichaelP]

I have no issue with the number of alphanumeric characters, I am questioning the uniqueness of the ID over multiple days and cameras as being ID'd in the QuickTime file from the RedAlert! export. Having the ability to change it to something more valid and unique in MetaCheater might be something to explore.

Michael

[M Most]

I have no issue with the number of alphanumeric characters, I am questioning the uniqueness of the ID over multiple days and cameras as being ID'd in the QuickTime file from the RedAlert! export. Having the ability to change it to something more valid and unique in MetaCheater might be something to explore.

I guess I'm missing your point here. On all productions that I've ever worked on - and, granted, I'm a product of the "Hollywood" system - camera rolls are numbered from 1 to whatever over the length of the production. So on day 1, you'd start out with A1 for the "A" camera and B1 for the "B" camera, and by day 30, you might be up to A300 and B300. But you don't start from 1 each shoot day, you consecutively number through the length of the production. So unless the script supervisor - or the AC's - make a mistake, every roll has a unique identifier. Now, it is also true that in film, you also have the shoot date as a secondary identifier, but with files, you have that as well (file creation date). And, as I mentioned, unless and until the metadata in the R3d files can be edited, it could be very counterproductive to alter those reel numbers down the post chain.

Oh, and by the way: this utility works superbly. I now feel we (as a facility) can support cutting Red productions on Avid with a very solid workflow. Thanks to all.

[MichaelP]

All I am saying is that if the default TAPE ID from RedAlert! is A001 as extracted from MetaCheater from the same camera on day one, day two, day three, etc. there will be no unique identification for file name to timecode. I don't see Creation date coming through in MetaCheater - it would need to grab that from the properties of the file as it may not persist into the metadata of the QT file itself. If it did, Shoot Date and camera ID could be concatenate to create a unique SourceID within Avid. There is also the small issue that RedAlert! adds a quality tag such as _m to the end of the file so there is not a direct one to one relationship to the original file. That needs to be taken care of either in MetaCheater or RedAlert! exporting out without the appended quality tag. If it needs to do so, perhaps putting them all into a directory of the quality first, then preserving the original file name in the .mov file.

I agree with what you are saying since a human managing the daily count of reel ID's and tape names manages how the structure of naming schema will work. Such as 01001 is Tape 001 of episode 01 of a season series. One could go oven farther and define it as 0101001 as Season 01, Episode 01, Tape 001.

I don't have access to a lot of R3D files, so this may be a moot point, but I would like to see two files from two different days shot at the same time of day exported out of RedAlert! to see what the default source ID that is listed in the MetaCheater application. My concern is the default name of the truncated source name as it stands right now. I have created a special EDL format that allows for 16 characters in the source to track longer source file names for file based workflows so the uniqueness of the file name can also be tracked as source ID in an EDL. The issue of course is the file name can be fragile should it get changed in the process - not so much an issue in Avid since we abstract file name from source name so the editor can give it a more useful name like 1/1 for Scene 1 Take 1, and still maintain the original source file name and count as frame counts with <SourceFileName>-<frames>.

We also agree that there is a lot more metadata available in the file that is not being exported out in either RedAlert! or RedCine. It's a matter of getting access to that in an easier way. And lets not forget that this is a Mac only solution from RedAlert!

MetaCheater is a great utility and will find its way into many other workflows than just RED.

Michael

[MichaelP]

Brain lapse... this can be done in MetaCheater (Sorry Jabez... more feature requests) as the shoot date in in the file name and it would need to be parsed within MetaCheater and allowed to become part of the TAPEID as a default way to allow for source ID to be generated. The metadata can then be tracked in their own columns if needed within editorial. An additional metadata tag would/could be generated to associate dailies with a particular feature, program, episode, ad campaign, etc.

Speaking of additional metadata, we could also track whatever color changes were done to the baked in look of the export from either RedAlert! or RedCine and pass those back as part of the conform process... again, need that richer metadata export...

Michael

[Anthony Gratl]

I nominate Cogito as Reduser of the week for this! thanks man.