dbminter

Actually, I just came back here to say the same thing myself. This ProShow can make an ISO, mount the ISO, add the VIDEO_TS folder from the virtual drive into a Build job in ImgBurn, write a new image, and burn it. If the disc still fails to play, then it's either ProShow making improper VIDEO_TS or it could be the manufacturer of your DVD+R DL. Although that 2nd explanation doesn't explain away why it doesn't play on a PC.

When you say you can't burn, you mean you can burn, right, it's just that the disc doesn't play? Try posting the log of a burn of a disc that doesn't play. I have an idea of what might be the problem. Although it wouldn't explain why it doesn't play on a PC. First, put one of these failed discs in a PC drive and open its contents in Windows/File Explorer. Is there a VIDEO_TS folder in the root directory? To get the log of a burn, in ImgBurn, under Help, ImgBurn Logs. The folder containing the logs opens. Open the log file, find the part of the log with a burn of one of these discs that doesn't play, and copy and paste the contents into a reply.

And this is the first time you've gotten an ISO from ProShow that was larger than a DVD-5 and had to go to a DVD+R DL? If so, I would guess ProShow is not making compliant ISO files for DVD-9.

No, I can't guarantee anything, unfortunately. I use a VanTech USB 3.0 enclosure with the LG WH16NS60 without problems to the VERBAT-IM BD-R made by Verbatim. So, that's what I'd recommend. My tower doesn't have half height bays, so I had to USB route since most slim models are trash. Even the one that came with mine, while so far no problems writing, is a super slow writer. Writes 2 to 3 times slower than half height drives. You may be tempted to get the cheaper LG WH16NS40. I wouldn't recommend it if you ever plan on writing DL BD-RE or BD-R. I've seen several reports here, backed up by my experience with BD-RE DL, that the NS40 will fail Verify 9 times out of 10 with DL BD media. Which the NS60 does not. But, if you never plan on writing DL BD media, the NS40 passed all other tests I threw at it. Again, can I guarantee switching drives will fix the issue? No. But, I can say you won't know for sure unless you try switching drives.

Well, you're using the good BD-R from Verbatim and not CMC Verbatm BD-R, so that's a start. That would generally mean there's probably a conflict between your burner's firmware and that kind of media. You could try and see if there's a firmware update for your burner, but there probably isn't. The only other solution is to try a different BD burner from another manufacturer or another model number and see if that helps. I had an ASUS BW-16D1H internal model, I believe. I don't remember if I used it long enough to try BD-R in because my first tests were abysmal with that drive. It constantly destroyed rewritable media! 8x Ritek DVD+RW and Verbatim 2x BD-RE non CMC. So, I sent the drive back for a replacement. That drive did the same thing so it was a firmware/hardware issue.

Well, I would THINK just powering off the device and powering it back on would be enough. But, I've never had a laptop, so I don't know how power cycles work on those.

If you want to be really safe should the device ever drop communication, power off the enclosure, power off the PC, restart the PC, and power back on the enclosure. This would ensure a complete wipe of everything in memory from ImgBurn/Windows/the device.

In future, if you encounter weird problems like that, try powering off the PC if the BD drive is internal or powering off the enclosure if it's external. Don't just reboot. A power cycle can clear out sometimes weird nagging things like that.

What country do you live in? I'm seeing more and more instances on this board of Verbatim BD-R being made by CMC Magnetics. The ones I keep getting from Amazon.com in the US are VERBAT-IM and still continue to be the "good" stuff. Anyway, I'd be wary of those CMC MAG discs, too. The nature of their media is you can go half way through a stack with "no problems," then encounter the entire rest useless. That's how cheap and unreliable CMC is. Unfortunately, CMC now OWNS Verbatim.

Well, actually, I don't know but I'm glad you got it sussed out.

From what I've seen elsewhere on this forum and in other forums, VLC can be a very problematic DVD player software. I don't use it. I use Media Player Classic - Home Cinema, so I can't help you there.

Hm, I've never encountered a case where a DVD works on a DVD player but NOT on a PC drive. The other way around, yes, we hear stories of that all the time. What PC software do you have that plays DVD's?

You keep mentioning trying to burn a file to create a DVD Video disc. That may be your problem. In order to get a DVD that plays on a DVD player, you have to have a VIDEO_TS folder. Is this ProShow Producer producing a VIDEO_TS folder, a file, or an ISO on its own you're trying to burn with ImgBurn? If you have a VIDEO_TS folder, the simplest way to do it is to use Build mode and add the VIDEO_TS folder to the job. ImgBurn will make all the necessary changes for DVD Video itself. Another thing that might help is post a log of one of these DVD Video disc images you burned that aren't playing on a DVD player. I have an idea that you may have a disc that works but the media manufacturer may be the reason it doesn't play in a DVD player. Under Help, choose ImgBurn Logs, open the log file, and copy and paste the necessary part of the log. Also, do you have PC software that can play DVD's? If so, try putting one of these discs that doesn't play in a DVD player into a PC drive and see if it plays on the software player.

