Search the Community

So, you're saying if a title set has chapters in it, ConvertXToVideo will create a separate MP4 for each chapter? That's useless and a pain! I want an entire movie as 1 title set, not 20 separate MP4's I have to merge.

Are you saying ConvertXToVideo won't make the same kind of DVD menu that ConvertXToDVD does when you use ToVideo to make a VIDEO_TS? Meaning, the VIDEO_TS just starts playing the moment the disc starts? If it does, I can still use ConvertXtoVideo to import a BD, create a VIDEO_TS, then use that VIDEO_TS as input in ConvertXToDVD to create the kind of menu discs I'm used to.

I've been trying to find out what is it exactly that's going on with ConvertXToDVD and BD file. I've thrown in some Blu-ray Rip's that were an mp4 file and had no problem re-encoding them with the subtitles put in. That's different, oh than a total Blu-ray file. Now if ConvertXToDVD does not include Blu-ray files when they say Convert X, which means that Blu-ray is not included in that X, then you're right they might want others to buy a different software for that. Listen you could get around all this simply by using the new VidCoder which will grab Blu-rays, DVDs, or whatever whether in disc form and not and convert it to an mp4. Yes I know it's the same thing as what you were doing before but maybe actually might just be simpler. Now I have the ConvertXtoVideo software and I'm not sure if putting in a Blu-ray folder would include everything. I do know that when you put in a DVD and it might have separate titles on that DVD it gives you an option to merge all the titles and then convert into whatever format. I've been using the MP4 format so I don't know if it will do that with the DVD format because remember DVD will only take so much compression and what not. Next time Matilda Blu-ray folder file or whatever inside convertxtovideo go to any plus signs or whatever that are on on the main interface and see if you can click and see whatever else it attached to that file. If it did then just right to it and see if you have an option to merge everything together to that one file and create a DVD out of it. Try the trial of ConvertXtoVideo and see what happens with a Blu-ray to DVD conversion. I would do it on my end but I don't have any true Blu-ray files or folders with me. I'm having a similar problem with VIdcoder. I put in a DVD folder and it actually has four, five different titles on it in vob files. Now since I didn't check the window next to the first file I didn't know that they were actual titles in there and so when I encoded the DVD folder it actually just encoded the first title. so I have to include all the titles into the encoding job at the bottom in the queue. Only thing is it will output seven different MP4 titles without merging them. Convert X to video does a real beautiful job of merging all the titles and converting them to MP4. It actually stays with the original audio and video resolution as well. So you just might want to look into that ConvertXtoVideo and check it out. if you do decide to get it, go straight for the recent Beta version because they fix the hardware encoding optimization option. It is buzzing now where before it was only at 30 frames per second I'm getting 230.6 frames per second from DVD to MP4 conversion. VIdCoder is 64bit and using multi-threading. It really is about the best freeware h.264 encoding app out there.

Yes I feel your frustration believe me! Convert x to DVD is plain and simply a quick fix to get a DVD out of some other file, though it does have its limitations. What you can try to do is when you load the Blu-ray folder see if there's an option to merge all the files together right there and then that are in the input window. Right click and see if the option is there. Also go into the settings and see if there's a setting that maybe the default has for just picking main title. Another thing you can try is in the editing window where you can add subtitles and audio and all that click on the plus sign next to the video and see if you can add something else and just throw the whole file in there and see what it will pick up. There's an option in CyberLink Power2Go to create Video DVDS. If it's included with your PC definitely give it a try. It will convert and burn your M2TS folder to a DVD Video VTS folder. VSO sent me the download link to another version or whatever because it wouldn't convert a regular Blu-ray mp4 file that I had which it should have no problem with.they said the issue was with the hardware optimization and so they said that the version they sent me should fix that. It's full of bugs! Many many bugs! And I already suggested to them to just update the most recent version and forget about all those old versions because they're wasting a lot of time and all that. That's what Windows 10 did basically they just playing around with newer Hardware making it better to work with. I have yet to install it because I'm playing around with the new VidCoder which if you haven't got a chance you should install and give it a try because it's really banging! WinXDVDAuthor is free. Give it a play. It works very well when it works.

I use Rufus for burning existing ISO's to flash drives. You could use ImgBurn to create an ISO destined for a flash drive in Build mode, but the actual burning would have to be done by Rufus. As was said, it's probably easier just to use the Windows Media Creator Tool to download and burn its ISO to a flash drive.

