|
|
Posted by Rick Merrill on 10/15/07 11:46
nappy wrote:
> "Rick Merrill" <rick0.merrill@NOSPAM.gmail.com> wrote in message
> news:VcidnQI3yrnsK4_anZ2dnUVZ_qXinZ2d@comcast.com...
>> 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.
>>
>
> Rick you misunderstood my points and the area of the discussion. It was not
> about capturing. But importing files from the FS.
> The two are a bit different.
>
> 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"
Once imported
> they are concatenated into single files. The references refer to multiple
> files on the FS. But to the app importing the files they are singel files.
>
> Has nothing to do with capturing recorded segments.. each of the files we
> are discussing in this thread would be one recording. Not multiples. If they
> were mults the FS woudl not need to create mutiple files to represent the
> recording.
>
>
>
>
>
Navigation:
[Reply to this message]
|