Bad files on DR-HD100
 

I just test recorded some shots using my HD100 (A version) w/ the DR-HD100 and two out of the four clips I recorded (in 24p) wouldn't open. They show up as clips with the appropriate file size, etc., but when I go to open them, I get a message that says "Error opening movie - the movie could not be opened".

I had this happen before when I was shooting 30p so I doubt its a 24p thing. Fortunately, I have the tape as a backup, but I'd rather not run into this problem. This will be my second shoot with the DR-HD100 and I've had the problem twice forcing me to digitize a number of clips.

Is there something I could be doing wrong or are other people running into this problem?

My setting on th HD100 are 1394 rec. trig. - synchro, back space (hdv) - p-1394, DR-HD100 A. OFF - ON
(I'm not sure what that last setting means - it sounds contradictory!)


Thanks.

Did you try the "repair" function on the Firestore? If you go to the utilities menu, you can repair the disk and it should fix those clips.

Hannah,

I did that, but not until after I'd erased them, so I don't know if that would do the trick. I did another batch afterwards and they all were fine. Maybe that's the way to go. Next time, I'll try repairing the disk.

Thanks.

If you erased them from the drive but still have them on another drive, transfer them back over and repair it, leaving the file names the same (or at least as a timecoded file name). Many times we will get the files that are 0KB files and we just erase those, but we have never had a problem once we repaired the clips.

Same here
 

Posted this some days ago:
"I'm using the DR-HD100 with the GY-HD100E, latest firmware (2.1). Thanks to the upgrade it records QuickTimes 750p25. Until then I've never had any problems with the firestore. But now it starts writing files that have the estimated size, but they seem to be broken. I can't access them. Tried everything. The "funny" thing is, that this issue appears randomly. I can take 30 clips on a long shoot (without powering the unit down) and 3 of the files are corrupt. Next time everything's just fine and two hours later 3 of 5 files are broken. Tried the build-in disk repair (under UTILITIES), but no luck."
When recording m2t, everything is fine. So I think it must be the QuickTime wrapper. I've noticed, that the downloadable upgrade and that one on the CD I purchased have different md5 values. I booted the DR-HD100 from the factory image (reset to vers. 1.0) and applied the downloadable upgrade. Haven't had time to do intensive tests, but now the QuickTimes are ok. (Knock on wood...)

QuickTime corrupt
 

It is not certain, in m2t is no problem, in dv either. It is as if the QuickTime container did not close well some archives.
In truth the Dr-100 if who has recorded clips, but he has closed them badly, but luckily he has solution: -)
To recover the corrupt archives, we connected the DR-100 in way “DV I/O” and opened the DVHScaps, from this gratuitous program we captured as if a magneto one was, m2t will recover the archives in format. Also we can use the DR-100 from our NLE (Premier, FCP, Edius, etc) and will capture the material like any magneto. Later with mpegstreamclip we turned them to HDV 25 without no problem. It is clear that it is a failure of the Focus but at least any paper clip is not lost, and that for my is reassuring.
greetings.

Still no go
 

