7.32 1724 & NB & Nvidia FX3800

[createmedia]

The updated driver from NVidia isn't very good 340.84 so I went back to 340.52. Even at that driver I am not sure whether that relates to the problem below.

340.84 cannot determine the difference between GPU1 and GPU2 settings and keeps flipping to GPU2 after apply is clicked to let GPU1 handle open GL.

I have therefore made a clean install of 340.52 going back one step.

With open hardware monitor system tray Icons loaded it is possible to monitor hardware status whilst editing.

Edius 7.32.1724 and NB 140827 causes memory leakage into GPU2 RAM and each time a NB effect is opened and closed more memory is used in GPU2 and not flushed which when it reaches 97% causes Edius instability problems.

However GPU1 is set as the open GL and Cuda rendering engine, using the Nvidia control panel, so there is no logical reason for GPU2 RAM to become filled. I have seen this before with previous revisions of NB, which used to be solved by taking the cuda and open GL off atomatic selection in the Nvidia control panel and up until recently the problem had gone away.

The current only solution is to turn off the NB GPU acceleration for all products and then it works ok (but just doesn't render as fast).

Combinations........


Mike

[createmedia]

If in the Nvidia control panel I swap GPU1 for GPU2 for Open GL rendering the NB effect memory leakage swaps to the GPU not selected.

Glow however (Light Effects) takes 9 minutes to render a 35 second clip without GPU acceleration but 40 seconds with GPU enabled.

So clearly the GPU is a useful accelerant it's a pity it has recently gone weird.

On Exiting Edius, there is a long hang about a minute before Edius.exe closes and only at that point is the GPU memory cleared.

Mike

[createmedia]

This seems a good article it needs to be done in NB

http://stackoverflow.com/questions/7144195/cudadevicereset-for-multiple-gpus

Mike

[createmedia]

Tested in Premiere Pro CC2014 doing the same thing so sigh of relief its not an Edius issue.

Mike

[createmedia]

In order to try to break out of this circle of events I have just found an Nvidia K4000 GPU (single slot) on ebay brand new but at a good price (ex equipment) 3GB RAM it will do the 4 outputs I want; 2 Display ports, DVI-DL 1VGA direct with a splitter cable and one VGA via a DVI to VGA converter and get rid of the two off FX3800 cards and any confusion that causes.

More later when it arrives.

Mike

[antonsvideo]

I use the K4000 with 3GB Ram, great card and does not block PCIe slot below

all cards should be designed like that

but gamers think bigger is better :)

[createmedia]

Yes Anton one reason I chose it as is single slot. I have the two Display ports going to the PC monitors, and intended with the K4000 A DVI splitter the VGA lead going to an electronic VGA switch and the DVI to VGA converter to the other port on the switch and on to the 49inch display for demos. I can therefore put left or right PC monitor up on the big TV. I clone the desktop onto the other ports.

It leaves me then with a PCIex16 spare slot

Hopefully this will get round this GPU memory leakage issue I have been plagued with.

Next move will be to upgrade the Decklink 4k extreme to the 12G version a card that will support 4k/50p but that needs the PCIe8/16 slot.

Does the card help with NewBlue filters for non rendered playback? I suspect its still a render to get real time playback even with that.

Mike

[antonsvideo]

all newblue are realtime here with K4000 and hexacore CPU in a 1920x1080 project

have not tried Newblue in 4k

[createmedia]

OOOeee that's good thanks Anton

Fed up with chug, chug, chug.

I will try 4K when I get the card and set up.

Mike

[createmedia]

The results are mixed. The NVidia K4000 card is much better playing video on the desktop (1920 by 1200) no video tearing (where the top half of the picture rendered at a different time than the bottom half on a pan shot) and 4k plays well on the desktop.

Some NewBlue Fx are real time others are not, Glow for instance isn't. 1920 by 1080 50i

Consistent playback of NewBlue Fx such as viewfinder that are not real tiime with the BMD Decklink 4K extreme card will cause Edius to not respond after a while as below;

The program EDIUS.exe version 7.3.2.1724 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 2b28
Start Time: 01cfe3e4ff37b8aa
Termination Time: 692
Application Path: C:\Program Files\Grass Valley\EDIUS 7\EDIUS.exe
Report Id: 46c6186f-500e-11e4-bf73-78acc03c2f0a

Preceded by

The NVIDIA OpenGL driver has not been able to initialize
a connection with the GPU. This might be due to out of memory error,
an exhaustion of system resources or too many graphical applications running.
The application will not render correctly.

No memory leakage seen with NB and the K4000.

Tried 3 different NB FX on a clip but film Pro crashed it again but had switched to the Storm 3G Elite Hardware. Exactly the same error in Event Viewer as above.

GPU core 44% GPU memory at 23% during playback. Pre-loading the buffer helps and what looked like a countdown carries on at 250.

Adjusting the controls too fast in NB seems to kick off a crash.

Mike