freeMXF.org

Open discussion about freeMXF.org tools and MXF in general
It is currently Tue Feb 18, 2020 3:27 am
Board index » MXF Categories » General MXF



Post new topic Reply to topic  [ 3 posts ] 
Author
Search for:
Message

Offline
Board User

Joined: Fri Jul 28, 2006 2:58 am
Posts: 10

Post Posted: Mon Aug 28, 2006 7:53 am 
Top  
I am checking some MXF files including from internet.

I guess that the number of tracks of Top-Level File Package and the number of Delta Entries in Index Table Segments are same and corresponding order for frame mapping files.

And.
Some MXF file contain a KLV Fill to timecode position at essence container.
Another MXF file contain system items and KLV fill.
The track number of timecode of both files is zero.

Question.
1. Is required entry for timecode component for index table segments ?

2. If no corresponding order between track of top-level file package and entry of index table segments,
is required to check 1st content package set for essence element key, track number of top-level file package, and address from index table, then make the mapping of track->index table->essence element.

Thanks to read :D

 Profile  

Offline
Insider

Joined: Thu Apr 15, 2004 10:39 am
Posts: 198
Location: Scotland

Post Posted: Mon Aug 28, 2006 4:53 pm 
Top  
I think that the whole thing that you are asking here is "how do I tie the tracks in a top-level source package to the elements in an index table (as described by the delta array".

If so this is slightly tricky!

There is not a one-to-one relationship between the two items. There can be more or less elements indexed in an index table that tracks in the source package.

Some key facts about indexing:

* Timecode tracks are not held in the essence container, all the data is in the header metadata, so they will never get indexed.

* An index table may index each KLV fill in the essence container, but this is optional.

* A very basic index table just indexes the start of each edit unit, and it is up to you to locate each essence element in that edit unit.

* More complex index tables generally index each essence element such that you get the same number of indexed elements as there are essence tracks

* The order of tracks or track numbers is not related to the order in the index table - you have to read the first edit unit and work out which element relates to which track.

* You may find that something is indexed, but you can't identify it (because it is described by some dark metadata in the header) - in this case just ignore that element

* You may find that one or more essence tracks does not have an index element - if this is the case you just have to search for it - it is probably easiest to locate the start of the edit unit and scan all KLVs until you find the one you are wanting.

* Index tables are not easy :roll:

 Profile WWW  

Offline
Board User

Joined: Fri Jul 28, 2006 2:58 am
Posts: 10

Post Posted: Tue Aug 29, 2006 5:36 am 
Top  
Thanks Mr Matt Bread. :D

I see, and need to check 1st content package and key for track number. :shock:

 Profile  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

Jump to:  


Who is online

Users browsing this forum: No registered users and 3 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group :: Style based on FI Subice by phpBBservice.nl :: All times are UTC