Announcement

Collapse
No announcement yet.

Export Errors and Glitches

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

  • Export Errors and Glitches

    I'm getting fed up of errors and glitches when exporting videos since upgrading to Edius X (frames of blockiness and green flashes). I thought it was my machine, but it happens on my new Desktop too. I was getting greater errors exporting VBR H264 so I changed to CBR - but it still happens. It happens on ProRes too. I used to be able to export a video and send it to a client. Now I have to watch it through and export it again if there are errors. Sometimes I have to do this 2 or 3 times until it is glitch free - very impractical if i am exporting a 2 hour show and working to a deadline. What on earth could be causing this? I've tried not doing anything while it is exporting but this doesn't change the outcome.
    Matt, AdVision TV Ltd

    Main System: Edius X WG 10.30 - AMD Ryzen Threadripper 3960X 24 Core Processor 3.79 GHz, 64GB Ram, Win 10, NVIDIA Quadro RTX 4000 Graphics Card

    Laptop System: Edius X WG 10.30 - Intel Core i9-9900K @ 3.6Ghz, 64GB RAM

  • #2
    Did you move your graphics card from your old to your new pc? Just asking as I have had export errors as well with AMD processors and Nvidia GPU and it appeared to be the graphics card. Also does it happen when you export h.264 using CPU only or using the Nvidia option?
    What I also have experienced is transition effects from prodad sometimes come out messed up.

    Comment


    • #3
      No - completly separate machines. Sadly it does it during normal video - not just on transitions etc.
      Not sure about where the option is to choose CPU or NVIDIA? Should there be a tick box on export (I can't see one) or do I need to set it up elsewhere?
      Matt, AdVision TV Ltd

      Main System: Edius X WG 10.30 - AMD Ryzen Threadripper 3960X 24 Core Processor 3.79 GHz, 64GB Ram, Win 10, NVIDIA Quadro RTX 4000 Graphics Card

      Laptop System: Edius X WG 10.30 - Intel Core i9-9900K @ 3.6Ghz, 64GB RAM

      Comment


      • #4
        under the H.264/avc option you can choose between h.264/avc or H.264/avc (nvidia), the nvidia option also makes use of your graphics card while exporting.
        Attached Files

        Comment


        • #5
          I will give the NVIDIA a go and report back. However, it would be great if it didn't do it with the CPU (which is very powerful) and it doesn't get me around ProRes exports!?
          Matt, AdVision TV Ltd

          Main System: Edius X WG 10.30 - AMD Ryzen Threadripper 3960X 24 Core Processor 3.79 GHz, 64GB Ram, Win 10, NVIDIA Quadro RTX 4000 Graphics Card

          Laptop System: Edius X WG 10.30 - Intel Core i9-9900K @ 3.6Ghz, 64GB RAM

          Comment


          • #6
            When you use h.264 (nvidia) export option the CPU will still be used in combination with the Nvidia card and you should get faster export times, if you use H.264 without nvidia option the GPU will still assist if there are Primary color corrections on clips, at least that is what I see in windows taskmanager while exporting. Do both of your pc's that get export errors have Nvidia Quadro cards?

            Comment


            • #7
              Both have export errors. One is a laptop and one is a workstation.
              Matt, AdVision TV Ltd

              Main System: Edius X WG 10.30 - AMD Ryzen Threadripper 3960X 24 Core Processor 3.79 GHz, 64GB Ram, Win 10, NVIDIA Quadro RTX 4000 Graphics Card

              Laptop System: Edius X WG 10.30 - Intel Core i9-9900K @ 3.6Ghz, 64GB RAM

              Comment


              • #8
                I don't have Edius X, so can't help with that specifically. Since your problem seems to be happening on two different machines that use different hardware, the problem is more than likely an installation, configuration or source file issue.

                I will ask a few questions and suggest that you supply a little bit more information to allow people to help, and hopefully speed up the process, such as:

                What are you using for your source files? Is it a mish mash or all the same kind? if it's a mish mash are the errors only happening when exporting/encountering a particular type on the timeline?

                What are the properties of the project compared to the source files? (same framerate? same raster?)

                Are you using any plugins? If yes, are they native or 3rd party? If yes, try an export without plugins to try to point to the source of the problem (if it still happens without plugins, it is likely an edius/source decode problem. If the files are H264 or H265 based, Edius has system decoder settings to enable GPU assist for decode, so you can check those settings). Some plugins are CPU bound and some are GPU bound. Some can be either or, such as the PCC which has a system setting to enable the GPU to accelerate. Changing this GPU assist for PCC may help if it is in use.

                What are you using for your media drive? (SSD, HDD, NVME?) How is it connected? (internal sata/sas, external sata/sas/usb/thunderbolt, SAN, etc) (please tell me it is not the internal C: drive)

                When you installed Edius, did you disable your virus scanner (this includes windows defender if you don't have a 3rd party scanner) first as per the installation instructions, and do you have exceptions made in the virus scanner for the grass valley program folder, hidden appdata grass valley folders and your media drives? Do you have a firewall exemption made for the Edius render services? (if you didn't have the virus scanner disabled during install, uninstall edius, but do not deactivate it, disable the virus scanner and re-install edius. some files that edius installs can be erroneously flagged as viruses and blocked by a virus scanner, this is why there is a recommendation to disable during install and add the exceptions, adding an exception to the media drive also helps so the scanner doesn't slow down access to the media)
                Last edited by BernH; 01-15-2022, 01:36 AM.
                Edius WG 9.55.7761, various 3rd party plugins, VisTitle 2.9.5.6, 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


                • #9
                  Originally posted by BernH View Post

                  When you installed Edius, did you disable your virus scanner (this includes windows defender if you don't have a 3rd party scanner) first as per the installation instructions, and do you have exceptions made in the virus scanner for the grass valley program folder, hidden appdata grass valley folders and your media drives? Do you have a firewall exemption made for the Edius render services?
                  And just in case advisiontv has missed it: here is more info: https://forum.grassvalley.com/forum/...the-moderators
                  I have seen a few posts appear with edius issues that are linked to not following these "tips".

                  Comment

                  Working...
                  X