dbminter

The way creating custom .CUE files is now in ImgBurn is a little limited. You HAVE to write these .CUE files to CD's. You cannot write to image files or to any other disc format besides CD-R/RW. So, if you wanted to create an image file of an Audio CD created by an ImgBurn .CUE, you have to burn to CD and only CD (Doesn't work to other faster disc types.) and then read the CD to an image file.

As I said, I'd avoid using those Ricoh DL media all together. The only consistent quality DVD+R DL are Verbatim's MKM media. Low quality media like Ricoh and CMC cause nearly half of the problems seen on this board. It's not a miracle that changing to quality media resolves a good portion of people's problems. It's not a guaranteed solution, of course, but it's what I generally look at in logs of failures. When you get the Verbatim MKM's, look for the DataLife Plus series. NOT the Life series. DataLife Plus is MKM. Life series is cheap ass CMC media. DataLife Plus you will generally only find in online stores, like where I get mine from: Amazon.com. Brick and mortar stores will generally only carry the Life series, which, as I said, are CMC junk.

Hate to burst your bubble, but ASUS no longer manufacturers my USB BD drive. And do NOT get their latest internal burner, the BW-16D1HT! I tried two of them and both had the same fatal flaw, so it's a design problem with the drive: they destroy rewritable media! Ritek 8x DVD+RW and Verbatim BD-RE DL are all borked and unusable after the ASUS writes to them. However, IF you can find one, it's the BW-12D1S-U. Now, ASUS DOES make this: https://www.amazon.com/dp/B071VP89X1/ref=sr_ob_2?ie=UTF8&qid=1509752901&sr=8-2 The BW-16D1X-U listed above MAY be the internal ASUS junk model I had in an external enclosure. The two drives have relatively similar drive strings in their names, so I have a feeling this USB drive is just their junk internal BD burner in a USB enclosure. However, I haven't tried BD-R DL in my ASUS, only BD-RE DL. You seem to want my drive for your BD-R DL issue I replied to in another thread. So, I can't say if that particular ASUS will work for your need or not. Sorry.

Since you seem to be new at burning BD-R DL's, I'm guessing you've never used this drive before to burn those discs. It's probably just a really rotten drive at burning DL media. Like LG's BD drives. You seem to be getting these errors at the layer change, and, as you seem to indicate, there are playback errors are at the layer change, too. You're using quality BD blanks, so it's probably just a case of your drive not liking them. Your drive is probably older than the Verbatim blank architecture and there's probably not a firmware update for that media. Try updating the firmware. Right click on the drop down list of the drive in Write mode and choose the firmware update check option. Most likely, your fix is probably to try a new drive. Try a Pioneer one, the 209 or 2209. I've never used BD-R DL media, but I do use Verbatim BD-RE DL media. I have two BD drives, an LG and the Pioneer. The Pioneer is the only one that writes properly to these BD-RE DL's. And guess what generally happens in the LG? Failure of Verify at the layer change. If a DL media burn/Verify is going to fail, it will almost always fail there, at the layer change.

I may have to someday. It's been like almost 15 years since DVDShrink was last updated before its developer moved it exclusively to a Nero version application. I have to guess, at some point, the software will simply stop loading on modern PC's one day. I worry that DVDReMake will do likewise as it's been almost 10 years since that was last updated.

Also, you will probably not encounter a lot of Blu-Ray movie discs with contents on them that will fit on a DVD-9. Especially a DVD-5. Could one use CloneBD to shrink a BDMV contents to a size that fits on DVD-9? Does that software even compress BDMV, even from, say, a BD-50 to a BD-25?

Yeah, I knew that was what he was saying. I was just guessing that since it didn't work for VIDEO_TS DVD-9 contents put on a BD-RE, it wouldn't work the other way, too. Now I know it doesn't work both ways. I'll probably forget it in the future, though.

