dbminter

The bottom line is you get one image per disc. So, you can't burn more than one image to a disc.

They're neither matted or shiny. They're inkjet printable. As for the board behavior, it's just the server acting up, most likely. Give it a few hours/a day, and it should resolve. I had no problem posting this just now. It's a hardware issue. It can't be software related because it's happened on 2 1909 images that were working fine, on my 1903 that was working fine, and on my 1809 factory default installation which was working fine. It only happens when ANY external USB hard drive is connected. Regardless of what drive, what USB port, what USB cable, and what power supply, it happens. It didn't do this until the 21st, so, since it happened out of the clear blue, judging from all the other I've been debugging with dozens of restores and testing combinations, it's a hardware error inside the PC. I disconnected ALL peripherals, except a mouse, keyboard, and external HD's. I connected different mice and keyboards via different means, from wireless to wired on different ports, so it's not those peripherals. When Explorer.exe/the Start menu crash, turning off the connected USB HDD and restarting makes the problem go away. Reconnect the device, and Explorer.exe/the Start menu crash. Since it happens regardless of the drive I connected, it's not one particular drive. It's not the particular USB port because I tried two on the back and one on the front. Since it happens on 2 different USB HDD's, both from WD but different models and capacities, it has to be a hardware error inside the PC. Either the motherboard, the RAM, the CPU, or the USB controller. Can't be the ports because regardless of port, regardless of whether they're front or back, it occurs. I've exhausted everything I can do at this point. After 3 days of testing, it will have to go to Best Buy for them to examine... who won't find anything wrong! I've been down this road before. It's a god problem. After jumping through hoops, spending money, there's no logical reason and no fix. God problems have no fixes. Beyond what Best Buy can do, which is nothing, I'll have to get another PC. Just a cheap one, though, as I'm still paying off one the I got in 2018!

ImgBurn doesn't do any image conversion at all. It just burns what you feed it. It can create images, but not convert between types. And, I don't think Mac is supported, so ImgBurn couldn't create those images, anyway, even if you did feed it a bunch of files to make it bootable.

Got and tested my DVD-R's. The good news is the WH16NS60 STILL likes those. At least the ones I got for now, but who knows if they're still quality MCC or if CMC made them. So, I can swap in my NS60 for the BDR-212 again. The bad news: now, I've got a serious bug that is not behaving to any logical behavioral pattern. After 45 to 60 minutes of being logged in, Explorer.exe/the Start menu "crash." Nothing runs and Windows cannot be restarted, forcing a power off. When Windows starts on ALL subsequent attempts, Explorer.exe/the Start menu "crash," rendering the system useless. What is so problematic is it does this on Windows 10 1909 images where it wasn't before. On two different 1909's. And on 1903 as well. The only image it's not doing on is the factory default image: Windows 10 1809. So, I may have to end up reinstalling everything! At least, though, doing that may be able to isolate the problem and I can fix my regular image installations. So far, I've upped 1809 to 1909 without an apparent manifestation of the problem. What's so annoying is the ONLY way to test this is after each debugging step to do NOTHING for an hour to see if it happens!

My DVD-R's should arrive tomorrow. New ConvertXToDVD gold version released! 7.0.0.69 - 0013736: [Bug] [VSORep] disabled emails appears on the pre-filled box - 0013764: [Bug] [VSORep] closed ticket if we cannot retrieve the status - 0013772: [Bug] Subtitles issue -> red subtitle with green border - 0013788: [Suggestion] [HELP MENU] Change "Report a bug" to "Support Center" + icon

Actually, turns out the problem was with that particular .VRO as I cannot recreate the issue by creating new multiple stream recorded VRO. So, the entire problematic4 GB VRO must be sent to VSO for analysis. I've already submitted another bug report with the files attached, but because of its size, it's awaiting pending approval for sending to VSO. Got an Amazon.com order just shipped today of some new Verbatim DataLife Plus inkjet printable MCC DVD-R's. I'll swap in the WH16NS60 for testing these DVD-R's and see if they work. If they do, then, the BDR-212 goes out of cycle and the NS60 is cycled back in as my primary use device.

