Firestore Import problems with FCP 5.1.2 red status ...

[HD Studio Belgium]

Hi ...

I started this topic some time ago but thought I had done something wrong in doing
multiple P2 organize commands after three different recordings on same FS100 ...

Today however I went out with an empty completely 'format drive' and shot only 2 minutes of footage.

I imported my HVX P2 card through FCP 5.1.2 ... with new capture window and no problem. Afterwards I conncet FS 100 ... thumbnails show up in capture window ...
I can even play the clips in preview ! ... but when I want to import them into the queu
a red status warning sign shows up and the auto import does nothing !

Last time I thought it was my doing ... but this is straight from a new formatted drive ...
the odd thing is that I can play the clips in preview ... but not import ...
Help would be really welcome ...

Thanks ...

Using a new MacPro dual core 2.66 with 4 GB of ram OS X.4.7 and FCP 5.1.2

[Matthew McEwen]

I sent you a Private Message. I need some more information that may help in sorting this out.

Thanks,
Matt

[chadgalloway]

I've just experienced the very same problem. I own 2 FS-100s . Shot all this morning and now on import, using FCP 5.1.2, Have a single shot that is playable in the import window but will not transfer. It has a Spanned in brackets next to the shot. Tried all the obvious actions such as reboot, new project, etc.

Any advice would be hugh. Thanks a lot.

Chad
chadgalloway@gmail.com
604 219 5847

[HD Studio Belgium]

Mike I didn't get the private message ... I only got an email from techsupport@como.com or was that it ?

[HD Studio Belgium]

Matthew,

I upgraded the firmware to 2.0.1. Did a system reset. Did a repair disk and repair clips.
Connected FS100. Through FCP 5.1.2 ... import Panasonic p2 ... thumbnails show up ...
can even play the clips in preview and set in and out points ...
when I drag them into import pane or even add them to queu ... the red status shows up. Sometimes it goes spinning as if it will download but the progress bar doesn't move and then it goes to red status.

What am I doing wrong?

2 attachments ... grab from FCP and grab from contents of FS100 drive ...

[nsoltz]

What I usually do (and am doing it, in fact as I write this response) is copy the files from the Firestore to my hard drive. I then import the mxf files into FCP from the files on the hard drive(s) rather than from the FS-100.

Ned Soltz

[HD Studio Belgium]

Hi Ned,

Are you using Final Cut pro 5.1.2 ? After searching some forums ... ther seems to be a real issue with this upgrade and P2 import files ... I am not alone!
Tried your moving to harddrive and had no luck.

[BenB]

Belgium, what firmware version are you running on the FS-100?

[HD Studio Belgium]

Firmware version 2.0.1 ...

Hitting a retry does not work for me ... moving the contents folder files to a harddrive doesn't help ... I'll go in search of a FCP 5.1.1 setup now ... Matthew ... please don't stop looking into this ... there's lots of people on digitalcow forum having the same problem ...

[HD Studio Belgium]

By the way ... thanks everybody for the suggestions ... this forum is really very valuable ...

