dbminter

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.

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.

I was thinking it should be in the Guides section. I had forgotten it was already there under the title End Of The World problem.

There's really not much else you can do. I don't know how to do it but there are supposedly ways you can manually set the layer break that may get around this. Others may tell you how to do that. There is one thing you can do in the meantime. You can use DVDShrink to shrink down your VIDEO_TS contents to a new VIDEO_TS. Use a custom compression ratio and keep shrinking the VIDEO_TS down until you get a size ImgBurn is happy with. However, this will reduce the video quality, and it will vary depending on how much you shrink it. But, on an upscaling DVD, you won't notice it. And if you only have to shrink it like 1% or 5%, again, you won't notice too much of a quality dip.

From what you've described, the problem would be either 1.) the mini DVD-R's have somehow changed manufacturing process so they're not the same quality they used to be; it happens. It happened to me before. 2.) the Resident Evil image you have is bad 3.) your iHAS burner has gone bad. What to do? Well, you should try testing these things in a certain order. Try getting some Verbatim DataLifePlus/AZO DVD-R and see if they burn okay. That will test both #1 and #3 in the above list. I don't see why you have a particular desire to use mini DVD-R since they are so hard to find quality blanks. If the Verbatim (NOT the Life Series you find in stores. They're junk.) burn fine, then you know the problem is not with your burner or the image and with the mini DVD-R's you'd been using. If you still have a problem, then the problem is either with the image or the burner. Unfortunately, there's very little you can do to test the image itself. About all you can do at that point is replace the iHAS burner. If you still have a problem after that, the problem is most likely a corrupt image file.

Yeah, I wouldn't rely on CMC even if they do pass Write and Verify. There would probably be playback issues and longevity issues. I would think the CMC wouldn't last very long. I know I had some Ritek DVD+R DL I was testing out because I found them in an Office Depot store. They wrote fine, but, a year later, they weren't readable.

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.

The general rule of thumb is when you're dealing with multi-layer media, regardless of if it's DVD+/-R DL or BD-R/RE D/T/QL, Verbatim is the only consistent performance quality. So, Ritek will be more iffy. I'm surprised you got any kind of decent quality out of CMC DL media. I wasn't even aware CMC made BD-R DL media. Which will just cause me more worry whenever I should ever have to get some. I've never used any before, just Verbatim and TDK BD-RE DL.

Well, I can't explain why you got success before with the WH16NS40 and I can't say much about the WH14NS40, but the WH16NS40 absolutely does not properly write/Verify dual layer BD media. Fails Verify 9 times out of 10. I had multiple units of this drive and it did the same thing. And this behavior was verified by someone else on the forum. The only thing that seemed to work, and it wasn't always certain, was not to burn images with ImgBurn but to use the write on the fly method. So, it may have been the 1.03 firmware the entire time. Seems they borked that firmware like Pioneer is now constantly borking their firmware. And here I thought the 1.03 firmware only introduced a plug to keep people from copying discs. Looks like they screwed the performance of the firmware, too. Since you don't mind trying new drives as a possible solution, I'd recommend trying LG's WH16NS60. It doesn't have that problem that the WH16NS40 had and is now my go to BD drive. However, it is a bit more expensive since it's an UltraHD drive. And if you don't need that feature, you may not want to invest in it. I don't need that feature, but I invest in the drive because, well, it works. You're using Verbatim IMF BD media, which is the best out there, so I wouldn't change BD-R SL type. I'd not use the Ritek media at all as I know Ritek has certain playback issues with their BD on the PS3. Plus, Ritek has a higher failure and incompatibility rate than the Verbatim IMF media.

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.

Unless he wants the image files for a backup or to mount as a virtual drive. As for playback, unfortunately, the answer isn't as simple as yes or no. It depends on the player you put the disc in, the type of CD-R you use, and sometimes even which drive burns the CD.

I failed to notice that. That is why it didn't play. So, whatever created your Blu-Ray output appeared to have not actually created anything that plays. In your BDMV folder, is there a subfolder called STREAM? I THINK that's where BD Video is stored. At least, that was on the only BD Video I can remember ever navigating. I don't do BD Video creation too often, so I know very little about its functional structure versus what I know about DVD. Is there anything in STREAM? If so, how large are the contents?

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.

That could be probably one of two main things in your case. 1.) Whatever made the Blu-Ray video folder you imported may not have authored it correctly. 2.) Your log says you used a Ritek disc. Your Blu-Ray player may not like Ritek discs. They do have well known recognition issues with players. I know the PS3 doesn't like Ritek BD-R and doesn't play them properly. It does seem the job was detected as a Blu-Ray movie because the log says the appropriate settings were changed to reflect a Blu-Ray disc. If that's the case, try Verbatim BD-R SL/DL. Also, you used a BD-RE versus a BD-R. RE does have more compatibility issues with players versus BD-R. Try a WORM (Write Once Read Many) BD-R SL/DL. And don't try Verbatim BD-R SL. DL is quality, SL is cheap CMC Magnetics crap, which is even worse than Ritek. In the meantime, try this disc that doesn't play in someone else's Blu-Ray player. See what results you get.

No, that's probably my fault. I forgot about the different file system in Blu-Ray Video versus DVD Video. If you were following the DVD guide, it would probably say use ISO9660 + UDF instead of just UDF. Anyway, just select Yes to let ImgBurn make the default changes for you. ImgBurn is smart enough to detect if you're probably making a Blu-Ray/DVD Video and prompt the user to make any appropriate changes that are not set by the user/changed by the user.