Vegas11/CineForm black frames -- positive news.

Comments

David Newman wrote on 2/5/2012, 9:58 PM
No, we just not expect a version 6 of NeoScene, but we have enhanced it add the new build will be out this week (version 5.6.2 I believe.)
Glenn Thomas wrote on 4/18/2012, 11:49 PM
I'm just wondering if this has been resolved yet? I'm running the latest version of Cineform Studio Premium (unless a new version been released since last week), and Vegas 10e. These black frames and whole black clips are now appearing more frequently and worse than ever before. I've tried restarting the computer and re-rendering the frames/clips that were black, but they're still appearing black. Very frustrating.

I don't know if upgrading to Vegas 11 will fix this? I don't need any of the additional features in 11, but I'm really starting to lose my patience here.
Laurence wrote on 4/19/2012, 12:11 AM
to use Cineform without black frames, I have to go back to V9. I don't use it anymore.
TheRhino wrote on 4/19/2012, 5:42 AM
I also get black frames with Cineform & Blackmagic MJPEG 422 codecs in 10e and 11. Therefore I too have to go back to Vegas 9e to get any work done when using either Cineform or Blackmagic codecs. I can live with other issues but not when my final renders end-up with several seconds of black footage.

I get the same results using different computers one of which has only Vegas & the Cineform & Blackmagic codecs - no other programs or FX installed...

This is a SERIOUS FLAW that has not been resolved in the last (2) versions of Vegas. Vegas 11 is the worst because it can spit-out just a handful of black frames that are hard to detect unless you test all outgoing footage.

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...

JJKizak wrote on 4/19/2012, 6:48 AM
Not sure why but I have never had black frames with Cineform from day one.
JJK
David Newman wrote on 4/23/2012, 5:10 PM
Glenn,

There was definitely a CineForm particular fix in Vegas and CineForm components to make 11 much better, such that we have no reproducible cases of this under Vegas 11.

All,
If what TheRhino suggests is true, and that multiple codecs are still showing this problem, that might be again out of our hands. Yet, I and most other users do not see this. I spoke with Sony Vegas engineering at NAB on this very issue, neither group are seeing this issue. If you have a project and clip(s) that have this problem, share it with the Sony and CineForm support teams so we can get to bottom of this.

Thanks,
David
TheRhino wrote on 4/24/2012, 8:04 AM
David,

I'm convinced the bug is within Vegas 10 & 11 and not 3rd party codecs. Vegas 9e uses the same codecs on the same system and has never rendered to black for me. On a 6-core 980X system with two separate RAIDs I can open (4) instances of Vegas & render (4) projects at once without a hiccup. This is pushing things but it still works. My normal workflow has me rendering one project in the background while I work on another in the foreground.

If I load the same project into Vegas 10e or 11.595 I get the render to black issue. I get the render to black issue even when I have only one instance of Vegas 10 or 11 running, but the problem seems to increase if I open more than one instance. Therefore I never render in the background in V10 and I simply do not use V11.

This tells me that the Blackmagic & CineForm codecs are fine but there is something wrong with how V10e & V11 handle renders.

Another observation is that on my 6-core 980X system with the exact same VEG, 9e 64 only uses about 60% of the CPU rendering whereas 10e 64 uses 100% which renders-out the project 40% faster. V11.595 is back down to only using 60% of the CPU. Therefore there have obviously been big changes in how the render engine works between 9e, 10e & 11.595. There should not be a 40% change in render speed unless major changes have been made.

EDIT: I have multiple workstations and the problem is still present after a fresh install of Windows 7 64, SP1 update, fresh Vegas install & fresh codec install - no other programs, no Internet, no Virus scanning software, nothing but Vegas, Blackmagic codec & Cineform...

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...

Mordy G wrote on 5/2/2012, 2:58 PM
I have noticed the black frames are not limited to Vegas, or Cineform specifically.
I never had anything like this happen until I started using all kinds of third party intermediate codecs like Matrox, DNxHD and Cineform to bring footage from After Effects to Vegas and vice versa.

First I noticed random black frames in Vegas renders when using DNxHD. After figuring it was some kind quicktime quirk (I know Vegas and Quicktime don't always get along so well), I switched to other codecs, including cineform. But it wasn't just in the finished render, I could see the black frames in the timeline as well.

So, I started using a different computer for Vegas, and for a while everything was fine. Then when I installed After Effects, DNxHD and Cineform on the same new computer, it started happening again... only this time THE BLACK FRAMES WEREN'T EVEN VEGAS' FAULT! Apparently, opening the cineform render from AE in media player revealed that playback would freeze exactly where Vegas displayed a black frame. Clearly, the file was corrupted during render. I can't seem to figure out what combination of things installed causes this, but let me say that its extremely annoying to work like this!

My Sony Vegas is still version 9, After Effects CS5.5, and latest Cineform codec (I even uninstalled DNxHD in case that was somehow still messing things up).

*Sigh*
vtxrocketeer wrote on 5/2/2012, 3:22 PM
Mordy, any reason you're not using still image (e.g., PSD) sequences when bouncing footage between AE and Vegas? That's a very robust work flow, though it doesn't address at all the problems with the video codecs and black frames you mention. Just a suggestion...