Discovered a pretty fatal bug in ConvertXToDVD that goes back at least a year. If you import a VRO file that is made up of multiple recordings on a Panasonic DVD Video recorder, regardless of the contents running time, ConvertXToDVD only imports/converts 1 minute of contents. I regressed from 7.0.0.68 to 64 and it does it then, too. Even on 69 Beta. I know VRO works because this failing VRO is just under 2 hours and I had an over 2 hour VRO that converted in 64 a few months ago. The only difference was that VRO was one recorded stream, whereas this failing VRO is made up of 4 separate recordings. I submitted both a bug report and on the VSO forums.

There are command line switches to ImgBurn, but I've never used them before. You could create a .BAT file calling ImgBurn.exe with these parameters to automate the process. Then, all you'd have to do is create 10 different .BAT files because each one would have a different input/output name. Just double click on the .BAT file and it executes. However, someone else will have to tell you about the command line parameters, as I've never used them before, sorry.

Have you used this software before and it didn't do this? Because it seems to be the default behavior of the output of this software. To reload the video at the end of playback. However, since this appears to be BD Video related, I know next to nothing about how that behaves.

Funny, the exact same thing happened again on the first disc from a different stack of BD-R's! Medium corrupt error but a 2nd attempt to burn it starts. Weird. So, it must be something going wrong with this Pioneer crap. It seems the reason the 2nd attempt works is because no actual data was written before the failure. It says 0 KB written when I cancel the operation.

As he said, the problem is the authoring software you're using to create VIDEO_TS folders for DVD Video is starting automatic playback of the title when you play the disc. Now, if you mean automatic play means when you insert the disc it starts playing the Blu-Ray on your player, that's a problem with your Blu-Ray player.

I echo your last statement. I was completely surprised the 2nd attempt to write to it actually worked.

Verify rates depend on three factors: 1.) the rated fastest read speed in the firmware for a particular medium 2.) the highest rated read rate as defined by the manufacturer on the medium 3.) the highest maximum available speed as defined by the hardware. Oh, and the software being used has some say in it. For instance, a software may be crippled to a slower rate, despite the available fastest speed. And, yes, you can get Verify rates much faster than the write rate. For instance, before Pioneer blew it with the firmware, my Memorex BD-RE would write at 2x but Verify up to like 8x towards the end.

There's a slew of new VSO beta software released. ConvertXtoDVD - Latest beta - 7.0.0.69 ConvertXtoHD - Latest beta - 3.0.0.71 ConvertXtoVideo - Latest beta - 2.0.0.99 DVD&Blu-ray Converter - Latest beta - 4.0.0.99 For me, the most important release is ConvertXToDVD. Change log: 7.0.0.69 Released 2019-11-13 Yet another subtitle bug fixed ============================================== 0013736: [Bug] [VSORep] disabled emails appears on the pre-filled box 0013764: [Bug] [VSORep] closed ticket if we cannot retrieve the status 0013772: [Bug] Subtitles issue -> red subtitle with green border 0013788: [Suggestion] [HELP MENU] Change "Report a bug" to "Support Center" + icon So, it looks like VSO won't be jumping straight to 8.0's 64 bit release as they indicated in the past, but will release an interim version.

Looks like the volume issue I had in ConvertXToDVD 7.0.0.68 Gold was file dependent. I made another disc with a different source file and didn't experience a drastic rise in volume level on it.

Actually, I believe the GT80N is an LG drive. Just that other companies rebrand them as OEM equipment for their machines. See this: https://www.lg.com/us/burners-drives/lg-GT80N-internal-dvd-writer

This 2nd PC you're erasing on, are you using the same GT80N DVD burner in it, too? It could be that the GT80N does not like that CMC MAG disc you're using.

Try something else other than CMC MAG discs. CMC Magnetics is the worst optical disc manufacturer out there. It wouldn't be a surprise if that was the culprit. The problem is finding DVD+RW that AREN'T CMC. Try to see if you find any from Verbatim that are DataLife Plus. However, Verbatim was recently sold to, yes, you guessed, CMC, so it's a crap shoot what you'll get now! You could try Ritek/Ricoh, which makes 4x and 8x DVD+RW, but it's becoming harder to find 8x DVD+RW from them.

