dbminter

Yeah, game CD's sometimes won't read in with certain combinations of discs and drives with ImgBurn. It appears when there are multiple tracks, it can be problematic. When you're mixing one track of data and tracks of audio. That's why I keep Alcohol 120% Free lying around. On the rare occasions when I come across this.

Yeah, I've been using UDF (only) 2.60 for years now on Windows 10 for all my data file backups and they read fine. I only ever change the settings from my defaults when creating DVD Video or BD Video discs, and I let ImgBurn make the necessary changes for me when it prompts me for those media. In fact, BD Video may not even need changes, just DVD Video to UDF+ISO9660 1.02

BTW, there's no need to screen capture log window entries. What you can do is highlight the log entry text you want to post using the mouse or SHIFT and arrow keys, then right click on what you highlighted and select Copy then Paste it into a post entry on the forum.

You're using the bad Verbatim. CMC MAG is the kind used in Verbatim Life series discs. CMC is the worst junk out there. Granted, I've never heard of Life Series making BD-R. Or are you using BD-RE? I noticed the write speed was 2x, which means you could be using BD-RE which makes sense with the BD-RE since Verbatim BD-RE are CMC junk. If you're using BD-RE, try Panasonic's discs.

UFD 2.60 is "read only" in Windows 7/Vista/8/10, whatever that means. So, as long as you don't format the M-Disc as a giant floppy for future additions of files, which ImgBurn doesn't do, I don't see you'd have a problem reading it in Windows 7. But, to be safe, you could probably enable UDF 2.50, just to be sure, since that is both read and write enabled in Windows 7. You'd probably only encounter problems with older UDF and ISO9660 with filenames that contained odd characters, like Japanese.

Yes, I'd blame the UME discs, too. The only really good options for DL discs are Verbatim DataLife Plus/AZO discs or TDK DL discs. Don't get the Verbatim Life series you find in stores. They'll be cheap CMC junk. You can only find the good stuff online.

Really, you won't have to worry about any setting for data backups to M-Disc. There's nothing special about M-Discs that requires any special changes to image file settings. It depends on what you're backing up. Depending on the file names and characters used in them, you may get by using ISO9660, but I'd recommend staying with UDF purely. Whenever I do data backups, I always use UDF 2.60. The discs read fine in Windows 10. You may not want to use UDF or such a newer revision if you want the discs to be readable on older versions of Windows that don't support UDF or the latest revision of UDF.

What is the maximum number of files allowed in a folder in an image Build job? Is it dependent on the file system chosen? Is it 9,999? Is it that Windows 10/NTFS has a maximum number of files allowed in a folder limit of 9,999? I thought there was some kind of file number limit to 9,999 at some point in history. Did a little digging. The maximum for NTFS is 4,294,967,295. But, what about ISO9660 or UDF on an optical disc? Thanks!

About my buying from NewEgg. I usually buy from Amazon.com, but sometimes there's no choice. For instance, Amazon.com rarely has the LG WH16NS60 available, but NewEgg does. Or it will be a case where the same reseller offers the same drive on Amazon.com and NewEgg, but sells it cheaper on NewEgg. It's not that NewEgg sells junk. The drive will be whatever it is when it arrives from the manufacturer. For instance, I want to get a WD 512 GB SDD HDD from Amazon.com, but they currently don't have it. Only resellers on Amazon.com do. So, I'll probably have to get it from NewEgg. NewEgg was the only seller who had the WD My Passport 4 TB portable mechanical USB HDD. Amazon.com didn't have it. And, of course, after I got mine from NewEgg, my local Target store had them on sale! But, the price was on par with what I paid for it on sale from NewEgg. I could have saved on the shipping, though.

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.

Especially if it's a modern application, which something from 2017 is, and it's installed with some kind of installation program, you can't just run the installer, copy over the installed files to a disc, and expect it to run. There's all kinds of Registry entries for various hooks and files that make it much more complicated to run software today versus 25 years ago.

It can't make 2 ISO's of the same file name unless you have a really big problem with your HDD file system. So, there must be 2 different file names with the .ISO extension. So, what would have happened is either one ISO is from a Read job or they're 2 different ISO build jobs where you or ImgBurn changed the output name. You say you put the EXE containing the icon and the AUTORUN in the root directory, but what exactly are the contents of your AUTORUN.INI? Is VS_PROFESSIONAL.EXE the main executable or just the icon file? Plus, can Visual Studio 2017, being a new application, actually be run from a disc or is it just the installer that would run from the disc? If you have them, use DVD+-RW discs to avoid going through discs when you're testing something like this. That way, you can reuse the same disc over and over. Plus, are you using Windows 10? I never nailed it down before but I don't think any discs ever automatically executed programs when I inserted them in a drive in Windows 10.

