Hello Madison...just a friendly (friendly now...not so friendly if this doesn't get addressed) reminder...we need to get the errant 2 black frame bug fixed...and not wait for a new version.....Hopefully others are tired of this as well......
Use the Support button at the top of this page, if you have not done so already, and submit this as a bug report. I don't think that people at Sony read these forums with any consistency, and it's never been clear, when they do read them, exactly where that person actually works in the organization. However, I am pretty sure that the Support submissions get read by someone whose job it is to not only provide responses to you, but also submit bug reports to engineering.
people have complained about this for years. it's a very unstable bug that's near impossible (i've found) to reproduce on different machines. IE it can happen on my machine in the exact same spot in a project, but if you did every single step i did with all the same media, you couldn't get it.
best you can do is use phone-mail support. :/ looks like the bug reporting feature is gone (but they added a 3rd party support company?).
Hey, the third part is a 100% satisfaction guarantee. Perhaps call them & have them fix it. :D
On my system, it happens with HDV (never saw it with DV) but it is sometimes one and sometimes two frames. If you zoom way in on the timeline, the thumbnail image of the frame on the timeline is good, but the preview window shows black. Sometimes if you close and reopen the project, it's ok again. It is "real" in the sense that rendering the video does show you that black frame in your output.
Yes, with HDV and always exactly two frames (so far at least). And they stay in the same place too. Sometimes I can make them go away (for a while) by closing the current project, opening some other project, closing that and reopening the first project. On the other hand, if I just close Vegas and reopen it with the same project, the black frames are back.
it's a memory cache issue...as far as i can see...and at least in my experience, if you change your ram preview amount the black frames go away...it went away for awhile permanently...version 6.0 (with DV), but is back with a vengeance on HDV footage in version 7. several times I've taken preview DVDs to clients and just hung my head in shame when they popped up. oh well...am i tired of this...yes, do i think anything will ever be permanently done about it...nope.
I caught your reference... that was a good book; I read it while on a plane trip.
Alan Cooper and his wife Susan used to be good friends. Alan invented Visual Basic which he sold to Microsoft for an embarrassingly small amount of money. He then started consulting on user interface design, and that book was a major part of that whole stretch of his life. Absolutely fascinating guy.
I've no desire to tempt the fates, but I don't encounter this black frame problem, neither editing nor rendering. Starting with Vegas 5 and DV, and going through v6 and v7 with HDV. I guess I did get some black frames using V5, but they were caused by my not closing cuts up properly. Is it somehow related to hardware (and firmware) rather than to Vegas? I used v5 on a Sony laptop and otherwise AMD CPUs.
It might be useful to see whether there is any common factor (other than Vegas) which might point to the source of the error. System hardware, OS, size of project (length and number of tracks, HDV, DV). What percentage of users encounter the problem?
i for one have / am suffering two black frames here and there. cap with internal and with hdv split. no rhyme or reason, but they crop up every so often. bloody annoying to say the least.
leslie
3.2-2gb-asus mb. projects media (capture) usually 30mins plus.
My very weak theory on this subject is during ripple edits sometimes a clip will be dragged all the way from the end to the beginning creating a black frame. This only happened to me while dragging a clip from the end to the beginning of a project over the in-between clips. Sometimes all hell would break loose. I use the copy/paste now but sometimes it gets shaky and copy/pastes over existing clips and I traced this to the clicking/highlight/mouse action----the mouse pointer not being exactly in a clips "neutral area" because the timeline wasn't espanded enough to view the insides of the clip properly. Couple this action to not "unhighlighting" another forgotton clip event prior to copy/pasting and "gazowee" what the hell happened?
JJK
There is nothing like waiting six hours for a render, only to find you need to do it again because of this problem. Often a second or third render has new black frames in new locations. As far as I'm concerned, native m2t editing is not practical until this bug is fixed.
I get it when I work with m2t files regularly but I never get it working with Cineform. It is an absolutely horrible bug in my opinion, and yet Madison doesn't even seem to aknowledge it's existence.
Until it is fixed, my recommendation is just to work with Cineform.
After looking at that thread, I decided to put one of my m2t files on the timeline and one of the Gearshift-produced proxies above it...and the 2 blackframes were only on the proxie....hmmm....so know I don't know if this is indeed a capture issue or a dv proxie creation issue....
Editing a 2-cam shoot, just came across the 2-black-frame HDV bug again, on both cameras, within seconds of each other! So I am forced to cut between them at the split second between the breaks. This must get fixed. I submitted the below comment to Sony support- let's see what they say.
---------------------------------------------------------------------------------------------------------
Sometimes, two consecutive black frames appear in HDV format 1080i video from a Sony FX1 when viewed within Vegas 7.0e, although the video is otherwise normal. This is a bug in Vegas. I have checked and these two black frames do NOT appear when the same .m2t file is viewed in other applications. Womble MPEG Video Wizard (2005) and Nero Showtime 2.0.1.9 both display the .m2t file 100% correctly with no black frames.