Clips go black

Comments

Marc S wrote on 9/28/2011, 8:46 PM
Gosh, this is getting to be a real pain. Renders are completely unreliable. I have to render my projects to a new track and then play through and find all of the time clips go black (which is often) and re-render those sections. Sony fix this!
Serena wrote on 9/29/2011, 2:27 AM
Marc, you do have a ticket about this in the support system?
Marc S wrote on 9/29/2011, 3:38 PM
No I have not filed a ticket on this. I'm trying to work out a Cineform levels issue with Sony on another ticket so I have not bothered since so many people have complained about the clips going black and I assume have filed tickets. Guess I should file a ticket but Sony response is very slow and on intermittent bugs like this they tend to go on for years.

Marc
Serena wrote on 9/30/2011, 12:37 AM
One user with a problem may be just that user's problem, but when many users have that problem then it is Sony's problem. And the same basic bug may be reported differently by one or two users, so never gets fed up to the development team. Presently I'm not suffering the black clip thing, for no clear reason, so I cannot hammer SCS for not fixing it. Part of the reason is I'm spending more time on production instead of post, but nevertheless my solid attempt to now reproduce the problem has failed (so far).
NickHope wrote on 10/16/2011, 5:17 AM
I am getting this problem today with regular PAL DV clips in Vegas Pro 10.0e.

I'm frameserving out with Debugmode Frameserver for external rendering. Occasionally after such operations, one or two clips and their preview go completely black and I have to reopen Vegas to see them again.

I haven't changed from Sony's own DV codec.

