Firestore Import problems with FCP 5.1.2 red status ...

Just posted feedback. I will also send word through my Apple contacts. I could provide all of you some email adresses, but then I would have to shoot you. Worse, I might have to turn my wife loose on you who is at the moment cooking up a new batch of Potassium Cyanide.

Ben-- while I did not consider it economically sensible for me to achieve the Apple Certified Trainer status, I do know never to advise anyone to trash files other than trashing prefs.

But what we definitely have here is an issue with FCP.

Ned
 
A new thought ... as some of you say ... it worked fine ... but now it doesn't ...
I have my timecode set at continuing ... meaning I am now somewehere at 6 hours 35 minutes 20 seconds 15 frames ... just a thought could it be a certain point in the timecode that triggers the bug ? I didn't reset the timecode for a while ... just a thought ... I'll reset it and see what happens ...
 
<Releation> entry

<Releation> entry

Deleting the "Relation" entry in the .xml file allowed me to import my bad clip into FCP 5.1.2.

Here are the steps to remove the entry.

1. Organize P2 (This only needs to be done once.
If you have already done an organize, then there
is no need to repeat this step)
2. Enter DD Drive mode (to mount the drive on the Mac)
3. navigate to the folder /CONTENTS/CLIP
4. Make A backup of the .xml file in question (just in case)
5. Use a text editor to edit the .xml file. My file was named "0229BW.xml"
6. Remove the <Relation> entry. This is everything in RED (shown below)
7. Save the .xml file
8. Un-mount the Firestore
9. Try to import it into FCP 5.1.2


Please let me know if this works for anyone else. I only had one bad clip, so I could not try it a second time.


Below is my .xml file. I removed everything in RED, then clip imported into FCP 5.1.2. I didn’t modify anything else in the .xml file.
--------------------------------------------



<?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>0229BW</ClipName>
<GlobalClipID>060A2B340101010501010D4313000000000F053A022D28308E87EA0200002069</GlobalClipID>
<Duration>8288</Duration>
<EditUnit>1001/60000</EditUnit>
<Relation>
<OffsetInShot>0</OffsetInShot>
<GlobalShotID>060A2B340101010502010D4313000000000F053A022D28308E87EA0200002069</GlobalShotID>
<Connection>
<Top>
<ClipName>0229BW</ClipName>
<GlobalClipID>060A2B340101010501010D4313000000000F053A022D28308E87EA0200002069</GlobalClipID>
<P2SerialNo.></P2SerialNo.>
</Top>
<Next>
<ClipName>0230RW</ClipName>
<GlobalClipID>060A2B340101010501010D4313000000000F0E05022D2830B316EA0200002069</GlobalClipID>
<P2SerialNo.></P2SerialNo.>
</Next>
</Connection>
</Relation>
<EssenceList>
<Video ValidAudioFlag="true">
<VideoFormat>MXF</VideoFormat>
<Codec>DV100_720/59.94p</Codec>
<FrameRate DropFrameFlag="false">59.94p</FrameRate>
<StartTimecode>00:00:00:00</StartTimecode>
<StartBinaryGroup>F2012482</StartBinaryGroup>
<Pulldown>2:3</Pulldown>
<AspectRatio>16:9</AspectRatio>
<VideoIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>1989120000</DataSize>
</VideoIndex>
</Video>
<Audio>
<AudioFormat>MXF</AudioFormat>
<SamplingRate>48000</SamplingRate>
<BitsPerSample>16</BitsPerSample>
<AudioIndex>
<StartByteOffset>32768</StartByteOffset>
<DataSize>13274064</DataSize>
</AudioIndex>
</Audio>
<Audio>
 
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 thet diamonf 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>060A2B340101010501010D43130000004567 23C6943105E90000000000000000</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 looks a bit long ... but so does diamonds ...
 
First up, XML files are only text files, so 4K is normal. Can you detail how you're importing? What device? How did you set it up? The given info does nothing to trouble shoot without the info we really need.
 
It Works !

It Works !

Oversight !

It was the firmware update on my Firestore !

So basically ... when I upgraded my Firestore with the clips already shot and organized on them ... it didn't work ... !

After Diamond told me about his .xml file and my missing <memo id2> where firmware 2.0.1 from focus is mentioned ... I did a format disk ... shot three new clips ... did a P2
organize ... connected DD ... went to import and it works !

So ... the point was ... I needed the firmware 2.0.1.05 and you have to have it upgraded before the shoot ... upgrading after the clips are on is no help.

I hope ... more people are helped by this ... for me I can flag this thread as solved.

Thanks all of you ...

No excuse for being lazy now ... Have to get out there and catch up with the lost days.
 
HD Belgium - are you trying to waste our time on purpose? In this post you clearly stated "What I have is FS-100 version 2.0.1.05102406" like 4 days ago...now you say you upgraded 2.0.1. were you lying? i must say i'm very confused.

regardless, for all the others here that have the latest firmware, the problem is still happening. glad you fixed yours - but no one else is helped.
 
hmmm .. lying is a bit strong ...

hmmm .. lying is a bit strong ...

As I write ...

I upgraded to 2.0.1 ... after I already had clips that did not import ... the upgrade to 2.0.1 ... did not help ... for those already on the drive present clips ...

It was after I deleted everything with a format DD ... and started recording new clips that ... the new ones ... did import.

So ... 2.0.1.05 firmware works for all new clips ... but all the clips I dumped before
on the backup drive ... can't be imported !

I hope I am making myself clear and that others can use this.

Thanks to all for the help ... and I hope I was not wasting anybody's time...

S.
 
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.
 
A couple of clips that did not span

A couple of clips that did not span

There might be a workaround for this issue reported by nsoltz and other members:

Here is a quote from nsoltz:

"My issue is probably a different one with what seemed to be a couple of clips that did not span. Everything is there but just broken into several clips. And no problems importing."

---------------------------------------------------------------------

Although this problem might belong to a different forum, I still want to post what worked for me and yachtclubav.

For some unknown reason, FCP 5.1.2 only recognizes every other clip as spanned. For example, 4 long clips (greater than 2:16), will be shown in the import window as the following:

Clip 1 -- Spanned
Clip 2 -- not spanned
Clip 3 -- Spanned
Clip 4 -- Not spanned

Keep in mind that clip 2 and 4 will be broken into 2 minute 16 second parts. This patter is very repeatable.

Here is what I suggest trying.

1. Make a backup of all .xml files. Located on Firestore in the folder /contents/clip
2. Delete all .xml files except the ones that belong to the spanned clip in question.
3. Start FCP 5.1.2
4. Try importing the clip.

I know this sounds crazy. But, the trick is to get your clip to be listed first in the P2 import window. If it is listed first, then it might show spanned.

Diamond






 
Is the Firestore firmware 2.0.3 update related to this ?

Is the Firestore firmware 2.0.3 update related to this ?

Hi ... picking up an old thread ... just saw the firmware 2.0.3 update mentioned by Focus ... Is this update related to this issue ?
 
That fix didn't work for me. It's Apple's P2 driver. 2.0.3 won't fix it, the problem is in Apple's OS.
 
You must log in or register to reply here.
Back
Top