And your Blu-Ray player probably won't play the BDMV folder off of the DVD-5/DVD-9 you burn it to if you just insert the disc and expect it to automatically start playing. Your player might load the contents if its navigation software supports reading that file type from a disc. However, I do know you can't take a VIDEO_TS and put it on a BD disc and get a Sony Playstation 3 to play it. PS 4 probably doesn't do it either. I'd suspect it's probably the same across all players since Sony helped design Blu-Ray, didn't they? So, you probably can't pop in the DVD with a BDMV folder on it and expect the player to recognize the inserted disc and play it as a Blu-Ray movie. However, your player's navigator might support loading it as a "file" from the disc. What you can do is use something VSO Blu-Ray Converter or maybe ConvertXToHD/DVD to convert the BDMV contents to a DVD. Of course, you'll lose all menus and it will be standard DVD definition instead of Blu-Ray high definition. But that should, at least, "guarantee" DVD playback of a Blu-Ray BDMV contents.

Yeah, I was just going to say, by uploading, do you mean it's taking an hour to burn the image to a disc? If so, that's a variety of possibilities and we would need a log of a burn/write operation. If you're uploading the file to Google Drive or OneDrive, then ImgBurn has nothing to do with that. Or are you trying to read a DVD from a drive and copy it to your hard drive. You could mean "uploading" the DVD contents to hard drive, but that's a copy/read operation. Not an upload.

Yeah, I wasn't sure what you were saying was happening, either.

Define unreadable. It's a Blu-Ray movie that won't play in a Blu-Ray player? Or, you insert the BD into a PC drive and there are no contents when you navigate to the drive in Windows/File Explorer? Try performing a Read operation on this disc. What does ImgBurn return? Was anything actually written to the disc?

Most likely mechanical failure. I can't see any firmware update fixing a problem like that.

Yeah, I'd have to say the eject issue was some kind of hardware failure, versus intentional. It was just a theory that it may have done that with discs it can't read. It shouldn't do that, though, because without an error indication from the drive, you can't tell if this is an intended feature or a hardware failure. Pioneer's have a similar issue. After about 7 to 9 months, the eject function doesn't work on the first attempt. Neither pressing the eject button or a manual software eject command from ImgBurn will work the first time, 1 in 10 times. A second attempt works, and it seems that all eject commands issued by ImgBurn as part of a Write operation, before a Verify, work. It's weird.

Hm, can't reproduce it now. Weird.

Can't say about the auto eject issue. That seems to be a drive problem. Or it could be by design. It may have been made to automatically eject discs it cannot read. However, you said later on you seemed to have had a problem where the RW's were bad. And a Full Erase fixed the issue. So, maybe fully erasing them and getting a successful burn to them will fix the Samsung issue? Sometimes, full erases of RW media can fix an issue. The latest firmware for the Pioneer 2209 BD drive borks writing to Ritek 8x DVD+RW. They will always fail Verify, whereas the previous firmware did not do that. If you fully erase the media the 2209 under that firmware wrote in another drive and burn again in that different drive, the media is usable again. Years ago, I think on Windows 7, the installation media that came with my new PC was on a DVD-9. And it will definitely fit on a DVD+R DL, although you're wasting about half the available space on the disc. But, it is a way to go in the future if you wanted to do that.

Well, I don't know what abgx is. And all my attempts in the past to overburn single layer media always failed. So, I'd say they'd always fail for me to attempt to overburn DVD+R DL. I just always said overburning never worked right. Beyond that, I'm out of advice.

