Jump to content

dbminter

Beta Team Members
  • Posts

    8,405
  • Joined

  • Last visited

Everything posted by dbminter

  1. Do you have any BD-RE's? I'm guessing you're trying to test a BD-R? If you have any BD-RE's and you tried this test on a BD-R, try a test on a BD-RE. This should isolate if your drive may not like that particular brand of BD-R. If it repeats for both types, it could still be the discs if the manufacturer is the same. If it repeats for both, there's probably something else going on.
  2. Advanced. Unfortunately, I've deleted the folder by now. It was a temporary folder with temp files. It was in my TEMP folder. It had 2 sub folders. I said there were files in the sub folder but there were only sub folders. EDIT: Actually, the folder was still there. I thought I had deleted it. I renamed it and tried again. It worked fine this time. I renamed it back to the old folder name and tried again. Ah, I discovered the "problem." I don't think it's a problem. I think it's expected program behavior. One of the folders was a VIDEO_TS. I was wrong in that I thought it was something else. The reason the drag and drop tests worked was because I renamed this VIDEO_TS folder to Test. When I renamed it back to VIDEO_TS and tried again, the issue reappeared. So, it seems to be standard behavior for importing VIDEO_TS, even when it's in a sub folder? ImgBurn automatically just imports all the sub folders into the job's root folder if one of the folders is VIDEO_TS? It is probably this way because most people importing a VIDEO_TS would be trying to make a DVD Video playable disc. Just so happened, I wasn't.
  3. I'm in Build mode and I've got a weird folder that isn't behaving normally when it's dragged and dropped into a job. The folder, when added, adds the folder contents, files and sub folders, but the root folder itself is not added. I tried a folder created right after I created the folder I tried to add and it behaved normally. It added the root folder and the contents were in the folder as files and sub folders. I can't figure out why this one folder is behaving this way in ImgBurn.
  4. Well, I've gotten through more than half of the cake stack and now I'm getting above 6x write rates again! I 21:12:40 Average Write Rate: 14,022 KiB/s (10.4x) - Maximum Write Rate: 20,820 KiB/s (15.4x) So, it seems about half of the discs in this stack were capped at 6x. I wonder why.
  5. Probably can't remove the alert. You'll probably get it every time. As far as I know, all you can do is select Yes each time. Although LUK might know some setting to change to remove a wide swath of various dialogs. He'd more about that. After all, he wrote it.
  6. The Windows 10 thing is a technical issue. It will be fixed when the next version of ImgBurn comes out. It has nothing to do with your issue.
  7. ImgBurn is telling you you shouldn't try burning that image. You can always say Yes to burning it and testing what you get. But, ImgBurn is telling you something for a good reason. You MIGHT find luck taking the ISO and using some other burner software to burn it. However, I'd still think there would be a problem burning it. And even if it burned it, you probably wouldn't get a playable DVD out of it. It might play the contents of the first layer, but who knows how it would handle the 2nd? As far as making it playable, I only know trying what I said. As far as I know, it's the only way it's going to work with a degree of certainty.
  8. Are you burning an ISO file created by DVD Styler? What you can try to do if the software will let you is write its output to a VIDEO_TS folder and use ImgBurn's Build mode. Then drag and drop VIDEO_TS into a Build job. If DVD Styler won't let you do this, alternatively, you can download Virtual CloneDrive, install it, and mount the ISO created by DVD Styler to a virtual drive. Then drag and drop the VIDEO_TS from the virtual drive into an ImgBurn Build job.
  9. Could be Taiwan. I can't remember if this cake stack is the one that came with these discs or not. Or if I just reuse the old stack. I think it's reused as the current style has changed and doesn't stack as well as the old ones. According to the image shown on the Amazon.com page http://www.amazon.com/gp/product/B000A0CV9S?psc=1&redirect=true&ref_=oh_aui_detailpage_o03_s00 there is no listing on the label as to where these discs were made. So, it leads me to believe even more my cake stack is an old one I've reused.
  10. It's the fault of the MCC DVD-R's! I got a replacement Pioneer burner. The box says 2209 but apparently the 209 is what is actually in the box, WHICH WAS THE SAME GODDAMN DRIVE I ALREADY HAD! So, naturally, it didn't fix my problem. Which means it's Verbatim's fault. They switched the manufacturing process for these DVD-R's. Where they had been writing at 16x before now these same discs only write at 6x. Which means it's the fault of the media.
  11. Often times with creating Audio CD's from files, I find random errors occur all the time. If you find one particular file format that works like FLAC, try downloading a converter for M4A and converting to FLAC. See if that works. I convert all the time for various errors and reasons with Free Audio Converter 4Dots. It supports FLAC and M4A. Often times I even have to load MP3's in it and convert them to NEW MP3's to get them to work. Big Finish Audio downloads are common problems I come across.
  12. Also some drives are just picky. I had a DVD in my collection that one of my drives wouldn't read. When I replaced the drive later, I tried again and it read it fine. And my current situation is I have an LG and a Pioneer Blu-Ray drives in my system. I've come across several discs where the LG errors out trying to read, but the Pioneer reads them fine.
  13. Well, there could be an issue depending on how you recorded these shows to DVD. If you used a standalone DVD recorder like Panasonic makes, some models make DVD's that can't be copied with ImgBurn's Read function. You have to use Build mode and drag and drop the VIDEO_TS folder into a new Build job to create a new image to make a "copy." About heeding the warnings of unwanted stuff, the easiest way to do that is to disconnect your modem before running the installer. The installer will run without OpenCandy phoning home and offering third party installs because it can never access the server that would feed these installs. You will get an error from OpenCandy not being able to download anything, but who cares?
  14. Hm, it's definitely the drive. Now I'm randomly getting 8x DVD+RW's capped at 6x. This disc just burned at 8x and then the next time it's capped at 6x, even though the log says effective write speed set at 8x.
  15. Not that it will help but here's the rest of the burn log. I 21:36:17 Operation Started! I 21:36:17 Source File Sectors: 2,005,504 (MODE1/2048) I 21:36:17 Source File Size: 4,107,272,192 bytes I 21:36:17 Source File File System(s): ISO9660, UDF (1.02) I 21:36:17 Destination Device: [0:0:0] PIONEER BD-RW BDR-209M 1.31 (S:) (SATA) I 21:36:17 Destination Media Type: DVD-R (Disc ID: MCC 03RG20) I 21:36:17 Destination Media Supported Write Speeds: 4x, 6x, 8x, 12x, 16x I 21:36:17 Destination Media Sectors: 2,298,496 I 21:36:17 Write Mode: DVD I 21:36:17 Write Type: DAO I 21:36:17 Write Speed: MAX I 21:36:17 Link Size: Auto I 21:36:17 Lock Volume: Yes I 21:36:17 Test Mode: No I 21:36:18 OPC: No I 21:36:18 BURN-Proof: Enabled I 21:36:18 Write Speed Successfully Set! - Effective: 22,160 KB/s (16x) I 21:36:18 Advanced Settings - Optimal Writing Speed: No I 21:36:18 Filling Buffer... (40 MiB) I 21:36:18 Writing LeadIn... I 21:36:42 Writing Session 1 of 1... (1 Track, LBA: 0 - 2005503) I 21:36:42 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2005503) I 21:45:09 Synchronising Cache... I 21:45:32 Exporting Graph Data... I 21:45:32 Export Successfully Completed! I 21:45:32 Operation Successfully Completed! - Duration: 00:09:14 I 21:45:32 Average Write Rate: 7,911 KiB/s (5.8x) - Maximum Write Rate: 8,182 KiB/s (6.0x)
  16. My Pioneer is locked at 6x write cap for 16x DVD-R's. The log says the write speed set is 16x: I 20:31:23 Write Speed Successfully Set! - Effective: 22,160 KB/s (16x) but the drive caps the write at 6x. I tried another disc from the same spindle in my LG and it wrote at a higher speed beyond 6x. My Pioneer is approaching 2 years old. Time to replace it? I'd use my LG to write but LG's suck. When I did the above write test in the LG, I couldn't Verify it in that drive. The drive never got to actually loading the disc. The drive light stayed on all the time. I had to power off the drive and manually run a Verify. What is the most current model of Pioneer Blu-Ray burner I should be looking for? Is it the BDR-209DBK? Seems the BDR-2209 is the latest XL one.
  17. I'm guessing from what LUK said you can't with that particular drive. I believe, though I don't know for sure, that you need certain burners to burn XBox 360 copies. I don't know why.
  18. Yeah, when I saw this post earlier this morning, I was wondering why you'd want a game disc to boot, anyway. Unless it's a DOS based game, there's not really a need to. I was thinking if it was a Windows based game or a console based game, you wouldn't really need it to boot into anything. As LUK said, how do you want it to boot? Boot into DOS? Boot into a Windows recovery environment? Boot into Win PE? Boot into Linux?
  19. Yeah, I never had any luck with overburing DVD's at all. Ever. CD's, yes, but not DVD's. Plus, those Memorex/Ritek discs aren't helping the cause either. I mean, using Verbatim DataLife Plus MKM's might improve the situation, but I'd doubt it.
  20. That would be my guess, too. I know that the PS3 actually checks the type of physical media inserted in order to play it. For instance, if you have a DVD that fits on a CD and burn it to a CD, it won't play on the PS3 because it sees a CD inserted and looks for CD content to play. Plus, DVD+R DL sized DVD's won't play on the PS3 if you burn them to BD's. Try burning those folders to a BD-RE or BD-R and see if that helps. Sorry, I meant to ask for a log, too, when I saw this post earlier this morning.
  21. I couldn't come across anything that explained the size of each layer for XL and quadruple layer BD discs. EDIT: Found the white sheet for TL/QL BD. http://blu-raydisc.com/Assets/Downloadablefile/BD-R_physical_specifications-18326.pdf TL layers are 33.3 GB. So, BD XL is not actually 100 GB but 99.9. And as I surmised, QL are made up of 4 32 GB layers. So, they did increase the size of the single layers found in the TL and QL discs.
  22. I'll try to find the spec sheet for Blu-Ray, then.
  23. So there is a 50 GB layer in triple layer Blu-Rays? Then for quadruple layer Blu-Rays they made the somewhat arbitrary layer size 32 GB? Then the triple layer ones should have been 96?
  24. Okay, so, I'm a little confused. Single layer Blu-Rays are a standardized 25 GB. It's a nice, rounded number. Not some arbitrary space size like 700 MB CD's or 4.7 GB DVD's. Then there's the double layer Blu-Ray, which is 50 GB. Which makes sense. It's twice the size of a single layer Blu-Ray and has 2 layers, 2 25 GB layers. Along comes triple layer Blu-Ray and here's where it makes no sense! How can triple layer Blu-Ray be 100 GB? The only way this seems to make any sense is if one layer is 50 GB and then the other 2 layers are 25. Does that mean double layer Blu-Ray actually only has 1 50 GB layer in it? Then why call it double layer? And then there's quadruple layer Blu-Ray with the seemingly arbitrary value of 128 GB! Actually, from a computer science POV, 128 is a common value as it's a multiple of 2.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.