EDIUS 7 - Massive Memory Leak with h264 Intel Export

[ntbone]

I finished my first video edit under EDIUS 7. I went to export using h264 exporter utilizing the hardware encoding via Intel Graphics and when I came back to my PC it was unresponsive. I finnaly got it to come back and noticed EDIUS had crashed and I had an error about Windows being low on memory.

I opened EDIUS up and tried again, this time monitoring its memory usage and sure enough as it began to encode the memory footprint just kept getting bigger and bigger. I did not wait for it to max out. I ended up having to disable the hardware encoder.

Anyone used the hardware encoding option in EDIUS 7?

[NakedEye]

Anyone used the hardware encoding option in EDIUS 7?

Hi Mate

Yes I have used it several times with timelines up to 1 hour 45 minutes and have not had any issues so far with Edius 7 or TMPEG VMW5. Sorry...

[Gavin++]

Yes, and it worked fine so far.

Can you provide some additional information?
(like specs of your PC, windows version, specs of your video project...)

Gavin

[ilfsn]

Yes, i have same problem with 1920x1080 59.94i 2 hours, with motion menu; memory usage in Task Manager was massive ( 7.8GB, my main memory was 8GB), but i let it finish and it back to normal.
Note: And motion menu with DVD is bug, but fine with BD.
Sorry for my bad English.

Xeon 1245v2, Gigabyte Z77, AMD HD 7770, Windows 7 Ultimate, latest driver Intel and AMD graphic.

[ntbone]

Running Windows 8. The video was about 12 minutes in length. Running EDIUS 7. One of the short clips at the very beginning had a VitaScene effect on it.

In order to utilize the hardware encoding for my PC I have to not only enable a monitor on the Intel graphics card, but it has to be the primary display. Any other configuration I have tried does not utilize hardware encoding.

PC Is a Core i7 3rd gen. Motherboard is an Asus Sabertooth Z77. Latest drivers for both graphics cards in the PC (Radeon 6950 and Intel 4000).

[ntbone]

Yes, i have same problem with 1920x1080 59.94i 2 hours, with motion menu; memory usage in Task Manager was massive ( 7.8GB, my main memory was 8GB), but i let it finish and it back to normal.

Mine kept growing and growing and growing. The first time it ran out, the second time I didn't wait. The commit size in task manager just kept going up, and fast.

[David Clarke]

Vitascene uses the GPU and with the Intel as the main card it is using that to do the Vitascene effects and the encoding. When I tested this with EDIUS 6.5 using the Intel as the main card almost cancelled out any benefit of Quicksync when using a Vitascene effect. This is the main reason why we say you should have the NVidia/ATI as the main card and the Intel as the secondary.

So I suspect the memory problem comes back to the fact that you have to set the Intel as the main card, rather than an EDIUS problem. Of course we never managed to solve why you had to do that in the other thread about this.

[Jerry]

I recently tried a new setup for my quicksync monitors. Instead of using The Nvidia on the primary and the Intel on the secondary I completey gutted the drivers for both and shut off the quicksync feed in the bios.
I then installed a driver that is compliant with my older GTX285 and set it up to run both the Primary and Secondary as a digital connection.
This was also confirmed within the screen resolution portion of the desktop panel. Right click the desktop and choose personalize. You will see two monitors at that point.

Now I went back into the bios and reactivated my onboard graphics. Keep in mind that auto is not the preferred choice. Designate what it is.
I have this connected by way of an analog connection to my secondary monitors vga port.
So when the system comes up and you go into personalize, you will see 3 monitors. On my system:
1. is Nvidia Primary-digital
2. is Nvidia Secondary-digital...this is an 'extend desktop monitor'
3 is Intel-analog...................this is also an 'extend desktop monitor'

My monitor opens to the digital choice before an analog source.
This way it can remain connected with out having to have a third monitor or having to use the Intel graphics for visuals.

The drawback to this is if you update your driver. You will have to reset everything each time you install a new driver. Once you do it a couple of times, it is very easy.

[Ron Evans]

I have 2 Dell 24" monitors. Setup is Primary monitor is HDMI from the GTX560, secondary is VGA shared from a KVM switch again from the VGA adapter( on the DVI connector of the GTX560 ). This monitor is shared with my mail and general use PC. VGA port of the motherboard goes to the VT2300LED monitor used by the SParkHD for preview. This arrangement works great as well as VGA from motherboard to the primary Dell. I have it connected to the VT2300LED as it is closer to the PC for the length of VGA cable I had !!! Displays 1 and 2 are on the GTX560 and display 3 on the motherboard. I have the desktop extended over displays 1 and 2. Motherboard bios is set for the graphics to be always on. When I first assembled the PC I used the motherboard graphics for initial Windows install etc using all the Gigabyte discs. Then installed the GTX560 turning off the on board display. Set everything up as I wanted then turned on the motherboard graphics to always on. Other than Windows update installing the wrong Intel driver everything has worked fine this way.

Ron Evans

[ntbone]

Fixed in 7.01. Both the memory leak and the issue I used to have in which I needed to make my Intel Card the primary card!!!! It exports very fast.

[Harro]

It is V7.01 NOT 7.1, big difference.

[ntbone]

It is V7.01 NOT 7.1, big difference.

Oops. Corrected.

[ntbone]

Was using EDIUS on my Surface Pro 2 and the problem is back again. With or without the use of the "hardware encoder" the app rapidly consumes memory resources then crashes.

[David Clarke]

This is a really old thread so pretty much all of the above will have not relation to your problem with a current surace pro. The questions would be

• What kind of problems?
• What version of EDIUS?
• Which version of Windows?
• What project settings, type of clip etc.