|
|
Posted by Rick Merrill on 10/15/07 22:14
nappy wrote:
> "Rick Merrill" <rick0.merrill@NOSPAM.gmail.com> wrote in message
>>> The FS 'chains' segments together with references to the multiple file
>>> segments so they look like single files to the importing app.
>> Is the following what you mean by "chains"?
>> "s_SAVBLD-092211-00"
>> "s_SAVBLD-092211-01"
>> "s_SAVBLD-092211-02"
>> "s_SAVBLD-092211-03"
>> "s_SAVBLD-092211-04"
>> "s_SAVBLD-092211-05"
>>
>>
>
> No those would be the independent file segments.
>
> I was referring to the method which the FS OS uses to provide the files to ,
> for instance, FCP's log and transfer.
Yes, FCP recognizes "s_SAVBLD-092211" as a single <thingy>, but it would
assume that "s_SAVBLD-092311" is another <thingy> until you tell it
differently.
> Perhaps the concatenation is done in the plugin for the file type, which for
> the FS100/HVX200, I believe is mxf.
MXF files are complex wrappers for as many as 4 parallel files. Sadly
not all vendors doing "mxf" agree on what is, like ragoo sauce, "in there."
FCP has a plugin/tool for doing mxf, but finding out what equipment is
compatible with said output is difficult!
Navigation:
[Reply to this message]
|