ConvertXtoHD not Burning Full file to Bluray
Posted: Fri Oct 19, 2018 8:26 am
I've been having issues for the last week, everything was working fine previously and I have a sneaky suspicion it has to do with the latest releases of the nVidia drivers (based on this thread: 64-beta-bugs-t20299.html)
What's happening:
- Files are converting/encoding according to the application
- upon completion of converting/encoding the burn phase starts but it goes by REALLY fast now.
- application claims operation is complete but when I retrieve the disc from my burner and look at the disc only a very small portion of the disc is used. The files themselves are well over 10 gigs and the discs i'm using are 25g verbatim BD-R's.
- I've used up 4 blanks and the same thing every time.
- it's as if it's trying to burn the menu portion, but fails to burn the video file
My system:
OS: Windows 10 Home 64-bit
GPU: nVidia GeForce GTX 1060 6gb (driver ver 416.34)
CPU: Intel Core i7-7700k @ 4.2ghz (8cpus)
RAM: 32gb G.Skill DDR4
Buner: Pioneer External BDR-XD053.10
ConvertXtoHD Settings:
Burn Speed: 4x
output format: bluray resolution: automatic
encoding: automatic target size: BD-25
Video processing: Letterbox - Linear VSO - Linear - VSO -
Hardware Optimizations: Enable all H264 hardware optimizations
Here is the last log file:
:std_log='C:\ProgramData\VSO\ConvertXtoHD\3\Log\ConvertXtoHD 3_mainlog.20181019.034942.387.log'
:library=false
:app_name=ConvertXToHD.exe
:app_version=3.0.0.58
:most_recent=first
:event_header='{time} {type}'
:LongDateFormat=yyyy"-"mm"-"dd
:ShortDateFormat=dd mmm
:LongTimeFormat=hh":"nn":"ss"."zzz
:ShortTimeFormat=hh":"nn":"ss
:status=stopped
:group_indent=4
04:15:12.767 ------------ ***************ConvertXToHD.exe:7668 Log session stop after 28 minute(s) 41 second(s) 662 millisecond(s)****************
04:15:09.642 Info Thumber terminated
04:15:09.541 Info Waiting for thumber to end
03:46:31.999 Info Menu templates loaded: 20
03:46:31.381 Info Command line: 0 parameter(s)
Param #00: "C:\Program Files (x86)\VSO\ConvertXtoHD\3\ConvertXToHD.exe"
03:46:31.381 Info Total Physical Memory : 32702 Mb.
Available Physical Memory : 25715 Mb.
Memory Load : 21%
Total Virtual Memory : 4095 Mb.
Available Virtual Memory : 3633 Mb.
Available extended Virtual Memory : 0 Mb.
Total Memory : 37566 Mb.
Available Memory : 28353 Mb.
03:46:31.381 Info Processor Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz with 16/8 core(s) CPU
Supported instruction set: MMX,sse,sse2,sse3,ssse3,sse41,sse42,avx,avx2,bmi1,bmi2,aes,Fma3
03:46:31.377 Info User OS: Windows 10 Home, Microsoft Windows 10 Home Edition (Build 17134)
file name : C:\Program Files (x86)\VSO\ConvertXtoHD\3\ConvertXToHD.exe
file version : 3.0.0.58
User language : English (United States)
System language : English (United States)
03:46:28.253 Info Loading templates from: "C:\Users\osmer\Documents\ConvertXtoHD_Resources\Templates\"
03:46:28.253 Info Loading templates from: "C:\ProgramData\VSO\ConvertXtoHD\3\Templates\"
03:46:28.252 ------------ ***************************ConvertXToHD.exe:7668 Log session start 2018-10-19 at 03:46:27.980***************************
03:46:28.251 Info Monotonizer (C:\ProgramData\vso\vsomsl): 0MB
03:46:28.250 Info Thumb cache (C:\ProgramData\VSO\vsothumbs): 93MB
03:46:28.248 Info Program data (C:\ProgramData\VSO\ConvertXtoHD\3\): 71MB
03:46:28.244 Info Working folder size (C:\Users\osmer\Documents\ConvertXtoHD): 0MB
03:46:28.243 Info Available Space D: 820.01GB of 931.39GB
03:46:28.242 Info Available Space C: 112.00GB of 231.87GB
03:46:28.241 Group Folder data
03:46:28.240 Info 1 writer(s) found.
03:46:28.227 Group Burn engine events
The software was impeccable prior these latest batches of nVidia updates, hence why I think it's something to do with the new batch of drivers. Wondering if there's a work around or if I need to revert them (which I'm hesitant to do since they work great for everything else).
What's happening:
- Files are converting/encoding according to the application
- upon completion of converting/encoding the burn phase starts but it goes by REALLY fast now.
- application claims operation is complete but when I retrieve the disc from my burner and look at the disc only a very small portion of the disc is used. The files themselves are well over 10 gigs and the discs i'm using are 25g verbatim BD-R's.
- I've used up 4 blanks and the same thing every time.
- it's as if it's trying to burn the menu portion, but fails to burn the video file
My system:
OS: Windows 10 Home 64-bit
GPU: nVidia GeForce GTX 1060 6gb (driver ver 416.34)
CPU: Intel Core i7-7700k @ 4.2ghz (8cpus)
RAM: 32gb G.Skill DDR4
Buner: Pioneer External BDR-XD053.10
ConvertXtoHD Settings:
Burn Speed: 4x
output format: bluray resolution: automatic
encoding: automatic target size: BD-25
Video processing: Letterbox - Linear VSO - Linear - VSO -
Hardware Optimizations: Enable all H264 hardware optimizations
Here is the last log file:
:std_log='C:\ProgramData\VSO\ConvertXtoHD\3\Log\ConvertXtoHD 3_mainlog.20181019.034942.387.log'
:library=false
:app_name=ConvertXToHD.exe
:app_version=3.0.0.58
:most_recent=first
:event_header='{time} {type}'
:LongDateFormat=yyyy"-"mm"-"dd
:ShortDateFormat=dd mmm
:LongTimeFormat=hh":"nn":"ss"."zzz
:ShortTimeFormat=hh":"nn":"ss
:status=stopped
:group_indent=4
04:15:12.767 ------------ ***************ConvertXToHD.exe:7668 Log session stop after 28 minute(s) 41 second(s) 662 millisecond(s)****************
04:15:09.642 Info Thumber terminated
04:15:09.541 Info Waiting for thumber to end
03:46:31.999 Info Menu templates loaded: 20
03:46:31.381 Info Command line: 0 parameter(s)
Param #00: "C:\Program Files (x86)\VSO\ConvertXtoHD\3\ConvertXToHD.exe"
03:46:31.381 Info Total Physical Memory : 32702 Mb.
Available Physical Memory : 25715 Mb.
Memory Load : 21%
Total Virtual Memory : 4095 Mb.
Available Virtual Memory : 3633 Mb.
Available extended Virtual Memory : 0 Mb.
Total Memory : 37566 Mb.
Available Memory : 28353 Mb.
03:46:31.381 Info Processor Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz with 16/8 core(s) CPU
Supported instruction set: MMX,sse,sse2,sse3,ssse3,sse41,sse42,avx,avx2,bmi1,bmi2,aes,Fma3
03:46:31.377 Info User OS: Windows 10 Home, Microsoft Windows 10 Home Edition (Build 17134)
file name : C:\Program Files (x86)\VSO\ConvertXtoHD\3\ConvertXToHD.exe
file version : 3.0.0.58
User language : English (United States)
System language : English (United States)
03:46:28.253 Info Loading templates from: "C:\Users\osmer\Documents\ConvertXtoHD_Resources\Templates\"
03:46:28.253 Info Loading templates from: "C:\ProgramData\VSO\ConvertXtoHD\3\Templates\"
03:46:28.252 ------------ ***************************ConvertXToHD.exe:7668 Log session start 2018-10-19 at 03:46:27.980***************************
03:46:28.251 Info Monotonizer (C:\ProgramData\vso\vsomsl): 0MB
03:46:28.250 Info Thumb cache (C:\ProgramData\VSO\vsothumbs): 93MB
03:46:28.248 Info Program data (C:\ProgramData\VSO\ConvertXtoHD\3\): 71MB
03:46:28.244 Info Working folder size (C:\Users\osmer\Documents\ConvertXtoHD): 0MB
03:46:28.243 Info Available Space D: 820.01GB of 931.39GB
03:46:28.242 Info Available Space C: 112.00GB of 231.87GB
03:46:28.241 Group Folder data
03:46:28.240 Info 1 writer(s) found.
03:46:28.227 Group Burn engine events
The software was impeccable prior these latest batches of nVidia updates, hence why I think it's something to do with the new batch of drivers. Wondering if there's a work around or if I need to revert them (which I'm hesitant to do since they work great for everything else).