dbminter

The only thing I know from the questions you asked is it is 12v. I have tried 2 different enclosures with different results. One is the Vantec NST-536S3-BK NexStar DX model here: https://www.amazon.com/gp/product/B01MRUN0HQ/ref=oh_aui_detailpage_o08_s01?ie=UTF8&psc=1 and the other is just called an Other World Computing Mercury Pro one here: https://www.amazon.com/gp/product/B06XRCCV44/ref=oh_aui_detailpage_o05_s00?ie=UTF8&psc=1 The Vantec was working fine initially on 2 different Dell XPS models, but now BD-R was failing nearly every time. The Mercury Pro one does better except for it not detecting some things being inserted like I said. And the Mercury Pro needs its USB cable removed and reinserted now every time the power is turned off to the drive before Windows recognizes the drive. The problem with the Mercury Pro is the power supplies don't seem to be very good. The first one I had stopped sending power to the enclosure after 2 months. OWC sent me a replacement for it, though. It could be the Pioneer being in the Vantec that is problematic. It does seem to work better in the Mercury Pro. Or it could be the Vantec has gone bad but given I'm also having some iffy results now on the Mercury Pro with my LG BD burner, I'm not entirely sure. I didn't have much problems before on my Dell XPS 8700 PC. It's on this Dell XPS 8930 that I've begun having issues. And you need enclosures for that model because Dell removed half height bays from the towers.

Well, as for direct DTS input, I wouldn't know, but I'd think if you converted the DTS to FLAC, you'd have the same audio details without loss and wouldn't have to worry if it's 44.1k 16 bit. You'd have to install the filters for FLAC, but I use FLAC all the time because it's lossless. Even when I have an MP3 that won't import, I convert it to FLAC, even though I'm not gaining anything above the source MP3 attributes.

I do prefer DVD+RW over DVD-RW but DVD-R to DVD+R. DVD-R is slightly larger and while it doesn't matter with modern players, DVD-R was more universally accepted in players. Once DVD+R became an accepted standard, it was more universally adopted by manufacturers. DVD+RW has faster write and erase speeds and the LeadIn writing doesn't take as long. And, at first, BD didn't win because there was another format war with HD-DVD!

I would be curious to see proof of CD+R because it never existed. CD-R and CD-ROM were all there were, at first. Then, after DVD-R, DVD-ROM, and DVD-RAM came out, a group of companies decided they wanted in on the profit and created their own standard: DVD+R and DVD+RW. Just to add more confusion and restart the format wars.

I know in the States, I used to find them on Amazon.com, but I don't think they're available there anymore. Now, I think you can only get the DataLife Plus Verbatim CD-R from the Verbatim web store.

I'm just guessing, but I think the OP is thinking of layer change versus layer break. It sounds like he wants a specific file to span between Layer 0 and Layer 1 on the BD-R/E DL.

So, it looks like he'll have to convert the DTS to FLAC (For lossless from the source.) because he can't seem to get his source files to input. That's what I have to do whenever ImgBurn encounters a file it won't convert.

So, would any of those filter packs in the Guide help him here at all?

Hm, I've never heard of a .DTS file, so I don't know if anything can convert them at all. And, I don't see DTS as a file type of filter you can install from the Guide here: So, that's about the extent of my advice, sorry. You could try this: https://www.media.io/convert/dts-to-dts.html Of course, there are problems with online converters. The file may not transfer correctly and you'll end up with a file that is corrupt. But, it appears to be free and supports converting DTS to many file formats like MP3 and FLAC.

You probably just need to install the proper filters for ImgBurn to create a CD from. What file type are the source files? MP3? FLAC? etc. Depending on the file type, you may need specific filters for a particular file type. If you can't get that work, what might work is converting the files from one type to another, even if it's just from MP3 to MP3, the same file type, etc. Not all files are created equal and not always compliant with their specs. What happens when I have a file I can't get ImgBurn to make an audio CD out of, converting the file to another file type generally works. There are all kinds of freeware software converters out there.