Since you say it's AVCHD, I'm guessing you're trying to make a Blu-Ray Video Disc. In that case, you'd need BDMV and Certificate folders in the root directory of your image. If you're creating a DVD Video Disc, you'll need a VIDEO_TS folder. The reason it's not playing could be a wide variety of causes. The BDMV/VIDEO_TS may not be compliant and thus doesn't play. That would be on whatever software you used to create the BDMV folder contents. I don't know if BDMV burned to a DVD+R DL will even work. I know the other way around, VIDEO_TS to BD-R, doesn't; I tested that myself. You may need a BD-R to get this to play, but I THOUGHT if your BDMV fit on a DVD+R DL, you COULD burn it to a DVD+R DL and get it to play on a BR player.

I decided not to switch back from Elby just to give it a go and see what it's like. If there's an issue, I'll switch back. And, when the next Windows 10 is released, I'll be restoring down my 1909 installation image, updating it, and saving a new Windows 10 image. That will restore the I/O back to SPTI anyway, if I don't do it in the meantime.

I have relatively few posts on the Redfox and VSO forums as compared to here and the Reflect forums.

I knew SPTI allowed for "soft" locks. Meaning you couldn't eject the locked access drive with a Windows/File Explorer Eject context menu command, but I wasn't aware it didn't not fully lock the physical eject method. Yes, ever since I got a Dell XPS 8930 a year and a half ago, I've wondered how an optical drive can be set up in a RAID configuration. It still says RAID on the Elby I/O interface option, though. And, yes, I am the same dbminter on the AnyDVD forum. I think I use the same nick on the ConvertXToDVD forum, too. And Macrium Reflect forum.

Except when they introduce bugs into new versions.

I just tested my installation of 5.5.2.0 and, on my machine, it DOES fix the locking drive for exclusive access failing issue 5.5.1.0 introduced. So, you should test it on your end and make sure it now works after updating to 5.5.2.0.

There's a new update, 5.5.2.0, but it's change log is a little odd: Fix: Bug introduced in 5.5.1.0, ElbyCDIO did not work with Windows Server OS, Windows XP, Windows Vista It doesn't mention this specific issue we've encountered on Windows 10. So, it may still be present in this new version.

