cre8tive said:
My reading of the posts is that it is MacOS related.
I could be wrong, but I thought it was an OS X and FCP issue only.
Is it also extending to Windows and PCs?
Let's solve this glitch once and for all
- Thread starter Barry_Green
- Start date
My reading of the posts is that it is MacOS related.
I could be wrong, but I thought it was an OS X and FCP issue only.
Is it also extending to Windows and PCs?
Here is a thread I started when I got the glitch...
If you click on the link you'll see the severely destroyed frame (I got two ruined frames this instance).
This has happened before, but I deemed it a HDD problem since I was transferring to my Laptop's 4200 rpm drive... if hadn't happened in for a long time so I forgot about it. But when I went out to get some available lighting test shots for this short I am shooting in a week I got it again...
I DID NOT have the write protection switch on the write-protect position when transferring.
I have a PC laptop... a dv8130us from HP... the glitch happened with my Laptop's internal and a WD 1TB RAID1/0 HDD hooked up via USB 2.0 which was at the moment set up in a RAID1.
I use Vegas 7.0e (latest as of this post), and I do have quite a bit of crap running in the background but not excessive.
I also tried using P2 Genie which I just got, but it could not back up a single dump... Iit wouldn't start and I got weird errors which I did not record. Then I tried copying manually and I got yet an other problem, where it couldn't copy some of the files... However I immediately tried dumping after a fresh re-start with nothing running and it didn't help. I then had to manually copy (no-biggie) and it did work that way only it errored on the copy if the LASTCLIP.txt which I created myself... but I got these horrible artifacts...
I ordered a different HDD, this time an enclosure from Thecus and two Seagate 7200.10 320GB drives. I wonder if I should just keep the 1TB for now since speed isn't much of an issue and aparently this doesn't isn't connection/HDD related. (I was waiting to get straight into a 4+ bay enclosure and the WD 1TB (P-O-S) was a hold-me-over to be used as storage later.
Where are we at? Is this something new? Does the write protection solve the issue? Has Pana commented?
If you click on the link you'll see the severely destroyed frame (I got two ruined frames this instance).
This has happened before, but I deemed it a HDD problem since I was transferring to my Laptop's 4200 rpm drive... if hadn't happened in for a long time so I forgot about it. But when I went out to get some available lighting test shots for this short I am shooting in a week I got it again...
I DID NOT have the write protection switch on the write-protect position when transferring.
I have a PC laptop... a dv8130us from HP... the glitch happened with my Laptop's internal and a WD 1TB RAID1/0 HDD hooked up via USB 2.0 which was at the moment set up in a RAID1.
I use Vegas 7.0e (latest as of this post), and I do have quite a bit of crap running in the background but not excessive.
I also tried using P2 Genie which I just got, but it could not back up a single dump... Iit wouldn't start and I got weird errors which I did not record. Then I tried copying manually and I got yet an other problem, where it couldn't copy some of the files... However I immediately tried dumping after a fresh re-start with nothing running and it didn't help. I then had to manually copy (no-biggie) and it did work that way only it errored on the copy if the LASTCLIP.txt which I created myself... but I got these horrible artifacts...
I ordered a different HDD, this time an enclosure from Thecus and two Seagate 7200.10 320GB drives. I wonder if I should just keep the 1TB for now since speed isn't much of an issue and aparently this doesn't isn't connection/HDD related. (I was waiting to get straight into a 4+ bay enclosure and the WD 1TB (P-O-S) was a hold-me-over to be used as storage later.
Where are we at? Is this something new? Does the write protection solve the issue? Has Pana commented?
Last edited:
Mike Savino
Member
Seems to happen to only a few of us. Panny has not responded because its not happening to everyone. Looks to me like it could be electrical problem cause at the same time my headphone jack started to become finicky and I can hear timecode clicking in the headphone when it does work. (Not recorded but audible when playing back through the small speaker on the side) Maybe a short or something.???
To answer the import to Mac questions, I first saw the glitch when played back from the camera. NOT ON THE MAC. And no I don't have the cards as they get erase almost everyday.
Shot two more cards full yesterday and nothing. Camera---to P2 Store----to Mac.
I have a big shoot next week. I'm sure with the stress of trying to complete as many set-ups as possible I'll get a glitch. I will be checking all good takes from now on.
I love the P2 work flow... I can't see myself going back to my tape camera. ( which I still have... just in case)
I will be sending the camera in for repair once next week's shoot is over. Maybe the service center will find something.?
To answer the import to Mac questions, I first saw the glitch when played back from the camera. NOT ON THE MAC. And no I don't have the cards as they get erase almost everyday.
Shot two more cards full yesterday and nothing. Camera---to P2 Store----to Mac.
I have a big shoot next week. I'm sure with the stress of trying to complete as many set-ups as possible I'll get a glitch. I will be checking all good takes from now on.
I love the P2 work flow... I can't see myself going back to my tape camera. ( which I still have... just in case)
I will be sending the camera in for repair once next week's shoot is over. Maybe the service center will find something.?
ullanta
Veteran
Mike Savino seems to be seeing glitches in-camera; he at least has a problem that's neither Mac nor PC related; and which wouldn't be helped by the write-protect tab (since that would preclude recording at all).
Sounds like his cam has a lot of other problems, though, as well (bad connectors, audio spikes)...
Sounds like his cam has a lot of other problems, though, as well (bad connectors, audio spikes)...
OK, so I just finished shooting "A Walk in the Dark" a short (10 to 15min) and we filled up my 8GB card about 25 times maybe 30... not a single artifact!
This time around I was dumping to an external HDD through my PC laptop using the write protect idea... I also made sure and had the PC powered with AC just for the heck of it...
Also, yesterday I went back to the bridge for an insert and I forgot to bring the HDD so I went ahead and dumped to my internal 4200rpm HDD while running on battery thinking that if anything went wrong I'd just come back (8 blocks away)... it is just fine!
For me the write protect eliminated artifacts all together... I was getting one to about 10 destroyed frames per 8GB card... now: ZERO
This time around I was dumping to an external HDD through my PC laptop using the write protect idea... I also made sure and had the PC powered with AC just for the heck of it...
Also, yesterday I went back to the bridge for an insert and I forgot to bring the HDD so I went ahead and dumped to my internal 4200rpm HDD while running on battery thinking that if anything went wrong I'd just come back (8 blocks away)... it is just fine!
For me the write protect eliminated artifacts all together... I was getting one to about 10 destroyed frames per 8GB card... now: ZERO
HarryMaynard
New member
P2 Glitch with Mac OS
P2 Glitch with Mac OS
I have had a similar problem ( tetris style blocks ) when I copy to the P2 Store it stops copying and flashes an LED warning. If I try directly into my PCMCIA slot it shows an 'error code 36' and identifies the corrupt clip. This only happens with one particular P2 card. I have tried 3 others, in both slots and they have all worked fine. It seems to me that it is the card that is at fault.
P2 Glitch with Mac OS
I have had a similar problem ( tetris style blocks ) when I copy to the P2 Store it stops copying and flashes an LED warning. If I try directly into my PCMCIA slot it shows an 'error code 36' and identifies the corrupt clip. This only happens with one particular P2 card. I have tried 3 others, in both slots and they have all worked fine. It seems to me that it is the card that is at fault.
What system and software versions are we referring to?
HarryMaynard
New member
Mac OS 10.4.9 P2 store connected directly with USB. If I copy to P2 Store then it shows 'error' . if I use P2 store as a card reader ( drag and drop ) then an error shows during transfer and stops. the only way round this has been to identify the clip and remove it by inserting the card back into the camera
HarryMaynard
New member
The Glitch
The Glitch
I had the 'Glitch' . . and I narrowed it down to the P2 card I was using. I tried all the other options, ie: write protect, from P2 store etc and it still showed up. . . but annoyingly, itermittant. I suspected the actual card. I sent it back to my suppliers, who sent it to Germany, who sent it to Japan. I received a new card after 3 weeks and the 'glitch' has disappeared. I sent with the card a description of the faults, but received no feedback from Panasonic.
The Glitch
I had the 'Glitch' . . and I narrowed it down to the P2 card I was using. I tried all the other options, ie: write protect, from P2 store etc and it still showed up. . . but annoyingly, itermittant. I suspected the actual card. I sent it back to my suppliers, who sent it to Germany, who sent it to Japan. I received a new card after 3 weeks and the 'glitch' has disappeared. I sent with the card a description of the faults, but received no feedback from Panasonic.
monkeyking
Well-known member
Was this a 16gb card?
I just shot tons of footage on a big expensive 14 hour day and EVERY SINGLE CLIP has the drop outs. Unbelievable. I'm a dead man. this clips played fine in the p2 viewer from panasonic.
Here's my workflow: hvx200 in 720 24pn on a 16gb card. camera has latest firmware for 16gb card. Put p2 card in pcmcia slot on a 2 year old Compact PC laptop. Load via laptop to maxtor drive via usb. Write protect was left untouched (off). Came back to studio to transfer to FCP and find that every clip is a mess. reimported, same problem. DON'T KNOW WHAT TO DO AND CANNOT FIND A WAY TO SALVAGE THE FOOTAGE. P2 CARDS WERE ERASED AS PART OF NORMAL WORKFLOW.
-dead in the water.
Here's my workflow: hvx200 in 720 24pn on a 16gb card. camera has latest firmware for 16gb card. Put p2 card in pcmcia slot on a 2 year old Compact PC laptop. Load via laptop to maxtor drive via usb. Write protect was left untouched (off). Came back to studio to transfer to FCP and find that every clip is a mess. reimported, same problem. DON'T KNOW WHAT TO DO AND CANNOT FIND A WAY TO SALVAGE THE FOOTAGE. P2 CARDS WERE ERASED AS PART OF NORMAL WORKFLOW.
-dead in the water.
If the digital fruit salad isn't there when you view the clips in P2 Viewer, then your clips are fine.
Either the files got corrupted in the transfer to the Mac, or FCP introduced the problem when it rewrapped the clips into QuickTime containers. There was a problem with that in early 5.0.x versions of FCP, and apparently there is a new but slightly different problem with handling P2 media in the latest FCS.
Either the files got corrupted in the transfer to the Mac, or FCP introduced the problem when it rewrapped the clips into QuickTime containers. There was a problem with that in early 5.0.x versions of FCP, and apparently there is a new but slightly different problem with handling P2 media in the latest FCS.
If you dumped to a Mac laptop or are cutting in FCP ask the others, I am in the PC realm.
Unfortunately, to my knowledge, there is nothing you can do to salvage the footage other than Photoshop every frame. I hope this is not the case for you, but once the transfer is done and there are corrupted pixels, if you re-used the cards then there is no clean version of the footage. I really wish I knew of a solution. Keep track of this thread just in case I am wrong but I wouldn't gt my hopes up man. I am really sorry.
The way to avoid corruption when dumping cards, which worked flawlessly for me, is to switch the write protection tab on the P2 card itself before copying the file over. This has proven 100% effective for me in an XP-32bit laptop. I was getting many corrupted clips, but not every single one... more like one out of three or less than that. Since I started hitting the write protection switch I have not gotten a single bad clip.
All my best to you bro.
Unfortunately, to my knowledge, there is nothing you can do to salvage the footage other than Photoshop every frame. I hope this is not the case for you, but once the transfer is done and there are corrupted pixels, if you re-used the cards then there is no clean version of the footage. I really wish I knew of a solution. Keep track of this thread just in case I am wrong but I wouldn't gt my hopes up man. I am really sorry.
The way to avoid corruption when dumping cards, which worked flawlessly for me, is to switch the write protection tab on the P2 card itself before copying the file over. This has proven 100% effective for me in an XP-32bit laptop. I was getting many corrupted clips, but not every single one... more like one out of three or less than that. Since I started hitting the write protection switch I have not gotten a single bad clip.
All my best to you bro.
hvx_germanboy
Well-known member
I am really sorry to hear that, but how is the situation if you see the footage in the P2 viewer now? No artifacts, or finally artifacts too?
I would always give it a try and connect the maxtor on a PC again and check it there...that should definitly give you the answer (in NLE or P2viewer) if your footage is still fine or has been corrupted on a MAC....good luck...!
murrayjob
Member
Has this "corruption" problem been resolved, I've owned a HPX502 (Asia-Pacific version of the 500) for just a couple of weeks.
I noticed 1x corrupted frame on each of three clips, only one frame but a real concern especially when you have no idea where it has come from, the original clips were fine in the camera but when I copied them to my laptop the corruption has appeared, any definitive answers or work around for this problem ?.
(Vision was shot SD DV 50i 4:2:0 from a 16gb card directly plugged in to the PCMCIA slot of an ACER Aspire 5024wlmi laptop PC running XP Home with 1x GB of Ram, files directly copied through to an external USB 2.0 250gb drive)
I noticed 1x corrupted frame on each of three clips, only one frame but a real concern especially when you have no idea where it has come from, the original clips were fine in the camera but when I copied them to my laptop the corruption has appeared, any definitive answers or work around for this problem ?.
(Vision was shot SD DV 50i 4:2:0 from a 16gb card directly plugged in to the PCMCIA slot of an ACER Aspire 5024wlmi laptop PC running XP Home with 1x GB of Ram, files directly copied through to an external USB 2.0 250gb drive)
Attachments
Ted Spencer
Veteran
Was the P2 card write protected when you copied the files? So far this seems to be the only solution. Instances of this problem on the PC, while formerly almost unheard of, now seem to be popping up from time to time. Previously it was thought to be a Mac-only issue.
Again, write-protecting the card before transferring is evidently the answer. If you still have the original data on the card, you could try retransferring. If not, you might be able to fix it in something like Photoshop since it's only one frame.
Best of luck to you.
Again, write-protecting the card before transferring is evidently the answer. If you still have the original data on the card, you could try retransferring. If not, you might be able to fix it in something like Photoshop since it's only one frame.
Best of luck to you.
Just to reiterate what Ted already dispensed. You are be one of the lucky ones. If it is only one frame you should be able to export those frames to Photoshop and clone them.
Also, I believe that not allowing WinCrap to try to write little markers of how far it has copied to the card does the trick. This is a guess, but that write-protecting the card saves your footage isn't guess. It has worked flawlessly for almost a year for me and nobody that read about the trick has come back to say they still have the problem.
Also, I believe that not allowing WinCrap to try to write little markers of how far it has copied to the card does the trick. This is a guess, but that write-protecting the card saves your footage isn't guess. It has worked flawlessly for almost a year for me and nobody that read about the trick has come back to say they still have the problem.