View Issue Details

IDProjectCategoryView StatusLast Update
0000710DCP-o-matic[All Projects] Featurespublic2016-09-02 02:02
ReportercarlAssigned To 
PrioritylowSeverityminorReproducibilityN/A
Status acknowledgedResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0000710: Set name of MXFs/CPLs etc.
Description[]
TagsNo tags attached.
Estimated work requiredSmall

Relationships

related to 0000366 resolvedcarl Filenames suggestions 
related to 0000945 new Illegal filenames can occur when using template naming 

Activities

manuelac

2016-01-27 02:47

developer   ~0001117

-Single reel or Multireel by content:
Use the original media file as the filename.
-Single media multireel by size:
Use the original media file as the filename, plus the reel number, plus the total number of reels.
-Multiple media and multireel by size:
Original media file by the start of the reel. Plus reel number, plus the total number of reels.

Exemple:
j2c_original media_mov_001of004.mxf

UUID can still be added if it's useful for machine processing or other.
The filename length limit for the common filesystems is 255 characters.

manuelac

2016-07-29 06:17

developer   ~0001364

In a similar way, Annotationtext can have more human readable information. Right now in PKL they are a mere duplicate of the Asset Id.

Some Annotationtext are indeed a duplicate of some kind to compensate errors of other software. Notably Doremi CinePlayer using the CPL reel Annotitiontext as the path to the file.

carl

2016-08-16 15:06

administrator   ~0001371

Are you saying that CinePlayer must have the path to the file in the AnnotationText?

manuelac

2016-08-16 15:34

developer   ~0001372

> Are you saying that CinePlayer must have the path to the file in the AnnotationText?
My bad, apparently is the <OriginalFileName> field, it's a known error that looks like it has never been solved on CinePlayer. I think it was added in DCP-o-matic at some point, this is the only reference I found http://dcpomatic.com/forum/viewtopic.php?t=95&start=10

Maybe the <OriginalFileName> field is the right place for the source filename? It's not exactly the same. And the naming template can have other uses. This solutions are not mutually exclusive.

Issue History

Date Modified Username Field Change
2015-10-11 12:16 carl New Issue
2015-10-30 13:34 carl Estimated work required Average => Small
2015-10-30 13:34 carl Priority normal => low
2015-10-30 13:34 carl Status new => acknowledged
2016-01-27 02:47 manuelac Note Added: 0001117
2016-06-07 04:40 manuelac Relationship added related to 0000366
2016-07-29 06:17 manuelac Note Added: 0001364
2016-08-16 15:06 carl Note Added: 0001371
2016-08-16 15:34 manuelac Note Added: 0001372
2016-09-02 02:02 manuelac Relationship added related to 0000945