BUG: DEFOCUS FX crashes VP14 down to SVP13 and SVP12.

OldSmoke wrote on 12/30/2016, 2:56 PM

I recently completed our annual Nutcracker On Ice show. All worked well aside from the Act1 project that I couldn't render with GPU ON (GPU acceleration of video processing). I had no time to find out why but now I have. In fact I couldn't even open the project anymore until I switched off GPU acceleration. By elimination I finally found the culprit. I applied DEFOCUS on 3 events and that caused the crash with GPU ON. I currently still work in Sony VP13 but I copied the multicam track over to VP14 and it crashed it too with GPU on. Same for Sony VP12 but surprisingly not Sony VP11. I also tested this with a random clip and same happened, meaning it is not related to multicam editing or the particular file(s). I also tried different flavors, XAVC-S, XAVC Intra, HDV and a few others, all crash the moment I applied Defocus FX is GPU is ON.

This is on my 3930K, x79 chipset and ASUS Fury X with latest driver and a fully updated Win10Pro.

Can someone with an Nvidia card and someone with a different AMD card try to apply the Defocus FX to any clip and see if that crashes SVP12, SVP13, VP13 or VP14 when GPU is ON? I just want to make sure it's not just my system. Maybe I am missing a .Net version? I have 3.5 and 4.6.2 on my system.

Comments

Cornico wrote on 12/30/2016, 4:46 PM

No problem here on laptop (signature) on VMS 13PL, VPRO 12, VPRO 13, VPRO 14.
The same .Net as you mentioned.

OldSmoke wrote on 12/30/2016, 5:26 PM

Thanks Cornico.

Both your systems use Nvidia and an Intell GPU; maybe that is why you don't have an issue?

Cornico wrote on 12/30/2016, 5:39 PM

With Vegas I only use NVidia while when I use Intell to start the program, New Blue begins to protest.
Normally starting the program with Intell und using NVidia for video accelleration gives the fastest results.

OldSmoke wrote on 1/1/2017, 5:46 PM

It would be really nice if someone with an AMD card could confirm my findings before I submit a bug report.

NickHope wrote on 1/1/2017, 9:51 PM

No problem here in VP12, 13 or 14 with AMD HD 6970 with driver 15.201.1151.1008. Windows 10 version 1511. More system specs in my profile. The playback is extremely laggy, as if GPU acceleration isn't helping at all, but it doesn't crash. I tried with DV, HDV, and GH4 UHD MP4.

BruceUSA wrote on 1/1/2017, 11:36 PM

No problem here with VP14 but awfully laggy as I don't think GPU acceleration is working at all and I did not bother to check GPU usage. How ever I can hear my fans is kicking in high speed because the CPU is loading heavily. Again I did not check the CPU usage either. . I did not try VP13 because I am in the middle of rendering a project. My clip are Samsung .h265 native UHD clip. Windows 10 Pro, version 1607 and latest AMD driver. AMD R9 290X.

bitman wrote on 1/2/2017, 12:19 PM

No problem here with VP14, plays back fluidly, not lagging. I have a Nvidea titan-x. VP14 setting has GPU active, with Nvidea selected. It has a GPU load of 50% (see screenshot) at playback. I usually keep dynamic RAM at zero instead of the 200 default in VP14 settings to keep VP rock stable with OFX plugins...

rest of system: win 10, 64bit, intel core i7 -4790K, everything updated to latest drivers and OS updates.

Kinvermark wrote on 1/2/2017, 12:52 PM

VP14 with amd r290 - no crash with HDV and Defocus effect. Driver 16.10.1 Dot net 4.6 full & client.

OldSmoke wrote on 1/2/2017, 1:49 PM

Thank you all for your replies. I would need one user that has a 300 or 400 series GPU with Fiji architecture to really conclude that the problem is caused by my system rather than a software or driver bug.

Again, thank you all that have replied for the time you spent testing it.

NickHope wrote on 1/3/2017, 2:04 AM

No problem here with VP14, plays back fluidly, not lagging. I have a Nvidea titan-x....I usually keep dynamic RAM at zero instead of the 200 default...

Interesting! What type of footage?

OldSmoke wrote on 1/3/2017, 10:48 AM

Update

I rolled back to driver 16.9.2 and Defocus is doesn't crash Vegas anymore; VP14 down to SVP13 and SVP12.

Playback is extremely slow and I don't see much GPU load either, this FX is not optimized for OpenCL. I will install my GTX580 and see if that makes a difference in playback performance.