U don't, with imgburn. It can only create discs or iso's. Use the windows 10 media creation tool (that's one of it's options) or Rufus. Take your pick Verstuurd vanaf mijn Nexus 6P met Tapatalk

No wonder you have a monster build! Dell too which I'm a fan. Believe me it's because of your build that ConvertXToDVD is buzzing! You have six cores and that means all six will be working on anything you do, especially single file inputs. If you want you could put upto six different input files, though ConvertXToDVD will not put them out individually. It will think you're creating a DVD out of all of them. If small sized yes you would have a very decent DVD output. You're lucky! You have Cyberlink software that came with your Dell. Power2Go is usually included in there as it is part of their products line. If so, open it, go to Video Disc option and select the AVC H.264 mp4 output to DVD disc. You're going to love it! It will take those Home movies and create a very nice playable M2TS file on DVD which is awesome. I found them exactly like that through bundled software that came with my LG Burner. All night I was fussing with a Blu-ray 1080p file that for w/e reason ConvertXtoVideo erred out, as did another software. It's an unusual file because although that it's Blu-ray, it's in 1920-800p instead of 1920-1080p. These programs have a flaw because it shouldn't matter what the original input is, it should convert it to whatever. I had to throw it inside ConvertXToDVD and put out a DVD. I wanted a MP4 file with burnt in subs so I could use Power2Go and convert it to DVD Video. Their outputs are better because of the TrueTheater etc... Way to go with the Dell! I might be wrong, though I think Intel might just work better with these programs. If for no other reason than they first created CPUs, for the most part.

Ok now the program I was alluding to concerning the 1080p file is ConvertXtoDVD. It will support any incoming file or non-protected disc to convert to DVD. Are you converting your Blu-ray titles into MP4/MKV before throwing that into ConvertXToDVD? There's no need as you can put the Blu-ray folder/file into ConvertXToDVD and straight away have it make you a DVD. The only thing you can't import is commercially protected disc, DVD or not. Everything else it mainly imports including Blu-ray containers. Unless you have more than 4 cores on your rig, there's no way a 90 minute movie unless Avi or other than 1080p/Blu-ray will pop out in 1/2 an hour. ConvertXToDVD especially with full high-definition 1080p Blu-ray files will not hover over 40 FPS during conversion. The faster it processes any file, and the only way it can do that is by upping the FPS during conversion, the faster you'll get the output DVD folder etc... ConvertXtoVideo is nothing but ConvertXToDVD in reverse kind of. It will take w/e file and convert it to w/e file, including a DVD. What I suggested was looking into Power2Go which as I mentioned does import MP4/MKV etc... and create a Blu-ray file that burns to DVD disc in the M2TS folder using the AVC H.264 codec. You're converting original Blu-ray folders into MP4/MKV correct? Then converting that to DVD? You could either throw that ripped Blu-ray straight into ConvertXToDVD or take that same Blu-ray folder and convert it to a playable AVC file on DVD. This way it'll play since Sony plays as is and DVD is playable. How much smaller do your Blu-ray files get after MP4/MKV conversion? ConvertXToDVD as I mentioned will almost add 2GB to a 1GB mp4 when finished processing to DVD. ConvertXToDVD also as I've read has to be closed after a while and a cleaning must take place in our PC, as it does collect remnant leftovers and then slow down. I just finished doing that earlier after I posted those slow FPS speeds. It went up to about 35 FPS, and still took more than a half hour to output the DVD file. I'm definitely going big on my next build to see the difference if any. The source file determines ConvertXToDVD speeds, not the build as much as it seems it should.

VSO has as I see an output default size for certain sized source files. If the source video is @ 2GB or a tad more, then their resulting DVD VTS Folder will be 3.94 GB or a tad less. So that's about 2GBs more than the source file. That'll almost always put it higher than a 4.7GB blank. Maybe I'll put 2 related source files on a DVD. It'll work out the same as using a DVD DL and adding more to that. I tested my external LITEON during a copying session, and let's just say I'll be using it more as a burner. It buzzes past my LG internal, though it was hooked up to ImgBurn. The LG was using another app. I have to load both burners in ImgBurn with comparable sources, and see how they fair. I'm waiting to see how LITEON'S external Blu-ray writer fairs. It hasn't been out that long. If you want to check out a Conversion app that surprised me and I have it, checkout Power2Go. I tested the Video to AVC H.264 Blu-ray conversion and it buzzed through with an exceptionally great looking M2TS file in the BDMV folder. Their conversion from .mp4 etc... to DVD VTS is also faster and with exceptional output as well. Only thing no subtitle support, which I'm beginning to not mind much during conversion, and more towards afterwards in the same folder as you suggested. I wonder why none of the usual suspects in Video Conversion, Burning, Editing, etc... don't create some software that'll either snatch the sub out of the file or somehow create/get the correct fitting one to include with source?

