[I]Unfortunately, I think the problem of corruption at scene breaks is a flaw in the capture, not in the playback, but I'd be happy to be proven wrong.[/I]

I believe you are correct, the problem occurs during capture. The corruption is in the captured files. After I trim the last few frames off of each file, the corruption is no longer there. If it were a playback issue, I would think the last few frames would always get corrupted on playback, and no amount of editing would eliminate the problem.

Rick

I would like to take part. I have experienced it before on different camera, to shoot and capture. The black frames more so then the red. However I have had the red frame problem as well.

not meaning to be a negative nellie,, well yes i am.
glad to see this beta attempt by the sony guys,, but the procedure is crazy.or rather what is the procedure.
how about updating where we post our system specs so you will know what we have, instead of kinda what we may have, and start a new thread with the new reader and a place to post results,, those who do not frequent this site all the time may not read 50 posts in to find the download

Could the Sony people please edit their original post and add the instructions for the download so that people will quit posting useless "Me too!" replies in this thread?

I just wanted to be sure...

Other than posting our results to this thread, such as the XDCAM HD problem with the beta plug-in, there's no where else we're supposed to report our results to, correct?

SCS is reading this thread and getting our results here, right?

Just wanted to be sure, a couple friends of mine also edit XDCAM HD in Vegas Pro 8, and we don't want to let a problem with it happen in the forthcoming Vegas Pro 8.0c.

Thanks.

Seems to be working well for me.

HDV footage (split into scenes) captured from a Canon HV20 using HDVSplit loads without issue onto the Vegas timeline.

I am now happy to finally have computer hardware and a new .dll that permit trouble-free editing with Vegas and HDV - except that I tried a capture using Vegas with scene splitting, and it failed in the same way it always has for me (there were three frames at the tail of the clip before, and two at the head of the clip ahead that needed to be removed for a clean picture cut - and there was usually no sound with the last five or six frames in a clip before the split).

I just ran some tests that may be of interest here. I ran a single clip split by Vegas (with the bad ending frames) through a program called Mpeg2repair, and it reported (not surprisingly, at least for the picture) 1 corrupted frame, 0 corrupted audio, 69 corrupted video bytes, and 0 time stamp gaps. I also made a file of a few unmodified clips butted together (these showed bad frames at the ends, but I did not use clip ends at the loop ends when making the file), and when this file was scanned (surprisingly - but I guess making this file was essentially reconstructing the original unsplit video), it showed 0 errors. I then made a file of a few clips that I had modified by removing bad frames at the ends, and the scan (not surprisingly) showed 0 errors. It will take me a bit more time to prepare clips for editing (if I want to do this all at once), but I can skim quickly along the timeline and stop at the easily-spotted cuts and remove the three frames on the left and two frames on the right of each cut fairly easily and quickly. This is not perfect (especially with a cut that is tight), but this is workable for me and it is a minor problem compared with my earlier ones (and I can use HDVSplit for capturing with frame-accurate scene-splitting if desired).

More --
I just made a five-minute test video from the 19 clips captured for the tests above (which were trimmed manually), with added head and tail leaders, a title, some brightness-contrast keyframing, and transitions between most of the clips. The output file appears to have no flaws, and when scanned with Mpeg2repair, it showed no errors.

YAY! 8^)

(My hardware and software list is given in a previous post in this thread.)

there are three frames at the tail of the clip before and two at the head of the clip ahead that must be removed for a clean picture cut As I suspected, the particular fix that is the subject of this thread is probably not going to do anything about the still-suspect Vegas HDV capture capabilities. That's too bad because, while not as big a problem for most people as the black/red frame issues, creating captured files which have corrupt head/tail frames is still completely unacceptable in any video editing program, much less one that sells for a premium price (for a desktop application) and whose makers went out of their way to change the product name to include the word "Pro."

The HDV capture problems, which are different from the HDV black frame problems, must be fixed.

DRuether:

There is a script that automatically rips off a given number of frames from the beginning or end of a clip. I don't know the name of it while I'm sitting here away from that PC, but it can take care of all the clips on a timeline at once.

Do a search on this forum, or perhaps someone else can chime in. If not, I'll try to track it down later.

--Or just capture with HDVSplit, which I use exclusively, primarily for its clip-naming abilities.

Woeful for me.

The update took a tsequence that was previously captured as two files and split it into 18. It also introduced significant video and video artifacts that make the files unusable.

I'll uninstall and reinstall...

The newer dll has been brilliant for me - allowing me to finally opoen up content that I could not import before, and I have not had a single crash or error from it so far.

There is a script that automatically rips off a given number of frames from the beginning or end of a clip. I don't know the name of it while I'm sitting here away from that PC, but it can take care of all the clips on a timeline at once.

-------

Here's the script I made, Trim_Captured_Clips_v1.0.

Personally, I prefer using HDVSplit, and now with the new DLL, I don't need to use the script.

I'm an Acid Pro beta tester. The link posted takes me to the Acid beta download site. Is there any way for me to get the proper download? By the way, I would LOVE to be a Vegas beta tester.

OK, I got it. I used a different browser that didn't already have the wrong login saved as a cookie.

Is it normal for all the peaks to be rebuilt the first time they are read with the new hdv reader?

The fix has worked so far. I have a question for you all. Since I have installed the fix, it seems the quality of the picture has increased considerably. Does anyone else notice this?

Thanks for the patch - my problematic projects with HDVSplit Data now work without any problems on the first view.
Patch came a little late for me but better now than never!
Greetinx Tom

So far the patch is working great. The project I am working on that wouldn't render without crashing Vegas rendered perfectly. This is the most stable I've seen Vegas since 7d.

"I'm an Acid Pro beta tester. The link posted takes me to the Acid beta download site...."

Hmm, don't suppose you would like to tell us more about this little chestnut?

marks

At first sight, this does seem to have cured the faults I had. However the tests that I was able to do quickly are limited because of deletion of faulty files and renaming them leading to some uncertainty as to whether I was recreating problems EXACTLY.

I did not see red frames when I expected to.

If you hear no more from me, it is good news!!

Still continuing to work well. Absolutely no problems with files captured with HDV split. Several hours into a project and not a single red frame, freeze, or crash. Viewing at Full Best at 15fps on a Core2Duo.

Nice!

Lets test :)

I would like to test.
thanks