Announcement

Collapse
No announcement yet.

Very long export even with hardware encoder

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

  • #31
    in that case I am unsure at this stage why you don't see both GPU in task manager
    Anton Strauss
    Antons Video Productions - Sydney

    EDIUS 9 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

    Comment


    • #32
      I have also a GTX 660 Ti GPU and I have one monitor connected to the GTX 660 by mini DP port and the second monitor by mini DP port of the motherboard and I see both GPU's,and I'm happy with the speed !
      Edius 9.5,Win 10 home
      Asrock Phantom gaming 6,
      CPU Intel I9-9900K
      500 Gb M.2 Samsung SSD 970 Pro plus
      1 TB M2 Samsung SSD 970Pro
      SSD OCZ 256MB
      WD 4TB HDD
      2 Dell monitors UP2716D

      Comment


      • #33
        Originally posted by edver1 View Post
        I have also a GTX 660 Ti GPU and I have one monitor connected to the GTX 660 by mini DP port and the second monitor by mini DP port of the motherboard and I see both GPU's,and I'm happy with the speed !
        Do you see two GPUs in your Task Manager as in Andrew's screenshot?

        Attached Files
        Gigabyte Z77X-UP4 TH, Intel Core i7 3770k 3.5GHz, 4 Core, 8 Threads, 32GB RAM, NVIDIA GeForce GTX 660 2GB, 500GB SSD HDD for OS, 40TB Usable Hard Drive Capacity, Window 10 PRO 64-bit Edius 9.5 WORKSTATION...

        Comment


        • #34
          So I wanted to check if a clean install of Windows would solve this (to rule out hardware issue) so I formatted the C drive (I have a backup image) and installed Windows. It installed some version of Intel Graphics and I wanted to check if it works in Edius. So I installed Edius but it won't accept my serial because it says I must first deactivate my previous activation. In the license manager it doesn't list any numbers to deactivate. Do I really have to restore the computer via the image, just to deactivate my Edius and then again format the C drive and install Windows and Edius??? Is there no way to deactivate via the EID site or some other way? Or maybe Antony can give me a temporary license number that would work for 15 minutes and then expire, just so I can test Edius for a minute?

          ps. I'm not even sure why I can't use my regular license. It's the same computer - just reinstalled Windows.
          Last edited by zvit; 07-30-2020, 04:47 PM.
          Gigabyte Z77X-UP4 TH, Intel Core i7 3770k 3.5GHz, 4 Core, 8 Threads, 32GB RAM, NVIDIA GeForce GTX 660 2GB, 500GB SSD HDD for OS, 40TB Usable Hard Drive Capacity, Window 10 PRO 64-bit Edius 9.5 WORKSTATION...

          Comment


          • #35
            Unfortuneatley yes. After the 2004 update the intel graphics driver was changed. Intel have released about 3 further updated to the driver. I find that Handbrake makes greater use of the intel gpu than edius.

            Before you deactivate take a note of the current version and maybe reinstall the version that came with the motherboard. Just might save a load of hassle with a complete new windows
            Sys1: Gigabyte Z370 HD3 i7 8086K(4.3Ghz), 16Gb ram, 256Gb SSD system + 2x2Tb video drives, Graphics: nVidia 1060 (W10 Pro) E8v3 WG; Vegas Pro17; DVD Architect 5.2
            Sys2 :Clevo i7 6700HQ 3.5Ghz,16Gb ram 2565Gb SSD + 1Tb (W10 Pro)
            Software: E8v3 WG; Vegas Pro17

            Comment


            • #36
              Originally posted by zvit View Post
              So I wanted to check if a clean install of Windows would solve this (to rule out hardware issue) so I formatted the C drive (I have a backup image) and installed Windows. It installed some version of Intel Graphics and I wanted to check if it works in Edius. So I installed Edius but it won't accept my serial because it says I must first deactivate my previous activation. In the license manager it doesn't list any numbers to deactivate. Do I really have to restore the computer via the image, just to deactivate my Edius and then again format the C drive and install Windows and Edius??? Is there no way to deactivate via the EID site or some other way? Or maybe Antony can give me a temporary license number that would work for 15 minutes and then expire, just so I can test Edius for a minute?

              ps. I'm not even sure why I can't use my regular license. It's the same computer - just reinstalled Windows.
              reinstalling Win will lose you one license count, so always deactivate first. I will sort you out
              Anton Strauss
              Antons Video Productions - Sydney

              EDIUS 9 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

              Comment


              • #37
                Thank Anton. I responded to your email.
                Just a thought, why doesn't Edius use the computer\machine ID instead of Windows installation? That way a person can activate a license as many times as he wants as long as it's on the same computer. This way is a win-win because it can't be abused (giving out the license for other computers) and I wouldn't have had this issue.
                Gigabyte Z77X-UP4 TH, Intel Core i7 3770k 3.5GHz, 4 Core, 8 Threads, 32GB RAM, NVIDIA GeForce GTX 660 2GB, 500GB SSD HDD for OS, 40TB Usable Hard Drive Capacity, Window 10 PRO 64-bit Edius 9.5 WORKSTATION...

                Comment


                • #38
                  from memory, when you reinstall Win10, the machine ID changes, I will double check next time I do it
                  Anton Strauss
                  Antons Video Productions - Sydney

                  EDIUS 9 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

                  Comment


                  • #39
                    Ok, well here's an even simpler suggestion: Allow us to deactivate\activate our purchased license numbers directly on our account, on the EIN webpage. Each number should have an "activate" or "deactivate" button.

                    chrome_U1eS2NKPnJ.png
                    Gigabyte Z77X-UP4 TH, Intel Core i7 3770k 3.5GHz, 4 Core, 8 Threads, 32GB RAM, NVIDIA GeForce GTX 660 2GB, 500GB SSD HDD for OS, 40TB Usable Hard Drive Capacity, Window 10 PRO 64-bit Edius 9.5 WORKSTATION...

                    Comment


                    • #40
                      personally I find it simple to select the license in LM and click the open padlock (deactivate) It is faster than logging in to the EDIUS ID page and most WG users don't even use the EID page
                      Anton Strauss
                      Antons Video Productions - Sydney

                      EDIUS 9 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

                      Comment


                      • #41
                        Originally posted by antonsvideo View Post
                        personally I find it simple to select the license in LM and click the open padlock (deactivate) It is faster than logging in to the EDIUS ID page and most WG users don't even use the EID page
                        True. I'm most probably just venting for how it affected me. After formatting the drive and reinstalling Windows and Edius, I wasn't going to restore the computer, deactivate Edius, then reformat the drive again and reinstall Windows and Edius again.
                        Gigabyte Z77X-UP4 TH, Intel Core i7 3770k 3.5GHz, 4 Core, 8 Threads, 32GB RAM, NVIDIA GeForce GTX 660 2GB, 500GB SSD HDD for OS, 40TB Usable Hard Drive Capacity, Window 10 PRO 64-bit Edius 9.5 WORKSTATION...

                        Comment


                        • #42
                          UPDATE: Reinstalling a fresh Windows after formatting C helped. So it's not a hardware issue. I then restored back to start again. Tried to reinstall Windows while keeping files and apps. Didn't help. Restored back to start again. Then I uninstalled EVERY program and Windows update from the past 6 months. (I know the driver worked a few months ago). But sadly, the same issue. So far the only solution is to format and install fresh Windows. Then I'd have to spend days reinstalling every software and tweaking Windows to my liking. I'd really like to avoid this. Any last words of advice?
                          Gigabyte Z77X-UP4 TH, Intel Core i7 3770k 3.5GHz, 4 Core, 8 Threads, 32GB RAM, NVIDIA GeForce GTX 660 2GB, 500GB SSD HDD for OS, 40TB Usable Hard Drive Capacity, Window 10 PRO 64-bit Edius 9.5 WORKSTATION...

                          Comment


                          • #43
                            I find the export without hardware encoder better quality and just as fast, at least on my system with all 32 cores at 100% it only takes 10min to export a one hour timeline to HD H264 mp4

                            have you tried the Intel graphics driver from the mobo driver CD?
                            Anton Strauss
                            Antons Video Productions - Sydney

                            EDIUS 9 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

                            Comment


                            • #44
                              For me, without it, it takes 15 minutes to export a 5-minute timeline. (4 cores (8 logical with hyperthreading))

                              I found the install logs!! It's a file called setupapi.dev.log in C:\Windows\INF.
                              After each install, I delete it so I can get a clean log of the version I'm trying.
                              Now at least I see WHAT directory is invalid! Also, I see the exit(0x0000010b) error that I also saw in the Windows Events! (I now just have to figure out WHY it's invalid.)

                              I created four log files for four install attempts but am not allowed to attach here.
                              So I uploaded them to GD. You can view/download them here: https://drive.google.com/drive/folde...Qn?usp=sharing
                              I put the driver version install attempt in the log file name
                              .
                              Maybe someone can take a look and better advise on how to solve this.

                              There are common errors in ALL version attempts. (Including the old version downloaded from the mobo site)

                              For example:
                              1. Device not started (unknown reason): Device has no problem.
                              2. Selected driver node does not match this device (force-install)
                              3. Invalid DelReg entry due to no value on a multi-sz delete.
                              4. CopyFile: 'C:\WINDOWS\system32\GfxUIEx.exe' to 'C:\WINDOWS\Temp\OLD9744.tmp' FAILED
                                ! flq: Error 267: The directory name is invalid.
                                !!! bak: Failed to copy 'C:\WINDOWS\system32\GfxUIEx.exe' to 'C:\WINDOWS\Temp\OLD9744.tmp'. Error = 0x0000010b
                                !!! flq: Failed to commit copy queue. Error = 0x0000010b
                                !!! flq: FileQueueCommit aborting
                                !!! flq: Error 267: The directory name is invalid.
                              These are two main ERROR part of the logs:

                              FIRST PART:

                              idb: Activating driver package 'igdlh64.inf_amd64_0d5be4a8324f3703'.
                              cpy: Published 'igdlh64.inf_amd64_0d5be4a8324f3703\igdlh64.inf' to 'oem46.inf'.
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2872
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2873
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2874
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2875
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2876
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2877
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2878
                              ! inf: Legacy directive 'RegisterDlls' will be ignored. Code = 2009, Line = 1493
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2922
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2923
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2924
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2925
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2926
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2927
                              ! inf: Invalid DelReg entry due to no value on a multi-sz delete. Code = 1266, Line = 2928
                              ! inf: Legacy directive 'RegisterDlls' will be ignored. Code = 2009, Line = 1420
                              ! inf: Legacy directive 'RegisterDlls' will be ignored. Code = 2009, Line = 1565
                              idb: Indexed 8 device IDs for 'igdlh64.inf_amd64_0d5be4a8324f3703'.
                              sto: Flushed driver database node 'DRIVERS'. Time = 0 ms
                              sto: Flushed driver database node 'SYSTEM'. Time = 0 ms
                              idb: {Publish Driver Package: exit(0x00000000)} 10:55:17.397
                              sto: {DRIVERSTORE IMPORT END} 10:55:17.466
                              dvi: Flushed all driver package files to disk. Time = 531 ms
                              sig: Installed catalog 'igdlh.cat' as 'oem46.cat'.
                              sto: {DRIVERSTORE IMPORT END: exit(0x00000000)} 10:55:18.028
                              sto: {Core Driver Package Import: exit(0x00000000)} 10:55:18.029
                              sto: {Stage Driver Package: exit(0x00000000)} 10:55:18.103
                              sto: {Setup Import Driver Package - exit (0x00000000)} 10:55:18.289
                              dvi: Class GUID of device changed to: {4d36e968-e325-11ce-bfc1-08002be10318}.
                              ump: {Plug and Play Service: Device Install for ROOT\DISPLAY\0000}
                              dvi: Class GUID of device changed to: {4d36e968-e325-11ce-bfc1-08002be10318}.
                              ndv: {Core Device Install} 10:55:18.754
                              ! pol: Selected driver node does not match this device (force-install)
                              dvi: {Install Device - ROOT\DISPLAY\0000} 10:55:18.810
                              dvi: Device Status: 0x01802001
                              dvi: Parent Device: HTREE\ROOT\0
                              dvi: {DIF_ALLOW_INSTALL} 10:55:18.814
                              dvi: Default installer: Enter 10:55:18.815
                              dvi: Default installer: Exit
                              dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 10:55:18.817
                              dvi: {DIF_INSTALLDEVICEFILES} 10:55:18.818
                              dvi: Default installer: Enter 10:55:18.818
                              dvi: Default installer: Exit
                              dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 10:55:18.897



                              SECOND PART:

                              ! flq: CopyFile: 'C:\WINDOWS\system32\GfxUIEx.exe' to 'C:\WINDOWS\Temp\OLDC6D5.tmp' FAILED
                              ! flq: Error 267: The directory name is invalid.
                              !!! bak: Failed to copy 'C:\WINDOWS\system32\GfxUIEx.exe' to 'C:\WINDOWS\Temp\OLDC6D5.tmp'. Error = 0x0000010b
                              !!! flq: Failed to commit copy queue. Error = 0x0000010b
                              !!! flq: FileQueueCommit aborting
                              !!! flq: Error 267: The directory name is invalid.
                              flq: {FILE_QUEUE_COMMIT - exit(0x0000010b)} 10:55:20.307
                              dvi: {Install Device - exit(0x0000010b)} 10:55:20.309
                              dvi: {Core Device Install - exit(0x0000010b)} 10:55:20.310
                              ump: {Plug and Play Service: Device Install exit(0000010b)}
                              !!! ndv: Device install failed for device.
                              !!! ndv: Error 267: The directory name is invalid.
                              ndv: Installing NULL driver.
                              ump: {Plug and Play Service: Device Install for ROOT\DISPLAY\0000}
                              ! dvi: Installing NULL driver!
                              dvi: {Core Device Install} 10:55:20.324
                              dvi: {Configure Device - ROOT\DISPLAY\0000} 10:55:20.325
                              dvi: Device Status: 0x01802001
                              dvi: Parent Device: HTREE\ROOT\0
                              dvi: Install Device: Configuring device. 10:55:20.329
                              dvi: Configuration: null
                              dvi: Install Device: Configuring device completed. 10:55:20.332
                              dvi: Device Status: 0x01802401 [0x1c - 0xc0000490]
                              dvi: Install Device: Starting device 'ROOT\DISPLAY\0000'. 10:55:20.333
                              dvi: Install Device: Starting device completed. 10:55:20.336
                              ! dvi: Device not started (unknown reason): Device has no problem.
                              dvi: {Configure Device - exit(0x00000000)} 10:55:20.337
                              dvi: {Core Device Install - exit(0x00000000)} 10:55:20.338
                              ump: {Plug and Play Service: Device Install exit(00000000)}
                              <<< Section end 2020/08/01 10:55:20.342
                              <<< [Exit status: FAILURE(0x0000010b)]


                              >>> [Device Install (DiInstallDevice) - ROOT\DISPLAY\0000]
                              >>> Section start 2020/08/01 10:55:20.343
                              cmd: "C:\WINDOWS\system32\mmc.exe" "C:\Windows\System32\devmgmt.msc"
                              ndv: Flags: 0x00000004
                              ump: {Plug and Play Service: Device Install for ROOT\DISPLAY\0000}
                              ! dvi: Installing NULL driver!
                              dvi: {Core Device Install} 10:55:20.352
                              dvi: {Configure Device - ROOT\DISPLAY\0000} 10:55:20.354
                              dvi: Device Status: 0x01802001
                              dvi: Config Flags: 0x00000000
                              dvi: Parent Device: HTREE\ROOT\0
                              dvi: Install Device: Configuring device. 10:55:20.357
                              dvi: Configuration: null
                              dvi: Install Device: Configuring device completed. 10:55:20.359
                              dvi: Device Status: 0x01802401 [0x1c - 0xc0000490]
                              dvi: Install Device: Starting device 'ROOT\DISPLAY\0000'. 10:55:20.360
                              dvi: Install Device: Starting device completed. 10:55:20.362
                              ! dvi: Device not started (unknown reason): Device has no problem.
                              dvi: {Configure Device - exit(0x00000000)} 10:55:20.363
                              dvi: {Core Device Install - exit(0x00000000)} 10:55:20.365
                              ump: {Plug and Play Service: Device Install exit(00000000)}
                              <<< Section end 2020/08/01 10:55:20.368
                              <<< [Exit status: SUCCESS]


                              >>> [Delete Device - ROOT\DISPLAY\0000]
                              >>> Section start 2020/08/01 10:55:23.411
                              cmd: "C:\WINDOWS\system32\mmc.exe" "C:\Windows\System32\devmgmt.msc"
                              dvi: Query-and-Remove succeeded
                              <<< Section end 2020/08/01 10:55:23.420
                              <<< [Exit status: SUCCESS]

                              *** END OF LOGS CODE ***
                              Gigabyte Z77X-UP4 TH, Intel Core i7 3770k 3.5GHz, 4 Core, 8 Threads, 32GB RAM, NVIDIA GeForce GTX 660 2GB, 500GB SSD HDD for OS, 40TB Usable Hard Drive Capacity, Window 10 PRO 64-bit Edius 9.5 WORKSTATION...

                              Comment

                              Working...
                              X