Right click one of the problem files once you've added it within the 'Create CUE File' feature/window. Pick the option to display the directshow filter list (if it lets you) and let me know what it says please. There must just be something weird in the file that your filters can't cope with. Removing the (ID3 etc) tags sometimes solves issues like this.

It lets me continue using the software by the way (if I click continue), I think it just stops the Bravo being used. Hope this helps (bottom part in bold is what appeared after I clicked F8 and searched)........ I 04:21:23 ImgBurn Version 2.5.8.0 started! I 04:21:23 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 04:21:23 Total Physical Memory: 16,735,172 KiB - Available: 6,244,560 KiB I 04:21:23 Initialising PTRobot... I 04:21:23 PT_SDK Version 1.6.2.0 I 04:21:23 Initialising SPTI... I 04:21:23 Searching for Auto Loader devices... E 04:21:25 Device->Initialise() Runtime Exception! E 04:21:25 Device: Disc Publisher II 1.43 03/19/2008 E 04:21:25 Exception: EAccessViolation E 04:21:25 This auto-loader will not be visible in the program. E 04:21:25 Device->Initialise() Failed! E 04:21:25 Device: Disc Publisher II 1.43 03/19/2008 E 04:21:25 This auto-loader will not be visible in the program. I 04:21:25 Found 0 Auto Loaders! I 04:21:25 Searching for SCSI / ATAPI devices... I 04:21:25 -> Drive 1 - Info: PIONEER BD-RW BDR-206D 1.06-ID61 (O:) (SATA) I 04:21:26 -> Drive 2 - Info: PIONEER DVD-RW DVR-112D 9.15 (Q:) (USB 2.0) I 04:21:26 -> Drive 3 - Info: ATAPI eHBU312 2 VL16 (T:) (USB 2.0) I 04:21:26 -> Drive 4 - Info: DVDFab Virtual Drive 1.1 (N:) (SCSI) I 04:21:26 Found 1 DVD±RW, 1 BD-ROM/HD DVD-ROM and 2 BD-REs! W 04:21:28 I/O Interface 'Debug Mode' has been Enabled! I 04:21:42 Searching for Auto Loader devices... D 04:21:42 PTRobot_EnumRobots - Robot Count: 1, Return Code: 0 I 04:21:42 Initialising Device (Auto Loader 1)... D 04:21:42 PTRobot_GetRobotInfo - Robot: 0x20000001, Return Code: 0 D 04:21:42 Robot Handle: 0x20000001 - Model: Disc Publisher II, Version: 1.43 03/19/2008 date/time : 2019-01-28, 04:21:42, 126ms computer name : INTEL-PC user name : edited operating system : Windows 8 x64 build 9200 system language : English system up time : 18 days 8 hours program up time : 21 seconds processors : 8x Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz physical memory : 6003/16343 MB (free/total) free disk space : (C:) 51.49 GB display mode : 1920x1080, 32 bit process id : $fb1c allocated memory : 65.43 MB executable : ImgBurn.exe exec. date/time : 2013-05-24 09:59 version : 2.5.8.0 compiled with : BCB 2006/07 madExcept version : 4.0.7 callstack crc : $0ba3c082, $be1836ba, $85b7b862 contact name : edited contact email : edited exception number : 2 exception class : EAccessViolation exception message : EAccessViolation. thread $e8e4 (TInterfaceThread): 0ba3c082 +ad17 PTRobot.dll 0ba367d6 +533a PTRobot.dll PTRobot_EnumDrives 00587016 +0742 ImgBurn.exe DeviceIO.cpp 8840 +92 TDevice.Initialise_AutoLoader_PTROBOT 00584b25 +0029 ImgBurn.exe DeviceIO.cpp 8489 +14 TDevice.Initialise_AutoLoader 005833a3 +0023 ImgBurn.exe DeviceIO.cpp 8140 +14 TDevice.Initialise 0057187a +04ce ImgBurn.exe DeviceIO.cpp 4143 +46 InitialiseDevices_AutoLoaders_PTROBOT 0056ff7a +0026 ImgBurn.exe DeviceIO.cpp 3910 +19 InitialiseDevices_AutoLoaders 005629f5 +013d ImgBurn.exe DeviceIO.cpp 1480 +49 InitialiseDevices 0071d156 +005e ImgBurn.exe InterfaceThread.cpp 2000 +14 TInterfaceThread.SearchForDevices 00715e79 +029d ImgBurn.exe InterfaceThread.cpp 155 +76 TInterfaceThread._DoInterface 00715b35 +001d ImgBurn.exe InterfaceThread.cpp 35 +6 TInterfaceThread.Execute 00a46edb +002b ImgBurn.exe madExcept _17342 008d8b98 +0034 ImgBurn.exe Classes _17197 008f73c8 +0028 ImgBurn.exe System _16782 00a46dbd +000d ImgBurn.exe madExcept _17340 00a46e27 +0037 ImgBurn.exe madExcept _17341 74188482 +0022 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($5e74) at: 00715a4a +0032 ImgBurn.exe InterfaceThread.cpp 21 +0 TInterfaceThread.Create main thread ($5e74): 0095e955 +12d ImgBurn.exe Forms TApplication.Idle 0095dd43 +017 ImgBurn.exe Forms TApplication.HandleMessage 0095e02b +0b3 ImgBurn.exe Forms TApplication.Run 0070c459 +5e5 ImgBurn.exe ImgBurn.cpp 272 +166 WinMain 00a80acc +14c ImgBurn.exe __startup 74188482 +022 KERNEL32.DLL BaseThreadInitThunk thread $ef40: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $fa80: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $fe48: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $6e84: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $dc1c: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $4150: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $ef8: 74188482 +22 KERNEL32.DLL BaseThreadInitThunk thread $e84: 739d597d +12d KERNELBASE.dll WaitForMultipleObjectsEx 00a46dbd +00d ImgBurn.exe madExcept _17340 00a46e27 +037 ImgBurn.exe madExcept _17341 74188482 +022 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($5e74) at: 73e0ed63 +000 combase.dll thread $db40 (TWorkerThread): 739c45f3 +93 KERNELBASE.dll WaitForSingleObjectEx 739c454d +0d KERNELBASE.dll WaitForSingleObject 009de881 +19 ImgBurn.exe Virtualtrees _16776 00a46edb +2b ImgBurn.exe madExcept _17342 008d8b98 +34 ImgBurn.exe Classes _17197 008f73c8 +28 ImgBurn.exe System _16782 00a46dbd +0d ImgBurn.exe madExcept _17340 00a46e27 +37 ImgBurn.exe madExcept _17341 74188482 +22 KERNEL32.DLL BaseThreadInitThunk >> created by main thread ($5e74) at: 009de776 +16 ImgBurn.exe Virtualtrees _16772 modules: 00400000 ImgBurn.exe 2.5.8.0 C:\Program Files (x86)\ImgBurn 0af60000 stcd3control.dll 5.2.707.0 C:\Program Files (x86)\Common Files\SureThing Shared 0ba30000 PTRobot.dll 1.6.2.0 C:\Program Files (x86)\ImgBurn 0bd90000 PTRobotDPPRO.dll 1.6.2.0 C:\Program Files (x86)\ImgBurn 0c030000 idmmkb.dll 6.19.9.1 C:\Program Files (x86)\Internet Download Manager 0c720000 PTRobotDP.dll 1.6.2.0 C:\Program Files (x86)\ImgBurn 0c8d0000 PTRobotStr.DLL 1.1.4.0 C:\Program Files (x86)\ImgBurn 0c9a0000 PTRobotDPse.dll 1.6.2.0 C:\Program Files (x86)\ImgBurn 0cb40000 PTRobot4100.dll 1.6.2.0 C:\Program Files (x86)\ImgBurn 0fa00000 CoreMessaging.dll 6.2.17134.471 C:\WINDOWS\System32 0ff40000 CoreUIComponents.dll 6.2.17134.376 C:\WINDOWS\System32 2ffb0000 TextInputFramework.dll 6.2.17134.376 C:\WINDOWS\System32 54260000 tiptsf.dll 6.2.17134.191 C:\Program Files (x86)\Common Files\microsoft shared\ink 544f0000 explorerframe.dll 6.2.17134.1 C:\WINDOWS\system32 5dc10000 MSACM32.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 63d10000 oledlg.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 63eb0000 wintypes.dll 6.2.17134.523 C:\WINDOWS\SYSTEM32 65110000 SHFOLDER.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 66f60000 twinapi.appcore.dll 6.2.17134.137 C:\WINDOWS\system32 670d0000 dcomp.dll 6.2.17134.1 C:\WINDOWS\system32 67210000 WindowsCodecs.dll 6.2.17134.345 C:\WINDOWS\SYSTEM32 67f60000 quartz.dll 6.2.17134.1 C:\WINDOWS\system32 68110000 d3d11.dll 6.2.17134.441 C:\WINDOWS\system32 6a280000 SPINF.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 6a300000 drvstore.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 6a450000 DEVRTL.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 6a610000 pdh.dll 6.2.17134.1 C:\WINDOWS\system32 6a660000 OLEACC.dll 7.2.17134.1 C:\WINDOWS\SYSTEM32 6a960000 dxgi.dll 6.2.17134.112 C:\WINDOWS\system32 6aa60000 RMCLIENT.dll 6.2.17134.471 C:\WINDOWS\system32 6aa80000 dataexchange.dll 6.2.17134.1 C:\WINDOWS\system32 6aba0000 olepro32.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 6c280000 MSIMG32.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 6cd90000 gdiplus.dll 6.2.17134.523 C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.17134.523_none_73d8c7959f75cd2a 6ffa0000 DEVOBJ.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 70030000 dbgcore.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 70060000 dbghelp.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 701f0000 SRVCLI.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 70210000 FaultRep.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 70270000 NETUTILS.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 70300000 ntmarta.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 70330000 WKSCLI.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 70c90000 dwmapi.dll 6.2.17134.1 C:\WINDOWS\system32 70cc0000 uxtheme.dll 6.2.17134.1 C:\WINDOWS\system32 70d40000 winmmbase.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 70e60000 PROPSYS.dll 7.0.17134.112 C:\WINDOWS\SYSTEM32 70fe0000 bcrypt.dll 6.2.17134.112 C:\WINDOWS\SYSTEM32 71190000 Mpr.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 71880000 WINMM.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 719f0000 WINSPOOL.DRV 6.2.17134.319 C:\WINDOWS\SYSTEM32 71c70000 COMCTL32.DLL 6.10.17134.523 C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.17134.523_none_42edd4b044e3535c 71e80000 NETAPI32.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 71ea0000 WSOCK32.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 72690000 IPHLPAPI.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 726c0000 VERSION.DLL 6.2.17134.1 C:\WINDOWS\SYSTEM32 73300000 Userenv.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 738a0000 CRYPTBASE.dll 6.2.17134.1 C:\WINDOWS\System32 738b0000 SspiCli.dll 6.2.17134.376 C:\WINDOWS\System32 738d0000 KERNELBASE.dll 6.2.17134.441 C:\WINDOWS\System32 73b20000 msvcrt.dll 7.0.17134.1 C:\WINDOWS\System32 73be0000 ucrtbase.dll 6.2.17134.319 C:\WINDOWS\System32 73d00000 WS2_32.dll 6.2.17134.1 C:\WINDOWS\System32 73d70000 combase.dll 6.2.17134.523 C:\WINDOWS\System32 73fd0000 clbcatq.dll 2001.12.10941.16384 C:\WINDOWS\System32 740c0000 ADVAPI32.DLL 6.2.17134.471 C:\WINDOWS\System32 74140000 IMM32.DLL 6.2.17134.1 C:\WINDOWS\System32 74170000 KERNEL32.DLL 6.2.17134.1 C:\WINDOWS\System32 74250000 FLTLIB.DLL 6.2.17134.1 C:\WINDOWS\System32 74260000 gdi32full.dll 6.2.17134.471 C:\WINDOWS\System32 743d0000 sechost.dll 6.2.17134.319 C:\WINDOWS\System32 74420000 windows.storage.dll 6.2.17134.471 C:\WINDOWS\System32 749e0000 SHLWAPI.dll 6.2.17134.1 C:\WINDOWS\System32 74a30000 SHELL32.dll 6.2.17134.441 C:\WINDOWS\System32 75d80000 USER32.dll 6.2.17134.376 C:\WINDOWS\System32 75f10000 MSASN1.dll 6.2.17134.1 C:\WINDOWS\System32 75fb0000 shcore.dll 6.2.17134.112 C:\WINDOWS\System32 76040000 setupapi.dll 6.2.17134.1 C:\WINDOWS\System32 76470000 kernel.appcore.dll 6.2.17134.112 C:\WINDOWS\System32 76480000 RPCRT4.dll 6.2.17134.471 C:\WINDOWS\System32 76540000 COMDLG32.DLL 6.2.17134.1 C:\WINDOWS\System32 76620000 MSCTF.dll 6.2.17134.376 C:\WINDOWS\System32 76770000 msvcp_win.dll 6.2.17134.1 C:\WINDOWS\System32 767f0000 PSAPI.DLL 6.2.17134.1 C:\WINDOWS\System32 76810000 OLEAUT32.DLL 6.2.17134.48 C:\WINDOWS\System32 768b0000 CRYPT32.dll 6.2.17134.1 C:\WINDOWS\System32 76ab0000 OLE32.DLL 6.2.17134.407 C:\WINDOWS\System32 76bb0000 cfgmgr32.dll 6.2.17134.1 C:\WINDOWS\System32 76d60000 WINTRUST.dll 6.2.17134.81 C:\WINDOWS\System32 76db0000 GDI32.dll 6.2.17134.285 C:\WINDOWS\System32 76de0000 win32u.dll 6.2.17134.1 C:\WINDOWS\System32 76e00000 profapi.dll 6.2.17134.1 C:\WINDOWS\System32 76e20000 bcryptPrimitives.dll 6.2.17134.471 C:\WINDOWS\System32 76eb0000 powrprof.dll 6.2.17134.1 C:\WINDOWS\System32 76ff0000 ntdll.dll 6.2.17134.471 C:\WINDOWS\SYSTEM32 771b0000 mscms.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 77e00000 ColorAdapterClient.dll 6.2.17134.1 C:\WINDOWS\SYSTEM32 7c000000 MSVCR70.dll 7.0.9466.0 C:\WINDOWS\SYSTEM32 disassembling: [...] 00586fec call +$4f059f ($a77590) ; memset 00586ff1 add esp, $c 00586ff4 8840 lea eax, [ebp-$324] 00586ffa 8838 mov dword ptr [ebp-$324], $a 00587004 8840 push eax 00587005 lea edx, [ebp-$724] 0058700b push edx 0058700c mov ecx, [ebp+8] 0058700f mov eax, [ecx+$22c] 00587015 push eax 00587016 > call dword ptr [$b38acc] ; PTRobot_EnumDrives (PTRobot.dll) 0058701c mov ebx, eax 0058701e 8842 mov al, [$ce7ae8] 00587023 test al, al 00587025 jz loc_587276 0058702b 8844 mov word ptr [ebp-$308], $a8 00587034 lea eax, [ebp-$78] 00587037 call -$183450 ($403bec) ; dstring.h.System.AnsiString.Create 0058703c push eax 0058703d lea eax, [ebp-$74] 00587040 inc dword ptr [ebp-$2fc] [...]

