No announcement yet.

Edius 6.54 Render Crashes New Blue

  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    I reported problems with KB2670838 back in March
    System Asus WS Z390 Pro MB, CPU i9 9900K, 32gb 3000mhz Ram, EVGA GTX1070TI, BM IP4K Win 10, BD Burner 1 Evo 840 and 4 Hotswap caddies
    Plugins Vistitle 2.8, TP7, NB TFX5
    Monitors Samsung 32 inch tv as main 1 LG M2350D,1 D2343 1 DM2350D as output to (3D) IP4K, PXW X70,Canon FX400


    • #17
      the following 6 updates will never be installed in any Win7 PC I build
      Anton Strauss
      Antons Video Productions - Sydney

      EDIUS X WG with BM Mini Monitor 4k and BM Mini Recorder, Gigabyte X299 UD4 Pro, Intel Core i9 9960X 16 Core, 32 Threads @ 4.3Ghz, Corsair Water Cooling, Gigabyte RTX-2070 Super 3X 8GB Video Card, Samsung 860 Pro 512GB SSD for System, 8TB Samsung Raid0 SSD for Video, 2 Pioneer BDR-209 Blu-ray/DVD burners, Hotswap Bay for 3.5" Sata and 2.5" SSD, Phanteks Enthoo Pro XL Tower, Corsair 32GB DDR4 Ram, Win10 Pro 21H2


      • #18
        More stuff NewBlue GPU switched on crashes Edius 6.54

        One last go at it.....

        Its still somewhat confusing because I have a Clevo i7 950 D900F laptop with an Nvidia 280M chip with the native display at 1920 by 1200. The Nvidia driver for this is exactly the same as the HP Z800 with two Nvidia FX3800 cards. Driver 320.49

        Firstly there isn't a problem when rendering at all with the laptop with NewBlue GPU acceleration turned on. So this is strange as the desktop is in comparison so fussy.

        NewBlue Builds are mostly 130227 & 8. Later build tests seem to make matters worse.

        I have done a Windows update compare list and the laptop and the desktop have an equivalent list.

        Before altering anything without the GPU acceleration switched on on the desktop NewBlue effects render ok. With them on the render did not complete and Edius crashed.

        The next step was to do some research with the Open GL GPU rendering on the web. There were suggestions about GPU response delays as I did find adding TDR values helped in the registry and rebooting.

        This was after crashing out the GPU driver by twiddling the knobs too fast in NewBlue control panels it led me to look in this direction.

        TdrDdiDelay = 50(D)
        TdrDelay = 60 (D)
        TdrLevel = 0

        Now we have render with GPU on in NewBlue completes and the first play through in Edius works. The second play through reveals the buffer running down to 1 and freezing Edius.

        If we now restart Edius and set the buffer down to 128MBytes now rendering a Newblue filter and playback works.

        I hope these findings are useful to somebody.

        That is about the limit of software knobs and buttons I can think of tweaking.

        I am in pause mode for Edius 7 as although ProDad are up to date with 64Bit Plugins (well done them) for Edius Boris Red and NewBlue aren't yet.
        Sys4: Z10PE-D16WS MB 2xE5-2696 Xeon 72 active logical cores. EWG9. 64G RAM. Aorus GTX1080Ti. 55" Q7 1500 NIT HDR 4K TV/Storm 3G Elite/Decklink 4K 12G/8CH audio monitoring, Yamaha RXA-870 A/V. Sys1-3 EWG8 + RX-E1+HDBX1000 MIP in HP xw8600 2 x X5492 CPU 8 cores, 8Gig RAM, Quadro FX3800. All sys Fibre to central media pool - 5TB Axus Yotta RAID + QLogic Fibre Switch. Central VCR rack plus YUV & audio to viewing room with Yamaha AX1 7.1 100 watt per channel amp with 1000W sub 63" HD 3D Samsung TV