See this post for the initial start of this "bug" which I can reproduce. http://forum.imgburn.com/index.php?/topic/24759-imgburn-created-2-folders-in-the-same-directory-with-the-same-name/ I don't think this did this before I updated to Windows 10 Fall Creators Update. After updating, it seems to have started. Although, it could always have been there and I never encountered a case where I came across it before. However, I believe I have done this before the update successfully. What happens is if you create a folder in an .ibb job (It does not work if you drag and drop files/folders into the root directory.) and drag and drop files and/or folders from a disc in an optical drive into that folder, when ImgBurn creates the image file, the target folder is renamed Temporary Burn Folder in the image. If the contents are dragged and dropped into the root directory, they're added correctly. If you add contents from an HDD, it does NOT rename the folder Temporary Burn Folder. Only on optical discs as the source. I've tested this several times and it always does this after my update to Fall Creators Update. I shut down the PC and powered off in case it was something with the drive gone wonky. But, I've been able to reproduce it each time. The easiest way to test this, I've found, is to create a folder called Test in the root directory of an .ibb job file. Insert a disc into an optical drive, preferably with small files and/or folders, and add a few small files and folders to Test. Build the image and mount it/burn it, and check the root directory. In every case I've done this, Test becomes renamed Temporary Burn Folder. And if there are multiple folders in the root directory with contents from multiple optical drives, EACH folder is rename Temporary Burn Folder. Although, as I said before, I've NO idea how this can even possibly be. However, in my quoted post from earlier, the folders were named Temporary Burn Folders in the .ibb. My repeated tests saving these jobs to .ibb, the .ibb no longer ever has the folders named as Temporary Burn Folder. They're always named what they were named when I created the folders and named them in the sub folder. Can someone test this for me and make sure it is a reproducible bug on Fall Creators Update? Or is it just on my setup? Thanks!

I can't explain this one, but it was present in the .ibb file I saved. So, it doesn't appear to be some kind of Windows Explorer reading the files wrong from disc. I have two folders named Temporary Burn Folder in a root directory called Disc on a BD-R I burned. These folders are supposed to be named 1 Of 2 and 2 Of 2. I reloaded the saved.ibb file and the two folders are both named Temporary Burn Folder in the .ibb. I can't explain this. How can ImgBurn save the same folder name to two different folders? Also, how can Windows Explorer navigate the contents when there are 2 folders with the same name? I've checked the contents on the BD-R I burned and both folders are navigable and contains no corrupted contents. I have to admit. I'm stumped on this one.

Did you actually try a burn on the USB drive or just perform a Verify on the two discs burned in the LiteOn? If the problem is the LiteOn burner not correctly burning, then the USB will fail to Verify the discs, too. If the USB burns but fails Verify, then there's something else up somewhere. And it's probably not disc related. Before burning in the USB, try using a disc that didn't burn in the LiteOn at all. If the LiteOn has gone bad, then the last burns to those 2 DVD+RW might have irreparably damaged the media. If you don't have other media, then I'd recommend a Full Erase of one of those 2 DVD+RW in the USB drive before burning the image, just to be better assured. As for the reason, it could be because the image is burning towards the edge of the disc. I believe the Fall Creators Update ISO is nearly the size of a DVD disc. (I burned mine to BD-RE because I have a BD drive and BD-RE writes faster than 8x DVD+RW. So, I'm not entirely sure about the size thing.) As you approach the outer edge of media, you increase the likelihood of errors occurring.

Yeah, that's the nature of the beast. Sometimes, you get correct burns even when there's a problem with the drive. Of course, it could be just a series of bad discs in the batch, too. I'd see if you get bad burns 3 times. My general mode of operation is I try 3 times to see if it's the discs before burning a 4th time in my 2nd drive, the Pioneer. If I get 3 bad burns in a row and the Pioneer burns it fine, then I would probably replace my LG drive, the main burner I use for almost everything.

Yeah, I agree with LUK. Splitting the image wouldn't have made any difference. It may have been just a bad blank in the box, like you said. It happens. I came across a bad DVD+R DL recently. My 2nd attempt to burn it and all subsequent DVD+R DL have burned fine. BTW, as a general rule of thumb, I try burning a failed image burn 3 times in a row to see if it's just a bad blank disc or not. After 3 discs, I'm relatively sure it's probably not the discs, unless it's a brand new stack/manufacture. After 3 fails in a row, I'm more inclined to blame the drive for the problem. Or could be a problem with the image. It happens, but rarely. As for the Pioneer BD I have, mine is the BDR-209M, aka the BDR-2209. The only difference between mine and the BDR-209DBK is mine supports writing to BD XL media and M-Disc media. If you never intend on writing to either of these types of discs, you can save a little money and go for the BDR-209. I've never heard of the BDR-S09XLT, so, I looked it up. It seems to be an older Pioneer model. I've heard of the BDR-S08XLT, but that's older than the 2209. It seems the XLT was an older generation of the 2209. Pioneer's website only lists they manufacture the 209 models. There are no XLT's anymore. You can still find XLT's online, but most of the prices I've seen are near $200, except for $90 from Groove Inc. However, the 2209 will also run you $90, so you're better off buying the newer drive. It's firmware was last updated a year ago whereas the BDR-S08XLT firmware was last updated 4 years ago. Now, there is a newer Pioneer BD model out there. It's a 4K Blu-Ray drive. However, there's no firmware update for it yet so it's so new it may be TOO new to recommend. Plus, it's nearly $25 more than the 2209. If you never intend on viewing 4K Blu-Ray, then there's probably no real need to get that one.

