Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. Winston

    Burning Errors - Dual Layer Dvd+R

    ah, thanks for the info. I did find some sites with firmware updates for other similar Matshita units, just not mine. I was told by the seller it typically doesn't have updates like you mentioned. thanks, Win
  3. dbminter

    Burning Errors - Dual Layer Dvd+R

    I didn't think the updating firmware would work. Most external drives rarely have firmware updates released for them. Don't know why. The Windows 10 recognized as Windows 8 is a holdover from how old ImgBurn's last gold release was. Between Windows 8 and Windows 10, Microsoft changed how Windows identifies itself. ImgBurn simply doesn't have the necessary code to differentiate Windows 10 yet. So, that's normal. This will be addressed in the next version. Of course, I can't say when that will be, obviously.
  4. Winston

    Burning Errors - Dual Layer Dvd+R

    Thank for the reply. I tried the firmware update, and my exact models doesn't show up. MATSHITA BD-MLT UJ272 (firmware 1.01) One thing that struck me as odd, and it may be that I'm uneducated about most of this stuff. When I boot up the imgburn software, I get the following, and it shows Windows 8. Is this supposed to be the O.S. i'm running? I ask because I'm running Windows 10. I 18:13:55 ImgBurn Version 2.5.8.0 started! I 18:13:55 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 18:13:55 Total Physical Memory: 67,038,552 KiB - Available: 56,122,924 KiB I 18:13:55 Initialising SPTI... I 18:13:55 Searching for SCSI / ATAPI devices... I 18:13:55 -> Drive 1 - Info: MATSHITA BD-MLT UJ272 1.01 (F:) (USB 2.0) I 18:13:55 Found 1 BD-RE XL! thanks again, Winston
  5. dbminter

    Burning Errors - Dual Layer Dvd+R

    It is entirely within my experience that a drive can work with all other kinds of media but one particular one and need replacing. For instance, a BD burner has 2 lasers: one for CD and DVD and one for BD. So, it can be a case where BD works and CD or DVD don't and CD and DVD are fine but BD aren't. And even in DVD only burners, it has been my experience that DVD+R DL function will fail first but SL media burn fine. It is generally not a case where PC's have gone wrong that cause bad burns. It's either the drive or the media. Since you said you had 2 of these drives and got the same results, the problem is most likely a combination of that media you're using in the drive you're using. You could try and see if there's a firmware update for your drive that might be better compatibility with the media. In Write mode, right click on the drive you're burning to and choose the last option in the context menu to check for firmware updates.
  6. Winston

    Burning Errors - Dual Layer Dvd+R

    First, thanks for the reply. One thing of note, is all other media burns just fine on this drive. Is it normal that a drive would start having issues burning one type of disc, and not the other? Also, I have 2 of these drives, and they both suddenly have the same issue. Which made me think it might be the pc, the software settings, or obviously the media. I guess my first test would be try a better quality DL disc type. thanks again. Winston
  7. dbminter

    Burning Errors - Dual Layer Dvd+R

    Well, you could have one of two issues or a combination of both. As was noted in the FAQ, slim models tend to be junk. It could have simply given up the ghost. As you note, Ritek/Ricoh media can be cheap discs. Depending on where you live in the world, it can be either decent 2nd tier quality media or junk. It could just be you got lucky 35 times in a row as the nature of cheap media means something you get a burn that works and sometimes you don't. Given you had no problems up until recently, it seems less likely the problem would be cheap media and more likely a problem of a cheap slim drive model burner.
  8. I would appreciate any help anyone can provide...I've just recently started having issues burning only dual layered DVD+R discs. Regular dvd burns just fine, as do 25gb & 50gb blu-ray discs. I've burned 35 of these discs with no coasters, but suddenly i'm having issues. The drive is a super Slim Drive USB3.0 model purchased on Amazon. Model ODP95-SU3 After reading the DL layer FAQ, it seems these slim, external laptop style drives are not great. The discs are GIGABLOCK brand dvd+r discs, rated at 8X. The error i'm getting is: Set L0 Data Zone Capacity Failed! Reason: ID CRC or ECC Error The logs is as follows... I 14:03:17 ImgBurn Version 2.5.8.0 started! I 14:03:17 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 14:03:17 Total Physical Memory: 67,038,552 KiB - Available: 58,335,276 KiB I 14:03:17 Initialising SPTI... I 14:03:17 Searching for SCSI / ATAPI devices... I 14:03:17 -> Drive 1 - Info: MATSHITA BD-MLT UJ272 1.01 (F:) (USB 2.0) I 14:03:17 Found 1 BD-RE XL! I 14:04:43 Operation Started! I 14:04:43 Source File: D:\@Films\Dune (1984) Alternative Edition Redux [fanedit][DVD-9][2h58m]\DUNEALTRDXDISC.MDS I 14:04:43 Source File Sectors: 4,165,440 (MODE1/2048) I 14:04:43 Source File Size: 8,530,821,120 bytes I 14:04:43 Source File Volume Identifier: DUNEALTRDX I 14:04:43 Source File Volume Set Identifier: 40EF5DEE003F8F3E I 14:04:43 Source File Application Identifier: IMGBURN V2.5.5.0 - THE ULTIMATE IMAGE BURNER! I 14:04:43 Source File Implementation Identifier: ImgBurn I 14:04:43 Source File File System(s): ISO9660, UDF (1.02) I 14:04:43 Destination Device: [0:0:0] MATSHITA BD-MLT UJ272 1.01 (F:) (USB) I 14:04:43 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D01-67) I 14:04:43 Destination Media Supported Write Speeds: 2.4x I 14:04:43 Destination Media Sectors: 4,173,824 I 14:04:43 Destination Media L0 Data Zone Capacity: 2,086,912 (Changeable: Yes) I 14:04:43 Write Mode: DVD I 14:04:43 Write Type: DAO I 14:04:43 Write Speed: 4x I 14:04:43 DVD+R DL Reserve Track: No I 14:04:43 Link Size: Auto I 14:04:43 Lock Volume: Yes I 14:04:43 Test Mode: No I 14:04:43 OPC: No I 14:04:43 BURN-Proof: Enabled W 14:04:43 Write Speed Miscompare! - Wanted: 5,540 KB/s (4x), Got: 3,324 KB/s (2.4x) W 14:04:43 The drive only supports writing these discs at 2.4x. I 14:04:43 Optimal L0 Data Zone Capacity: 2,082,720 I 14:04:43 Optimal L0 Data Zone Method: Copied From Original Disc W 14:05:22 Set L0 Data Zone Capacity Failed! - Reason: ID CRC or ECC Error E 14:05:51 Set L0 Data Zone Capacity Failed! - Reason: ID CRC or ECC Error E 14:05:51 Operation Failed! - Duration: 00:01:08 I 14:05:51 Average Write Rate: N/A - Maximum Write Rate: N/A I've no idea whats going on, unless suddenly the drive doesn't like this cheap media. thanks, Winston
  9. Ahhh... I'm new to this as you can tell. Thanks a ton for your response. Much appreciated!
  10. Earlier
  11. dbminter

    Issues trying to create image file from files

    The CUE file probably doesn't need to be in the same folder. The CUE may be picking up metadata present in the audio files you added.
  12. AuspiciousCrane

    Issues trying to create image file from files

    Thank you, that has worked. The CUE file contains enough information to pick up the correct track provided it is in the same folder.
  13. dbminter

    Issues trying to create image file from files

    You can rename the CUE file but it won't set the name of the CD in the CD Text. You will need to set the Title for the Disc or Session, I forget which one. I set it for both the Disc and the Session just to make sure. To burn the actual CD, in Write mode, load the .CUE file you created as you would an ISO/image file. When you do the actual burning part, the Audio CD is created on the fly; an image file is not created first to HDD. I don't know why this is, but that's how it behaves in ImgBurn. This Guide should help you with further questions:
  14. AuspiciousCrane

    Issues trying to create image file from files

    Thanks. I've just tried that but I still don't really know what I'm doing. I open Create CUE and I then pick the tracks that I want, filling in the fields for the CD text. I then hit 'OK' and the program does indeed create a .CUE file but it's named after track 01. How do I rename it to the name of the CD, and how do I then associate this .CUE file with with the corresponding music tracks, to make into a CD? There is no BIN file. If I try to create a disc from file ImgBurn can't see any files including the CUE file that I just created.
  15. dbminter

    Issues trying to create image file from files

    It seems you're trying to create an ISO for making Audio CD's. ImgBurn doesn't do that. If you create a .CUE file with ImgBurn to make an Audio CD, it burns it on the fly. It doesn't save to ISO first and, in fact, it can't. ISO isn't a viable format for Audio CD. It looks like you're creating a data disc with the folder of the WAV files in it as the root directory contents. What you want is the Create CUE file option. It's under Tools. You can then add the .WAV files for creation. BTW, there's no need to convert MP3 to WAV first when creating an Audio CD in ImgBurn. ImgBurn will support MP3 files for creating Audio CD's.
  16. Afternoon all, hoping for some assistance. How do you actually do the above? I use ImgBurn to add CD-Text to CDs that don't have it. Some of the CDs are 30-odd years old and in poor condition. What I do with these is rip them, which can take a very long time, but I then at least get a playable MP3 off my CD. I've used CloudConvert to turn these from .MP3 files to .WAV files, so what I should be able to do is create an image file from these files and edit the .CUE file to add CD-Text, right? This does not however work. I am doing as follows: Open E-Z mode picker. Click 'Create image file from files/folders'. For 'Source' I navigate to the folder with the .WAV files in it. ImgBurn then cannot see any files. When I click on it I get an empty screen and the message "No items match your search". The folder actually contains six .WAV files, which I can play if I click on them via File Explorer. If I select this empty folder anyway, followed by a destination, the attached window comes up. If I click Yes, what I get is a very small .MDS or 'disc image file' which ImgBurn also cannot see (attached). In the past, I have worked around this by burning the .WAV files thus created to a disc. Then I use it to Create Image File from Disc, then edit the .CUE file and created a new disc with CD-Text. This means I use up two discs creating one, and I then throw away the first one away, because it's just .WAV files without CD Text. There has to be a less wasteful way of doing this, whereby I can go from .WAV files on my hard drive to an image file on my hard drive that I edit before making a new disc from it (once)? Thanks for any help. Saturday Night Fever- The Original Movie Sound Track [Disc 2].mds
  17. The program reads the sectors in chunks. When the drive returns an error, it drops down to reading them 1 at a time so it can pick out the bad one. What’s happened here is that the drive errored out when reading the chunk, but then succeeded to read them all when doing it 1 by 1. I would the disc has the potential to be unreliable. Maybe do a stand-alone verify on it and see if the drive fails to read it again in those same locations.
  18. According to what I looked up, MEI-T02-001 are BD-R made by Panasonic/Matsushita. Recordable DVD discs made by Panasonic/Matsushita were some of the best quality you could get. So, it would probably be the case that you're using quality BD-R. Sometimes read issues happen, but ImgBurn "recovers" from them. These are usually cased by a drive being picky with that particular manufacturer's process for discs. The one time I had this happen with BD-R, ImgBurn tried the read again during the Verify and it was successful on the 2nd attempt. I then did a variety of read tests on the data and it seemed to just be a hiccup. If you're really concerned, see what happens when you create an image from these same BD-R that return the "read errors." See if you get more read errors. If it completes read, it's probably fine. If it doesn't, then, of course, it most likely isn't. And, if you're really concerned, since it appears it might be a Blu-Ray movie you made, try playing all of its contents. If they play without read errors, skips, pauses, pops in audio, pixelation in video, then the disc is most likely okay.
  19. I have had a couple of discs that failed verification listing an Error (Failed to Read Sectors, Cannot Read Medium - Incompatible Format). But I also had a couple of discs that listed this same statement, but as a Warning, not an Error. The program then completed verification and stated "Operation Successfully Completed". The program displayed 0 read errors and 0 miscompares. My question is, if Imgburn states that it failed to read sectors but then states that verification was successful, is the disc good or not? And why is failing to read sectors sometimes listed as a warning and other times as an error that ends up in a failed verification? ; //****************************************\\ ; ImgBurn Version 2.5.7.0 - Log ; Tuesday, 09 February 2021, 15:45:27 ; \\****************************************// ; ; I 13:30:25 ImgBurn Version 2.5.7.0 started! I 13:30:25 Microsoft Windows Vista Home Premium x64 Edition (6.0, Build 6002 : Service Pack 2) I 13:30:25 Total Physical Memory: 4,192,432 KB - Available: 2,363,132 KB I 13:30:25 Initialising SPTI... I 13:30:25 Searching for SCSI / ATAPI devices... I 13:30:26 -> Drive 1 - Info: HL-DT-ST BD-RE BH10LS30 1.02-A0 (E:) (ATA) I 13:30:26 -> Drive 2 - Info: DVDFab Virtual Drive 1.1 (D:) (SCSI) I 13:30:26 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE! I 13:32:59 Operation Started! I 13:32:59 Source File: V:\ISO 2\WINGS_OF_THE_HAWK.iso I 13:32:59 Source File Sectors: 16,496,224 (MODE1/2048) I 13:32:59 Source File Size: 33,784,266,752 bytes I 13:32:59 Source File Volume Identifier: WINGS_OF_THE_HAWK I 13:32:59 Source File Volume Set Identifier: 02E50775 WINGS_OF_THE_HAWK I 13:32:59 Source File Application Identifier: ScenaristScenaristBD I 13:32:59 Source File Implementation Identifier: ScenaristScenaristBD I 13:32:59 Source File File System(s): UDF (2.50) I 13:32:59 Destination Device: [3:0:0] HL-DT-ST BD-RE BH10LS30 1.02 (E:) (ATA) I 13:32:59 Destination Media Type: BD-R (Disc ID: MEI-T02-001) I 13:32:59 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x I 13:32:59 Destination Media Sectors: 24,438,784 I 13:32:59 Write Mode: BD I 13:32:59 Write Type: DAO I 13:32:59 Write Speed: 2x I 13:32:59 Hardware Defect Management Active: No I 13:32:59 BD-R Verify Not Required: Yes I 13:32:59 Link Size: Auto I 13:32:59 Lock Volume: Yes I 13:32:59 Test Mode: No I 13:32:59 OPC: No I 13:32:59 BURN-Proof: Enabled I 13:32:59 Write Speed Successfully Set! - Effective: 8,991 KB/s (2x) I 13:33:31 Filling Buffer... (40 MB) I 13:33:36 Writing LeadIn... I 13:33:37 Writing Session 1 of 1... (1 Track, LBA: 0 - 16496223) I 13:33:37 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 16496223) I 13:33:37 Writing Layer 0... (LBA: 0 - 12219391) I 14:20:15 Writing Layer 1... (LBA: 12219392 - 16496223) I 14:36:53 Synchronising Cache... I 14:36:57 Closing Track... I 14:36:58 Finalising Disc... I 14:37:14 Exporting Graph Data... I 14:37:14 Graph Data File: C:\Users\Administrator\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH10LS30_1.02_TUESDAY-FEBRUARY-09-2021_1-32_PM_MEI-T02-001_2x.ibg I 14:37:14 Export Successfully Completed! I 14:37:14 Operation Successfully Completed! - Duration: 01:04:14 I 14:37:14 Average Write Rate: 8,693 KB/s (1.9x) - Maximum Write Rate: 9,061 KB/s (2.0x) I 14:37:14 Cycling Tray before Verify... W 14:37:23 Waiting for device to become ready... I 14:37:44 Device Ready! I 14:37:45 Operation Started! I 14:37:45 Source Device: [3:0:0] HL-DT-ST BD-RE BH10LS30 1.02 (E:) (ATA) I 14:37:45 Source Media Type: BD-R (Disc ID: MEI-T02-001) I 14:37:45 Source Media Supported Write Speeds: 2x, 4x, 6x, 8x I 14:37:45 Image File: V:\ISO 2\WINGS_OF_THE_HAWK.iso I 14:37:45 Image File Sectors: 16,496,224 (MODE1/2048) I 14:37:45 Image File Size: 33,784,266,752 bytes I 14:37:45 Image File Volume Identifier: WINGS_OF_THE_HAWK I 14:37:45 Image File Volume Set Identifier: 02E50775 WINGS_OF_THE_HAWK I 14:37:45 Image File Application Identifier: ScenaristScenaristBD I 14:37:45 Image File Implementation Identifier: ScenaristScenaristBD I 14:37:45 Image File File System(s): UDF (2.50) I 14:37:45 Read Speed (Data/Audio): MAX / MAX I 14:37:46 Verifying Session 1 of 1... (1 Track, LBA: 0 - 16496223) I 14:37:46 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 16496223) I 14:37:46 Verifying Layer 0... (LBA: 0 - 12219391) I 15:24:00 Verifying Layer 1... (LBA: 12219392 - 16496223) W 15:25:39 Failed to Read Sectors 12654656 - 12654687 - Reason: Cannot Read Medium - Incompatible Format W 15:25:56 Failed to Read Sectors 12702848 - 12702879 - Reason: Cannot Read Medium - Incompatible Format W 15:26:10 Failed to Read Sectors 12739616 - 12739647 - Reason: Cannot Read Medium - Incompatible Format I 15:40:28 Exporting Graph Data... I 15:40:28 Graph Data File: C:\Users\Administrator\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH10LS30_1.02_TUESDAY-FEBRUARY-09-2021_1-32_PM_MEI-T02-001_2x.ibg I 15:40:28 Export Successfully Completed! I 15:40:28 Operation Successfully Completed! - Duration: 01:02:41 I 15:40:28 Average Verify Rate: 8,774 KB/s (2.0x) - Maximum Verify Rate: 9,639 KB/s (2.1x) I 15:45:27 Close Request Acknowledged I 15:45:27 Closing Down... I 15:45:27 Shutting down SPTI... I 15:45:27 ImgBurn closed! ;
  20. dbminter

    Any negatives to increasing buffer size ?

    I can't answer the buffer question (Typoed bugger at first! ) but I can answer the Pause one. The pause function is a sub feature of the red cancel button. When you press the red Cancel button during a burn, you're offered 3 choices: to Cancel, to Pause, and to Resume. However, it is NOT advised to Pause a write function as most of the time, writing cannot resume properly and you've effectively wasted a disc. I believe if you select the Pause function, ImgBurn tells you it may not properly resume writing.
  21. My IMGBurn is set to 80MB buffer and has been for the last 10+ years I have used it. I don't normally notice buffer issues but today I was burning to a DVD drive and BD drive at the same time from the same HDD and the buffer kept running out every 30 seconds or so on the blu-ray disc. I was burning the BD in IMGBurn and the DVD via my Bravo 2 PTPublisher. I realise burning 2 devices from the same hard drive is not advised, but this made me curious, given I have 32GB ram would increasing the buffer to the max 1gb help in these incidences when I forget ? For instance today I forgot I was burning from the same HDD (I use a drive pool to form a single drive letter from multiple HDDs, sometimes the ISO's end up on the same drive) and so once the BD was started I couldn't change buffer or cancel without ruining a disc, so I had to let it run with the buffer (default 80MB) going up and down like a yoyo which worried me a bit. So if I set it to the max 1gb just in case this happens again, is there any negatives to this and to leaving it set to 1gb all the time ? I only ever seem to use a max of 16gb of my 32gb ram so I have 16gb spare 99.9% of the time so 1gb poached shouldn't harm me from that point of view. Can I do the same for the Build tool buffer which I use all the time as well ? Just noticed in an old post from 2007 the author of IMGBurn mentions IMGBurn has a pause button, where is this located ? Also I notice my external USB 3.0 BD Drive is showing up as USB 2.0 in the IMGBurn logs, is this normal ? Or could it be due to the 10m USB distance I have the drive at (using powered repeaters) ? Thanks for the great software.
  22. Many thanks to you both - sorted out now!
  23. dbminter

    Boot Image field in ImgBurn (Advanced tab)

    I somehow missed that Guide entirely.
  24. You know? Years ago, I predicted the death of single layer recordable discs with the advent of DVD DL recordable discs. My reasoning was manufacturers would just make the one more expensive medium since it can be used for both sizes of discs. How wrong I was.
  25. Thank you LIGHTNING UK for checking that. That helps a lot.
  26. We have a system where we write to disk when data reaches the required disk size. But we also have a setting where we have to write after certain time is elapsed. It is at this time when size can be small. As 90% of time data is written to DVD DL only DVD DL disk are bought as it is cost effective to loose a disk instead of introducing error of inserting wrong disk.
  27. LIGHTNING UK!

    Boot Image field in ImgBurn (Advanced tab)

    If you’re trying to burn an XP install CD, why aren’t you following the XP guide instead of the Vista+ one? How to create a Windows XP installation disc (bootable) using ImgBurn. https://forum.imgburn.com/index.php?/topic/11190-How-to-create-a-Windows-XP-installation-disc-%28bootable%29-using-ImgBurn
  1. Load more activity
×

Important Information

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