van Oldenbarneveltstraat 33
6512 AS NIJMEGEN, the Netherlands
+31 24 3553311
----- Original Message -----Sent: Tuesday, September 08, 2015 6:19 PMSubject: Re: [Avid-L2] TC# to Frame# translation - Solved with a little help
Jay,Is it allright if I quote you on my site?If so, with (full) name, company?Let me know,BoukeVideoToolShed
van Oldenbarneveltstraat 33
6512 AS NIJMEGEN, the Netherlands
+31 24 3553311----- Original Message -----From: Jay MahavierSent: Wednesday, June 05, 2013 7:05 AMSubject: Re: [Avid-L2] TC# to Frame# translation - Solved with a little helpSo, the excruciating time consuming process that I was looking at of manually looking up and entering frame data into the DPX column in an Avid bin for nearly 4000 master clips has been reduced to just minutes. Bouke wrote a nice little application to take care of this task for me. I exported an ALE with the appropriate columns included and ran it through his app and it automatically filled the column with the appropriate data and then I imported it back into the project with the merge option and presto; task done. Now my cut list and pull list have all the file frame range data for pulling needed file sequences for VFX from the ArriRAW image sequences for one of our projects. This totally nailed the solution to my problem and saved me a great deal of time.
THANK YOU VERY MUCH BOUKE!
Jay
On May 30, 2013, at 3:19 AM, Edit B wrote:
> Jay,
> well, it does work swell over here...
> Importing an ALE (select clips, right click shortly, curse while avid seems to be crashed, wait some longer, then see the options list and select import)
> the 'merge event with known master clips' option adds metadata to the original master clips.
> Now, this can be the DPX column (if the format is correct, otherwise you'll get an error for each clip), or a custom column.
> If you state you can have your intern do it manually, what would be the difference between inserting the DPX info trough ALE import,
> or by importing it as a custom column and duplicate it into the DPX header?
>
> (and of course you can always run a macro, if there is indeed something i'm overlooking.)
>
>
> Bouke
>
> VideoToolShed
> van Oldenbarneveltstraat 33
> 6512 AS NIJMEGEN, the Netherlands
> +31 24 3553311
> ----- Original Message -----
> From: Jay Mahavier
> To: Avid-L2@yahoogroups.com
> Sent: Thursday, May 30, 2013 3:15 AM
> Subject: Re: [Avid-L2] TC# to Frame# translation
>
>
>
> Well, I can easily export a ALE and enter data in one of the fields and import it and link it back to the same existing media, but it does not seem to transfer that information over to what is already cut into the sequence. I'm thinking that my best option is the intern solution and brute force entry into the DPX column. Lesson learned.
>
> Jay
>
> On May 29, 2013, at 6:41 PM, Edit B wrote:
>
>> Jay,
>> the testing is easy, will take no time at all (meaning, for me, for you it will take 5 minutes)
>> Just export one clip, alter the ALE in a a text editor, re-import with ' link to selected ' (or whatever it is called, you'll figure it out.)
>> No idea how that translates to the masterclips though, or if any of it gets trought to your sequence (I very much doubt it though)
>>
>> Retroactively, the media files themselves contain several fields. (storing clipname / reel / other stuff..) If you can spare an entry that is present, the content could be altered with your framecount.
>> (Sounds more complicated than it actually is, but of course it implies a bit of a risk if i start opening your files and messing around with the bytes.)
>> Shortening the content of an entry is easy, making the content longer is close to impossible, so you need an entry that is at least 7 digits long.
>>
>> Also, for the next time, my Avid MXF creator can put as many custom fields in media files as you want.
>> (Well, not the current version, but it could be altered very easilly)
>>
>> hth,
>>
>> Bouke
>>
>> VideoToolShed
>> van Oldenbarneveltstraat 33
>> 6512 AS NIJMEGEN, the Netherlands
>> +31 24 3553311
>> ----- Original Message -----
>> From: Jay Mahavier
>> To: Avid-L2@yahoogroups.com
>> Sent: Thursday, May 30, 2013 1:30 AM
>> Subject: Re: [Avid-L2] TC# to Frame# translation
>>
>>
>>
>> Hmmm, that does sound interesting. I need to look into that idea. I didn't consider needing this before they started to do the cut so I don't know if it's something that would work retroactively on the clips. Or if I would have to go back and overcut everything. But that might be a plan for future shows. So that somehow as they are making the Avid dailies media form the ArriRaw sequence that they load up the needed data in the DPX column or something. I may seriously take you up on that, but let me look into it a little bit before I ask you to do a bunch of unnecessary work.
>>
>> Thanks,
>> Jay
>>
>> On May 29, 2013, at 5:23 PM, Edit B wrote:
>>
>>> Jay,
>>> If you can live with an ALE export, and import with relink option, it's not a big deal for me to create an extra column with any kind of counter you want.
>>>
>>> Bouke
>>>
>>> VideoToolShed
>>> van Oldenbarneveltstraat 33
>>> 6512 AS NIJMEGEN, the Netherlands
>>> +31 24 3553311
>>> ----- Original Message -----
>>> From: Jay Mahavier
>>> To: Avid-L2@yahoogroups.com
>>> Sent: Wednesday, May 29, 2013 10:25 PM
>>> Subject: Re: [Avid-L2] TC# to Frame# translation
>>>
>>>
>>>
>>> not anywhere close. I need a column that converts the TC to a corresponding frame number. The file images sequences do not start at 0. Like I mentioned in my original post, if the master clip has a starting TC of 2:00:00:00 then the image sequence has a starting frame number of 172800.
>>>
>>> Jay
>>>
>>> On May 29, 2013, at 3:15 PM, Jeff Hedberg wrote:
>>>
>>>> We do frame count EDLs by setting one of the AUX TC columns to 00:00:00:00, then use that as your source when making an EDL.
>>>> Would that get you what you are after?
>>>>
>>>> Jeff
>>>>
>>>> ------------------
>>>> Jeff Hedberg
>>>>
>>>> Director of Operations
>>>> Union Editorial
>>>> 575 Broadway,6th floor
>>>> New York, NY 10012
>>>>
>>>> On May 29, 2013, at 2:54 PM, Jay Mahavier <jay_mahavier@earthlink.net> wrote:
>>>>
>>>>> I know that there is a bin column called TC24 that you can duplicate 30TC into and it will convert it to 24TC. Use to use it all the time when we were still capturing our dailies from DVcam, but needed to make 24TC EDLs for on-line with SR tapes.
>>>>>
>>>>> But now that we are switching to file based I need a column that will convert TC to Frame count. Like 1:00:00:00 equals 86400 and 2:00:00:00 equals 172800 and so on. Because I need to make pull list that refer back to frame ranges in image sequences. And while there is the DPX and VFX columns it looks like I will have to fill out each one at a time. And I have 3857 master clips. I could really use a bin column that I can duplicate TC into and have it automatically generate the corresponding frame number. Maybe I'm overlooking it. Does anyone know of a simple way to get this done in Media Composer?
>>>>>
>>>>> Thanks,
>>>>> Jay
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> [Non-text portions of this message have been removed]
>>>>
>>>>
>>>>
>>>> ------------------------------------
>>>>
>>>> Search the official Complete Avid-L archives at: http://archives.bengrosser.com/avid/
>>>> Yahoo! Groups Links
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>> [Non-text portions of this message have been removed]
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Search the official Complete Avid-L archives at: http://archives.bengrosser.com/avid/
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>
>>
>>
>>
>>
>> [Non-text portions of this message have been removed]
>>
>>
>>
>> ------------------------------------
>>
>> Search the official Complete Avid-L archives at: http://archives.bengrosser.com/avid/
>> Yahoo! Groups Links
>>
>>
>>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Search the official Complete Avid-L archives at: http://archives.bengrosser.com/avid/
> Yahoo! Groups Links
>
>
>
This email has been checked for viruses by Avast antivirus software.
www.avast.com
This email has been checked for viruses by Avast antivirus software.
www.avast.com
Posted by: "Edit B" <bouke@editb.nl>
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (1) |
No comments:
Post a Comment