|
|
Posted by Rick Merrill on 10/15/07 00:38
Richard Crowley wrote:
> "Rick Merrill" wrote ...
>> nappy wrote:
>>>> What do you think your evidence is? (about the single file)
>>>
>>> Not sure what you are getting at there Rick. Can you elaborate on
>>> your question?
>>>
>>> The file system on a firestore is 32 bit. Thus the 2G limit. But when
>>> you upload the footage into your NLE it will show up as a single
>>> file. Provided of course that you are on a NTFS or OSX file system.
>>>
>>> That's the way it works with the FS100.
>>
>>
>> We seem to view "it will show" in different ways. Your NLE (and my
>> scheduling s/w for DV files) will display a group of files IF you have
>> stopped and started the recording. If you have not s/s then the NLE
>> is smart enough to know that all the -0x files are part of one <thing>.
>>
>> But if your OS looks at the files, it sees them as separate.
>>
>> "it will show" can refer to the Final Product (one file), but
>> the actual uploads (to the OS) are separate files. The NLE and
>> other systems produce a single file, but FTP, disk transfers, and
>> disk mounts show multiple files.
>>
>> In other words, this is a feature of the NLE, not of the FS100,
>> according to the makers of the FS100.
>
> You appear to have missed or fogotten the details of
> the question. i.e. a single long "shot" which may result
> in a sequence of 2GB files internal to the Firestore, are
> seen/downloaded/transfered as a single file upon retrieval.
>
> Not sure what the discussion is about, anyway. The Firestore
> works the way it works regardless of what anyone here says
> or thinks.
I'm a big fan of the FS devices, and Not a big fan of a "war of words",
but I also did not want someone to misunderstand the statement made:
"chain multiple segments together so they look like complete files" -
which is not true because it is the NLE that chains the segments
together, NOT the FS.
Navigation:
[Reply to this message]
|