Gaussian Blur on the other hand works fine and shows 100% GPU load on my Fury X.

@bitman

Your findings are interesting and like Nick I would like to know which footage you have tested it on.

bitman wrote on 1/3/2017, 11:57 AM

Hi Nick and OldsMoke,

I was using a video (with the defocus effect added) I took with a Nikon P600 from a feeding grizzly in Canada.

the project in Vegas was 50P, the footage 25P

Format                           : MPEG-4
Format_Profile                   : QuickTime
CodecID/String                   : qt   2007.09 (qt /niko)
FileSize/String                  : 74.7 MiB
Duration/String                  : 36s 80ms
OverallBitRate/String            : 17.4 Mbps
NCDT                             : NCTG

Video
ID/String                        : 1
Format                           : AVC
Format/Info                      : Advanced Video Codec
Format_Profile                   : Main@L4
Format_Settings_CABAC/String     : Yes
Format_Settings_RefFrames/String : 1 frame
Format_Settings_GOP              : M=1, N=6
CodecID                          : avc1
CodecID/Info                     : Advanced Video Coding
Duration/String                  : 36s 80ms
BitRate/String                   : 15.7 Mbps
Width/String                     : 1 920 pixels
Height/String                    : 1 080 pixels
DisplayAspectRatio/String        : 16:9
FrameRate_Mode/String            : Constant
FrameRate/String                 : 25.000 fps
ColorSpace                       : YUV
ChromaSubsampling/String         : 4:2:0
BitDepth/String                  : 8 bits
ScanType/String                  : Progressive
Bits-(Pixel*Frame)               : 0.303
StreamSize/String                : 67.5 MiB (90%)
Language/String                  : English
colour_range                     : Full
colour_primaries                 : BT.709
transfer_characteristics         : BT.709
matrix_coefficients              : BT.709

Audio
ID/String                        : 2
Format                           : PCM
Format_Settings_Endianness       : Little
Format_Settings_Sign             : Signed
CodecID                          : sowt
Duration/String                  : 36s 75ms
BitRate_Mode/String              : Constant
BitRate/String                   : 1 536 Kbps
Channel(s)/String                : 2 channels
ChannelPositions                 : Front: L R
SamplingRate/String              : 48.0 KHz
BitDepth/String                  : 16 bits
StreamSize/String                : 6.61 MiB (9%)
Language/String                  : English

bitman wrote on 1/3/2017, 12:23 PM

Hi Nick and OldsMoke,

I redid the defocus test on 3 extra different types of footage now, same results, all play fluidly (project setting is HD 1080p50 -8bit)

- 4k 3840*2160 High@L5.1) (25P) from GoPro

- XAVC High@L4.2 (50P) from Sony RX10 (1080p50.MP4) - audio PCM

- AVC High@L4.2 (50P) from Sony RX10 (1080p50.MTS) - audio AC3

OldSmoke wrote on 1/3/2017, 12:36 PM

@bitman

Thank you for doing all the testing. Maybe this particular FX is CUDA optimized? As mentioned earlier, I will install my GTX580 later today and do some additional testing.

PS: Make sure you haven't bypassed FX processing in the preview window😉

bitman wrote on 1/3/2017, 1:15 PM

It is so blurred on preview playback that I am sure the effect is not bypassed 🤓

Nvidea supports opengl quite good these days. Just guessing here (which I prefer not to) but I do not think any vegas effects use cuda, just opengl. And with 12GB on the titan-x videocard It will not be memory limited!

PS keep dynamic RAM at zero instead of the 200 default in VP14 settings, this change turned my system rock stable and does not seem to affect playback on my system, the drawback is a bit slower render times.

OldSmoke wrote on 1/3/2017, 1:55 PM

Preview Ram 0 makes no difference on my system and rather slows it down; mine is always at the default 200.

Very interesting find that this particular FX works fine with a Nvidia Titan card.

bitman wrote on 1/3/2017, 4:08 PM

FYI, I got the "former" Titan -X, called the GTX Titan-X (the maxwell variant), and not the latest and but confusingly also called Titan-X (without the GTX in front) this new card is based on Pascal architecture.

In the past I also had the predecessor Nvidia Titan (without the "X"). It is now in my son's PC 😉

NickHope wrote on 1/3/2017, 9:42 PM

Thanks for the feedback bitman. Very interesting indeed. As that card seems to be so much better than ours for this particular FX, I wonder how it does with other FX and Vegas video processing in general. If you have the time and inclination, maybe you could have a read of this thread and perhaps try some of the testing with the JR project and the Red Car project.

