dbminter

I do feel the need to pass this along. It appeared to be a fluke, but it did happen, so it's worth noting. I had a DVD-R of home movies converted to DVD Video. I know this disc was playable because after I created it just the other day, I read it to an image file with ImgBurn, loaded the image file in DVDShrink, and wrote a new VIDEO_TS output to test it. It passed. Sunday, I put the same disc back in and copied the VIDEO_TS folder in File Explorer, but it would not play or load in anything, even DVDShrink. I put the disc back in today and read it back into an image that did read properly in DVDShrink. So, I haven't quite figured it out yet. It may have just been a fluke. It may have been a issue with the USB enclosure. On the LG WH16NS60, you have to sometimes turn off the enclosures and turn them back on before Windows will recognize data from DVD's. Some kind of Windows bug. A similar one may have happened in this case. Plus, I've been unable to reproduce the issue. Sunday, I copied another DVD-R of home movies the same way without issue just before the one I described above.

Was it ONLY those two files? If it was only those two, I would concur that it was user "error" and those 2 files alone got name changes in the DLE.

No, the Read speeds are set on the media regardless of the maximum write speed used to burn a disc.

A write of a full BD-R should take about 15 to 20 minutes at 12x and a read operation is faster than a write.

That sounds a bit slow for a BD-R. Unless it was a DL BD disc.

Being on BD-R shouldn't matter as to what app opens the files. Unless the files on the BD-R do have a different extension and you were asked what to open these "new" file types with. And your standalone player not showing the files also makes me think the files have a different extension on them on BD-R. One way to check and make sure is to open a Command Prompt and do a DIR on the BD-R drive contents to make sure the files still have their proper extension on them.

Oh, that explains why the extensions were missing. What this doesn't explain is how the files not a BD-R can play in VLC when you double click on them but the files on the BD-R do not. That would be almost as if the .MKV extension WERE missing from the files on the BD-R.

I'm not familiar with that model. I have used the WH16NS40 and NS60 before. I used the NS60 for years. I never had such issues. Firmware probably wouldn't make a difference in a case like this.

A sector by sector read approach, as ImgBurn would do, would be faster than the somewhat brute force method that File Explorer does. What BD drive are you using, BTW? The locked up responses sound more like hardware inconsistencies, which would be down to the drive. For instance, it rarely takes more than 10 seconds for a folder's contents on a BD-R to be recognized on my system in File Explorer.

I have tended to notice varying degrees of response times for BD-R's. For instance, writing the LeadIn for a BD-R in ImgBurn can take anywhere from 30 seconds to 3 minutes and 30 seconds. There appears to be no rhyme or reason. Next time you think you need to kill the process, wait 5 minutes first just to be sure. 5 minutes is more than enough time.

Well, that question doesn't really have a straight forward answer. It depends on what kind of BD-R you burned. If it's a data BD-R, I would guess the best metrics would be to try and perform a Read operation on it. If the Read operation completes, then the disc is probably okay. You could also check the Graphs ImgBurn produced for the PIE and PIO results, but I know next to nothing about those as I don't bother with that data. If it's a BD Video, a Read test is another good metric, but you won't really know without performing a scan test in a BD player. You will need to perform a forward scan in the player at a speed that is not too slow but also not too fast so that any bad data would be skipped over. And that isn't a standardized value as BD players each have different levels of forward scan speeds. Define "flakey" randomness of reliability. Are you getting read errors in Windows? Slow downs in read and then faster reads?

Is that Hide extensions for known file types a File Explorer option the user can set? I think I disabled it some time ago.

I would be willing to guess even though it's a PC game, the reason for failing is the same: mixed mode of data and audio tracks.

If I had to hazard a guess, it's a Playstation 1 game doing this. If it is, you've encountered one of the PS1 discs that ImgBurn cannot read with your hardware. There are certain PS1 games with certain hardware that ImgBurn can't read. What I've found is for those discs, I use Alcohol 120% to read them in.

I've no idea why you have VLC icons associated with those files in the top screenshot. They are not standard extensions of audio or video containers. The screenshot at the bottom is what you should always be seeing. Unless those files actually have the extension of .MKV after them. So, the top file is actually called file.2000.MKV. That would explain why the top screenshot says they are MKV files. Why the file extensions aren't visible in the top screenshot, I couldn't say. And why the .MKV extension would not be present on the BD-R also has no explanation. There are no settings that would cause a file extension not to be saved on an ImgBurn burned disc and no settings to rename files unless the file names exceed 256 characters, based on the file system setting you choose. It COULD be "fixed" if you selected the UDF 2.60 File System, but that is pure speculation. Particularly without knowing what File System you originally burned the BD-R with.