I used the dlls of the guide: in the last few days he did not let me download them and so I used those dates from Primera, but they are a later version and therefore we see that they do not go well with imgburn. For the second question, I do not want to make them convert files. I meant that I have a DVD with 4-5 movies in mp4 or avi and I wanted to copy the files and not create the ISO: is it possible?

Hello, I want create file iso from a lot of dvd..

I've another question: have you a guide to use imgburn to create iso from dvd (video or data)?

Ok so after you convert say a .mp4 file to DVD using ConvertXToDVD, you take the resulting VTS folder and burn it along with the source .mp4 file to a DVD blank? Now ImgBurn can either burn it as is, ir rather data, or as a DVD Video correct? My question is if one chooses to burn it as a DVD Video doesn't all the files have to be in VTS structure? Or it justs means that the contents are being burnt to a DVD blank? ImgBurn doesn't convert non-dvd files to a VTS folder as ConvertXToDVD does correct? Or does it mean that it'll burn w/e to a DVD blank and make it playable? I think imgBurn knows when a VTS folder is involved and asks "would you like to create a DVD Video Disc?" I'm going to do it this way and it can only be done with a ConvertXToDVD video file because of its optimization. Another proggie will burn as is, and there won't be any room for the source file. According to VSO per their guide on hardware optimization, ConvertXToDVD doesn't use it although it's available. Believe me many have questioned this. I'm almost positive that there is software out there that will use it and speed things up even more. Thing is how reliable is it either hardware-wise or customer support-wise?