Something is wrong, somewhere, but it's so random I can't get a bead on it. It has something to do with semaphore time outs, but they appear to be happening randomly. Regardless of the enclosure used, although the Other World Computing one is doing better. It just doesn't recognize the drive has been inserted until the cable is removed/reinserted. Just now, though, an attempted write to a DVD+RW sat for more than 2 minutes at writing the lead in. The drive did nothing but blink, but that was because it was a blank, formatted disc with nothing ever having been written to it before. Blank rewritable media that have been formatted seem to do this on ALL drives I've ever tested. So, the WriteIn never started. Had to power cycle the device, after which I got a semaphore timeout error. BUT, is that BECAUSE I powered off the drive? Or had it already timed out before I was forced to cycle the power?

My guess is all 3 failures are because they're listed as CMC MAG media. The CD-RW and DVD-RW failed to fully erase and the DVD-R burned but failed to Verify. Since all those media are said to be CMC MAG, your failed attempts to erase/write to CD-RW and DVD-RW are probably because they're cheap discs. And the reason you Verify failed is probably because of the same thing. Try something other than cheap discs.

Yes, I see it. Where it says Please Select A File, choose the button on the right end. Then, select the yellow button with the magnifying glass in the upper right. Add the image files, I'm guessing one at a time, unless they're all in the same folder. Then, use the Write button which is located to the far right next to Remaining Copies. I've never used this feature, but this should get you to where you want to go.

I am guessing you mean how to queue a bunch of image files for burning one after another? I don't know if there's a way to manually create a Queue. I know you can Save and Load Queues but, and I'm not entirely sure, I think Queues are generated internally by ImgBurn only when multiple image files are created/read by ImgBurn. It adds each image file to the Queue which you can then Save and Load later for burning. If there is a way to manually create a Queue, someone else will have to tell you how to do it as this is the extent of my knowledge on the subject.

Well, I just can't tell. I accidentally ejected a disc while a read operation was in progress. When I reinserted the disc to start the read operation again, ImgBurn locked up. Had to power off the enclosure, disconnect the USB cable from the back of the enclosure, and reconnect it. The 2nd read attempt then started. So, I just don't know!

Hm, something weird is going on somewhere. I put in the 2nd enclosure with the LG drive, which I don't entirely trust either because after less than 2 months, it's power supply died and the company replaced it. That was working fine, but, now, whenever I power off the enclosure after the drive is recognized by Windows, powering on the drive doesn't recognize it until either the USB cable is removed and inserted from either end or Windows is restarted. I just now did a BD-R burn and although the burn finished, Verify never started. The drive ejected the media and reloaded it. ImgBurn then said the device was waiting with the Tray Closed, but nothing happened. :O The drive never lit up and the Verify never started. Cancelling the Verify was without incident and manually issuing the Verify passed entirely fine. I even restored my system to factory default and the drive still isn't recognized on power cycle until restart/the cable is removed/inserted from either end. It used to not do that. It used to be detected fine all the time. I don't know if this was working fine after the BIOS update or not. Or if this behavior began after updating the BIOS. The above Verify not starting may have been a fluke. Just now burned a DVD+RW and Verify started fine. However, the problem before was on a BD-R, so I'll try burning another one of those. Just tried a BD-R burn and Verify started fine. So, before must have been a fluke. I'll, of course, keep an eye on it.

