Let's solve this glitch once and for all
- Thread starter Barry_Green
- Start date
Brian_Broz
Active member
Ok I admit I haven't read the 5 pages of posts...but I can tell you what the problem is FOR SURE. I have experienced this issue with too many Powerbooks!
The problem is related to playing footage from either an internal drive, but usually do to connecting external devices to the Powerbook's FW400 port.
100% of the time, getting a PCMCIA to Firewire card solved the problem (in my experience) as apparently the built-in fiirewire shares the bus on the motherboard with several other connections (the PCMCIA does not).
Barry I'm not sure if you've solved this issue...but it's usually a $50.00 fix (PCMCIA to FW400 adapter card). In my experience the footage is not damaged.
I have also witnessed this issue on 2 acer Ferrari laptops (tacky as heck) which was also resolved by a PCMCIA to FW400 adapter.
Try that and let us know. Perhaps someone has already answered this...sorry but I don't have time tonight to read the whole thread.
Cheers and hope this helps!
Regards,
Brian Broz
www.higherdefinition.com
The problem is related to playing footage from either an internal drive, but usually do to connecting external devices to the Powerbook's FW400 port.
100% of the time, getting a PCMCIA to Firewire card solved the problem (in my experience) as apparently the built-in fiirewire shares the bus on the motherboard with several other connections (the PCMCIA does not).
Barry I'm not sure if you've solved this issue...but it's usually a $50.00 fix (PCMCIA to FW400 adapter card). In my experience the footage is not damaged.
I have also witnessed this issue on 2 acer Ferrari laptops (tacky as heck) which was also resolved by a PCMCIA to FW400 adapter.
Try that and let us know. Perhaps someone has already answered this...sorry but I don't have time tonight to read the whole thread.
Cheers and hope this helps!
Regards,
Brian Broz
www.higherdefinition.com
ozduc
Well-known member
This thread will be long but it does narrow a few things down.
For about 4 months I have been using the HVX and P2 with my G4 PowerBook, first with OS 10.3.9 and FCP 5.0.4 and in the last month with OS 10.4.8 and FCP 5.1.2. My ususal work flow has been to insert the P2 cards into the G4 PCMCIA slot and copy the contents and last clip.txt to a bus powered acomdata 5400rpm ondago drive (while in the field) or directly to a hitachi 7200 rpm drive hooked up via FW800. (if power was available). So far I have not had an issue with any corrupt pixilated footage.
On the weekend myself and a collegue shot a bunch of footage (about 7 x 8gb cards) and used my G4 PB to load them to the acomdata drive. I always check the footage in the import P2 window of FCP to make sure it is OK before I format the card. All the cards copied OK.
After returning home on monday I copied the footage to one of my hitachi drives and once again checked in the import P2 window of FCP and everything was OK.
Here's where things get interesting.
Yesterday I go to my collegues house with my portable bus powered drive and hook it up to his Mac Pro desktop. He has a brand new G-Drive (that has just had a 0 level format done on it) hooked up via FW800, so I plug the acomdata drive into the FW400 port on the back of that and copy over the 7 cards worth of material.
Upon completion, I go to the import P2 window of FCP to check the footage and all the footage, I mean every clip, is totally and completely corrupt and pixilated, way worse than Barry's pic at the beginning of this thread.
So I check the footage from the acomdata drive on his macpro and it looks fine.
Then I disconnect his G-drive from the desktop and hook it up to my laptop and check the footage and it is still corrupt.
So I erase all the footage from the G-drive and start again but this time I connect the acomdata and G-drive to my laptop to do the copying.
Upon completion I check the footage on the G-drive in the import P2 window in FCP on my laptop and everything is OK. So I then connect the G-drive up to his Mac Pro desktop and open the P2 import window in FCP and ALL the footage plays fine, no corruption at all.
Being that we are both running the same OS and same version of FCP, I thought it must be something to do with the Mac OS on the intel machine. However after reading some of the other posts in this thread it appears to have happened to people with Power Macs as well.
I could be totally off base here, but this would indicate to me that the problem is at the finder level of the OS as it happened at the copying stage of the files from one drive to another. By this time there weren't even any P2 cards in site.
Hopefully this will narrow things down a bit for the fine folks at apple to address this major problem.
For about 4 months I have been using the HVX and P2 with my G4 PowerBook, first with OS 10.3.9 and FCP 5.0.4 and in the last month with OS 10.4.8 and FCP 5.1.2. My ususal work flow has been to insert the P2 cards into the G4 PCMCIA slot and copy the contents and last clip.txt to a bus powered acomdata 5400rpm ondago drive (while in the field) or directly to a hitachi 7200 rpm drive hooked up via FW800. (if power was available). So far I have not had an issue with any corrupt pixilated footage.
On the weekend myself and a collegue shot a bunch of footage (about 7 x 8gb cards) and used my G4 PB to load them to the acomdata drive. I always check the footage in the import P2 window of FCP to make sure it is OK before I format the card. All the cards copied OK.
After returning home on monday I copied the footage to one of my hitachi drives and once again checked in the import P2 window of FCP and everything was OK.
Here's where things get interesting.
Yesterday I go to my collegues house with my portable bus powered drive and hook it up to his Mac Pro desktop. He has a brand new G-Drive (that has just had a 0 level format done on it) hooked up via FW800, so I plug the acomdata drive into the FW400 port on the back of that and copy over the 7 cards worth of material.
Upon completion, I go to the import P2 window of FCP to check the footage and all the footage, I mean every clip, is totally and completely corrupt and pixilated, way worse than Barry's pic at the beginning of this thread.
So I check the footage from the acomdata drive on his macpro and it looks fine.
Then I disconnect his G-drive from the desktop and hook it up to my laptop and check the footage and it is still corrupt.
So I erase all the footage from the G-drive and start again but this time I connect the acomdata and G-drive to my laptop to do the copying.
Upon completion I check the footage on the G-drive in the import P2 window in FCP on my laptop and everything is OK. So I then connect the G-drive up to his Mac Pro desktop and open the P2 import window in FCP and ALL the footage plays fine, no corruption at all.
Being that we are both running the same OS and same version of FCP, I thought it must be something to do with the Mac OS on the intel machine. However after reading some of the other posts in this thread it appears to have happened to people with Power Macs as well.
I could be totally off base here, but this would indicate to me that the problem is at the finder level of the OS as it happened at the copying stage of the files from one drive to another. By this time there weren't even any P2 cards in site.
Hopefully this will narrow things down a bit for the fine folks at apple to address this major problem.
Barry is Video Columbo..... solving mysteries.... Good work man. I commend you. I am not a Mac user, but i am learning this anyhow so that if i ever have to use one i know what to look out for.
I thank all of you gentlemen.
I thank all of you gentlemen.
I'm not a MAc user however I wonder if you guys shouldn't be casting a wider net.
I recently got a tape from a FCP user that had similar problems, nothing to do with the HVX200 even remotely and the problem occured during PTT. Footage looked fine on the FCP T/L and a repeated PTT of the same section was perfect.
The problem tape had around 30 seconds where first the image went like it had massive tape dropouts and then what looked for all the world like a head clog on one head except it wasn't quite the same, one head band had a static frozen image from the start of the problem area and the other was being updated correctly. During all this the audio was totally gone.
It looks like a generic firewire driver issue is what's at the root of the problem but then again reading a P2 directly from a PCMCIA slot shouldn't involve the same driver however the same part of the kernal could be in use and that might be where the bug lies. That it seems to span various OSs is no surprise either, oftenly the same chunks of code survive even complete OS revisions.
Maybe I'm right off track here but I think widening the survey group beyond just HVX 200 users might be more revealing and fairer to the HVX200.
I recently got a tape from a FCP user that had similar problems, nothing to do with the HVX200 even remotely and the problem occured during PTT. Footage looked fine on the FCP T/L and a repeated PTT of the same section was perfect.
The problem tape had around 30 seconds where first the image went like it had massive tape dropouts and then what looked for all the world like a head clog on one head except it wasn't quite the same, one head band had a static frozen image from the start of the problem area and the other was being updated correctly. During all this the audio was totally gone.
It looks like a generic firewire driver issue is what's at the root of the problem but then again reading a P2 directly from a PCMCIA slot shouldn't involve the same driver however the same part of the kernal could be in use and that might be where the bug lies. That it seems to span various OSs is no surprise either, oftenly the same chunks of code survive even complete OS revisions.
Maybe I'm right off track here but I think widening the survey group beyond just HVX 200 users might be more revealing and fairer to the HVX200.
I have a MacPro. I mount the cam with a card in it and copy to the desktop.
Then I copy that to an SATA drive in one of the bays.
Never had a problem. I just don't use firewire hard drives.
Fingers crossed.
Then I copy that to an SATA drive in one of the bays.
Never had a problem. I just don't use firewire hard drives.
Fingers crossed.
adam powell
Well-known member
Hi Gents,
Just recently got hold of a 17" macbook pro, 2gig of ram. Running FCP 5.1.2
I've been running some tests to see if I want to edit my next project on a mac (been using Aspect HD on the PC but the Banding scares me)
Anyway, things aren't going well I've done tests using 2 methods....
ONE/ camera plugged into firewire port, copy the p2 folders (contents & Lastclip.txt) to the systems HD (no external drive as yet..waiting to see if this works before I go out and get a g-sata) then import.
one clip, straight from P2 in camera to MacHD then imports fine.
HOWEVER..
test TWO/ Plugged in a Lacie big disk via usb, dragged folders to the systems HD and tried to import. No dice.
I go into the folders...check permissions, and they are set to read only.. SO I change everything to Read & Write.
Go into FCP....click import and it works....fantastic...problem solved???
NO, I try again a few moments later and none of the clips from the lacieHD work...the one taken directly from the camera is fine, works every time.
now all im left with is a memory of that fleeting moment when all my clips would import.
(I've checked and double checked the files are still set to Read & Write, I could be missing something but in all honesty Im totally baffled.)
Just recently got hold of a 17" macbook pro, 2gig of ram. Running FCP 5.1.2
I've been running some tests to see if I want to edit my next project on a mac (been using Aspect HD on the PC but the Banding scares me)
Anyway, things aren't going well I've done tests using 2 methods....
ONE/ camera plugged into firewire port, copy the p2 folders (contents & Lastclip.txt) to the systems HD (no external drive as yet..waiting to see if this works before I go out and get a g-sata) then import.
one clip, straight from P2 in camera to MacHD then imports fine.
HOWEVER..
test TWO/ Plugged in a Lacie big disk via usb, dragged folders to the systems HD and tried to import. No dice.
I go into the folders...check permissions, and they are set to read only.. SO I change everything to Read & Write.
Go into FCP....click import and it works....fantastic...problem solved???
NO, I try again a few moments later and none of the clips from the lacieHD work...the one taken directly from the camera is fine, works every time.
now all im left with is a memory of that fleeting moment when all my clips would import.
(I've checked and double checked the files are still set to Read & Write, I could be missing something but in all honesty Im totally baffled.)
adam powell
Well-known member
sorry to be a pain, I know this isn't the point of the thread but if anyone has any suggestions on this I'd like to hear (via this page or PM?)...is it simply a bug with 5.1.2 ?
adam powell
Well-known member
ok so hopefully its not user error...
anyone got a work around? (Pm pm)
anyone got a work around? (Pm pm)
Rygh
Active member
I have had major drop outs lately on my cards. I have been paying a little more attention to see if I indeed captured sucessfully all the clips. My problems have nothing to do with FCP, or even the transfer. Just straight from the card itself. Here is how some problems happened to me.
This last shoot I had one clip on my 8gig P2 that did not record correctly. It would not show up on the camera (the clip before it in the viewer showed an exclamation mark on the upper right thumbnail), the clip also did not show on the P2 Viewer (just blank, where there should be a thumbnail), but P2 Genie brought up the clip, which I watched, it ran for 40 seconds fine, then it just took a dump to snow. The clip before it which I thought was fine, played through, but throughout the clip audio would take a dump and come back up for a couple of times.
I put this 8gig card to the side and marked it suspect to being a bad card. Went on another shoot without that card and put my P2 card in my Powerbook G4 to monitor the footage on P2 Log. All the clips were blank. After regaining my composure, I put the card back in the camera and viewed the clips in the camera, all were there. I remembered this happened before, and it was as simple as re-inserting the card back into the computer, and it worked fine.
However this problem did not resolve my issue with the suspected damaged 8gig P2 card. The camera could not repair the card, and I am still unable to save it.
I have narrowed it down to the camera, P2 card, and the powerbook. Why the camera? I have had difficulty with timelapse where I was unable to shut it off. So after trying anything I could think of I had to physically shut the camera off, and of coarse that clip is ruined. So I don't know if it hurt the P2 card so that it will cause all these problems for me. This timelapse was done on the same suspected card (although it has been reformated a few times over before having the next problem.)
They are spuratic, and that is what is frustrating.
This last shoot I had one clip on my 8gig P2 that did not record correctly. It would not show up on the camera (the clip before it in the viewer showed an exclamation mark on the upper right thumbnail), the clip also did not show on the P2 Viewer (just blank, where there should be a thumbnail), but P2 Genie brought up the clip, which I watched, it ran for 40 seconds fine, then it just took a dump to snow. The clip before it which I thought was fine, played through, but throughout the clip audio would take a dump and come back up for a couple of times.
I put this 8gig card to the side and marked it suspect to being a bad card. Went on another shoot without that card and put my P2 card in my Powerbook G4 to monitor the footage on P2 Log. All the clips were blank. After regaining my composure, I put the card back in the camera and viewed the clips in the camera, all were there. I remembered this happened before, and it was as simple as re-inserting the card back into the computer, and it worked fine.
However this problem did not resolve my issue with the suspected damaged 8gig P2 card. The camera could not repair the card, and I am still unable to save it.
I have narrowed it down to the camera, P2 card, and the powerbook. Why the camera? I have had difficulty with timelapse where I was unable to shut it off. So after trying anything I could think of I had to physically shut the camera off, and of coarse that clip is ruined. So I don't know if it hurt the P2 card so that it will cause all these problems for me. This timelapse was done on the same suspected card (although it has been reformated a few times over before having the next problem.)
They are spuratic, and that is what is frustrating.
I've had it happen on a couple occassions. Nothing horrible, I just took out the frame and replaced it... but it was there. My thought, and I could be wrong, was that upon first viewing that scene (the first few times, actually) it wasn't there -- when editing in FCP. Then a few days later I was editing (again in FCP) and I saw it. It seemed so blatant that I couldn't believe I hadn't seen it sooner. Made me wonder if it was an external hard-drive glitch (which is where it is stored and where I am editing the footage from).
Here is my process:
1) I dump P2 into my PC laptop's portable external drive (2.5 Hitachi) using the Panasonic P2 software -- or more recently P2 Genie.
2) Then, I attach the portable external drive to my Mac Desktop and drag the contents onto my Mac's harddrive.
3) Then, I import into FCP and start editing.
Pretty basic routine, I'd think.
Here is my process:
1) I dump P2 into my PC laptop's portable external drive (2.5 Hitachi) using the Panasonic P2 software -- or more recently P2 Genie.
2) Then, I attach the portable external drive to my Mac Desktop and drag the contents onto my Mac's harddrive.
3) Then, I import into FCP and start editing.
Pretty basic routine, I'd think.
berserkerfilms
New member
more updates on the glitch, has been reported to apple already. everytime i import this p2 card into fcp it causes it to crash on me, it is the 5th one out of 15 from this particular import. the others work fine. what i have noticed is that there is a mission file from the icon folder. this is on top of the fact that disk repair says that:
Verifying volume “NO NAME”
** /dev/disk4s10
** Phase 1 - Read FAT
FAT starts with odd byte sequence (f8fffffff8ffff0f)
Correct? no
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
/CONTENTS/VIDEO/0002Z9.MXF has too many clusters allocated
Drop superfluous clusters? no
/CONTENTS/AUDIO/0002Z900.MXF has too many clusters allocated
Drop superfluous clusters? no
/CONTENTS/AUDIO/0002Z901.MXF has too many clusters allocated
Drop superfluous clusters? no
/CONTENTS/AUDIO/0002Z902.MXF has too many clusters allocated
/CONTENTS/AUDIO/0002Z902.MXF has too many clusters allocated
uperfluous clusters? no
/CONTENTS/AUDIO/0002Z903.MXF has too many clusters allocated
Drop superfluous clusters? no
** Phase 4 - Checking for Lost Files
Free space in FSInfo block (3515) not correct (731)
fix? no
Next free cluster in FSInfo block (3) not free
fix? no
49 files, 23392 free (731 clusters)
Error: The underlying task reported failure on exit
1 non HFS volume checked
Volume needs repair
we are really busy on a documentary and every day counts so until i can figure this out Im really stuck because there is valuable footage on there. I can see all the other files, the audio, video proxy, clip and voice it is just the one file missing from the icon folder. i have tried to hard import it without using any software and then lauch from fcp, to import directly from fcp and to use p2 genie for the import. im running an intel mac, the latest one, and i can't figure out a way around this. Please help. I have also tried to restart, reimport multiple times, often on 12 mount instead of the full 15 on the remounts unless i fully restart. so i need to fix the disk image/drive whatever you call it so that i can get the p2 store reformatted and keep on rolling.
peace out
Verifying volume “NO NAME”
** /dev/disk4s10
** Phase 1 - Read FAT
FAT starts with odd byte sequence (f8fffffff8ffff0f)
Correct? no
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
/CONTENTS/VIDEO/0002Z9.MXF has too many clusters allocated
Drop superfluous clusters? no
/CONTENTS/AUDIO/0002Z900.MXF has too many clusters allocated
Drop superfluous clusters? no
/CONTENTS/AUDIO/0002Z901.MXF has too many clusters allocated
Drop superfluous clusters? no
/CONTENTS/AUDIO/0002Z902.MXF has too many clusters allocated
/CONTENTS/AUDIO/0002Z902.MXF has too many clusters allocated
uperfluous clusters? no
/CONTENTS/AUDIO/0002Z903.MXF has too many clusters allocated
Drop superfluous clusters? no
** Phase 4 - Checking for Lost Files
Free space in FSInfo block (3515) not correct (731)
fix? no
Next free cluster in FSInfo block (3) not free
fix? no
49 files, 23392 free (731 clusters)
Error: The underlying task reported failure on exit
1 non HFS volume checked
Volume needs repair
we are really busy on a documentary and every day counts so until i can figure this out Im really stuck because there is valuable footage on there. I can see all the other files, the audio, video proxy, clip and voice it is just the one file missing from the icon folder. i have tried to hard import it without using any software and then lauch from fcp, to import directly from fcp and to use p2 genie for the import. im running an intel mac, the latest one, and i can't figure out a way around this. Please help. I have also tried to restart, reimport multiple times, often on 12 mount instead of the full 15 on the remounts unless i fully restart. so i need to fix the disk image/drive whatever you call it so that i can get the p2 store reformatted and keep on rolling.
peace out
bbalser
Veteran
Oooooo, I don't think running Disk Repair on a P2 card was the smartest thing to do. Nope, I'd never do that. I'd run the repair utility in the HVX itself, but I'd never trust Apple's Disk Repair on a P2 card. For a whole variety of reasons I don't think it's a good idea. And running Disk Verify, I would think, based on my previous professional career, that anything it said about the state of a P2 card would be valid.
Now, all these "drop outs" on P2 cards, are we certain this is a Mac only thing? I'm just starting to suspect...
Now, all these "drop outs" on P2 cards, are we certain this is a Mac only thing? I'm just starting to suspect...
I use a PC laptop and still get the glitch
I use a PC laptop and still get the glitch
I use a PC laptop and still get the glitch.
My workflow:
I use two 4gb P2 cards cycled through a feature film shoot.
As one fills, offload it via P2 Genie into an HP Windows XP laptop's PCI slot.
Back at the editing station, I transfer all the MXF files from the laptop to an external hd via USB.
I connect the USB to the Mac, import into FCP 5.1.1 using Import>P2.
Occasionally, I'll see the glitch. I can sometimes reimport the file and the new QT file will be clean. But not always.
Ken
I use a PC laptop and still get the glitch
Barry_Green said:
I use a PC laptop and still get the glitch.
My workflow:
I use two 4gb P2 cards cycled through a feature film shoot.
As one fills, offload it via P2 Genie into an HP Windows XP laptop's PCI slot.
Back at the editing station, I transfer all the MXF files from the laptop to an external hd via USB.
I connect the USB to the Mac, import into FCP 5.1.1 using Import>P2.
Occasionally, I'll see the glitch. I can sometimes reimport the file and the new QT file will be clean. But not always.
Ken
Barry_Green
Moderator
It's still due to the Mac. The very fact that you can re-import and it doesn't glitch that time shows you that the cards that were copied by the PC are solid and reliable.
I hate to say it, because I know that something like 80% of HVX users are on the Mac, but dang it, something's broken in there and needs to be fixed. The PC side is flawless, the Mac side needs to be and it currently isn't.
I hate to say it, because I know that something like 80% of HVX users are on the Mac, but dang it, something's broken in there and needs to be fixed. The PC side is flawless, the Mac side needs to be and it currently isn't.
adam powell
Well-known member
I formatted my lacie to apple (hfs+)
last test i did I copied files to my lacie via a PC laptop then plugged the lacie directly into the mac and imported from there..worked fine.
gonna run a couple more tests...also some people have been telling me lacies are rubbish. and im gonna lose all my data.
and the world's gonna end. so I guess i need to find some money for a new external drive, did someone say this workflow was easy?
last test i did I copied files to my lacie via a PC laptop then plugged the lacie directly into the mac and imported from there..worked fine.
gonna run a couple more tests...also some people have been telling me lacies are rubbish. and im gonna lose all my data.and the world's gonna end. so I guess i need to find some money for a new external drive, did someone say this workflow was easy?