dbminter

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.

What about data CD? I forget, is that read to an ISO instead of a BIN/CUE and BIN/CUE is just reserved for audio CD's if you don't have CCD files checked?

Depending on where they layer break is and if it's not seamless, you may never notice it. If they place it where there's no audio or moving video, you probably won't notice the pause. I always use seamless because I find the pause annoying. Now, sometimes, there are stray layer breaks that ImgBurn misses. Those can generally be removed manually by either DVDShrink (Doesn't always work. For instance, on the 2002 Battlestar Galactica series DVD's.) or manually editing the IFO's with IFOEdit.

Since you seemed to indicate this was working before and stopped and since you've tried different media including Verbatim MKM, the problem, IMO, would be either your drive or the image you're trying to burn. If it does the same behavior on other image files, you know it's not the image file at fault. And since you indicated this was working before, it doesn't seem to be the fault of a slim line drive, although if you need to get a drive that properly supports overburning DVD+R DL, don't get a slim model drive if you can. Slim model drives are notorious for being problematic. This would also seem to indicate something is wrong with your drive if it was working before. If it was working before with this drive, then it may have just reached the end of its life.

What your AV most likely flagged was OpenCandy, a PUP, potentially unwanted program. It's not a virus, just don't get click happy when running the installer as you might install an add on software it recommends that you don't want. And make sure you downloaded it from the official mirror. Other locations like to wrap around their own unintended consequences. http://download.imgburn.com/SetupImgBurn_2.5.8.0.exe

I've never used anything else but ImgBurn. I think I might have used ConvertXToDVD's feature just to test it out, but I've always preferred having the options to set myself. So, since it's the only software I've used, it's the only thing I know that does ask for layer break information. It's there to give the user the option to set the layer change at different points where allowed. ConvertXToDVD is just setting it wherever it wants to place it. It thinks the user probably doesn't want to be bothered with that kind of information. Anyway, the bottom line is, yes, when the VIDEO_TS spans both layers, a layer break/change is required. ImgBurn just gives the user the opportunity to set it where they want. For instance, I like placing layer breaks at the beginning of a movie/episode where possible. Where not, I try to select something like a period of solid black between a scene/commercial break slot.

If by louder you physically mean the DVD player is making more noise than when it plays a DVD-ROM DVD Video disc, there could be reasons why a player might have "issues" with a recorded DVD. Based on the kind of dye on it and the laser in the player, it may be putting more read wear on the assembly trying to read it.

I'm sorry. I didn't word myself very well. I mean layer breaks aren't necessary for DVD+R DL if the VIDEO_TS fits on one layer but adding extra data files to the job makes it fit on a DVD+R DL. Layer breaks are necessary but you don't have to assign them for DVD-R DL, I think. However, who really uses THAT format, anyway? So, I don't think layer breaks are user defined for DVD-R DL because the layer change is always at a specific part on the media. I don't know that for certain, as it's been over a decade since I created a DVD Video on DVD-R DL. I know far more about VIDEO_TS structure than I do about BD Video. In fact, without actually looking at a BD Video disc structure, I can't name, from memory, the name of the folder the video is actually contained in in BD Video.

Well, it depends on how you define "layer break." There's the change between Layer 0 and Layer 1 which is absolutely necessary, but what is generally referred to as the layer break may not. Because you can make seamless and non-seamless layer breaks. Seamless layer breaks won't have the pause in the video when the layer changes. Non-seamless will pause. And it depends on the size of the VIDEO_TS. If you have a combination of VIDEO_TS and data that makes a DVD-9, if the VIDEO_TS is small enough to fit on one layer, you won't need a layer break. You'll only be prompted for layer breaks if the VIDEO_TS spans both layers. I am guessing, though I never used ConvertXToDVD for actual DVD creation, just the creation of VIDEO_TS, that the software automatically uses seamless layer breaks. VSO Downloader worked for the brief period I used it. I dropped it like a hot potato because VSO lies about it being "free." It's time crippled. It's only free for like a week, then it stops working until you pay for it. That's not free; that's a trial. The current version of ImgBurn returns Windows 10 as Windows 8 because of how Windows identifies itself. Since Windows 10 was released after the release of the last stable version of ImgBurn, ImgBurn identifies Windows 10 as Windows 8. This will be fixed in the next stable release of ImgBurn when it comes out.

There may be some glimmer of hope that VSO is back in business. They recently released an update (Or maybe a beta.) to VSO Downloader. Which would indicate they may be back to coding.

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.

Generally, semaphore time issues are a plague of external drives. They're caused by a conflict between the USB to SATA bridge in the unit and the controller on your motherboard. The only solution that tends to work is to get a different drive. Or replace your motherboard, but that's using a bazooka to swat a fly. Since you said this happens on CD-R and BD-R, as you said, you can pretty much rule out the discs. So, I wouldn't necessarily blame the Ritek BD-R's you're using. Although Ritek media can cause all kinds of compatibility problems with drives. If your CD-R are also Ritek or CMC, you could try getting some Verbatim BD-R or DataLifePlus/AZO CD-R. (NOT the Life Series you find in stores. They're CMC junk.) However, I doubt that would help, but it would definitely pin down it's not the media you're using if you try with the best and get the same result.