Well, it's not the USB cable. I connected a new cable, but it was the 2nd enclosure and a LG drive that were the problem of the drive not showing up. Whenever the drive is powered off, it doesn't show up again in Windows until the PC is restarted (Logging off Windows doesn't work.) or the USB cable is removed and reinserted at either end. It seems to be something with this 2nd enclosure or the LG drive and a recent BIOS update that cause this. Because, before, this drive always was detected without issue when powered off and on each time before September 1st, when this BIOS update was installed. So, this means the issue has to be 1.) the other enclosure 2.) the Pioneer 2209 in the enclosure 3.) something with the September 1st BIOS update or 4.) something in Windows causing the device to drop communication. It's not #2 because I tried swapping in different 2209's in the first enclosure and it still wouldn't write correctly. It has to be either the first option or the 3rd. I say it's the enclosure. I was getting the 0.0x problem on a different Dell PC with this enclosure and the 2209.

Hm, well, it's always possible you just happened to get a bunch of decent burns out of junk media before the real junk hit you. It's highly unlikely, though. Especially given if it also happens on Sony media, too. However, you really shouldn't be using the CMC media, anyway. Just because cheap media burns and plays doesn't mean it should be used. It will have a higher tendency to be unreadable before the quality media does. Now, if you're getting another ISO with no errors, it's probably a corrupt ISO file that was causing the problem.

It appears to be exactly what I thought. Notice this line of the log: I 15:09:58 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3) (Speeds: 3x, 4x, 6x, 8x) CMC MAG tells me you're using Verbatim's Life Series of DVD-R, which are junk. I am guessing you have never tried these discs before? Or have you used them before and suddenly you're getting failures? Either way, it can be the case where you get some good burns and then all of a sudden you get bad ones with CMC Magnetics media. As I said, try Verbatim DataLife Plus DVD-R, which you will only find online. Although you said you tried Sony before, too, and it failed? With the same error message? Sony isn't the best quality media, either, so that could be a problem, too. Anyway, my first step in troubleshooting an issue like this would be to try known high quality media first. If you still get an error message with 3 different media types, and you're getting the same error message, then something else is up.

Help us help you. Post the log of the failed burn. Under Help choose ImgBurn logs and copy and paste the appropriate section (The entire log of the whole burn.) with the failed burn. My initial guess? You're using Verbatim Life Series DVD-R, which is junk, and not the DataLife Plus Series, which is the only quality media they make. The log will tell me that.

Wait, could this issue be caused by a bad USB 3.0 cable? I put in the other enclosure, but upon connecting and powering on, ImgBurn nor Windows recognized the device as connected. So, I tried a different USB cable on a different port and the drive was recognized. So, I put this new cable in the port where the old cable was, and Windows recognized the device. This leads me to believe the issue was a bad USB cable. Could a bad USB cable cause a semaphore timeout issue like this?

Yes, I'm not sure if it's the enclosure, the drive, the media, or some combination of them. Given this has happened on my oldest and newer 2209's, I'm more inclined to believe it's the enclosure. Yeah, it's most likely the enclosure. I just put in my newest 2209 and on the first attempt to burn another BD-R, it dropped to 0.0x. It's either that or these BD-R's, which I'm highly less inclined to believe. Does the attached screen shot of a failed burn help? It's taken right after the drive drops communication and writes plummet to 0.0x. I notice this time it says something about a semaphore timeout issue. So, that indicates to me it's the enclosure dropping communication, but I don't know.

