Search the Community

When you say DVD recorder that created the disc you're trying to copy, do you mean a burner like a drive in your PC or an external DVD video recorder like a Panasonic drive? I can understand why it might say that on a Panasonic drive and will explain more later if that's the case. When you're in Build mode, it's not asking you to locate an image file. In this case, in your case, you'd want to put in the disc you're trying to make a copy of and drag and drop all files and folders from the disc in your drive into a Build image project. Build will then create an image file from those files you added for burning to a disc.

Hello, I used to use an earlier version of this software that would allow me to create an ISO image from a DVD created in my DVD recorder. I don't remember the version number, but I lost that software in a hard drive meltdown. I downloaded the current version and tried to create an ISO file, but I got the following error message: "Sorry, using Read mode to create an image file from a multi-track DVD-ROM disc is not currently supported. Instead, use Build mode to create a new 'clean' image based on the contents of the disc." I tried changing to build mode, but it is asking me to locate the files, which don't exist yet. I know that my DVD recorder didn't change the way it creates a disc, so I'm confused at why the software will no longer create the ISO file. Any ideas? Thanks, Mike

I'm not sure if you need an M-Disc drive to read a written M-Disc BD-R. I know with M-Disc DVD, as long as you have a drive that reads DVD+R, it will read M-Disc DVD's. I believe even standalone DVD movie players will play DVD Video discs burned to M-Disc DVD's if that player supports playing DVD+R. I believe M-Disc was specifically made for this kind of compatibility. So, I'd guess an M-Disc BD-R burned in an M-Disc capable drive would read on a standard BD drive. Be aware, of course, since you used a TL disc, you'd need a BD drive that supports reading TL media, and not all BD drives do. Of course, if you always buy an M-Disc capable drive, you won't have to worry about it not being able to be read back in. As for restoring, it depends on what you backed up and how you backed it up. If you used ImgBurn to just add files and folders to an image file job, then all you can do is use File Explorer to drag and drop the files/folders in Windows/File Explorer and replace the files in the destination if they already exist. If you're more concerned about restoring an entire drive from disaster, you'd be better off investing in a drive imaging application like Macrium Reflect (Which is what I use and also offers file and folder backups.) or True Image (Which I've used in the past but don't recommend any longer and it used to support file and folder backups 10 years ago when I last used it.). So, if you're looking to restore something like Windows, then Windows/File Explorer isn't the way to go as you can't just replace files in Windows/installed applications and expect it to work. You'd be better off served by an imaging application. And what you can do is create images to a local HDD and then use ImgBurn to copy these images to an M-Disc for archival purposes.