I supposedly used to have the ability to delete posts, but I never found out how to do it. Sorry. As for the hardware acceleration, I don't know if it works on my ConvertXToDVD or not. I just know I have it enabled, but I don't know if it actually does anything or not. Yeah, the VIDEO_TS that ConvertXToDVD creates is pretty well optimized. I don't know how they do it either. For instance, you can take a DVD-9 VIDEO_TS as a source and many times get ConvertXToDVD to generate a VIDEO_TS that fits on a DVD-5. I generally keep 1 container per ConvertXToDVD DVD disc because I also add the container file source to the DVD Video disc I create with ImgBurn and the resulting VIDEO_TS folder. For things that are smaller but related in some way, like say episodes of a TV series, I'll put a few per disc. 8 half hour episodes per disc and 4 hour episodes per disc, which is what most pressed DVD-9's will do unless they compress the Hell out of them to fit more episodes to a disc. I've seen some ridiculous ones like 12 half hour episodes to a DVD-9!

Yeah, the RW logo doesn't necessarily mean it's a rewritable disc. It's the logo of the DVD+RW consortium who created DVD+R and DVD+RW. They force people to put their logo on the media as means of advertising and to charge an extra fee. Of course, what I do with a best of the best MP4 is create a DVD out of it, burn the DVD with the VIDEO_TS folder AND the MP4 to a DVD AND keep the MP4 file on my external HDD. But, I'm paranoid and don't want to lose anything.