Oh, also about the BD-RE Verifying slowly. While it can be "lived" with, e.g. the burn process and Verify complete fine, because the Verify is capped at 2.1x for most of the Verify, a BD-RE filled to its capacity would take about 40 minutes to finish Verifying! When it can be completed much quicker in other drives. Although not the LG BU40N which is my current internal drive. That's super slow, at, well, everything! That's why I want to get some working high quality Verbatim DataLife Plus DVD recordable media working with the LG WH16NS60. While it can't write 16x Verbatim BD-R at 16x (Although LG's site rates the drive at 16x write max for BD-R! ) it can properly write to 8x DVD+RW each time and it Verifies Memorex/Ritek 2x BD-RE at full Verify speeds. So, I'd prefer to use that drive over the Pioneer BDR-212.

By died, I meant the DVD+RW had reached the end of its write life span. Meaning it would no longer properly write all sectors correctly. In theory, a Verify SHOULD fail on these unreadable sectors. Somehow, through the magic of god, these discs WILL pass Verifies, but WON'T play the bad sectors because they're not readable.

I can't quite tell if this is a bug in ConvertXToDVD 7.0.0.68 Final or if it's just a result of the first file I fed it since updating, but it may be a problem. The sound level was like double what it normally should be. Meaning, I had to turn down the volume on my TV to a much lower level that I usually have to with a ConvertXToDVD disc. VSO is known to mess up volume levels with its updates of ConvertXToDVD in the past. However, this was just the first file I fed it since updating, so I've only had the chance to generate 1 disc since the update. The audio level could be a result of the file I fed it. I'll know more with my next disc.

You forget the MAJOR bug in the Pioneer that's been in there for like 3 years now. It doesn't properly write unformatted 8x DVD+RW. SOMETIMES when those discs are first written in a different drive, the BDR WILL properly write to them; sometimes not. I always Verify because it's quicker than letting my DVD play and discover the unplayable part at the end of the disc, after you've spent all that time playing everything else. And, of course, it rarely fails to Verify at the beginning, when you can save some time. It almost always fails towards the end to waste more time. Just because you pop in a DVD to make sure it starts to play doesn't mean it will play EVERYTHING. The LG WH16NS40 had an annoying trait where it would pass Verify but STILL be unplayable in certain parts because the disc had actually died! The NS60 fixed this. Write/Verify speed rates are dependent on the drive's firmware and the read/write strategies on the medium. For instance, most drives write 8x DVD+RW at 6x for 2 minutes before they get to 8x. Sony's drives, though, immediately started at 8x and they were the only ones I ever saw that did that. I never understood that, actually. If a medium can write at Xx max, why can't it just go to that max at the beginning?

I sent Pioneer another tech support e-mail, this time about how Ritek 2x BD-RE only Verify at 2.1x for most of the Verify and then speed up to normal rates near the end. I was pretty much told to get lost! Here's the reply: "I have not heard back from the engineers regarding this issue. It appears I am not going to have a solution to your issue. If you like, I can offer you a refund for the drive." Basically, they're saying they're not going to fix the issue, despite the YEARS I've spent telling them about them! They have NO intent of fixing them, even though, in the past, they were aware of the SAME issues with the firmware starting after 1.30 and FIXED in 1.50. I'd take them up on their refund offer if it weren't for the fact that NO ONE can do their job right! I can't use LG because it may be impossible to use quality Verbatim DVD on the WH16NS60.

I've gotten some contradictory results with the BDR-212 and 8x DVD+RW. I fed it some more previously written ones and they write fine now. Like the current behavior is SUPPOSED to be on Pioneer's latest spate of firmware. However, my last tests with freshly formatted and written media on the LG BU40N STILL failed on the 212! So, now, I don't know what to think.

Have never seen this before while trying to burn a BD-R: I 18:58:48 Writing LeadIn... W 18:59:20 Failed to Write Sectors 1056 - 1087 - Reason: Write Error W 18:59:20 Retrying (1 of 20)... W 18:59:20 Retry Failed - Reason: Medium Format Corrupted E 19:08:39 Failed to Write Sectors 1056 - 1087 - Reason: Write Error I 19:08:39 Synchronising Cache... W 19:08:43 User opted to skip the 'Close Track/Session/Disc' functions. E 19:08:43 Failed to Write Image! I tried using the same disc again and it successfully burned. It's Verifying right now. I'll check out the contents after it succeeds (IF it does.) but it's really weird. So, what could have caused this and why did it eventually write a 2nd time to the same medium? Thanks!