I have an older IBM CD-ROM game that has 96 audio tracks and one data track. When trying to image the disc ImgBurn gets to "Analysing Tracks... (Session 1, Track 2)" and then just stops. I've let it sit there for up to an hour, and saw no progress. I was able to create a MDF/MDS file using Daemon, with the hope that I could then mount the MDF virtually and image to bin/cue via ImgBurn from there, however it behaved the same as it does with the original disc. The log follows: I 13:39:26 ImgBurn Version 2.5.8.0 started! I 13:39:26 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 13:39:26 Total Physical Memory: 67,028,784 KiB - Available: 56,327,944 KiB I 13:39:26 Initialising SPTI... I 13:39:26 Searching for SCSI / ATAPI devices... I 13:39:26 -> Drive 1 - Info: PLDS DVD-ROM DS-8DBSH RD11 (D:) (SATA) I 13:39:26 -> Drive 2 - Info: DiscSoft Virtual 1.0 (E:) (Virtual) I 13:39:26 Found 1 DVD-ROM and 1 BD-ROM XL! I 13:40:24 Operation Started! I 13:40:24 Source Device: [1:0:0] PLDS DVD-ROM DS-8DBSH RD11 (D:) (SATA) I 13:40:24 Source Media Type: CD-ROM I 13:40:24 Source Media Supported Read Speeds: 10x, 16x, 20x, 24x I 13:40:24 Source Media Sectors: 78,371 I 13:40:24 Source Media Size: 184,328,592 bytes I 13:40:24 Source Media Volume Identifier: _ I 13:40:24 Source Media File System(s): ISO9660 I 13:40:24 Read Speed (Data/Audio): 4x / 4x I 13:40:24 Destination File: F:\_.BIN I 13:40:24 Destination Free Space: 2,125,000,032,256 Bytes (2,075,195,344.00 KiB) (2,026,557.95 MiB) (1,979.06 GiB) I 13:40:24 Destination File System: NTFS I 13:40:24 File Splitting: Auto Once I hit abort it then follows with: E 13:47:14 Average Read Rate: N/A - Maximum Read Rate: N/A And finally, here is the info reported by ImgBurn when it scans the disc: PLDS DVD-ROM DS-8DBSH RD11 (SATA) Current Profile: CD-ROM Disc Information: Status: Complete State of Last Session: Complete Erasable: No Sessions: 1 Sectors: 78,371 Size: 160,503,808 bytes Time: 17:26:71 (MM:SS:FF) Supported Read Speeds: 10x, 16x, 20x, 24x TOC Information: Session 1... (LBA: 0 / 00:02:00) -> Track 01 (Mode 1, LBA: 0 / 00:02:00) -> Track 02 (Audio, 02:20:29, LBA: 12591 / 02:49:66) -> Track 03 (Audio, 00:07:28, LBA: 23120 / 05:10:20) -> Track 04 (Audio, 00:07:24, LBA: 23673 / 05:17:48) -> Track 05 (Audio, 00:06:21, LBA: 24222 / 05:24:72) -> Track 06 (Audio, 00:06:72, LBA: 24693 / 05:31:18) -> Track 07 (Audio, 00:06:18, LBA: 25215 / 05:38:15) -> Track 08 (Audio, 00:06:21, LBA: 25683 / 05:44:33) -> Track 09 (Audio, 00:06:72, LBA: 26154 / 05:50:54) -> Track 10 (Audio, 00:07:33, LBA: 26676 / 05:57:51) -> Track 11 (Audio, 00:08:32, LBA: 27234 / 06:05:09) -> Track 12 (Audio, 00:08:08, LBA: 27866 / 06:13:41) -> Track 13 (Audio, 00:08:21, LBA: 28474 / 06:21:49) -> Track 14 (Audio, 00:10:67, LBA: 29095 / 06:29:70) -> Track 15 (Audio, 00:20:27, LBA: 29912 / 06:40:62) -> Track 16 (Audio, 00:06:24, LBA: 31439 / 07:01:14) -> Track 17 (Audio, 00:07:38, LBA: 31913 / 07:07:38) -> Track 18 (Audio, 00:06:19, LBA: 32476 / 07:15:01) -> Track 19 (Audio, 00:06:23, LBA: 32945 / 07:21:20) -> Track 20 (Audio, 00:06:24, LBA: 33418 / 07:27:43) -> Track 21 (Audio, 00:06:20, LBA: 33892 / 07:33:67) -> Track 22 (Audio, 00:06:25, LBA: 34362 / 07:40:12) -> Track 23 (Audio, 00:06:21, LBA: 34837 / 07:46:37) -> Track 24 (Audio, 00:06:18, LBA: 35308 / 07:52:58) -> Track 25 (Audio, 00:06:18, LBA: 35776 / 07:59:01) -> Track 26 (Audio, 00:23:05, LBA: 36244 / 08:05:19) -> Track 27 (Audio, 00:06:23, LBA: 37974 / 08:28:24) -> Track 28 (Audio, 00:09:29, LBA: 38447 / 08:34:47) -> Track 29 (Audio, 00:11:03, LBA: 39151 / 08:44:01) -> Track 30 (Audio, 00:09:25, LBA: 39979 / 08:55:04) -> Track 31 (Audio, 00:06:18, LBA: 40679 / 09:04:29) -> Track 32 (Audio, 00:06:20, LBA: 41147 / 09:10:47) -> Track 33 (Audio, 00:06:22, LBA: 41617 / 09:16:67) -> Track 34 (Audio, 00:06:24, LBA: 42089 / 09:23:14) -> Track 35 (Audio, 00:06:21, LBA: 42563 / 09:29:38) -> Track 36 (Audio, 00:07:22, LBA: 43034 / 09:35:59) -> Track 37 (Audio, 00:06:18, LBA: 43581 / 09:43:06) -> Track 38 (Audio, 00:11:68, LBA: 44049 / 09:49:24) -> Track 39 (Audio, 00:06:17, LBA: 44942 / 10:01:17) -> Track 40 (Audio, 00:06:21, LBA: 45409 / 10:07:34) -> Track 41 (Audio, 00:06:22, LBA: 45880 / 10:13:55) -> Track 42 (Audio, 00:06:20, LBA: 46352 / 10:20:02) -> Track 43 (Audio, 00:08:22, LBA: 46822 / 10:26:22) -> Track 44 (Audio, 00:06:22, LBA: 47444 / 10:34:44) -> Track 45 (Audio, 00:06:25, LBA: 47916 / 10:40:66) -> Track 46 (Audio, 00:06:18, LBA: 48391 / 10:47:16) -> Track 47 (Audio, 00:06:25, LBA: 48859 / 10:53:34) -> Track 48 (Audio, 00:06:19, LBA: 49334 / 10:59:59) -> Track 49 (Audio, 00:06:19, LBA: 49803 / 11:06:03) -> Track 50 (Audio, 00:10:42, LBA: 50272 / 11:12:22) -> Track 51 (Audio, 00:07:39, LBA: 51064 / 11:22:64) -> Track 52 (Audio, 00:06:20, LBA: 51628 / 11:30:28) -> Track 53 (Audio, 00:12:40, LBA: 52098 / 11:36:48) -> Track 54 (Audio, 00:13:20, LBA: 53038 / 11:49:13) -> Track 55 (Audio, 00:06:23, LBA: 54033 / 12:02:33) -> Track 56 (Audio, 00:06:24, LBA: 54506 / 12:08:56) -> Track 57 (Audio, 00:08:14, LBA: 54980 / 12:15:05) -> Track 58 (Audio, 00:06:19, LBA: 55594 / 12:23:19) -> Track 59 (Audio, 00:07:22, LBA: 56063 / 12:29:38) -> Track 60 (Audio, 00:06:22, LBA: 56610 / 12:36:60) -> Track 61 (Audio, 00:09:47, LBA: 57082 / 12:43:07) -> Track 62 (Audio, 00:07:61, LBA: 57804 / 12:52:54) -> Track 63 (Audio, 00:06:24, LBA: 58390 / 13:00:40) -> Track 64 (Audio, 00:08:50, LBA: 58864 / 13:06:64) -> Track 65 (Audio, 00:06:20, LBA: 59514 / 13:15:39) -> Track 66 (Audio, 00:06:18, LBA: 59984 / 13:21:59) -> Track 67 (Audio, 00:06:46, LBA: 60452 / 13:28:02) -> Track 68 (Audio, 00:06:23, LBA: 60948 / 13:34:48) -> Track 69 (Audio, 00:06:20, LBA: 61421 / 13:40:71) -> Track 70 (Audio, 00:06:18, LBA: 61891 / 13:47:16) -> Track 71 (Audio, 00:09:24, LBA: 62359 / 13:53:34) -> Track 72 (Audio, 00:06:20, LBA: 63058 / 14:02:58) -> Track 73 (Audio, 00:07:47, LBA: 63528 / 14:09:03) -> Track 74 (Audio, 00:06:18, LBA: 64100 / 14:16:50) -> Track 75 (Audio, 00:06:22, LBA: 64568 / 14:22:68) -> Track 76 (Audio, 00:07:69, LBA: 65040 / 14:29:15) -> Track 77 (Audio, 00:06:22, LBA: 65634 / 14:37:09) -> Track 78 (Audio, 00:11:05, LBA: 66106 / 14:43:31) -> Track 79 (Audio, 00:06:23, LBA: 66936 / 14:54:36) -> Track 80 (Audio, 00:06:60, LBA: 67409 / 15:00:59) -> Track 81 (Audio, 00:06:40, LBA: 67919 / 15:07:44) -> Track 82 (Audio, 00:06:25, LBA: 68409 / 15:14:09) -> Track 83 (Audio, 00:06:20, LBA: 68884 / 15:20:34) -> Track 84 (Audio, 00:15:51, LBA: 69354 / 15:26:54) -> Track 85 (Audio, 00:26:18, LBA: 70530 / 15:42:30) -> Track 86 (Audio, 00:08:38, LBA: 72498 / 16:08:48) -> Track 87 (Audio, 00:06:22, LBA: 73136 / 16:17:11) -> Track 88 (Audio, 00:06:20, LBA: 73608 / 16:23:33) -> Track 89 (Audio, 00:06:18, LBA: 74078 / 16:29:53) -> Track 90 (Audio, 00:06:69, LBA: 74546 / 16:35:71) -> Track 91 (Audio, 00:07:27, LBA: 75065 / 16:42:65) -> Track 92 (Audio, 00:06:69, LBA: 75617 / 16:50:17) -> Track 93 (Audio, 00:06:24, LBA: 76136 / 16:57:11) -> Track 94 (Audio, 00:06:20, LBA: 76610 / 17:03:35) -> Track 95 (Audio, 00:06:48, LBA: 77080 / 17:09:55) -> Track 96 (Audio, 00:06:19, LBA: 77578 / 17:16:28) -> Track 97 (Audio, 00:04:24, LBA: 78047 / 17:22:47) -> LeadOut (LBA: 78371 / 17:26:71) Track Information: Session 1... -> Track 01 (LTSA: 0, LTS: 12591) -> Track 02 (LTSA: 12591, LTS: 10529) -> Track 03 (LTSA: 23120, LTS: 553) -> Track 04 (LTSA: 23673, LTS: 549) -> Track 05 (LTSA: 24222, LTS: 471) -> Track 06 (LTSA: 24693, LTS: 522) -> Track 07 (LTSA: 25215, LTS: 468) -> Track 08 (LTSA: 25683, LTS: 471) -> Track 09 (LTSA: 26154, LTS: 522) -> Track 10 (LTSA: 26676, LTS: 558) -> Track 11 (LTSA: 27234, LTS: 632) -> Track 12 (LTSA: 27866, LTS: 608) -> Track 13 (LTSA: 28474, LTS: 621) -> Track 14 (LTSA: 29095, LTS: 817) -> Track 15 (LTSA: 29912, LTS: 1527) -> Track 16 (LTSA: 31439, LTS: 474) -> Track 17 (LTSA: 31913, LTS: 563) -> Track 18 (LTSA: 32476, LTS: 469) -> Track 19 (LTSA: 32945, LTS: 473) -> Track 20 (LTSA: 33418, LTS: 474) -> Track 21 (LTSA: 33892, LTS: 470) -> Track 22 (LTSA: 34362, LTS: 475) -> Track 23 (LTSA: 34837, LTS: 471) -> Track 24 (LTSA: 35308, LTS: 468) -> Track 25 (LTSA: 35776, LTS: 468) -> Track 26 (LTSA: 36244, LTS: 1730) -> Track 27 (LTSA: 37974, LTS: 473) -> Track 28 (LTSA: 38447, LTS: 704) -> Track 29 (LTSA: 39151, LTS: 828) -> Track 30 (LTSA: 39979, LTS: 700) -> Track 31 (LTSA: 40679, LTS: 468) -> Track 32 (LTSA: 41147, LTS: 470) -> Track 33 (LTSA: 41617, LTS: 472) -> Track 34 (LTSA: 42089, LTS: 474) -> Track 35 (LTSA: 42563, LTS: 471) -> Track 36 (LTSA: 43034, LTS: 547) -> Track 37 (LTSA: 43581, LTS: 468) -> Track 38 (LTSA: 44049, LTS: 893) -> Track 39 (LTSA: 44942, LTS: 467) -> Track 40 (LTSA: 45409, LTS: 471) -> Track 41 (LTSA: 45880, LTS: 472) -> Track 42 (LTSA: 46352, LTS: 470) -> Track 43 (LTSA: 46822, LTS: 622) -> Track 44 (LTSA: 47444, LTS: 472) -> Track 45 (LTSA: 47916, LTS: 475) -> Track 46 (LTSA: 48391, LTS: 468) -> Track 47 (LTSA: 48859, LTS: 475) -> Track 48 (LTSA: 49334, LTS: 469) -> Track 49 (LTSA: 49803, LTS: 469) -> Track 50 (LTSA: 50272, LTS: 792) -> Track 51 (LTSA: 51064, LTS: 564) -> Track 52 (LTSA: 51628, LTS: 470) -> Track 53 (LTSA: 52098, LTS: 940) -> Track 54 (LTSA: 53038, LTS: 995) -> Track 55 (LTSA: 54033, LTS: 473) -> Track 56 (LTSA: 54506, LTS: 474) -> Track 57 (LTSA: 54980, LTS: 614) -> Track 58 (LTSA: 55594, LTS: 469) -> Track 59 (LTSA: 56063, LTS: 547) -> Track 60 (LTSA: 56610, LTS: 472) -> Track 61 (LTSA: 57082, LTS: 722) -> Track 62 (LTSA: 57804, LTS: 586) -> Track 63 (LTSA: 58390, LTS: 474) -> Track 64 (LTSA: 58864, LTS: 650) -> Track 65 (LTSA: 59514, LTS: 470) -> Track 66 (LTSA: 59984, LTS: 468) -> Track 67 (LTSA: 60452, LTS: 496) -> Track 68 (LTSA: 60948, LTS: 473) -> Track 69 (LTSA: 61421, LTS: 470) -> Track 70 (LTSA: 61891, LTS: 468) -> Track 71 (LTSA: 62359, LTS: 699) -> Track 72 (LTSA: 63058, LTS: 470) -> Track 73 (LTSA: 63528, LTS: 572) -> Track 74 (LTSA: 64100, LTS: 468) -> Track 75 (LTSA: 64568, LTS: 472) -> Track 76 (LTSA: 65040, LTS: 594) -> Track 77 (LTSA: 65634, LTS: 472) -> Track 78 (LTSA: 66106, LTS: 830) -> Track 79 (LTSA: 66936, LTS: 473) -> Track 80 (LTSA: 67409, LTS: 510) -> Track 81 (LTSA: 67919, LTS: 490) -> Track 82 (LTSA: 68409, LTS: 475) -> Track 83 (LTSA: 68884, LTS: 470) -> Track 84 (LTSA: 69354, LTS: 1176) -> Track 85 (LTSA: 70530, LTS: 1968) -> Track 86 (LTSA: 72498, LTS: 638) -> Track 87 (LTSA: 73136, LTS: 472) -> Track 88 (LTSA: 73608, LTS: 470) -> Track 89 (LTSA: 74078, LTS: 468) -> Track 90 (LTSA: 74546, LTS: 519) -> Track 91 (LTSA: 75065, LTS: 552) -> Track 92 (LTSA: 75617, LTS: 519) -> Track 93 (LTSA: 76136, LTS: 474) -> Track 94 (LTSA: 76610, LTS: 470) -> Track 95 (LTSA: 77080, LTS: 498) -> Track 96 (LTSA: 77578, LTS: 469) -> Track 97 (LTSA: 78047, LTS: 324)

