Vic, remembering that m2t is a GOP compression, make sure you have "quantize to frames" enabled. Alt+F8 or Options menu. Hope this works for you, I have never experienced the problems you refer to . . . V7e.

"Edits that do not occur on frame boundaries can produce an undesirable visual result."

Darryl

Vic, if the black frames are exactly two, and appear occasionally in the middle of a m2t clip - two workarounds are working for me:
1. Take Dynamic Ram down to Zero. The missing frames return. (This was discovered by farrs and works for many, but not all.)
2. Drag to create a short region which includes the black frames. Render to New Track, using the HDV template. For me, this also brings back the missing frames.

Good luck,
Peter

"Vic, my understanding is that this occurs when editing native m2t footage - if you use Gearshift proxy's or Cineform files, the issue doesn't seem to rear its ugly head."
=========================================================

I edit almost nothing but M2T directly on the timeline. I NEVER have crashes on 7d, but it's quite the different story on 7e. (I've rolled back to 7d after a rather huge number of 7e crashes... the crashes have gone)

As I have said before in other posts, I am almost sure this is a 7e bug. If you look at the posts carefully, you will notice a sharp increase in "CRASH" complaints since the introduction of 7e.

Actually, Vic, I'm more interested in what has changed in your system or workflow to have these problems suddenly start. I haven't had these problems that some other people have. And I'd like to keep it that way!

Did you recently install some new software or hardware?
Did you change anything in your workflow, like capture with a different program?

i too suffer the 2 blk frames. haven't as yet tried the ram to 0, or re-installing 7d. but the last time i had it, it was most frustrating. (quantise is always on).

i had to move to 7e cause 7d had a bug that would occasionally lose tc, or not read tc on batch capture (pal sd) - i do a lot of edl work)

as yet my clients haven't moved to hd - so my experiences are limited to my own productions shot on a v1. the 2 frame thing is annoying, but the above was costing me time and money.

let's hope we get a 7f that cures this before having to shell out on v8....

leslie

"i too suffer the 2 blk frames. haven't as yet tried the ram to 0, or re-installing 7d. "
=============================================================

I still get the black frame issue in 7d, but the crashes (for me anyway) are non existent pretty much in 7d as opposed to 7e.

With 7e I would get a crash if I even looked at vegas the wrong way....especially with renders. I must have done 4 or more videos in 7e and not one did a complete render without crashing (for absolutely no apparent reason) at least 10 times. The last video I did was so bad that I finally just began to start vegas rendering where the last crash left off.... and I then took all of the crash pieces, treated them like scenes, imported them to pinnacle studio, put it all together on the timeline and rendered out as one video......... it was a loooong night!!

Ushure -

I can't really give a definitive answer as to "what changed" since, once I got serious about editing HDV, functionally everything changed.

Plus, unlike a lot of you, I haven't be "full steam" editing. I've more been gathering footage and doing really simple edits. Now as memory serves, I didn't have too many problems with the 2 frame issue (although, I DO think there were some) and NO crashing problems with 7c and 7d.

So I have been shooting and editing in those two programs (from Sony Z1) on a Pentium 920 Duo Core since last November, basically w/o incident.

Last month, I upgraded the system to Q6600, Raid 0, 2 Terrabytes of outboard SATA data, and two terrabytes of onboard system, program, backup and "working guts" drives (if that makes any sense). And I upgraded to 7e.

Last week I restarted editing - still simple stuff. But suddenly the two frame drops have become an issue and forget about crashes - too many to count.

This morning, in frustration I removed 7e and reloaded 7d. Clips that were crashing on contact (literally touch the clip with the cursor, freeze the entire project terminally) are playing in 7d.

More to come - this is really fresh, but encouraging.

v

"This morning, in frustration I removed 7e and reloaded 7d. Clips that were crashing on contact (literally touch the clip with the cursor, freeze the entire project terminally) are playing in 7d."

=======================================================

YUP!

You're experiencing EXACTLY what I did.... 7e, total disaster........ 7d, rock solid again. There is something bad going on with 7e.