It's probably the LG BH16NS40's fault. That's an older model of LG's BD drive, I think. Mine was like last updated 2 years ago and it's the WH16NS40, which is the current model. However, I think it's just that LG BD drives are terrible at writing DL media. I've never written a BD-R DL with this drive, but I have tried several BD-RE DL's. I used Verbatim's quality ones, too, and tried both writing images and writing the discs as giant floppies formatted in Windows Explorer. The image burns fail Verifies more often than pass when my Pioneer writes the same images to the same discs fine. And the files written to the formatted BD-RE DL completed writes, but the file contents were corrupt on the discs! So, I think the bottom line is though LG BD drives support writing to BD DL media, it doesn't do it anywhere near well. I don't use my LG for writing BD-RE DL. Just my Pioneer. Thus, I'd try replacing your older LG with a Pioneer BD drive. Your LG BD seems to be older than mine, so its firmware and hardware would definitely, most likely, have more trouble burning any BD media type that was created after the drive was made/the firmware was last updated for it. BTW, I also think when my burns failed to BD-RE DL, it failed at the layer change. With multiple layer media, any failure you're going to encounter, burn or Verify, will generally occur around the layer change. Either just before, at, or just after the layer change.

Technically, every disc is a data disc. It's how the hardware recognizes the format of the data that determines whether it will play it. Stick any Blu-Ray movie disc in a PC BD drive and open it in Windows/File Explorer, and you'll see a file and folder structure. Actually, I think audio CD's aren't data discs, now that I consider it. If you insert a music CD into a PC drive, I think Windows/File Explorer will only recognize it as an audio CD. You can create multi-track (I think it's a separate track.) for data on a music CD that Windows/File Explorer will recognize as data. But, traditional audio CD's played on a stand alone audio CD player aren't data discs because they were created like 35 years ago. As LUK said, the folder (I keep forgetting its name.) that stores the actual video streams, may not be authored correctly. Or the job settings that created the image were not correct for BD Video. Could also be that your Blu-Ray player doesn't like that particular BD disc brand you burned to. Is this your first time burning BD Video or have you done it before and it's suddenly started making discs that don't play?

If ImgBurn completed without errors and you're getting read errors on DVD players, you probably used a cheap DVD+R DL. Since you said Verbatim, you might have used a Life Series bought in a brick and mortar store. Those will be cheap CMC discs. Unless you got the DataLifePlus series, which you can generally only find online, they probably won't be the good MKM we recommend. Post the log of a burn. Access the log under Help and copy and paste a relevant log. We'll know a little bit more from that. If you can't get a log for one of these burns, insert one of these discs that isn't playing correctly into a PC drive, open ImgBurn in Write mode, and look for an MID field in the pane of information on the right hand side. Does the MID string say MKM or CMC? Or what does it say? PC drives are generally more forgiving than a stand alone DVD player. That's probably why it works on a PC drive but not a stand alone DVD player. Plus, when you say you get read errors, what do you mean by that? Any specific error messages? Will the discs load in a stand alone DVD player and just play back with choppiness/skips/pauses/pops in the audio? It could be your burner not liking that kind of disc and is not burning them well, even though it completed without errors. If that's case, you'll need to either get different discs, which only the MKM Verbatim DVD+R DL are any good, switching isn't really an option, or get a different burner.

Yeah, um, image files have files and folder inside of them.