OldSmoke wrote on 1/3/2017, 9:56 PM

@bitman

Just one more thing to check. What is your preview quality setting?

Update:

I installed my GTX580 along side the Fury X and I can confirm that even my old GTX580 does fair much better with this particular FX. I don't get full fps at Best/Full but I do get around 15fps on a 60p clip.

I also forgot to mention that strange user interface of the defocus FX in VP11, it doesn't look like a normal Vegas plugin interface. Remember, VP11 did not crash with the FX at all.

bitman wrote on 1/4/2017, 12:08 PM

@OldSmoke

FPS per file type / preview size / with and without defocus
Preview Quality set to Good/full
Project is HD, 50p with video file types :

- 1080p25 (Main@L4) MOV mpeg4 QuickTime from Nikon P600
Preview display size: 679x382x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 28fps, without defocus 50fps
Preview display size: 1298x730x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 23fps, without defocus 50fps

- 4k 3840*2160 (High@L5.1) (25P) from GoPro
Preview display size: 679x382x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 21fps, without defocus 50fps
Preview display size: 1298x730x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 20fps, without defocus 50fps

- XAVC High@L4.2 (50P) from Sony RX10 (1080p50.MP4) - audio PCM
Preview display size: 679x382x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 26fps, without defocus 50fps
Preview display size: 1298x730x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 23fps, without defocus 50fps

- AVC High@L4.2 (50P) from Sony RX10 (1080p50.MTS) - audio AC3
Preview display size: 679x382x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 26fps, without defocus 50fps
Preview display size: 1298x730x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 23fps, without defocus 50fps

bitman wrote on 1/4/2017, 12:19 PM

@ OldSmoke

Bumping up the preview quality setting from good/full to Best/full does not seem to affect the fps much:

Preview Quality set to Good/full AVC High@L4.2 (50P) from Sony RX10 (1080p50.MTS) - audio AC3
Preview display size: 679x382x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 26fps, without defocus 50fps
Preview display size: 1298x730x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 23fps, without defocus 50fps

Preview Quality set to Best/full AVC High@L4.2 (50P) from Sony RX10 (1080p50.MTS) - audio AC3
Preview display size: 679x382x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 27fps, without defocus 50fps
Preview display size: 1298x730x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 22fps, without defocus 50fps

bitman wrote on 1/4/2017, 12:39 PM

@ OldSmoke

Something interesting, I changed the GPU acceleration from Nvidea Titan-x to my Processor's GPU :
i7-4770k (has intel HD graphics 4600), but what an unbearable low FPS !!!

Preview Quality set to Best/full AVC High@L4.2 (50P) from Sony RX10 (1080p50.MTS) - audio AC3
Preview display size: 679x382x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 5fps, without defocus 50fps
Preview display size: 1298x730x32 (on a 34 inch ultra-wide (21x9) monitor)
with defocus effect 5fps, without defocus 50fps

bitman wrote on 1/4/2017, 1:35 PM

Thanks for the feedback bitman. Very interesting indeed. As that card seems to be so much better than ours for this particular FX, I wonder how it does with other FX and Vegas video processing in general. If you have the time and inclination, maybe you could have a read of this thread and perhaps try some of the testing with the JR project and the Red Car project.

I already did some rendering tests at the (current) end of that thread 😃. I can always do some quick tests of certain fx's on specific files (if you provide the link) if you like to know the fps or rendering time etc.., but for larger scale testing I lack the time.

OldSmoke wrote on 1/4/2017, 3:52 PM

Something interesting, I changed the GPU acceleration from Nvidea Titan-x to my Processor's GPU :
i7-4770k (has intel HD graphics 4600), but what an unbearable low FPS !!!

Well, I get the same behavior with the Fury-X card; as if it's CPU only. I get full fps with a 1080 60p XAVC-S file from my AX100 but only at Good/Half and that is with the GTX580 for video acceleration. The GPU load on the GTX580 is around 85%. There seems to be something about this plugin that makes it work better with Nvidia cards. VP11 doesn't seem to make use of any of my cards when selected for video acceleration; no load at all.

I wonder if there are others that work better with Nvidia cards. Is there a toll would be able to tell whether OpenCL or CUDA is used on a specific card?

I also found that these Starburst and Rays (not Light Rays) behave similar.

Edit:

Found this on CC from 2013. Might still be true today. Especially the "Ray" FX looks suspicions.