FS-100 Import Problem and Solution

N

nsoltz

Veteran
This is for Matt, BenB and others who are having some strange issues with FCP 5.1.2 import.

Out of the country on critical shoot. First issue was a spanned clip which FCP did not recognize as spanned. No damage here-- everything there but just fragmented.

Second dump of FS-100 went without a hitch.

Third time-- spanned clips were recognized as such. One clip, however, would play in the import P2 window and appear to import when added to queue. It however did not show up in Browser. In my capture scratch folder, it showed up as (clip name)FFFFF and had a size of 4K. Repeated the procedure for this clip about 10 times.

This was on MacBook Pro Core 2Duo 2.33 (brand new machine before leaving).

Just got home and even before fully unpacking imported directly from FS-100 (fortunately, it was my last shoot and I had not reformatted the FS-100) on my daul G5. Imported without a problem, gave me the whole movie and I'm totally happy since this was a critical piece of B-roll.

Matt, I'll be in touch by email when I get the chance and can get you the log file.

Ned Soltz
 
Ned -

1. I am encountering clips coming in without spanning now about 50% of the time. All data is there, just 2:16 sections of video.

brainstorm - In our other FS-100 topic Diamond offered a possible solution to the red error:unkown import problem - deleting the relation data in the clip XML file. I am thinking there might be a way to adjust this data to inform FCP that it is looking at a complete spanned clip. I think if the right minds set out to figure out a hack in the code you could simply adjust some data when fcp sees it as incomplete when it should be spanned. obviously i am not the right man for the job and i have no idea if this is possible at all...but just a thought.

2. regarding the (clip name)fff 4k file. i had this a while back on my powerbook and it worked when i got home on my G5. I had it happen again on the macbook and realized i was using quite long file names in the P2 broswer. I shortened the file name to about 10 characters and it worked no problem. It makes no sense to me, but it worked and i haven't had the problem since.

--anthony
 
Thanks for that suggestion, Anthony. I had given the clip a unique name in the P2 import window but don't remember how many characters it was. Will have to try it again.

Some very interesting suggestions here...

Ned
 
I believe there are some characters that are not permitted -- I would defintely stay away from symbols like pound signs, percent signs, slashes etc.
 
Hi guys ... I have not found a solution for my problems in my set-up ... now that you mention it ... I am working on brand new intel machines ... before on my G5 it worked fine ... I changed over early october. Is that the possible the problem ? FCP 5.1.2 on intel gives us that red warning sign ? I got a mail from tech support looking into the problem ... their set-up worked ... I just wonder what exactly is their set-up ? Intel or G5 ? Quicktime 7.1.3 ? At this stage I am about to go and buy some G4 Powerbook on ebay ...
 
We are still trying to get to the bottom of this. But we have found the following work-around for the clips that would not import. So, give this a try...

Remove all the .xml files (DO NOT DELETE THE XML, just put it somewhere else temporarily) in the clips folder except for the one that wouldn't import and then re-import that clip. It does appear to come in OK. You can move the XMLs back to the CLIPS folder after the import. It is no longer a spanned clip, but at least it imports. Not a final solution, but certainly a work around for customers that hit this issue.

Matt
 