[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.

Ned

[BenB]

2.0.1.what? Need full number, there's two versions of "2.0.1".

Only FCP 5.1.2 will span, 5.1.1 will not, and you lose all sorts of P2 Import abilities going back to 5.1.1. I'm going to venture a guess this won't work, as 5.1.1 was SUPER buggy with P2 data, horribly buggy.

[HD Studio Belgium]

What I have is FS-100 version 2.0.1.05102406

[yachtclubav]

I must chirp in here as I had the same thing happen this week. Using 2.0.1.05102406 on the FS and FCP 5.1.2. There was a 12 minute clip I was trying to import in FCP. of course it was 6 or so clips spanned together. When i drag it to the queue it went red with Error : Unkown. The clip would play fine in the viewer.

I went back to the firestore to use repair clip from the utils menu, thinking that could help it. That ended up erasing the video data from the first clip in the spanned set. So then i was able to import all the 2:16 chunks of video after the first clip, but lost the first 2:16.

Does this sound like what is happening to you all - well the first part at least?

I am also having major problems with spanned clips coming in as incomplete clips. It seems to be really hit or miss....sometime they span - sometimes they don't.

[nsoltz]

OK... this is what I am experiencing... spanned clips not spanning but reporting as incomplete. Now I have not lost any data and everything has imported. Additionally, many other clips are spanning properly.

Ned Soltz

[yachtclubav]

yes ned - same here.

to be clear i am having two problems - which i realize should be dealt with in seperate posts. but since we're here:::

1. red status error : unkown. clip plays fine in viewer - will not import in FCP 5.1.2.

2. random incomplete clips. Some clips come in spanned properly. Some clips show up as incomplete.

- this is the first time I have had problems with my FS (have only had for 1 month). Seems to be centered around the 5.1.2 upgrade.

Does anyone know how to downgrade to 5.1.1? Is the P2 bugginess that BenB reports a major problem?

thanks-
anthony

[HD Studio Belgium]

Well I couldn't find the 5.1.1 upgrade ... I reinstalled ... 5.1 crossgrade discs ... but now can't find 5.1.1 ... Are we sure the problem is with FCP 5.1.2 or did some of you get the problem after upgradong quicktime to 7.1.3 ... I just can't remember if I ever was able to use my FS 100 in 5.1.2 ... or if it actually did work until I installed the upgrade to quicktime ... or if it simply never worked ...

The odd thing is I remember speaking to Matthew at IBC in Amsterdam and he was using the beta of 5.1.2 ... and that one seemed to work ... or am I confused and was it
Canon who was using the beta at the time ?

I will now try to copy my content folder on the P2 card (No Name) of the HVX when it is mounted on the desktop ... I'll see if I can transfer the files and then afterwards import them ...

Keeps us busy on a sunny saturday ... I really should be filming out there ... but then If I can't import it ... a catch 22 ...

[BenB]

Ok, I just joined the ranks. My first, thankfully not of any value, clip just hit the snag. Just like you guys, plays fine, but when you add it to the import queue, error.

I also tried P2 Log, and it's worse. P2 Log won't import anything at all from the whole batch of clips, no matter if I try them one at a time, or all together. It gives me an error message that names a specific clip. And get this, the clip it names is DIFFERENT from the one FCP has a problem with!

At least FCP is getting some of it in, where as P2 Log, as is common in my experience with it, failed miserably.

I'm thinking the P2 driver for the Mac needs a fix. Spreading questions via every avenue I have available to me to find out what's going on.

I strongly recommdn ALL FCP users go to this URL ASAP and file complaints about P2 being super screwy with Macs.

http://www.apple.com/feedback/finalcutpro.html

I'm BEGGING you all to do it! This would be the most sure fired way to get Apple to move their ass on this.

[yachtclubav]

Yikes!

Just filed my concern/complaint with the apple feedback dept. What is interesting to me is that the drop down menus for version numbers of FCP and QT do not include 5.1.2 or 7.1.3.

I cannot isolate whether it was 5.1.2 upgrade or 7.1.3 upgrade that started this happening. Am trying to find 5.1.1 from 5.1 crossgrade discs as well - no luck. please post if you find this update somewhere.

The weird thing is I've had 5.1.2 working plenty of times. The red error only happened 5 days ago - completely isolated from upgrading anything and at that point I started reading numerous occurances. Not glad that it's happening to everyone - but at least i'm not going loony. It is terribly confusing though as it seems to be random.

Since it could be some time before we do see this addressed does anyone know if using Serious Magic DVCProHD Decoder would at least pull video from the MXF file so it can at least be salvaged. P2 Log didn't do anything to help me either.

Isn't this supposed to be working already?!?!?

[BenB]

I don't think it's a 5.1.2 issue, or QT issue, because some users had this problem before the upgrade. Because P2 Log has major problems, too, and it happens to P2 cards in card slots, in the camera, in P2 Stores, FS-100, I conclude it's an Apple P2 driver thing. I can see no other possibility.

I took some not so bright suggestions from another FCP trainer, trashed some files, and now my P2 Import window won't span clips anymore. Trashing things may make things worse.

[nsoltz]

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

[HD Studio Belgium]

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 ...

[BenB]

I reset my TC every shoot, that's not it. To some, it never worked fine, too.

[diamond]

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>060A2B340101010501010D4313000000000F053A022D28308E 87EA0200002069</GlobalClipID>
<Duration>8288</Duration>
<EditUnit>1001/60000</EditUnit>
<Relation>
<OffsetInShot>0</OffsetInShot>
<GlobalShotID>060A2B340101010502010D4313000000000F053A022D28308E 87EA0200002069</GlobalShotID>
<Connection>
<Top>
<ClipName>0229BW</ClipName>
<GlobalClipID>060A2B340101010501010D4313000000000F053A022D28308E 87EA0200002069</GlobalClipID>
<P2SerialNo.></P2SerialNo.>
</Top>
<Next>
<ClipName>0230RW</ClipName>
<GlobalClipID>060A2B340101010501010D4313000000000F0E05022D2830B3 16EA0200002069</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>

[Matthew McEwen]

See other possible work around on this thread...
http://www.dvxuser.com/V6/showthread.php?t=78220

[HD Studio Belgium]

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 ...

[BenB]

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.

[HD Studio Belgium]

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.

[yachtclubav]

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.

[HD Studio Belgium]

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.

[BenB]

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.

[yachtclubav]

I made a new thread to outline the methods that have worked for me in several tests. These current threads seem cluttered and i wanted to keep it organized somewhere... but sorry for the mulitple threads on the same topic!

http://www.dvxuser.com/V6/showthread.php?t=78488

[diamond]

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

[HD Studio Belgium]

Hi ... picking up an old thread ... just saw the firmware 2.0.3 update mentioned by Focus ... Is this update related to this issue ?

[BenB]

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.