And you don't need to create multiple topics for the same issue. http://forum.imgburn.com/index.php?/topic/25482-multiple-viruses-on-first-mirror-digital-digest/ Verstuurd vanaf mijn Nexus 6P met Tapatalk

Im trying to rip my disks of Legends of Dragoon (for better performance in ePSXe), on Windows10. Everything I read says ImgBurn is the goto program for this. But I cannot get it to complete the rip. If I select the Disk to Image file operation, it gives me no errors but completes in 1 second and leaves a 0kb .bin and a 1kb .cue. If I try the Create Image from Files and point it at the disk, I get ~59% through before I get a error that says it failed to read a file "Reason: Incorrect Function". I havent been able to find anything online to explain this. Any idea what is going wrong? Im given to understand that ImgBurn doesnt support the Subchannel side of things for actual burning, but does for ripping from the disk (which is all I need). EDIT: Ill post the log shortly, sorry it was not included.

I had a Blu-Ray where I had to use MKV in order to enable selectable subtitles. I posted on the Handbrake forum why I couldn't disable the burned in the subtitles. From the log, it had something to do, I think, with a particular audio file type in the Blu-Ray. I was using MP4, but under this particular instance, MP4 would only always create burned in subtitles. Once the forum told me to try MKV instead, it worked.

Yes, I always had the impression tick boxes like RECURSE DIRECTORIES could be assumed to be persistent across Imgburn sessions, which is why I didn't think of that being an issue and hadn't looked there for a potential problem. I didn't load any saved projects either and have lately mostly used Imgburn with the settings it last saved. I always do only open one instance of Imgburn, never more than one. I would think that would be asking for trouble what with drive locking, etc so I definitely haven't had multiple instances of the program running as I didn't want to risk any drive access conflicts. The FOLDER SKIPPED log messages remain a mystery, but at least now I was able to write out the DVD image to the DVD+RW disc and get on with what I needed that for. I just tested Imgburn again. No disc inserted in the ODD this time. But unticking the RECUSE DIRECTORIES box and then trying to create the exact same layout in the disc layout editor, reliably reproduces the same problem with the SKIPPED FOLDERS messages. So for whatever reason Imgburn logic decides to do that, I'm not sure. I surmised originally that it was warning me that I'm losing folders in the layout even though I dragged it to the layout in the editor (when RECURSE box is unticked).