It's NOT the Intel Macs, the problem is on all Macs, it's the P2 driver (in the opinion of most of us who've been wrestling this problem for a good while now). Getting a G4 won't change anything, it'll be a huge step backwards.
 
All my .xml files are only 4K ...

All my .xml files are only 4K ...

Hi ...

Matthew's reimport doesn't work for me as all 60 plus clips of my clip content don't import ... they are all 4K in size ... this is what it reads in a text editor ...
the<relation> part that diamond mentions is not in my .xml files ...

This is how it reads ...

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<P2Main xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:schemas-Professional-Plug-in:P2:ClipMetadata:v3.0">
<ClipContent>
<ClipName>0244FW</ClipName>
<GlobalClipID>060A2B340101010501010D4313000000456723C6943105E90000000000000000</GlobalClipID>
<Duration>297</Duration>
<EditUnit>1/25</EditUnit>
<EssenceList>
<Video ValidAudioFlag="true">
<VideoFormat>MXF</VideoFormat>
<Codec>DV100_1080/50i</Codec>
<FrameRate>50i</FrameRate>
<StartTimecode>01:38:32:23</StartTimecode>
<StartBinaryGroup>D70F5023</StartBinaryGroup>
<AspectRatio>16:9</AspectRatio>
<VideoIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>171072000</DataSize>
</VideoIndex>
</Video>
<Audio>
<AudioFormat>MXF</AudioFormat>
<SamplingRate>48000</SamplingRate>
<BitsPerSample>16</BitsPerSample>
<AudioIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>1140480</DataSize>
</AudioIndex>
</Audio>
<Audio>
<AudioFormat>MXF</AudioFormat>
<SamplingRate>48000</SamplingRate>
<BitsPerSample>16</BitsPerSample>
<AudioIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>1140480</DataSize>
</AudioIndex>
</Audio>
<Audio>
<AudioFormat>MXF</AudioFormat>
<SamplingRate>48000</SamplingRate>
<BitsPerSample>16</BitsPerSample>
<AudioIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>1140480</DataSize>
</AudioIndex>
</Audio>
<Audio>
<AudioFormat>MXF</AudioFormat>
<SamplingRate>48000</SamplingRate>
<BitsPerSample>16</BitsPerSample>
<AudioIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>1140480</DataSize>
</AudioIndex>
</Audio>
</EssenceList>
<ClipMetadata>
<UserClipName>FS Default Clip Name 20060622-131321W01</UserClipName>
<DataSource>SHOOTING</DataSource>
<Access>
<CreationDate>2006-06-22T13:13:22+00:00</CreationDate>
<LastUpdateDate>2006-06-22T13:13:34+00:00</LastUpdateDate>
</Access>
<Device>
<Manufacturer>Focus Enhancements</Manufacturer>
<SerialNo.>0002EA0200001883</SerialNo.>
<ModelName>FS100</ModelName>
</Device>
<Shoot>
<StartDate>2006-06-22T13:13:22+00:00</StartDate>
<EndDate>2006-06-22T13:13:34+00:00</EndDate>
</Shoot>
<MemoList>
<Memo MemoID="0">
<Text>20060622-131321W01.xml</Text>
</Memo>
<Memo MemoID="1">
<Text>0244FW</Text>
</Memo>
</MemoList>
</ClipMetadata>
</ClipContent>

</P2Main>

... me again ... the global clip id number is a bit long huh ... ?
 
Last edited:
BenB said:
It's NOT the Intel Macs, the problem is on all Macs, it's the P2 driver (in the opinion of most of us who've been wrestling this problem for a good while now). Getting a G4 won't change anything, it'll be a huge step backwards.
Click to expand...
I don't think it's the P2 driver, it isn't even used when you import from a Firestore.
 
It works ...

It works ...

...
To be to the point ... I do not have the long clip 'spanned' problems ... what I had was simply the red status on import problem.

I did upgrade my firmware as Focus told me ... BUT ... I had already clips on the drive for which I had done a p2 organize ... that resulted in .xml files in which opened in a text file had no <memoid> mentioning the 2.0.1 upgrade!

...

So I did a format DD ... shot a few clips ... disd the p2 organize ... DD drive enable ... import and sure it works ...
...

So ... you need firmware 2.0.1.05 but only the clips for which you do a P2 organize after the firmware upgrade will have the right .xml file ...

Look at the .xml file ... at the bottom you will find what it was all about for me ..
Hope this will solve the problem for others ...

Thanks for all the feedback ... great forum !

Greetings from Brugge in Belgium. (chocolate and beer)

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<P2Main xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:schemas-Professional-Plug-in:P2:ClipMetadata:v3.0">
<ClipContent>
<ClipName>0445BW</ClipName>
<GlobalClipID>060A2B340101010501010D431300000000072F1F022D2838B729EA0200001883</GlobalClipID>
<Duration>242</Duration>
<EditUnit>1/25</EditUnit>
<EssenceList>
<Video ValidAudioFlag="true">
<VideoFormat>MXF</VideoFormat>
<Codec>DV100_1080/50i</Codec>
<FrameRate>50i</FrameRate>
<StartTimecode>06:24:00:22</StartTimecode>
<StartBinaryGroup>D70F5023</StartBinaryGroup>
<AspectRatio>16:9</AspectRatio>
<VideoIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>139392000</DataSize>
</VideoIndex>
</Video>
<Audio>
<AudioFormat>MXF</AudioFormat>
<SamplingRate>48000</SamplingRate>
<BitsPerSample>16</BitsPerSample>
<AudioIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>929280</DataSize>
</AudioIndex>
</Audio>
<Audio>
<AudioFormat>MXF</AudioFormat>
<SamplingRate>48000</SamplingRate>
<BitsPerSample>16</BitsPerSample>
<AudioIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>929280</DataSize>
</AudioIndex>
</Audio>
<Audio>
<AudioFormat>MXF</AudioFormat>
<SamplingRate>48000</SamplingRate>
<BitsPerSample>16</BitsPerSample>
<AudioIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>929280</DataSize>
</AudioIndex>
</Audio>
<Audio>
<AudioFormat>MXF</AudioFormat>
<SamplingRate>48000</SamplingRate>
<BitsPerSample>16</BitsPerSample>
<AudioIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>929280</DataSize>
</AudioIndex>
</Audio>
</EssenceList>
<ClipMetadata>
<UserClipName>FS Default Clip Name 20061117-074731W01</UserClipName>
<DataSource>SHOOTING</DataSource>
<Access>
<CreationDate>2006-11-17T07:47:31+00:00</CreationDate>
<LastUpdateDate>2006-11-17T07:47:46+00:00</LastUpdateDate>
</Access>
<Device>
<Manufacturer>Focus Enhancements</Manufacturer>
<SerialNo.>0002EA0200001883</SerialNo.>
<ModelName>FS100</ModelName>
</Device>
<Shoot>
<StartDate>2006-11-17T07:47:31+00:00</StartDate>
<EndDate>2006-11-17T07:47:46+00:00</EndDate>
</Shoot>
<MemoList>
<Memo MemoID="0">
<Text>20061117-074731W01.xml</Text>
</Memo>
<Memo MemoID="1">
<Text>0445BW</Text>
</Memo>
<Memo MemoID="2">
<Text>Software Version # 2.0.1.05102406</Text>
</Memo>
</MemoList>
<Thumbnail>
<FrameOffset>0</FrameOffset>
<ThumbnailFormat>BMP</ThumbnailFormat>
<Width>80</Width>
<Height>60</Height>
</Thumbnail>
</ClipMetadata>
</ClipContent>

</P2Main>
 
I've been using the 2.0.1.05 firmware and have the problems, they just are not consistant. So, the firmware update isn't the solution.
 
You must log in or register to reply here.
Back
Top