Announcement

Collapse
No announcement yet.

Render and add to timeline is back in Edius X but...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Render and add to timeline is back in Edius X but...

    Testing Edius X against 9 I find that render and add to timeline takes 4 times longer in X than in 9 despite walking away from the PC. If it is a background task and no other Edius foreground tasks exist why is it so much slower?
    Sys4: Z10PE-D16WS MB 2xE5-2696 Xeon 64 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

  • #2
    Try setting that specific background task to high priority instead of normal.
    Steve


    Please don't send me Private Messages for support. Contact Grass Valley support

    Comment


    • createmedia
      createmedia commented
      Editing a comment
      Not very satisfactory as it needs to be set to each item that is rendering there is no global setting

  • #3
    The priority only makes a 7% improvement and of course the render has already started when the priority is to be changed.

    The offline media is added to the timeline whilst the render is completing, resulting in the checkerboard being displayed. This is not how Edius 9 worked and in X the media should only be added when rendering is complete.

    Sys4: Z10PE-D16WS MB 2xE5-2696 Xeon 64 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

    Comment


    • #4
      I wonder what the developers are on? Shocking mis -implementation of previous fully working well tested and important functions..who on earth comes up with these "improvements" ??

      Still not using X

      Paul :-)
      Edius Edits at: http://www.vimeo.com/user781619/videos

      1) AMD 3900X 12 core 4.6Ghz 2) Asus X79 4930K 6 core @4.4GHz Water Cooled. 480GB REVO3x2 System drive, 4TB Raid 0, 4 TB E-Sata Raid 5, 32GB RAM, GTX1070Ti Decklink HD Extreme. 3X Sony AX53 Sony AX700 BMPCC 4K

      http://indiestereographer.blogspot.co.uk

      Comment


      • #5
        Originally posted by PaulTV View Post
        I wonder what the developers are on? Shocking mis -implementation of previous fully working well tested and important functions..who on earth comes up with these "improvements" ??

        Still not using X

        Paul :-)
        I am still on 9 as well Paul. Until the quirks are ironed out of X, I am happy where I am. I love the idea of background processing in X, but the implementation is not what I envisioned. I came from Fast/Pinnacle/Avid Liquid. Background rendering in there was exactly that. It rendered in the background, looking for free clock cycles to start rendering, with a time delay that was user assignable, meaning that I could specify a 1 second wait before rendering began to make sure I wasn't doing anything in the foreground. Of course that was in the days of single core or dual core, so the wait was more important, but the implementation was brilliant given the hardware of the day. Exports however were always foreground.

        All that said, with current multi-core CPU's and possibly even GPU assist, a similar style of implementation even inclusive of exports would be quite doable, maybe reserving a 2 or 4 of CPU cores or threads for strict foreground use and allowing the rest to be tasked for background use only if free clock cycles are available, or even pushing the background processing to the GPU if it has free compute time. I think something like this would be the absolute ideal, allowing for very good foreground and background use simultaneously.
        Edius WG 9.54.6706, various 3rd party plugins, VisTitle 2.8.0.5, Win 7 Ultimate SP1, i7-4790K @ 4GHz with HD4600 GPU embedded, MSI Z97 Gaming 7 Motherboard, 32GB Kingston HyperX RAM, nVidia GTX680 4GB GPU, Matrox MX02 Mini MAX, Corsair 750W PSU, Corsair H110i GT Water Cooler, Corsair C70 case, 8TB Internal RAID 0/stripe (2x4TB Seagate SATAIII HDD's, Win7 Software stripe), 1TB Crucial MX500 SSD, Pioneer BDR-207D, Dual 1920x1080 monitors (one on GTX680 and one on Intel HD4600).

        Comment

        Working...
        X