Thank you for reply. Those files work fine with AnyBurn for example… mmh, but it must be closed source too (I'm not sure). Yes, can burn Enchanced CD starting from BIN/CUE, but can create them too? Can it create an image file from a new project with: 1st session with audio tracks + 2nd session with data track in CD-ROM XA Mode 2, Form 1 format?

Hello, I've installed Imgburn because is one of the very few burners able to decently manage old mixed mode discs (1 session: 1st track data, next tracks audio) for ancient Amiga/PC games of the '90... I also have Daemon Tools 10.10 Lite to mount and convert between file formats (bin+cue, nrg, mds/mdf....) and here is the problem with Imgbrun: trying to load a mds/mdf it reported a "Error: can only open mds version 1.x, this one is 2.1" :-( then with a .nrg file of a mixed mode CD it says can only manage nrg files single track :-( ...so my question is: will these formats compatibility improved anytime soon? It is a great burning software but the partial compatibility with some common formats make it... meh... for some tasks. Last question: can ImgBurn burn/create images in Enhanced CD mode ( https://en.wikipedia.org/wiki/Blue_Book_(CD_standard) ) too?

Long time imgburn user and contributor. About to burn my first M-disc. I have a LG full height player that says M-disc on it's front (Model BE16NU50). 100G M-disc, this will be a data file backup. What are the best settings to create this disc with? : Mode 1 or 2? UDF only or UDF+ISO9660, or something else? Which UDF revision? Anything else I need to know? Damn discs are pricey, I want to get it right on first try for obvious reasons.

I think you're barking up the wrong tree here. ImgBurn will only burn DVD's with VIDEO_TS folders you give it. So, Premiere Pro CC 2019 created a file for you, but you'll need to convert that file to some kind of VIDEO_TS DVD folder. You'll need something like ConvertXToDVD or similar conversion/encoding software to create a VIDEO_TS for ImgBurn to burn. Unless you just plan on putting this Premiere Pro file on a disc and you have a DVD/Blu-Ray player that will play container files. Then, it depends on what file formats your player supports. If that's the case, ImgBurn won't care what file format it is. What will matter is what kind of file systems your player supports from disc.

I would like to burn DVDs with 5.1 Surround Sound that will play in my home theater system Have managed to work in Premiere Pro CC 2019's latest update and create an exported file which contains 5.1 surround sound. Now need to burn a DVD with that type of sound. Which exported file type would be best for ImgBurn to create such a DVD? Thanks for info. Bert

Thanks! I haven't used the quick ok in a while as I really didn't know what it did. I just use the Ok button. If I don't tick (enable) "preserve full path name" I have to leave it in the same folder with the source files. So when the queue is opened and you load a saved queue, it will not load it in if you moved the .cue file without ticking (enabling) "preserve full path name". I have a question regarding the edit function regarding tracks, titles,... After you make changes to say one track and you have to change more, do you simply go to the next tracks and ImgBurn automatically saves the changes? It must be that way because there is no save changes button other than Ok, and if you hit that it takes you directly to the next phase of creating the .cue. I was messing around with that yesterday for a long while because of one track having some character that couldn't be processed/parsed. It would create the .cue file without that track unless you edited it correctly. I couldn't for the life of me see how to save the changes until by accident I guess I proceeded with Ok and it finally took. Is there a reason other than anticipating the changes were made why a confirmation wasn't implemented? You could be in there for a really long time not knowing changes are made on the fly. The guide mentions the refresh button after editing. Is that the save button? Maybe I hit that by accident and finally was able to include that file? Has anyone suggested a save function after editing? Wouldn't be a bad implementation. Please let me know the correct method for editing and saving. Thanks as always.

The "Quick OK" button is described in the Guides - The ImgBurn Functions - Section [*]4.4 Create CUE File... Also the "Preserve Full Pathnames" is described there.

@ dbminter. No. He sure has the "Preserve Full Pathnames" unchecked and uses the "Quick OK" button to get to the burn point in the "Create cue file..." window. @ dr_ml422 If you are using "Quick OK" button you need to tick (enable) "Preserve Full Pathnames" box, than you can move the cue wherever you want if you want to save it for further uses. Otherwise you need to use "OK" button that will bring up a "Save as..." window to select a location and that will automatically enable Preserve Full Pathnames in the cue file even if it is unticked (disabled) in the "Create cue file..." window.

The CUE files do not have to be in the same folder as the source files to burn an Audio CD with; I always save my CUE files to the Desktop for sake of easy finding and my source files are always all over the place, usually. The only thing I can think of that may be doing that for you is if you have Preserve Full Pathnames checked. Go into Create CUE File and see if that box is checked. If it is, try unchecking it and see if that helps.

There are some weird compression cases where even less than 120 minutes of input will generate DVD-9 sized VIDEO_TS outputs. It's rare, but I use ConvertXToDVD to convert some containers in the past that were under 2 hours, but generated DVD-9 sized VIDEO_TS output. My only explanation was how the source file was authored. Some kind of compression that maybe didn't really compress very well. Or could be, as you say, the audio format of the sound track in the container might not have been a compressed one. I still don't understand what the OP is saying when you says he had 1 video title set (VTS) regardless of how he authored the input. Adding each "scene" as its own "chapter" would create a single VTS. Adding each scene on its own should create a VTS for each scene. Then again, I'm not familiar with the conversion software he's using, so it may behave oddly.

You could always create a set of par2 recovery files for the image - so you can recover it if that should happen.

Hello, I have searching for a solution to this problem but since I do not speak English, I do not understand and I can not find a solution. I want to create an data .iso image file with the system ISO9660:1999 and MODE1/2048, but when i compare the files from created .iso file with the original folder, i see that the files or folders with letters like á, é, í, ó, ú etc., these letters have changed. Is possible to create an data .iso file with this letters? how is the correct configuration for this? i need use ISO9660:1999 cause i have files, folders and subfolders with a excessive number of characters in his names and are not modifiable. Thank you very much for you help for my! ImgBurn.log

Hi.. I wanted to create an ISO file - that's an image file, right? And I've seen a 'how to' showing Imgburn creating an ISO as an image file. But I got a .bin and a .cue file, no ISO. What's doing? I'm using win10, is that the problem?

Actually, no, I had forgotten you had said anything about h264 output failing before with ConvertXToVideo. And if it does do that on episodic DVD's, I'd prefer it do it that way. I'd rather have each episode as a separate container. If you wanted to, you could take each container and use the Merge function in ConvertXToDVD to create a single title set. Anyway, let me know if that option change does any good. However, the software should allow the user to choose not to separate single episodes. I can understand why it does it, though, because the IFO's would, even taken all episodes as one giant VTS on the DVD as separate title sets. One thing I think I'll try. Taking the MPEG4 output into AVIDeMux and recode it as h264. See what I get. Let me see if I can recover the output from before and try that now. I was able to recover the deleted file from the old Windows where I tested ConvertXToVideo before restoring my live system image backup before testing it and another application I was trying out. So, now, AVIDeMux is recoding the MPEG4 video to H264. Didn't help out much. Just down from 931 MB to 720 MB.

Had a chance to install the trial of ConvertXToVideo. EPIC failure creating MP4 with H264. Creates a file with audio but no video on MP4 and H264 video! However, I had multiple chapters in the Blu-Ray I used as input and the program did NOT create individual MP4 files for each chapter. There's no reason why the program should create individual MP4's for each chapter. I tried to recreate the file as MP4 with Mpeg4 as the video type. Got video in my file that time. Don't know why the H264 isn't working. I know I've got the necessary codecs because AVIDeMux will save nVIDIA H264 video in its output that plays, so it's probably some kind of bug in the ConvertXToVideo software. Ah, I think I may have discovered where your one file per chapter may be coming from. Under the setting in ConvertXToVideo, check under Chapters. Do you have the box checked that says Create one title set per chapter when loading a file? If you have that checked, try unchecking it and see if that doesn't improve your file set creation. That setting may only apply to DVD Video or BD Video creation, though, but it may fix the output behavior you've been getting. I tried creating to DVD Video and it seems to work fine. So, the H264 error would prevent me from using this software to do my DVD to container conversion. Mpeg4 is too large an output format. It creates 1 GB 10 minute files. But, it does work to convert BD Video. It does import all titles, the main feature and bonus features.

It is possible, but I don't think ImgBurn can do it and I doubt you can do it with just the Create CUE File option if it is possible for ImgBurn to do it. What you'd have to do is create a disc with 2 tracks (Or is it sessions? I forget which one ImgBurn can't do.) one with the audio CD tracks on it and one with a 2nd bit where you'd store the data part of the audio CD.

Now, are you sure these stutters aren't in the original VIDEO_TS output you have? Try playing the DVD from the VIDEO_TS folder from the hard disk you're importing in Build mode, inferring you used Build mode to create this image. See if you get the same stuttering between sectors. It seems highly unlikely you'd get the same results from playback both on a PC DVD drive and a standalone DVD player unless it wasn't in the original video. The other common denominator is the DVD burner you're using. Maybe it isn't very good. I know LiteOn drives can add random pauses to DVD Video that aren't layer breaks. I don't know what track record the TSSTcorp CDDVDW SH-222AB has. What is the source of this image? Did you Build it from a VIDEO_TS folder or was the ISO generated by another application? Other application generated ISO's are well known for producing output that isn't right.

Generate a BIN file from a CUE file? Not with ImgBurn, no. What you'd need to do is burn the CD with the CUE and then create an image from that CD in ImgBurn to get a BIN/CUE file set. As far as I know, anyway.

I forgot that you had mentioned about Dell not installing half height Bay's anymore. Yes the limitation is on the external burners after all! They will not go a certain speed I guess unless it said on the box when you bought it that it was 24x capable. if it didn'tsay that on the box when you bought it they will not go that speed at all the drive when it comes out the manufacturer has to have the ability to go that speed and then coupled with the blank they'll both figure out if they'll go up to that speed together that's why I mentioned that they must have a contract with verbatim because they suggested using their brand with the writer that I bought and also it came with that burning suite that I mentioned before. I've used the suite and that's the one way I say it sounds like it's ready to take off from an airline ramp! LOL! Image burn shows me the speed as it's going in progress though and that's a big big plus! so that's why I could look at the speeds when reading and like I said yesterday it went up to 19 on the read rate so I wouldn't be surprised that it went more or less to 24 on the write rate. I will check that out with some Data. You know that I'm trying to burn DVDs as data, how would I go along doing that? I don't think it takes away from the structure does it? Imgburn will automatically see it's a DVD and create an image during build mode then burn it. I used to be able to burn as data and still be playable.

Yes, I should have been clearer before about the Create CUE File function. That won't create BIN/CUE files, just CUE files that write the converted audio files directly to a CD-R as an Audio CD.

Depends on what you're intending to do. Are you trying to create BIN/CUE from discs with WAV files on them or are you trying to create audio CD's from the WAV files on these discs? If you're trying to create BIN/CUE from discs, use the Read mode in ImgBurn. (If you select in the settings to create .CCD files for Virtual CloneDrive/CloneCD, then you won't get BIN/CUE but IMG files.) If you're in the EZ Mode Picker, you'll want the Create image file from disc option. If you're trying to create audio CD's from the WAV files, you'll want the Create CUE File option under Tools.