Jump to content


Beta Team Members
  • Posts

  • Joined

  • Last visited

Everything posted by dbminter

  1. Actually, I believe given how much data is needed to be written to Blu-Ray, you must use a USB 3.0 enclosure for a Blu-Ray drive if you plan to write Blu-Rays to it. Otherwise, you might get by with a Blu-Ray burner in a USB 2.x enclosure if you plan on only writing CD's and DVD's in it. The USB speed has nothing to do with how fast any device in an enclosure will write. Media are capped at specific speeds depending on the media. Even reads probably wouldn't be faster. While the USB 3.0 would send data faster, the device is still capped at a maximum speed it can read at.
  2. 1.8 GB for a 3 hour movie is WAY too small. You could get that if you compressed the video in two passes, but the video quality would be awful. A 3 hour movie would normally be a DVD-9, or roughly twice the size of a DVD-R. If I had to hazard a guess, this is probably a video container file of the movie and not a VIDEO_TS DVD Video compliant disc. So, most likely, a standalone DVD player probably wouldn't play it even if the burn was successful.
  3. I'd settle for a 10th anniversary release celebrating the last release.
  4. The DRW-24F1ST is a DVD drive. So, you don't need anything greater than USB 2.x. USB 3.0 for a DVD drive won't be any faster than if you used a USB 2.x interface.
  5. Mirror 7 is the repository that ImgBurn.com itself hosts. "Provided by ImgBurn"
  6. Handbrake might work. It will convert full Blu-Ray discs to container files and it has an option to load individual files. But, I don't know whether Handbrake will convert a single existing M4TS file or not. But, you can try it. However, the underlying problem still exists. If your Blu-Ray player doesn't support playing container files natively, then there's no need to do a conversion.
  7. Well, it depends on what you're burning. There's nothing to "change." If you're burning a container file to the BD and your players don't support playing container files, you need to convert the files to BDMV compliant BD Video compliant files. As to what can convert a file to a BD, you'd have to search for that as I don't do BD Video discs. I guess to make it easiest, what exactly are you burning to the BD? What files/folders names?
  8. ImgBurn does no conversion. The only thing I can think of in this case depends on what you're trying to feed into your Blu-Ray player. Is there a BDMV folder in the root directory of the BD disc? What might have happened, even though it's a little unlikely in that direction but more likely in the other, is that your older Blu-Ray player supported playing container files directly from a Blu-Ray disc and your newer players don't. Your newer players may be looking for a BDMV folder to play and don't support playing container files. It depends on what you put on the BD recordable disc.
  9. Ah, I failed to notice that. Yeah, as long as that % isn't over 100, you're fine. Just click OK.
  10. Generally, file loading problems at creating a CUE stage are due to corrupt files or improperly authored files. The best thing you can do here is use something like free audio converter, load the files in question, and create new lossless files. FLAC is probably most universal. After creating the new lossless files in free audio converter, load those free audio converter files as you were attempting to do before and see if that helps.
  11. Probably not. It's a firmware error writing to that particular DID. The whole point of 8x DVD+RW is to write at 8x. If I wanted to write at 4x, I'd buy Verbatim DataLife Plus DVD+RW, which is 4x. DataLife Plus is the best out there, but it maxes at 4x. The only 8x DVD+RW media manufacturer is Ritek. So, if you never write at 8x with the 213, just get the 4x Verbatim media which does work. Well, it probably works. I don't think I ever tested my Verbatim 4x DVD+RW on the 213, though.
  12. Yes, the NS60 is not commercially available anymore. Even though LG claims to still sell it, the only way to get them is to send in existing NS60's for replacements. Which means you must buy the NS40. I haven't had an NS40 is a while, but a fatal flaw in them that existed for a long time was though they claim to support writing BD-R/RE DL, they will fail to write properly 9 times out 10. Still, the NS40 is the least worst of what is available out there. ALL BD drives have some sort of fatal flaw, but the NS40's was only the one: DL BD media. So, basically, the only thing I recommend is the NS40. Unless you never plan on writing DVD+R DL, then go with the ASUS or if you never plan on writing 8x DVD+RW, the Pioneer 213 appears to "work" now.
  13. The 213 only got worse! Pioneer did update the firmware to fix BD-R, CD-R, and DVD+R DL, where the 213 WAS working with 8x DVD+RW FINALLY after TEN years... Pioneer BROKE 8x DVD+RW AGAIN in the 213!
  14. The biggest take away from the log is the burns are failing (That's why Verifies are failing.) precisely at the layer change. This is the most common place for an error to occur. Unfortunately, since you tried two different drives and got the same result, the problem is down to the Verbatim BD-R DL themselves. Since they had been working and then suddenly stopped, and since they are failing on 2 different burners, you can be pretty sure it's the media that's the problem. Since they had been working before, the most likely answer is Verbatim changed the production lines of their BD-R DL. This is usually only fixable by a firmware update to the drive. You could try telling the burner manufacturer of the issue. If you provide enough detailed information, you might get tech support to update the firrmware, but be it known most tech support doesn't listen to you when you tell them what needs to be done. I've tried to get Pioneer to fix a 10 year old firmware fatal flaw in over 5 DVD and BD models, but they refuse to address it.
  15. Ritek, depending on where you are in the world, can either be good 2nd tier media (North America) or pretty bad (Europe). However, I've never used Ritek BD-R DL before, or even Ritek BD-R SL. 99.99% of all the BD-R I've ever burned are Verbatim VERBAT-IM media. I've burned 2 Sony BD-R and 50% of them failed. I burned 2 to 4 other non Verbatim media only because they were given to me with some DVD-R's I bought from a friend who had a supply he no longer needed.
  16. My recommendation still stands. Try to find Verbatim BD-R DL with the VERBAT-IM Disc ID. If those fail, try a different BD burner. I've never used Verbatim BD-R DL but I've used Verbatim BD-R for years. And my BD-RE DL were all Verbatim, but those didn't have a high long term lifespan.
  17. I have no direct experience with BD-R DL. Just with BD-RE DL. My experience with BD-RE DL is I'd sometimes write to them for the first time and try to write to them again a year later and they'd fail. And I've seen several issues reported with BD-R DL on these forums. So, I have no empirical evidence to go by, but the circumstantial seems quite damning.
  18. Well, a well made product won't have a problem. If the firmware is correct for the writing strategy to the media, it won't matter. However, I do know that the ASUS has had issues since it was released, and I don't use them because they don't write properly to DVD+R DL. They haven't updated the firmware in 4 years, and only a firmware update will fix the issue. I took a look at that link. I took 3 years of high school German but I'm not that good. Yet, I did manage to navigate to the item. I've never seen those before. You could try the Verbatim BD-R DL if you can find them on Amazon.de. Another problem is the issue of BD-R DL media itself. These seem to have had problems from the release. The WH16NS40 from LG never did write properly to BD-RE DL, so I would guess BD-R DL had the same problem. Then again, I've only ever used Verbatim BD-RE DL media in the NS60.
  19. Updating the program won't help here. It's down to either how Windows detects the device or the interface driver you're using in ImgBurn. That 2nd option, though, may be something you can do about that. Under Tools --> Settings --> I/O, there's an Interface setting. Try selecting each one one at a time and see if that improves operation of the device. I would recommend you close ImgBurn and reopen it each time you change the Interface setting.
  20. Never heard of Primeon, so I can't comment on their quality. I know that ASUS model has had various quality issues since its release. Upon release, it destroyed DVD+RW and BD-RE discs. The last time I tried one, it didn't write properly to DVD+R DL.
  21. Generally, these kinds of returned metadata errors are the fault of the software or hardware displaying them. However, in this situation, given the returned values, I would check one thing. There is a Performer field for Disc CD-Text and each individual track. Make sure there is different Performer text for each CD-Text for each track. If there is in the CUE, then try changing the Performer field for the Disc CD-Text to blank. However, this could result in simply blank Performer fields. One thing you can try before getting CD-RW's is to create image file sets and then mount the .CUE file as a virtual drive in something like Virtual CloneDrive. Then, you can play the image files like a virtual CD in VLC. This means you don't use any discs at all to burn to, which can be particularly useful for testing issues like this.
  22. The artist names that are wrong. What is returning these artists' names? A standalone CD player or PC playback software? If you don't want to waste CD's and need to keep testing, try CD-RW's, which are rewritable. However, if you are having this issue with a standalone CD player, not all standalone CD players, particularly older ones, support reading from CD-RW's. And those that do don't necessary support all manufacturers' brands of CD-RW.
  23. Generally, there are little variations between discs in the same stack. It could depend on how close to the edge you get. The edge is always one of the iffiest parts to write to, going all the way back to CD-R. It's generally down to the quality of the drive and how well the firmware writes. What BD burner are you using?
  24. Well, I don't know what you mean by Blu-Ray "tile," however when you get to the outer edges of media, there's always the higher possibility of write failures. This is generally down to the firmware needing an update.
  25. ImgBurn just burns what it's fed. It would not take out the audio. Now, there might be a possible explanation why 25 GB discs would play and 50's wouldn't. Those 50 GB discs might simply not be recognized by your Blu-Ray player when you insert them. That would be a disc compatibility issue with your player. One way you can check, if you don't mind "wasting" a 50 GB disc as a test. Burn a 25 GB disc you know plays on your Blu-Ray player to one of these 50 GB discs. Make an image of one of these 25 GB discs you have tested as playing on your Blu-Ray player in ImgBurn and burn that image to a 50 GB BD-R. If it doesn't play back, you know your Blu-Ray player isn't recognizing those particular discs as having been inserted.
  • Create New...

Important Information

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