It definitely must a problem with the QT wrapper. At first sight the downloadable upgrade seemed to do the job. But I did some testing, and some files are broken again :-(
It only happens when recording 720p25 as QT (.mov), not when recording .m2t.

Fernando, can you please describe step by step how you manage to capture those broken files directly to your computer? Tried dvhscap and Final Cut Pro, in both cases the device is recognized, but I'm not able to capture anything.

Problem solved
 

I hopefully have solved the problem:
FireStore -> SETUP -> HDV TC TYPE -> REC TC (instead of TTC if you're editing in Final Cut)
Now all clips recorded by the DR-HD100 are fine.

FYI my FireStore settings:
RECORD -> NORMAL
HDD MODE -> HD RECORDER
HD FORMATS -> QUICKTIME
SETUP -> STOP NO VIDEO, EXT CTL OFF, TC EXT, TC / UB not set, HDV TC TYPE -> REC TC
FUNCTIONS -> FA JVC GY-HD

JVC GY-HD100E: OTHERS (2/2) -> 1394 REC TRIG SYNCRO

Andreas, when you list for your settings "REC TC (instead of TTC if you're editing in Final Cut)", do you mean that TTC is proper for FCP or that REC TC is? I'm not sure what editing system you use.

Also, I just finished another shoot (after upgrading to 2.2) and everything was fine - audio came through, etc. - except one nagging problem: out of my eight clips, one of them is a file that won't open - "error opening movie - the movie could not be opened". This happens on almost every shoot I go on. One of two files simply won't open. I shoot interviews, so these files usually represent minutes of lost interviews. Obviously I have the tape as backup, so it's not a disaster. Just an annoyance. Has anyone else had this problem? I'd love to know what - if anything - I'm doing wrong.

Thanks.

Hi Bill,

I'm cutting in Final Cut Pro 5.1.4. I do news and documentary, so I have to be fast and have to rely on my data.
According to the user manual of the firestore you have to set HDV TC TYPE to TTC. I just tried setting it to REC TC to get around this bad files issue. Now all of the files are fine without any hassle inside Final Cut. Just works. Have to do some critical shots tomorrow, will let you know if it works.
Hope that helps.

Andreas

Thanks. I'll be curious to see how it turns out.

I just did a quick search and discovered that REC TC makes the Firestore generate its own timecode. I can't do that as I need the timecode from the tape to match the timecode on the firestore. Is that not an issue with you?

Hi Bill,

while playing around to find a solution "REC TC" worked.
But today, in a real world situation on a real shooting, it failed. Again those bad files.
Seems that the firestore is reliable - until you really have to rely on...

Sorry about the bad news.

Please post, if you find a solution!

I noticed the same problem while recording QT25p.
This is already a serious issue, but I noticed something else :
Again, in QT25, some gaps of 12ms (no more, no less) appears randomly in the middle of a file. Never happened before I began to shoot with the 2.1 upgrade.

I hope Focus will manage to fix theses problems asap, since it's basically making the DRHD100 unreliable (And tend to make my editor act paranoid)...

Got a message from Focus Enhancement. They think it could be FCP 5.1.4 or Apple made some changes in QuickTime. The development team takes a look at the issues. And BTW, I was surprised about their quick answers. Great support!

I had this problem with 2.1 and never with 30P clips. Since 2.2 came I have been fine. They did address an issue with HDV 2P, but not sure if this was it or not. So far so good though.

No, vers. 2.2.0 didn't solve the problem. The issues are with 720p25 recorded as QuickTime, m2t works. Funny thing is I can capture those bad files the way Fernando mentioned. But this way some frames seem to be lost.
BTW, there's a thread on a German forum, same probs, also vers. 2.2.0:
http://www.finalcutprofi.de/phpboard...=156193#156193

How do we get the unit to act like a controllable deck in FCPro to playback these files? Is that how your outputting them? I can get it playing back on the LCD, but I can't seem to get FCPro to recognize the device. I am using the DV port on the DR-HD100.

When I use computer, nothing, or it just act like a removable in DD mode.

Hi Dave,

connect the firestore to your Mac via dv i/o. Power it on. Start FCP. Go to "Log and Capture". If your setup is correct the firestore will be recognized as a non-controllable device. Select the clip you want to capture (or set the firestore to "Play all"). Hit "Capture Now" in FCP and press the play button on the firestore.
I prefer capturing via DVHSCap or AVCVideoCap (part of Apple's FireWireSDK) and then converting the m2t files in mpegStreamclip. Using FCP I loose up to 6 sec of the beginning of each clip, while FCP says "searching for media".

Got an email today from Focus Enhancement:

"OK, I just ran some tests with the following....

JVC GY-HD101 camera - Rev A
DR-HD100 recording 720p/24 HDV QuickTime with software version 2.2 (JVC control mode).
Powerbook G4 with Final Cut Pro 5.1.4 and QuickTime version 7.1.3.

I did...
20 clip recordings with tape.
50 clip recordings without tape.

All clips imported and played fine.*

I also upgraded QuickTime Player to version 7.1.5 and re-recorded another 50 clips (w/out tape) and all imported fine.**

The only thing I can think of is Intel Mac vs. Power PC, but I noticed that the first customer in this string is also using a PowerPC Mac (quad G5) like my test machine.**

So, to really understand this, we need to try and get some bad clips from the customer and maybe find out some more info about their shooting setup.* Also, can you ask the customer if they tried to import the bad clips a second time?"

I've uploaded two broken clips so they can test them, let's hope they solve the issue.

To show that it's not only my problem with the firestore, please guys contact FE <<support(at)focusinfo.com>> too!

Andreas
if I want to log and capture on the final cut in my mac pro, as if it was to recorder DVI/O does not work.Mac intel does not work with DR-HD100, only work in mode computer I/O.

Why?

Hi Javier,
I don't know how things are on a MacPro. I've tested it on a G4 PowerBook and a G5 Quad. Works on both machines.
Connecting the firestore via dv i/o it will not appear on the desktop. Important: Make sure that you connect the firestore via dv i/o, then press "on", then start FCP. Your FCP setting should be 720p25 (easy setup).
But using FCP to capture you will loose up to 6 sec of the beginning of each clip (FCP says "searching media").
So I prefer capturing via DVSCap or AVCVideoCap and use mpegStreamclip to convert the captured m2t files. Did you try this?

I am using a Mac Pro and my set up is diff in that I am using a HD250. The 2.2 upgrade added support for the 250 in QT.

Out of a day of shooting perhaps 40 clips, about 8 are bad. I noticed at least two of the bad ones are 2 GB files that are then split at the 2GB mark and continue. The 2GB files are bad, while the ones that continue on are fine. But , then again, a few others are bad that are like 200- 400megs.

Dave

Focus USA:
"Can you please verify that the OTHERS->BACK SPACE setting on the GY-HDXXX camera is set to P-1394."
And Focus Germany:
"“If the customer has a tape in the GY-HD100E camera when recording, then their camera’s “BACK SPACE” setting may be set to “P-TAPE”. It should be set to “P-1394”.
If this setting is not available on their camera, then they will need to contact JVC to find out the details.”

Please, can someone test it? I don't have this setting available on my cam, JVC suggests an upgrade.

I still think it's the DR-HD100 that causes the problems, because we all in this thread are using different cameras but the same DR-HD100 v2.2.

Edit: Sorry, just noticed that the first one in this thread (Bill) wrote:"My setting on th HD100 are 1394 rec. trig. - synchro, back space (hdv) - p-1394"

Dr-HD100 and Ver 2.2
 

Hi:

Based upon the stated problems with the Version 2.2 software update as it relates to the QT format, I have delayed installing it for use with my HD 250U but I wonder if I am missing out on any other advantage of the upgrade?
In addition, is the mt2 format retained as a recording option and has it been determined if the reported issue is related to the Focus software or that of FCP 5.1.4?

Thank you inadvance,
Ron

Hi Ronald,

the advantage of the upgrade is to record QuickTimes you can edit directly in FCP.
Recording m2t files requires to convert them to something FCP can work with.
The m2t option remains after upgrading to 2.2. No changes there, just works as before.

It doesn't seem to be a FCP related problem, it looks like the DR-HD100 and the GY-HDxxx aren't interacting well.

Got this message from Focus:
"When I spoke to the development team about your files they said it was because of the camera firmware. So they think upgrading it would fix the problem. They are aware of Bill Parkers files and wanted to look at them. I asked him to send them a copy or upload them. I am not sure where they are with his files.

I kind of lean with you. I have another customer that has the GY-111 and it has the firmware upgrade yet he is also having problems. At this point we have 5 customers experiencing problems with 3 being from Europe. So we are not sure what is exactly going on.

The test group was able to recreate the problem by not having the OTHERS>BACKSPACE setting setup correctly. However, this is not the case with a couple of customers. The test group and most of our customers are not experiencing problems and able to record just fine. So it has been a difficult problem to troubleshoot.

If it isn't hard to do I would upgrade your camera just to see if it will fix the problem."

I've sent my GY-HD100E to JVC for upgrade. Hopefully get it back 'til end of the next week. Will report whether upgrading the cam has solved the problem.

Dr-Hd-100
 

Hi Andreas:

Thank you for your reply.
As far as I know, there is no firmware update for the GY HD-250U since it is a relatively new model and, in addition, a post from Dave Beatty (above) states that he has experienced problems with some QT clips and his HD 250. I wonder if all of those who have experienced problems are using the same version of FCP and if the issue is in any way related to its latest update, 5.1.4?
In any event, until the issue is resolved, I will continue to use the MPStreamclip conversion of mt2 files which adds only a minimal degree of inconvenience.
Ron

Hi Ron,

it's not that you only can't edit those bad files in FCP, there's no application to open them. Though they "contain" a playable stream. You can "recapture" them via FCP or DVHSCap (see previous posts). So those bad files are not lost. And I had bad files before FCP 5.1.4 / QuickTime 7.1.5 / OS 10.4.9.

You said the "conversion of mt2 files (...) adds only a minimal degree of inconvenience." I'm doing news, so time is the most critical thing.

I hinted the Focus team to the fact that we all use different cams with different firmware versions and we have the same problems. The only component we all use is the DR-HD100 v2.2. I may be wrong, but this tells me: it's not the cam, not FCP and not Apple's QuickTime that causes the problem.

So, having sent my cam to JVC and hoping the problem will be fixed is wishful thinking. But the Focus team continues researching the issue and man, their support is great. So I don't give up and hope I will be able to edit directly soon.

Dr-HD100 and Ver 2.2
 

Hi Andreas:

I agree, from a purely logical prespective, it would appear that the problem resides in the DR HD-100 software given the fact that not all files are problematic. Hopefully, Focus will arrive at a solution but for the time being, I see no advantage in updating my software to the version 2.2. The time lost in recapturing unreadible files is probably equal to the time spent in file conversion and that does not even address the frustration and anger that I would assume accompanies the interruption of workflow by the finding of unreadible files.
Ron

no issues after cam upgrade
 

Got my GY-HD100E back yesterday, JVC changed some hardware and did an upgrade, don't know what they exactly did, but now everything seems to work.
Spend hours on testing (HDV 720p25 QuickTime), shot a huge amount of short clips and also beyond the 2 gig limit, no issues. Seems the cam upgrade finally did the trick.

I wonder if there's a similar upgrade for the HD100. I already have the A version. I haven't heard any solutions to the problems I've been having. I'm not even sure if it's a Dr-HD100 problem or HD100 problem.

DR-HD100 v2.2.1 released
 

"Focus Enhancements DR-HD100 2.2.1 update README file

RELEASE NOTES:

version 2.2.1.04032307:
- Resolved occasional corrupt QT HDV files with non-continuous stream from the GY-HD camera."

I haven't tried it jet, because I'm in production right now, but I've been involved in beta-testing this upgrade, and the beta just works as supposed.

Thank you Focus! I love that company. Always listen to us here and get in the fixes quick.