Has anyone seen this bizarre User Clip Name error?

T

TwinCitiesShooter

Active member
I've had the mother of all nightmare repair issues going with Panasonic for almost a year. They've sent me four replacement HVX200A cameras, and they've all had problems. This last one, arrived today, finally seemed OK, but then I saw a bizarre issue Ive never seen before. The camera often records to a formatted P2 card with a User Clip Name starting in "1024" (e.g. the clip name is 1024xx). So I'll format the card, and it will then record the first clip as 0001xx, as it should. Great. As a test, I'll format again, and within one or two more formats, we're back to 1024xx. Sometimes it has even started the card with 0516xx, and sometimes it erases the single file on the card but then, despite being formatted, records the next shot as 0002xx.

1024 is 2 to the 10th power (516 is 2 to the 9th power), so I'm wondering if there's some computer-based reason for this error. I'd be thrilled if there was some menu option that could fix this. Any thoughts?

I've tried both Type 1 and Type 2 in the Metadata settings, and as a Hail Mary, I set the camera to "Initial" to wipe out all settings. Problem is still there. The camera has the latest firmware, and the problem occurs on three different P2 cards (two 16GB and an E-series 32GB).
 
Interesting thought, Barry, it's possible it's been sitting on the shelf at Panny for a long time. I can leave the camera (turned off) plugged into wall power for a day, maybe that will charge the internal battery?
 
No go. Left on wall power for the day, still on wall power, and the camera is recording to empty P2 cards starting with random clip numbers like 0041xx, 0008xx, etc., rather than 0001xx.

Anyone seen this issue before?
 
That sucks, Looks like it's gonna be number five. I hate to say it, but where's the quality control. Four cameras in a row, all malfuntioning? Geez thats not good.
 
I've been on the phone with Panasonic Tech Support half the morning. The interesting and semi-reassuring thing is that once he updated the camera in his hands to firmware 4.10 (the latest, and it's what I have), he was getting the same error! He's still trying to figure it out, but I thought I'd give the DVXUser community a chance to figure it out first. So if you have any ideas or have heard of this error, please chime in!
 
That's what I was thinking, but then everyone would be seeing it, not just me and the Panny tech. And I've tried every configuration of metadata settings we can think of. Bizarre...
 
You must log in or register to reply here.
Back
Top