I created a CD sized DVD Video image with Build and then used Write to write that image to a Ritek 8x DVD+RW. Here's the log: I 11:13:12 Microsoft Windows 10 Core x64 Edition (10.0, Version 1909, Build 18363) I 11:13:12 Total Physical Memory: 16,579,480 KiB - Available: 8,686,440 KiB I 11:13:12 Initialising SPTI... I 11:13:12 Searching for SCSI / ATAPI devices... I 11:13:12 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (N:) (SCSI) I 11:13:12 -> Drive 2 - Info: HL-DT-ST BD-RE BU40N A102-01 (K:) (RAID) I 11:13:12 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (L:) (SCSI) I 11:13:13 -> Drive 4 - Info: HL-DT-ST BD-RE WH16NS60 1.02 (R:) (USB 3.0) I 11:13:13 -> Drive 5 - Info: ELBY CLONEDRIVE 1.4 (Q:) (SCSI) I 11:13:13 Found 3 BD-ROM/HD DVD-ROMs and 2 BD-RE XLs! W 11:13:25 I/O Interface has been changed! I 11:13:25 Shutting down SPTI... I 11:13:25 Initialising ElbyCDIO... I 11:13:26 ELBYCDIO.DLL - Elaborate Bytes CDRTools - ElbyCDIO DLL - Version 6.1.9.2 I 11:13:26 ELBYCDIO.SYS - CDRTools - ElbyCD Windows x64 I/O driver - Version 6.1.3.0 I 11:13:26 Searching for SCSI / ATAPI devices... I 11:13:26 -> Drive 1 - Info: HL-DT-ST BD-RE BU40N A102-01 (K:) (RAID) I 11:13:26 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (L:) (SCSI) I 11:13:26 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (N:) (SCSI) I 11:13:26 -> Drive 4 - Info: ELBY CLONEDRIVE 1.4 (Q:) (SCSI) I 11:13:26 -> Drive 5 - Info: HL-DT-ST BD-RE WH16NS60 1.02 (R:) (USB) I 11:13:26 Found 3 BD-ROM/HD DVD-ROMs and 2 BD-RE XLs! I 11:13:42 Operation Started! I 11:13:42 Building Image Tree... I 11:13:44 Corrected file system selection for DVD Video disc. I 11:13:44 Corrected UDF revision selection for DVD Video disc. I 11:13:44 Calculating Totals... I 11:13:44 Preparing Image... I 11:13:44 Contents: 7 Files, 2 Folders I 11:13:44 Content Type: DVD Video I 11:13:44 Data Type: MODE1/2048 I 11:13:44 File System(s): ISO9660, UDF (1.02) I 11:13:44 Volume Label: [Not Configured] I 11:13:44 IFO/BUP 32K Padding: Enabled I 11:13:44 Region Code: 1, 2, 3, 4, 5, 6, 8 I 11:13:44 TV System: NTSC I 11:13:44 Size: 40,785,920 bytes I 11:13:44 Sectors: 19,915 I 11:13:44 Image Size: 41,418,752 bytes I 11:13:44 Image Sectors: 20,224 I 11:13:44 Operation Successfully Completed! - Duration: 00:00:01 I 11:13:45 Operation Started! I 11:13:45 Building Image Tree... I 11:13:47 Calculating Totals... I 11:13:47 Preparing Image... I 11:13:47 Contents: 7 Files, 2 Folders I 11:13:47 Content Type: DVD Video I 11:13:47 Data Type: MODE1/2048 I 11:13:47 File System(s): ISO9660, UDF (1.02) I 11:13:47 IFO/BUP 32K Padding: Enabled I 11:13:47 Region Code: 1, 2, 3, 4, 5, 6, 8 I 11:13:47 TV System: NTSC I 11:13:47 Size: 40,785,920 bytes I 11:13:47 Sectors: 19,915 I 11:13:47 Image Size: 41,418,752 bytes I 11:13:47 Image Sectors: 20,224 I 11:13:48 Operation Successfully Completed! - Duration: 00:00:02 I 11:13:48 Operation Started! I 11:13:48 Image Contents: 7 Files, 2 Folders I 11:13:48 Image Sectors: 20,224 (MODE1/2048) I 11:13:48 Image Size: 41,418,752 bytes I 11:13:48 Image Single Layer Profile: DVD-R/RW (Media Capacity: 2,297,888) I 11:13:48 Image Volume Set Identifier: 505B59B600004EE0 I 11:13:48 Image Implementation Identifier: ImgBurn I 11:13:48 Image File System(s): ISO9660, UDF (1.02) I 11:13:48 Destination Free Space: 874,760,036,352 Bytes (854,257,848.00 KiB) (834,236.18 MiB) (814.68 GiB) I 11:13:48 Destination File System: NTFS I 11:13:48 File Splitting: 4 GiB I 11:13:49 Writing Image... I 11:13:49 Operation Successfully Completed! - Duration: 00:00:01 I 11:13:49 Average Write Rate: 40,448 KiB/s (29.9x) - Maximum Write Rate: 40,448 KiB/s (29.9x) I 11:14:33 Operation Started! I 11:14:34 Source File Sectors: 20,224 (MODE1/2048) I 11:14:34 Source File Size: 41,418,752 bytes I 11:14:34 Source File Volume Set Identifier: 505B59B600004EE0 I 11:14:34 Source File Implementation Identifier: ImgBurn I 11:14:34 Source File File System(s): ISO9660, UDF (1.02) I 11:14:34 Destination Device: [0:2:0] HL-DT-ST BD-RE BU40N A102 (K:) (RAID) I 11:14:34 Destination Media Type: DVD+RW (Disc ID: RICOHJPN-W21-01) I 11:14:34 Destination Media Supported Write Speeds: 3.3x, 6x, 8x I 11:14:34 Destination Media Sectors: 2,295,104 I 11:14:34 Write Mode: DVD I 11:14:34 Write Type: DAO I 11:14:34 Write Speed: MAX I 11:14:34 Link Size: Auto I 11:14:34 Lock Volume: Yes I 11:14:34 Test Mode: No I 11:14:34 OPC: No I 11:14:34 BURN-Proof: Enabled E 11:14:47 Failed to lock drive for exclusive access. E 11:14:47 Reason: The system cannot find the file specified. E 11:14:50 Operation Aborted! - Duration: 00:00:13 I 11:14:50 Average Write Rate: N/A - Maximum Write Rate: N/A W 11:14:58 I/O Interface has been changed! I 11:14:58 Shutting down ElbyCDIO... I 11:14:58 Initialising SPTI... I 11:14:58 Searching for SCSI / ATAPI devices... I 11:14:58 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (N:) (SCSI) I 11:14:58 -> Drive 2 - Info: HL-DT-ST BD-RE BU40N A102-01 (K:) (RAID) I 11:14:58 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (L:) (SCSI) I 11:14:59 -> Drive 4 - Info: HL-DT-ST BD-RE WH16NS60 1.02 (R:) (USB 3.0) I 11:14:59 -> Drive 5 - Info: ELBY CLONEDRIVE 1.4 (Q:) (SCSI) I 11:14:59 Found 3 BD-ROM/HD DVD-ROMs and 2 BD-RE XLs! I'm not entirely sure what the extra log entries are for, but it's all there somewhere. Both the image creation and the attempted write. I removed some identifying log lines, though.

I can verify it's a bug in the Elby driver. I got the same result. Switching back to SPTI still worked.

This should be what you're looking for:

Where/when do you see this error message you described in ImgBurn? I'll see if I can replicate the issue on my end.

I use the apparent default, SPTI. It always worked for me, so I never had a need or desire to try anything else.