Not sure there's any point me filing a bug report as I'm on an unsupported O/S (XP x64) so I know what the answer would be.
Serena wrote on 10/18/2011, 6:10 AM
I've just renewed my request for the problem to be fixed. Today I've spent several hours trying to render a 3.5 minute short and I haven't been able to achieve a single render in which a random clip doesn't go black. It is the same effect as setting the mute switch on the video, although I presume that isn't what is happening. Audio never affected. If people don't put in requests for support then it is assumed to be an isolated problem of no global importance and is presumed to be some problem outside of Vegas (e.g. virus protection software, which I'm not running on my editing machine).
It was happening during editing and the fix was to close the project and reopen (no need to restart Vegas), and that wasn't much impediment. But in rendering the problem is a killer.
NickHope wrote on 10/18/2011, 6:25 AM
My problem seems to be related to bringing .avi files of a 3rd party codec back onto the Vegas timeline. I'm frameserving from timeline containing DV .avi files to Virtualdub via AviSynth, rendering Ut Video Codec lossless files, and bringing them back onto the Vegas timeline. Haven't established an exact pattern yet though, but there's some .avi conflict going on.
AudioDan wrote on 10/18/2011, 10:03 AM
I've been having a similar problem since Vegas Pro 8. I use 5DmkII footage (MOV) and have been experiencing black/green/red thumbnail previews in both the project media window and the timeline for at least two years. SCS told me it was a problem related to Quicktime being 32bit, and although Vegas 10 improved the problem slightly, it didn't solve it.

I tried last year to get a "show of hands" on the forum to see if anyone else had been experiencing the problem but I was promptly reprimanded by a long-time forum member who didn't like what I was saying and so the thread got lost amongst that argument instead of what I intended it for

Since then I had massive issues trying to find and AVI intermediate that didn't change the colour of my Canon footage, and the only two options I've found have been Sony's uncompressed codec (as AVI) and Cineform (as AVI). Though only by converting from the timeline have I been able to maintain the colour with Cineform. If I convert using Cineform's batch converter or with any other batch converter that can see the CF codec then the colour changes. I even tried adjusting it in First Light but couldn't get it to match.

Overall Cineform has been a solution for me though I should add that my computer is not connected to the internet and I always, by default, disable a good number of the background services that were mentioned earlier in this thread.

The only other thing I can add to this from my experience is that the solid colour preview issue seemed to be affected more by the number clips included in the project, than by the size of the files. That is, I could take a huge file and cut it up into a large number of clips and the problem wouldn't occur, but if I introduced a large number of small files into the project it would cause the preview issue.

I hope you get the problem resolved.
Regards,
Daniel
Serena wrote on 10/20/2011, 6:33 AM
Overcame the immediate problem by taking two Neo renders into a new project (each render having different black spots) and cutting those to give me a project with just 3 clips, then rendering that.
I had observed that the same set of clips were involved in turning black and that obviously at least one of those had been trimmed in the trimmer (which hasn't been functioning as it ought). Because of that malfunction only a few clips had been so processed, so I made a list of them and set about doing renders of the original project to record whether those were the clips involved in the problem.
Rather remarkably the problem has vanished --- all renders were fine. This may be the action of Murphy's Law, since I had got the render I needed, but I think not. Yes, the bad renders were happening yesterday and my machine was turned off overnight, so an obvious conclusion is that the problem is in the machine. However the "black clip" problem had been experienced frequently during several editing sessions, so it wasn't a simple matter of the computer needing a reboot to clear its mind.
Puzzling.
TheRhino wrote on 10/20/2011, 8:24 AM
I have had clips go black on the timeline and during rendering when using Motion-JPEG video on the timeline. This has forced me to waste time double-checking all rendered footage for black areas.

Just to be certain it wasn't something I loaded after Vegas 10e, I went back to a bare minimal OS image that just has Windows 7 64 and Vegas. Still does it without any other programs or Virus software running in the background...

One solution has been to cut the problem area into smaller chunks & re-save the new VEG file (since it would be a pain to re-edit all of those smaller chunks if needed...) Although I still render-out the full video, Vegas seems to handle the smaller chunks fine. Also, I have moved the source video to another hard drive & told the VEG files to search for them in the new directory. This has also helped but it is a pain.

I am really hoping Vegas 11 fixes this. Haven't had the courage to start using 11 yet, but will try it when I have some less critical work on the plate...

Workstation C with $600 USD of upgrades in April, 2021
--$360 11700K @ 5.0ghz
--$200 ASRock W480 Creator (onboard 10G net, TB3, etc.)
Borrowed from my 9900K until prices drop:
--32GB of G.Skill DDR4 3200 ($100 on Black Friday...)
Reused from same Tower Case that housed the Xeon:
--Used VEGA 56 GPU ($200 on eBay before mining craze...)
--Noctua Cooler, 750W PSU, OS SSD, LSI RAID Controller, SATAs, etc.

Performs VERY close to my overclocked 9900K (below), but at stock settings with no tweaking...

Workstation D with $1,350 USD of upgrades in April, 2019
--$500 9900K @ 5.0ghz
--$140 Corsair H150i liquid cooling with 360mm radiator (3 fans)
--$200 open box Asus Z390 WS (PLX chip manages 4/5 PCIe slots)
--$160 32GB of G.Skill DDR4 3000 (added another 32GB later...)
--$350 refurbished, but like-new Radeon Vega 64 LQ (liquid cooled)

Renders Vegas11 "Red Car Test" (AMD VCE) in 13s when clocked at 4.9 ghz
(note: BOTH onboard Intel & Vega64 show utilization during QSV & VCE renders...)

Source Video1 = 4TB RAID0--(2) 2TB M.2 on motherboard in RAID0
Source Video2 = 4TB RAID0--(2) 2TB M.2 (1) via U.2 adapter & (1) on separate PCIe card
Target Video1 = 32TB RAID0--(4) 8TB SATA hot-swap drives on PCIe RAID card with backups elsewhere

10G Network using used $30 Mellanox2 Adapters & Qnap QSW-M408-2C 10G Switch
Copy of Work Files, Source & Output Video, OS Images on QNAP 653b NAS with (6) 14TB WD RED
Blackmagic Decklink PCie card for capturing from tape, etc.
(2) internal BR Burners connected via USB 3.0 to SATA adapters
Old Cooler Master CM Stacker ATX case with (13) 5.25" front drive-bays holds & cools everything.

Workstations A & B are the 2 remaining 6-core 4.0ghz Xeon 5660 or I7 980x on Asus P6T6 motherboards.

$999 Walmart Evoo 17 Laptop with I7-9750H 6-core CPU, RTX 2060, (2) M.2 bays & (1) SSD bay...

TheRhino wrote on 10/20/2011, 8:29 AM
Oh, another problem is that when I cut the problem section into smaller chunks, occassionally the smaller chunks all start at the beginning of the original clip instead of maintaining continuous video of the original clip. If I go-back to an earlier save and re-do the cuts, everything works out ok. Again, it's a pain because I loses confidence that my renders will not have any black scenes....

Workstation C with $600 USD of upgrades in April, 2021
--$360 11700K @ 5.0ghz
--$200 ASRock W480 Creator (onboard 10G net, TB3, etc.)
Borrowed from my 9900K until prices drop:
--32GB of G.Skill DDR4 3200 ($100 on Black Friday...)
Reused from same Tower Case that housed the Xeon:
--Used VEGA 56 GPU ($200 on eBay before mining craze...)
--Noctua Cooler, 750W PSU, OS SSD, LSI RAID Controller, SATAs, etc.

Performs VERY close to my overclocked 9900K (below), but at stock settings with no tweaking...

Workstation D with $1,350 USD of upgrades in April, 2019
--$500 9900K @ 5.0ghz
--$140 Corsair H150i liquid cooling with 360mm radiator (3 fans)
--$200 open box Asus Z390 WS (PLX chip manages 4/5 PCIe slots)
--$160 32GB of G.Skill DDR4 3000 (added another 32GB later...)
--$350 refurbished, but like-new Radeon Vega 64 LQ (liquid cooled)

Renders Vegas11 "Red Car Test" (AMD VCE) in 13s when clocked at 4.9 ghz
(note: BOTH onboard Intel & Vega64 show utilization during QSV & VCE renders...)

Source Video1 = 4TB RAID0--(2) 2TB M.2 on motherboard in RAID0
Source Video2 = 4TB RAID0--(2) 2TB M.2 (1) via U.2 adapter & (1) on separate PCIe card
Target Video1 = 32TB RAID0--(4) 8TB SATA hot-swap drives on PCIe RAID card with backups elsewhere

10G Network using used $30 Mellanox2 Adapters & Qnap QSW-M408-2C 10G Switch
Copy of Work Files, Source & Output Video, OS Images on QNAP 653b NAS with (6) 14TB WD RED
Blackmagic Decklink PCie card for capturing from tape, etc.
(2) internal BR Burners connected via USB 3.0 to SATA adapters
Old Cooler Master CM Stacker ATX case with (13) 5.25" front drive-bays holds & cools everything.

Workstations A & B are the 2 remaining 6-core 4.0ghz Xeon 5660 or I7 980x on Asus P6T6 motherboards.

$999 Walmart Evoo 17 Laptop with I7-9750H 6-core CPU, RTX 2060, (2) M.2 bays & (1) SSD bay...

NickHope wrote on 10/20/2011, 12:30 PM
Rhino, are those problematic Motion-JPEG files avi files?
Laurence wrote on 10/20/2011, 1:18 PM
My occasional black frame problem is with photo jpeg .mov clips, at least that's where I've noticed it. Haven't tried these clips with Vegas Pro 11 yet.
John_Cline wrote on 10/20/2011, 4:56 PM
I get the occasional black frame issue on Cineform files, in fact, it's not just a black frame, it's usually an entire clip that goes black for no apparent reason. This happened in v10 and now v11.
Serena wrote on 10/20/2011, 7:41 PM
John, yes, the entire clip going black is the problem. Somehow comforting that you have experienced this because it allays the fear that it's all in my imagination.
Laurence wrote on 10/20/2011, 9:21 PM
I just ran a test render. Black frame bug is still there with Vegas 11 unfortunately.
Laurence wrote on 10/21/2011, 12:10 AM
Black frames with Vegas 9 as well. The only way around it with Photo Jpeg mov clips is to use HDLink with Cineform I'm afraid.
NickHope wrote on 10/21/2011, 4:22 AM
Yep, mine is the whole clip, not just frames. I'm seeing the problem with Ut Video Codec .avi files.
John_Cline wrote on 10/21/2011, 4:42 AM
I think we can all agree that it isn't any one specific codec that has the problem, it's potentially all of them. I've even had JPG and PNG stills go black. This certainly seems to point the finger squarely at Vegas.
Laurence wrote on 10/21/2011, 8:04 AM
this is a very serious bug.
fordie wrote on 10/21/2011, 10:43 AM
I too can report this as a bug, its so frustrating rendering a large project overnight to then realise that you have lost 5 seconds of footage because its just black.
It happens at random points with no warning. very frustrating and has cost me hours of work. I have very little confidence in large renders anymore.
I hoped vegas 11 would perhaps solve this but I see a report that it hasnt....
vegas 10E 64 bit windows 7 64 bit..
NickHope wrote on 10/21/2011, 10:57 AM
One rather pathetic workaround to save yourself a wasted render is to zoom into the timeline a bit and scan along the timeline for "empty" events. In my case it's obvious if an event is going to be black or not because the thumbnails disappear and I just see a white event. Before doing it, turn on all thumbnails (options > preferences > video > thumbnails to show in video events > all).

Restarting Vegas fixes it for me, so it's probably a good idea to restart Vegas right before a big render.
fordie wrote on 10/21/2011, 12:09 PM
thanks, good advice..but I wish sony would fix it.
Vegas Filmmaker wrote on 10/21/2011, 2:14 PM
Same problem here. I frequently have to restart projects because of this. All my footage is avi that Cineform Neoscene makes from AVCHD footage.