DVD+R compatibility really only matters if you're going to burn DVD Video contents to them. Older stand alone DVD players have some read issues with DVD+R. If you're not worried about putting one such disc in an older DVD player, then go with DVD+R. DVD+R is slightly larger (A few MB.) than DVD-R. So, sometimes you may create an image that fits on a DVD+R but won't fit on a DVD-R. I actually encountered that just earlier this morning. If you're primarily going to just burn non DVD Video data contents, go with DVD+R. Most modern DVD players shouldn't have trouble playing a DVD+R. All modern PC DVD drives should support reading DVD+R. If you have a choice between using a CMC DVD+R or an MCC, I would always recommend the MCC. I had a few CMC DVD+R because I needed a 10 pack to test LightScribe writing with, back when they made drives that supported it. So, I had about 9 discs left over to use up, since I didn't want to use CMC discs for my own contents. So, I used them as temp burners for some DVD Video contents my mother wanted to see. Turned out it was a waste of time as her DVD player wouldn't even recognize playable discs had been inserted. That's how much CMC media is. Sony has been farming out the DVD-R it used to make to Ritek for over a decade. It's decent enough 2nd tier media I've used before with no problem. I have never encountered a package of DVD's with many discs in them that had different MID's on different discs. Generally, when such things happen, it's from shady sellers who have opened various packages and mixed and matched discs into a new selling package to maximize profits. For instance, put a quality name on the outside of the package, but use cheaper media on the inside to make more money and make the buyer think they're getting quality product.

