Stills problems in Vegas 11 build 521 and 511

kingpeterz@btinternet.com wrote on 2/22/2012, 11:51 AM
Recently, with Vegas 11 build 521, fade in and out no longer works with imported stills, or with generated media such as tiltes, test patterns, solid colours etc (by dragging the top right and left corners of the title media on the timeline). Also, the drop shadow effect produces a solid block of colour behind the text, i.e. it is not feathered, and has no transparency. I am using the Sony "titles and text" generated media, but the same thing happens with the Protype tiltler, NewBlue titler, and legacy titler

With stills, Instead of a fade, there is a flickering of posterized colours over the first and last 4 or 5 frames, with the number of colours reducing frame by frame to four colours than black before the fade ends.

Video, on the other hand, can still be faded in an out, so this is exclusively a still image related problem.

I have opened a number of different projects in this version and version 5.11, shut down the computer and restarted, to no avail. I have reinstalled both verions. I am not aware of changing any settings,.

I do not experience the same problems in another video editing program, Magix Movie Edit Pro 16, on the same computer, so it does not appear to be a hardware or Windows problem.

I am wondering if anybody else has had this problem. I may have to do a clean uninstall and reinstall, but I would rather not, if at all possible.

Any ideas would be most welcome

Peter King

Comments

ForumAdmin wrote on 2/22/2012, 12:09 PM
Hi Peter,

Have you applied the Levels plug-in to your project? If you disable GPU acceleration, does the problem go away? There is currently an issue with Levels that results in this type of behavior (when running on GPU, with certain cards). A fix is coming soon.

Hope this helps,
Paddy
SCS
Cliff Etzel wrote on 2/22/2012, 12:22 PM
issue yesterday that again confirmed why I won't use Vegas Pro 11 for any projects as much as I would like to:

simple one track video and audio each. Video clips had brightness/contrast applied only. Clips were tried both as basic AVID DNxHD and Cineform Intermediates each time. No mix and match - all were the same intermediate each time I tried.

Went to render a 720p standard Vegas template h264 mp4 - could not render the timeline which was 60 seconds. Errors was listed as unknown and could complete the request.

I tried both GPU acceleration and disabling it with no resolution to the error.

How can I be expected to take the word "Pro" in Vegas Pro if I can't complete a simple render like this?

I love the "Concept" of Vegas Pro, but the execution has me left sticking with Premiere Pro for the foreseeable future.
TheRhino wrote on 2/22/2012, 12:55 PM
I'm not using GPU processing and Vegas 11 521 crashes whenever I am using my only two 3rd party codecs - Blackmagic MJPEG and AVID DNxHD. My source video is MJPEG and my renders are DNxHD. Vegas 10e doesn't crash, but renders some of the (small) clips to black. Therefore I cannot use Vegas 10e or 11 521 for the majority of my work. I am running a very clean system - no other software or codecs installed.... The exact same media files do not crash my other NLEs - including Vegas 8c on a separate boot drive...

Some of these projects are only 15 minutes long. If I restart Vegas & re-render, they sometimes turn-out OK. However, any project over 1 hour typically renders to black somewhere near the end - so I have to start all over and render-out in small chunks. This worrysome double-checking all outgoing footage is taking away all time-savings advantage of using Vegas over other NLEs. Typically I am 2X faster using Vegas but not when it keeps crashing...

EDIT: V11 just crashed as I was typing this! I wasn't even doing anything. I stopped to check how a transfer from tape was progressing on another machine. I checked my emails & wrote on this forum. When I returned to V11, I get another "Vegas Pro has stopped working... I didn't have the timeline playing or anything...

Problem Event Name: APPCRASH
Application Name: vegas110.exe
Application Version: 11.0.0.521
Application Timestamp: 4f14a595
Fault Module Name: sfapprw.dll
Fault Module Version: 11.0.0.521
Fault Module Timestamp: 4f14a1d7
Exception Code: c000001d
Exception Offset: 000000000011575f
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: f02e
Additional Information 2: f02ee8cdb4f16f1be219d7c80343eebd
Additional Information 3: cf25
Additional Information 4: cf25b41c3cc383d45ad025abcf6cca29

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

jerald wrote on 2/22/2012, 4:12 PM
Cliff Etzel & TheRhino,
It seems to me that this thread is intended for a specific issue about still images, and that the ForumAdmin responded with helpful info (thanks for that, ForumAdmin).

If you're expecting a response to your posts, you may have better luck if you post in a new thread with a Subject Line that is appropriate to your topic. If you're unhappy that I posted this, then please just ignore this post. Just trying to help.
Jerald
kingpeterz@btinternet.com wrote on 2/22/2012, 5:41 PM
Hi Paddy,

Yes, you have the answer! I checked the track header, and sure enough, the compositing Levels plug-in was active. When I deleted that, everything returned to normal once again. I don't understand what is the purpose of Levels plug-in. I can't see how I could have added it to the track header by accident, and I am sure that I didn't do so intentially. So, how did it get there? I wonder if this is a default setting introduced in Build 521. It was not in build 511. It is strange that uninstalling and reinstalling did not remove the plug-in from the header, but I guess doing a full clean uninstall would have achieved that.

Anyway, thanks for your valued assistance. I was going nuts trying everything I could possibly think of, but would never have guessed the problem lay with a plug-in I had not even realised existed.

Grazie wrote on 2/22/2012, 10:30 PM
I wonder if this is a default setting introduced in Build 521

I don't repro here. No Default SONY "Levels Fx" Plugin within Track Header.

Cheers

G