No, ImgBurn would not have made any changes to file extensions. If they were .MKV files, ImgBurn wouldn't make random and apparently arbitrary extension name changes like .2000 and .1997_mpeg4. Given that, I can't think why ANYTHING would do that. If this BD-R was burned recently, the ImgBurn.log file might still contain the necessary info from that write. Under Help, choose ImgBurn logs and open the .LOG file from the folder that opens. Check the log file and see if there's any results from this BD-R burn in question.

I did find one drawback. Like with the LG WH16NS60, 16x Verbatim BD-R only write at 12x max. Now, 12x was the maximum set write speed. Actual write speeds may get to 16x, but I doubt it. This BD-R I wrote didn't even get to 10x because it was less than half capacity. Now, this isn't the same as a BD Video disc test, but what I did was I had 2 DVD+R DL's of DVD Video of some home movies. I copied the VIDEO_TS folders of both discs to a temporary location and burned them to a BD-R. I then used DVDShrink to read back in the VIDEO_TS contents from the BD-R and write new VIDEO_TS outputs. No visible errors and no write abends. Write operations completed okay.

I did find one drawback. Like with the LG WH16NS60, 16x Verbatim BD-R only write at 12x max. Now, 12x was the maximum set write speed. Actual write speeds may get to 16x, but I doubt it. This BD-R I wrote didn't even get to 10x because it was less than half capacity. Now, this isn't the same as a BD Video disc test, but what I did was I had 2 DVD+R DL's of DVD Video of some home movies. I copied the VIDEO_TS folders of both discs to a temporary location and burned them to a BD-R. I then used DVDShrink to read back in the VIDEO_TS contents from the BD-R and write new VIDEO_TS outputs. No visible errors and no write abends. Write operations completed okay.

No to both. Actually, I've never burned a single BD-R DL before. I've burned BD-RE DL's in the past, but never the WORM variety.

You can't span discs in ImgBurn. It only burns one project to one disc at a time. As for the non skipped part text in black, for whatever reason, those files were not included in the image creation. Why, I couldn't say. Could have something to do with the project settings or the files could be locked by the system. As for the text in red, I'm not familiar with the WUModels folder, but that is definitely being locked by Windows for whatever reason and thus it cannot be accessed. The Recycle Bin files and System Volume Information are also folders that cannot normally be accessed by file access means. That's why access was denied for them. For instance, if System Volume Information is visible in File Explorer, if you tried to open the folder, you'd get an access denied error from Windows.

Pioneer's used to be great. For several years, they were my go to DVD drives. You probably just never encountered the deal killer: 8x DVD+RW writes. You need a USB 3.0 enclosure to properly use a BD drive in. And I've only ever encountered 2 USB 3.0 enclosure models out there. The one made by VanTec and the one made by Other World Computing. VanTec's model is a little more difficult to put drives into. VanTec's 2nd generation model had a flaw where you could not update the firmware of LG's WH16NS60's in them. The OWC one has a flaw with WH16NS60's. If you power off the enclosure and power it back on, Windows will NOT recognize the drive until you restart Windows. Pioneer and ASUS drives do not do this. Don't know about the WH16NS40, since you can't get the NS60 anymore.

Playback test of DVD Video of Imation Ritek RITEK-008-00 8x DVD+RW: Passed.

Playback test of DVD Video of Imation Ritek RITEK-008-00 8x DVD+RW: Passed.

Post an ImgBurn log of a failed burn. I am willing to bet the problem is you're using CMC Verbatim Life Series DVD+R DL, which are junk and fail all the time. Particularly if you have failed burns all the time. I've been burning double layer DVD's since like 2009 and only 1 ever failed on me that wasn't the fault of a drive that needed replacing because it had died. But, I've used Verbatim DataLife Plus/AZO DVD+R DL, the only compatible kind of double layer DVD media, 99% of the time. Admittedly, any burner application actually crashing at the layer change is a new one on me. I've never seen ImgBurn crash during any write to any media. Of course, it depends on your definition of "crash." It might have returned an error message and stopped burning, but that's not the application "crashing."

Skip Pioneer's. Pioneer always borks their firmware and have done so for the past decade. The 213 is their latest model, but it has several problems. I'd recommend ASUS's BD burner, the BW-16D1HT and put it in a USB enclosure. If you want a BD burner, the LG WH16NS40 is really the only other option. The NS60 worked well, but it's not available anymore. I haven't used the NS40 is several years, but it did have some flaws.