Thanks for the follow up. After a few more failures just now trying to successfully create the disc layout for the DVD+RW write, it turns out the problem is due to the RECURSE SUBDIRECTORIES tick box being disabled. I'm glad it was something simple. Yet strangely, only the long path folders generated the SKIPPED FOLDERS log message but other folders with much shallower folder nesting did not (and also appeared to be added to the disc layout successfully despite recurse option disabled). I also noticed that the RECURSE SUBDIRECTORIES tick box for some reason sometimes does not persist across Imgburn sessions. This means I have to check the status of that box each time I start up Imgburn. As far as UDF 2.50 support for BD reading, I'm aware that actually UDF 2.50 was supported beginning with Windows Vista. Win-XP can support BD reading via UDF 2.50 if a 3rd party UDF driver supporting UDF 2.X is installed, such as the Nero UDF driver for In-CD packet writing, and that works fine reading BDs written in UDF 2.50 also. Also, just to be sure, if I choose only UDF as the file system, then under the ADVANCED - RESTRICTIONS tab, is it correct to assume that the any file system not used, in this case ISO9660 and JOLIET, that their tabs' settings are completely irrelevant regardless of what they may be set to, since I've selected only UDF as the file system? I was wondering if the on-line Imgburn guides / settings reference have ever been made into a downloadable PDF?

http://forum.wininizio.it/index.php?/topic/71535-masterizzare-file-mds-iso/ (il post non è mio) sorry but with your Italian translated automatically with chrome for me it is a bit tiring;) no offense;) Is MDS a pointer to real ISO? probably the position of interruption of the level in your case (translated I do not understand) :( So basically, I'm going to burn the right MDS file? tell me yes. If in the future I should remaster the mds file I have on the pc I could do a good thing: 1) the iso file and the mds file create a folder. 2) So I'm quiet and I have all the saved copies ready to re-burn;)

I'm trying to archive a number of folders and files onto a single layer DVD+RW disc which has already been properly formatted by Imgburn using the full erase function with the PROPERLY FORMATTED option enabled. There are several concerns / problems arising from building the image with the disc layout editor: I've already read up on the Imgburn guides before posting this. 1. I am still unclear about which file system needs to be used for a DVD-ROM format write - should only UDF 1.02 be selected, or should ISO9960 + UDF 1.02 be selected? I assume MODE-1/2048 data type is selection to be used. Since this isn't intended to be a DVD-Video format, I'm unsure if UDF should even be included as part of the file system selection. 2. If I use more than one file system, is it necessary for more than one volume label to be entered into all the file systems' volume label fields in order for the same volume label to appear under all file systems used in the write? 3. I have a folder on the source disk (HDD) that has more than 8 levels of folder nesting. I'm not sure how I did it the first time, but after using the disc layout editor, I go back to the INFORMATION tab and then click the CALCULATOR button to determine disc space consumption and only on the very first time I did this, the log reported that the long file paths file names were somehow altered (presumably because file path length was too long). Altered to what I'm not sure for starters, but now on a second session of Imgburn I tried to repeat the same process and the disc layout editor simply completely IGNORES the long pathed folders and they are now OMITTED from the layout completely. So I'm not sure which options I did or didn't tick the second time around that caused the file layout editor to ignore folders that had long paths. These tick boxes that I'm not sure about includes: FOLDER FILE NAME LENGTH - I selected LEVEL-2, 31 characters, and also ticked the boxes for ALLOW MORE THAN 8 DIRECTORY LEVELS and also ALLOW MORE THAN 255 CHARACTERS IN PATH. But no matter what I do, the disc layout editor continues to ignore long path folders from the layout I create even though I do drag the folders into the layout. It would seem to me that I may need to ZIP the long path folders into a ZIP file for optical disc write if the folder nesting is too deep. But I'd like to know which tick boxes I mentioned above should be enabled or not. I knew there was some deep nesting in some folders and had expected this sort of problem to arise during layout creation.