Most of my drives have been internals. Even my external ones now are internal ones put into enclosures. My experience with external drives is they last about as long as the internal drives. The half height drives are the only ones you can really trust. Slim models are typically junk. So, because my Dell doesn't have half height bays anymore, I've had to get enclosures for half height drives. I wouldn't be too worried about your experience. Life hates me and has proven it. So, I'm probably just targeted. But, I also do put my drives through a lot of use. I usually burn something of some kind about once a day. I pretty much now have to take out the warranties or suffer for it. If I don't, I'll pay for it. If I do, I'll have no need for the warranty. So, best to just chip in the cash and go with the flow. On a related note, I've burned my first of the 16x BD-R. They have the same DID as the 6x Verbatim BD-R so they probably would be more compatible with older drives, which are overclocking the maximum rated burn speed. Got near 16x speed, too, on a nearly full image. Burned and Verified without error. Now to perform a manual verification of the contents on the disc against their sources to make sure.

Built to last? Ha! I've been in the optical burner gig for 17 years and the best result I ever got out of an optical drive was a Pioneer BDR-2209 that lasted 2 years before dying. That is definitely beyond the norm. The average is about 7 to 9 months.

You shouldn't have to manually check Preserve Full Pathname each time. I would think it should be checked once you check it once and remain checked until you uncheck it. And according to ianmaty, using the OK button automatically enables that option for you. And it must because I always clicked OK and never used Quick OK and I never had to put my CUE files in the same folder as my input files. As you make changes to metadata, it's "saved" when you make the changes. There was a CUE file editing software someone once mentioned, but my tests with it utterly failed to load in the CUE file I created with ImgBurn. On an unrelated note, but related to past discussions in this thread on maximum media write speeds, had to order some more Verbatim BD-R. Verbatim has apparently stopped production of the 6x rated speed BD-R and has replaced it with 16x BD-R. I was always using 6x but getting like 12x speeds max on that media because most drives overclock the max rated speed for 6x BD-R. I'm just hoping these 16x BD-R write okay. Had to fall back to a few years old Pioneer BDR-2209 because the replacement LG WH16NS60 I got February 23rd died already. I didn't get the extended warranty so once the 30 days return window passed, I'm out of luck. First time in years I never needed the extended warranty and, from now on, will always get it. So, now, of course, it will be wasted money, but better to appease the universe than be out $115 for a drive that can't write BD-R anymore. The LG WH16NS60 has a peculiarity. When its BD laser dies (BD drives have 2 different lasers. One for CD/DVD and one for BD.) it scratches the recording surface of BD-R, rendering them unwritable. My first LG WH16NS60 did the same thing after 9 months and this latest one after less than 2.

I always wondered what the Quick OK button did in that context. I never used it, always using OK.

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.

Odd. It is interesting the pauses only occur when you play a physical disc and don't occur when you mount the image and play that via VLC. If the problem was in the VIDEO_TS output or the image, it would show up in VLC when you played the VIDEO_TS/mounted image file.

I think you're confusing the definition of Title Set. You've most likely either got one Title Set with 14 scenes or you've got 14 Title Sets, one for each scene. If you've got 14 Title Sets, the pauses may simply be when the DVD player is accessing the next Title Set on the disc. However, I think, didn't you say you were seeing these pauses in VLC when playing the VIDEO_TS from your hard drive? If so, you shouldn't see a noticeable pause in the video unless the software that made the VIDEO_TS added something it shouldn't have.

I don't understand the difference. It sounds like both ways you're putting all 14 scenes in one title set. Well, it's always possible the software is adding 14 non-seamless layer breaks, one after each scene. Since you say DVDShrink removes these pauses, it could be the case. You could try using DVDShrink without compression. That may give you uncompressed video but remove all the layer breaks. There is more than 1 pause, correct? If there's just the one pause, that's the single DVD-9 layer break. But, DVDShrink CAN (Doesn't always work.) remove the layer break if you have that option set in the software. Plus, some idiots author DVD's with more than 1 layer break and some are non-seamless. And the really annoying ones require IFOEdit to fix! Hell, I even found a layer break once on a DVD-5! And it COULDN'T be removed! Any attempt failed and produced a non-playable DVD.

Wait, are you sure these aren't the pauses that occur naturally between title sets? Are these scenes added as their own individual title sets? For instance, if you had 5 scenes, are there 5 title sets? Or did you add all 5 scenes in one title set? The software may have added pauses between the scenes you added.

I know there are simply some things you can't do with ISO9660. For instance, I'm pretty sure - isn't acceptable and you have to use _. : also isn't allowed, I don't think. If you have offline install files, you probably don't need ISO9660, anyway. You can just try adding them to a Build job using UDF and check the log window to see if any file name changes were made. If no file or folder names were changed, then the files are exactly the same as they were when you added them. No changes were made so they should still work on UDF.

I don't know if this will work, but try changing the ISO9660 file system option to UDF 2.60. See if you get better results. Ah, LUK replied while I was, basically making the same suggestion.

Could be a mult-track CD? If it were a true data CD, with no audio track on it, it would read to an ISO, I'd think. I just tried it with a data CD and it read to ISO. But, you said it was a game installation CD, so it may not necessarily be a data CD only, especially if you need to insert the disc in the drive in order to play it.