What exactly does the Reason: Not Ready To Ready Change - Medium May Have Changed mean? I ask because in this one enclosure I've put a Pioneer 2209 in, I get some really bad results. The drive seems to drop communication. Write rates will drop to 0.0x and never resume. This time, I actually got an error message in an aborted write. I 17:38:00 Operation Started! I 17:38:00 Image Contents: 185 Files, 15 Folders I 17:38:00 Image Sectors: 7,809,504 (MODE1/2048) I 17:38:00 Image Size: 15,993,864,192 bytes I 17:38:00 Image Volume Set Identifier: 4D278CBD007728D3 I 17:38:00 Image Application Identifier: ImgBurn v2.5.9.0 I 17:38:00 Image Implementation Identifier: ImgBurn I 17:38:00 Image File System(s): UDF (2.60) I 17:38:00 Destination Free Space: 82,462,683,136 Bytes (80,529,964.00 KiB) (78,642.54 MiB) (76.80 GiB) I 17:38:00 Destination File System: NTFS I 17:38:00 File Splitting: 4 GiB I 17:38:01 Writing Image... I 17:41:56 Operation Successfully Completed! - Duration: 00:03:55 I 17:41:56 Average Write Rate: 66,463 KiB/s (15.1x) - Maximum Write Rate: 178,957 KiB/s (40.8x) I 17:42:31 Operation Started! I 17:42:31 Source File Sectors: 7,809,504 (MODE1/2048) I 17:42:31 Source File Size: 15,993,864,192 bytes I 17:42:31 Source File Volume Set Identifier: 4D278CBD007728D3 I 17:42:31 Source File Application Identifier: ImgBurn v2.5.9.0 I 17:42:31 Source File Implementation Identifier: ImgBurn I 17:42:31 Source File File System(s): UDF (2.60) I 17:42:31 Destination Device: [0:0:0] PIONEER BD-RW BDR-209M 1.51 (R:) (USB 3.0) I 17:42:31 Destination Media Type: BD-R (HTL) (Disc ID: VERBAT-IMe-000) I 17:42:31 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x, 10x, 12x, 16x I 17:42:32 Destination Media Sectors: 12,219,392 I 17:42:32 Write Mode: BD I 17:42:32 Write Type: DAO I 17:42:32 Write Speed: MAX I 17:42:32 Hardware Defect Management Active: No I 17:42:32 BD-R Verify Not Required: Yes I 17:42:32 Link Size: Auto I 17:42:32 Lock Volume: Yes I 17:42:32 Test Mode: No I 17:42:32 OPC: No I 17:42:32 BURN-Proof: Enabled I 17:42:32 Write Speed Successfully Set! - Effective: 71,920 KB/s (16x) I 17:42:32 Advanced Settings... I 17:42:32 BD Optimum Writing Speed: Not Supported I 17:42:32 BD-R High Speed Recording: Not Supported I 17:42:32 Optimal Writing Speed: No I 17:42:32 Filling Buffer... (40 MiB) I 17:42:32 Writing LeadIn... I 17:42:43 Writing Session 1 of 1... (1 Track, LBA: 0 - 7809503) I 17:42:43 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 7809503) W 17:47:13 Failed to Write Sectors 4507008 - 4507039 - Reason: Not Ready To Ready Change - Medium May Have Changed W 17:47:13 Retrying (1 of 20)... W 17:47:15 Retry Failed - Reason: Invalid Address For Write W 17:47:15 Retrying (2 of 20)... W 17:47:15 Retry Failed - Reason: Invalid Address For Write W 17:47:15 Retrying (20 of 20)... W 17:47:15 Retry Failed - Reason: Invalid Address For Write E 17:47:20 Failed to Write Sectors 4507008 - 4507039 - Reason: Not Ready To Ready Change - Medium May Have Changed E 17:47:20 Next Writable Address: 4506080 / 1001:23:05 I 17:47:20 Synchronising Cache... W 17:47:23 User opted to skip the 'Close Track/Session/Disc' functions. E 17:47:23 Failed to Write Image! I 17:47:27 Exporting Graph Data... I 17:47:27 Export Successfully Completed! E 17:47:27 Operation Failed! - Duration: 00:04:51 I 17:47:27 Average Write Rate: 32,659 KiB/s (7.4x) - Maximum Write Rate: 48,416 KiB/s (11.0x) I've had this drive for 6 months, since around March. I once had to replace a 2209 within 7 months, so, could it be that the drive is dying? I wonder if it's the enclosure because I believe I had this occur on my newer 2209, too. Plus, the Medium May Have Changed message leads me to wonder if the drive dropped communication and resumed. I've wondered if this enclosure is simply dropping communication with the drive. Then again, I've had several write failures in this same 2209 in a different enclosure, but those were bombed out writes with error messages. None of this 0.0x crap. But, that could be a batch of not as quality BD-R's even though they are Verbatim. I think I'll try putting in the newer 2209 I got in May in this same enclosure and see if the process improves. In the meantime, any advice anyone can follow up on would be appreciated. Thanks!

Yes, Ritek media can be iffy. It's not as cheap as CMC, but it is a lesser tier media. It's been known to cause issues with some drives. Try Verbatim DataLife Plus DVD-R which you can only find online. NOT the Verbatim Life Series you'll find in stores. That will be CMC garbage.

Under Help, choose ImgBurn logs. Open the log and find the appropriate burn where it failed and copy and paste that part of the log. If I had to hazard a guess, you're probably using Verbatim Life Series CMC media or some other cheap discs that is causing the problem. The log will tell us that.