laserfan
-
Posts
169 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by laserfan
-
-
Excellent, many thanks LUK for this detailed explanation. I'm going to add it to the "Self Help" file I keep on this stuff!
-
1. Best is to cut between two VTS...
Oh, yes I get it now.
2. Looks to me as the VTS_04 holds no video. Might be a fake VTS that's been removed during the rip...Well it's not a rip, but a VIDEO_TS I made myself using a program called AVStoDVD, and yes it has a menu, then multiple TV episodes. But what is odd to me about ImgBurn's display is that there is no actual file called simply "VTS_04" in the titleset, just two VOBs specifically VTS_04_1.VOB and VTS_04_2.VOB. So I'm not sure why ImgBurn lists it at all, unless it is some peculiarity of the authoring method used by AVStoDVD.
No matter I guess, it's just that I burn DL DVDs so seldom that this display puzzled me to want to understand it better.
-
Presented with the "Create Layer Break Position" dialog for a DL DVD burn, I have 4 green stars (Excellent) to choose among for my layer break, but for only one of these is the "Preview Selected Cell" available; for the other 3 this button is greyed-out--apparently only lines with "Start Times" can be previewed:
50/50 VTS_03_0.BUP N/A... 50/50 VTS_04_0.IFO N/A... 50/50 VTS_04_1.VOB N/A... 50/50 VTS_04 N/A 1 1 1 1/1 00:00:00 No
Note the last two are shown as the same LBA of 2027402 -> 2027408, but only the very last line item was available to Preview. Questions:
1. Given the first three don't have any Video to Preview, should e.g. the BUP be the best choice? Indeed it appears these are listed in order of desirability? That to have the layer change at a BUP or IFO is ideal cuz no video?
2. These VTS_04 that appear to be referring to the identical file are confusing to me. If these were the only two choices, would it be best to choose VTS_04_1.VOB? What's the diff with the next line VTS_04 in this context?
Thanks in advance for any enlightenment.
-
Change if from Max to whatever you want.
Ha, ha! I hafta say, "hiding in plain sight"!!!
Thanks.
EDIT: I have to mention another nice feature of IsoPuzzle: the ability to pause-and-restart a rip. So if the current Read Speed is not working (or any other setting for that matter) we can only Abort and start-over from scratch.
-
1. Get a fan for the reader, even if I doubt it will impact the reading.
2. Already there
1. I would argue that the drive just has to suffer if you let it read for hours & hours (& hours)
2. Please tell! (I can't find any read speed settings)
-
I just had a great success using IsoPuzzle to recover a BD that had developed Read problems. Although I can't be certain of it, after several days of using several drives off-and-on (getting some sectors to read-back with most tries), and still having some 800,000 sectors left to recover, I tried launching Nero DriveSpeed in the hope of altering the read speed of my SATA drive to gain more readability. It appeared it was not working, but then I suddenly got all 800,000 sectors to read. A perfect ISO. Then I noticed DriveSpeed was still running-but-minimized. Dunno if DriveSpeed did the trick, but like the idea of adding to ImgBurn:
1. Drive cooldown
2. Changing drive read speed
-
It would have been nice to have this in ImgBurn, but it's not exactly simple to implement this kind of functionality...
Of course, but as I understand it (and I might be wrong), it is open source code so maybe could be incorporated to ImgBurn. Glad to hear you used it; I only tried first on a BD.iso (movie) and the almost 50GB iso took several hours to make an .ecc file which is 7GB big! Won't be used for protecting against BD failures, and maybe not even your home movies!
But next I tried it on a data CD (700Mb) and took maybe only a minute to make the .ecc file, and that file was "just" 94.5Mb which is not too painful to keep on a hard drive or flash disk.
AFAICT it only makes .ecc files from ISOs, therefore if starting from scratch you have to make an ISO first, then separately burn the disc, as well as separately make the .ecc file (from the ISO) for safekeeping. Fiddly stuff.
Another reality of the program is that if a disc's readability gets too bad, the ecc file/correction may not work, so it's suggested to check the discs once in a while for level of errors.
In any case it might be nice to have it built-in to ImgBurn such that to make a data disc you drag/drop the files, then ImgBurn makes an ISO as a temp file, creates the .ecc from same, then burns it, in one-click. Well, we could hope...
-
Found a bad data CD in among my backup discs the other day, and used IsoPuzzle to get most of it back. In searching here prior to suggesting adding a cooldown feature like IsoPuzzle to get past these unexpected CD/DVD/BD readability problems, I found mention of an even better idea, the DVDisaster ECC data creation method. Apparently you can create the CD/DVD/BD disc with ECC data embedded, or (much better IMO) create an outboard ECC datafile for your CD/DVD/BD that you keep safely somewhere else, and if your CD/DVD/BD develops readability issues you can use the ECC file you made & stored way-back-when to recover your data.
I imagine LUK that you know about this already--if you've ever considered a "Pro" version ($) of your program I for one would surely pay for such an enhancement! Or is there some fatal flaw in the concept??
I'm going to give that program a try to see how it works, but it seems on the surface to be a natural for ImgBurn which is already the best burning software in existence!
-
You're doing something wrong, or the player is at fault. I have used ImgBurn to write BDMV/CERT folders to BD-R, DVD-R RW, DVD+R, and even CD-R and they all play on my various Blu-ray players.
-
Different buffer
That one is on the I/O tab, page 2.
Thanks LUK!
-
I changed this setting today, under the Build tab Page 2, from 40 MB to 80 MB. But in my burn logs I still see 40 MB e.g.
...
I 16:58:47 BURN-Proof: Enabled
I 16:58:47 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x)
I 16:58:47 Advanced Settings - Optimal Writing Speed: No
I 16:59:05 Filling Buffer... (40 MB)
I 16:59:07 Writing LeadIn...
I 16:59:08 Writing Session 1 of 1... (1 Track, LBA: 0 - 2286863)
I 16:59:08 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2286863)
I 17:13:23 Synchronising Cache...
I 17:13:24 Closing Track...
I 17:13:26 Finalising Disc...
...
Is this not where I would see the setting change that I made?
-
Just try some different media. Your problem is likely a mismatch between your burner and the media, although it is possible I suppose that the cake is all bad.
I have had "synchronizing cache" problems myself, but whenever it's happened to me, it's been clearly the fault of a couple of discs in a cake. Indeed, I posted about this problem not too long ago, which I had with the first two or three discs in a cake, and since then the rest of the cake has burned just fine.
Ritek does not suck like it used to, but clearly your burner doesn't like them.
-
Well if the discs burn without errors and play, then maybe you shouldn't argue with success!
Others here will know better than I, but the "Waiting..." messages suggest to me that your PC gets busy doing something else, or maybe your hard drive is badly fragmented. Do a Disc Check on all drives, and clean-out all temporary files and junk, and then run Defraggler to see how bad they are (and to fix if needed).
Next I suppose you should give us all PC specs including drive loading.
-
Might be that the other program is using Immediate I/O in another way. You could try to enable that setting in the I/O tab. You can read more about it in the guide.
Thank you, Cynthia, though I must admit I'm not sure I understand the guide verbiage as it seems to have more "double negatives" than my brain can absorb. If my setting is at Default (unchecked/Disabled) then that means the 2nd i.e. "It's then down to [imgBurn] to figure out when the drive has finished performing the [synchronizing cache] function"? Indeed it appears that ImgBurn keeps trying & trying forever and the green access LED is steady lit on my drive until I power-down the PC and restart.
I'll try it and report back if it fixes the problem.
# Don't Use Immediate I/OThe Immediate I/O only comes into play when sending the Erase/Format Disc, Sync Cache, Close Track, Close Session and Finalise Disc commands. They're the only ones where the program really has to 'wait' for it to finish.
When this setting is enabled, the drive performs the function associated with the command before returning control to the program.
When the setting is disabled, the drive just validates the command before returning control to the program. It's then down to the program to figure out when the drive has finished performing the function associated with the command.
By not using it, there is no way to provide the user with any sort of progress % feedback etc as the drive only returns control to the program once it's totally finished. Normally the drive just validates the command and then returns control to the program - the program then polls the drive to see if it has finished and picks up the progress info along the way.
If you encounter an error like this one:
W 00:00:00 Potential 'WaitImmediateIO' Deferred Error - (99%, 0/3) - Program Memory Area Update Failure
it might be a good try to enable this setting.
The default setting is 'Disabled'.
-
I just went with IsoRecorder instead. Seems to work fine. Maybe W7 Pro iso is incompatible with ImgBurn....or I made a crucial mistake somewhere. Either way, problem solved.
I'm a very long-time user of ImgBurn and just had several bad burns in a row where I too stuck at "Synchronizing cache" with errors identical to the OP. In examining these Verbatim MCC-004-00 DVD+R (AZO) discs there appears a very slight "ripple" in the sublayer at the very outermost edge as if I got a bad cake (100 discs!) though I haven't looked at all of them yet. This apparent defect does however appear well-outside the range of the burned data (4,686,774,272 bytes of a total 4,700,372,992) as is evident from where the burned area stops and the "ripple" appears. It almost seems, if I understand the "synchronizing cache" thing correctly (that it's writing the last bit of data from memory to the drive) that ImgBurn wants more than it needs i.e. all of this last area to be perfect? Is it attempting to write more than I've asked? Opened another cake of these same discs and they appear perfect and indeed burned perfect with this same program.
I resurrect this thread because after making the several bad burns with this media I DL'ed BurnAware Free and it burned the program without issue and verified-and-plays just fine (Blu-ray program on DVD disc for playback on BD settop players), as IsoRecorder apparently did for the OP. So why do these other burners work and ImgBurn does not... I'm raising this again only because I thought it might trigger some thought on the part of LUK or other experts here as to what these (many, compared to other) incidents reported here might be about, and I can probably reliably test any new settings or fixes with this cake that I have. Yes, I've seen this "Stuck at Synchronizing cache..." problem in the past, but so seldom as not to concern me as at least DVD+R discs are cheap these days.
I don't have a bad burn log (looks like the OP's, then when I abort the software hangs with the drive light on and I have to reset my computer; nothing gets saved to the ImgBurn log!) but here's a good one (of this same program on a good DVD) if you want it. Again, if there are any settings you'd like me to try I'd be glad to do so as it seems I have some discs that can be counted on to yield to this issue.
; //****************************************\\ ; ImgBurn Version 2.5.5.0 - Log ; Friday, 04 March 2011, 19:29:15 ; \\****************************************// ; ; I 17:48:46 ImgBurn Version 2.5.5.0 started! I 17:48:46 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7600) I 17:48:46 Total Physical Memory: 8,387,752 KB - Available: 6,997,828 KB I 17:48:46 Initialising SPTI... I 17:48:46 Searching for SCSI / ATAPI devices... I 17:48:46 -> Drive 1 - Info: PIONEER DVD-RW DVR-109 8.58 (F:) (ATA) I 17:48:46 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (V:) (SCSI) I 17:48:46 -> Drive 3 - Info: HL-DT-ST BD-RE GGW-H20L YL05 (G:) (ATA) I 17:48:46 -> Drive 4 - Info: HL-DT-ST BDDVDRW GGC-H20L 1.03 (H:) (ATA) I 17:48:46 Found 1 DVD±RW, 1 BD-ROM/HD DVD-ROM, 1 BD-ROM/HD DVD-ROM/DVD±RW and 1 HD DVD-ROM/BD-RE! I 17:49:03 Operation Started! I 17:49:03 Building Image Tree... I 17:49:03 Calculating Totals... I 17:49:03 Preparing Image... I 17:49:03 Contents: 9 Files, 14 Folders I 17:49:03 Content Type: BD Video I 17:49:03 Data Type: MODE1/2048 I 17:49:03 File System(s): UDF (2.50) I 17:49:03 Volume Label: NUTCRACKER I 17:49:03 Size: 4,685,879,392 bytes I 17:49:03 Sectors: 2,288,032 I 17:49:03 Image Size: 4,686,774,272 bytes I 17:49:03 Image Sectors: 2,288,464 I 17:49:03 Operation Successfully Completed! - Duration: 00:00:00 I 17:49:24 Operation Started! I 17:49:24 Building Image Tree... I 17:49:24 Calculating Totals... I 17:49:24 Preparing Image... I 17:49:24 Contents: 9 Files, 14 Folders I 17:49:24 Content Type: BD Video I 17:49:24 Data Type: MODE1/2048 I 17:49:24 File System(s): UDF (2.50) I 17:49:24 Volume Label: NUTCRACKER I 17:49:24 Size: 4,685,879,392 bytes I 17:49:24 Sectors: 2,288,032 I 17:49:24 Image Size: 4,686,774,272 bytes I 17:49:24 Image Sectors: 2,288,464 I 17:49:26 Operation Successfully Completed! - Duration: 00:00:01 I 17:49:26 Operation Started! I 17:49:26 Source File: -==/\/[bUILD IMAGE]\/\==- I 17:49:26 Source File Sectors: 2,288,464 (MODE1/2048) I 17:49:26 Source File Size: 4,686,774,272 bytes I 17:49:26 Source File Volume Identifier: NUTCRACKER I 17:49:26 Source File Application Identifier: ImgBurn v2.5.5.0 I 17:49:26 Source File Implementation Identifier: ImgBurn I 17:49:26 Source File File System(s): UDF (2.50) I 17:49:26 Destination Device: [1:1:0] PIONEER DVD-RW DVR-109 8.58 (F:) (ATA) I 17:49:26 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 4x, 6x, 8x, 12x, 16x) I 17:49:26 Destination Media Sectors: 2,295,104 I 17:49:26 Write Mode: DVD I 17:49:26 Write Type: DAO I 17:49:26 Write Speed: 8x I 17:49:26 DVD+R Reserve Track: No I 17:49:26 Link Size: Auto I 17:49:26 Lock Volume: Yes I 17:49:26 Test Mode: No I 17:49:26 OPC: Yes I 17:49:26 BURN-Proof: Enabled I 17:49:26 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x) I 17:49:26 Advanced Settings - Optimal Writing Speed: No I 17:49:46 Filling Buffer... (40 MB) I 17:49:48 Writing LeadIn... I 17:49:48 Writing Session 1 of 1... (1 Track, LBA: 0 - 2288463) I 17:49:48 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2288463) I 17:57:11 Synchronising Cache... [color="#FF0000"]<---RIGHT HERE IS WHERE MY SYSTEM GETS STUCK WITH THE "BAD MEDIA" THAT BURNAWARE FREE BURNS JUST FINE![/color] I 17:57:12 Closing Track... I 17:57:15 Finalising Disc... I 17:57:38 Exporting Graph Data... I 17:57:38 Graph Data File: D:\video\PIONEER_DVD-RW_DVR-109_8.58_MCC-004-00_8x_NUTCRACKER.ibg I 17:57:38 Export Successfully Completed! I 17:57:38 Operation Successfully Completed! - Duration: 00:08:11 I 17:57:38 Average Write Rate: 10,355 KB/s (7.5x) - Maximum Write Rate: 11,445 KB/s (8.3x) I 17:57:38 Cycling Tray before Verify... I 17:58:05 Device Ready! I 17:58:06 Operation Started! I 17:58:06 Source Device: [1:1:0] PIONEER DVD-RW DVR-109 8.58 (F:) (ATA) I 17:58:06 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: MCC-004-00) (Speeds: 4x, 6x, 8x, 12x, 16x) I 17:58:06 Image File: -==/\/[bUILD IMAGE]\/\==- I 17:58:06 Image File Sectors: 2,288,464 (MODE1/2048) I 17:58:06 Image File Size: 4,686,774,272 bytes I 17:58:06 Image File Volume Identifier: NUTCRACKER I 17:58:06 Image File Application Identifier: ImgBurn v2.5.5.0 I 17:58:06 Image File Implementation Identifier: ImgBurn I 17:58:06 Image File File System(s): UDF (2.50) I 17:58:06 Read Speed (Data/Audio): MAX / MAX I 17:58:06 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2288463) I 17:58:06 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2288463) I 18:04:33 Exporting Graph Data... I 18:04:33 Graph Data File: D:\video\PIONEER_DVD-RW_DVR-109_8.58_MCC-004-00_8x_NUTCRACKER.ibg I 18:04:33 Export Successfully Completed! I 18:04:33 Operation Successfully Completed! - Duration: 00:06:27 I 18:04:33 Average Verify Rate: 11,826 KB/s (8.5x) - Maximum Verify Rate: 17,314 KB/s (12.5x) I 19:29:15 Close Request Acknowledged I 19:29:15 Closing Down... I 19:29:15 Shutting down SPTI... I 19:29:15 ImgBurn closed!
-
As LUK said, to build a valid Blu-ray disc structure, you need Authoring software. Do a search on "blu-ray disc authoring" or some such to get yourself educated, or find a multiAVCHD discussion and start reading! Consumer software to do this is available from many companies e.g. Sony and Corel/Ulead etc.many tnx for reply. as i said, this is new to me so experimenting atm. dont quite understand what you mean so could you be a bit more specific? sorry to sound so dumb.Edit: oops LUK beat me to it...
-
Just visiting a website on a non-updated machine can get it infected.
Indeed, I was using Firefox myself just yesterday and suddenly a boatload of scary-looking windows displaying "trojans" and "viruses" that I was supposedly infected with, and a very official-looking (with Windows logos) dialog to remove those problems. I closed Firefox and checked my PC (first w/Defender, then I installed MSSE and checked again) and the incident was a false alarm, though if I had clicked on one of the "clean" buttons I'm sure all hell would have broken loose.
Was using Firefox 3.6.10 and now updated to 3.6.11--not sure if FF security hole was to blame or not.
-
What I need from my scanner software is the ability to select specific portions of a field to scan in. My old scanner, a OneTouch Visioneer 8100, had this ability.
I'm not sure what you mean by "specific portions of a field"? I have the recent Visioneer Strobe 500 with their OneTouch 4.6 software (and PaperPort from Nuance) and the OneTouch software has a feature called "Redaction". With redaction, you specify areas to NOT SCAN, and can fill these-in with a color, as many as you want. So I imagine if you want a specific area on a page to scan, you can specify white for as many rectangles as you need to isolate the scanned area.
-
They're all the same - I've just snooped on the I/O from the other two to double check... Using Verify mode would be better than Read mode... no reason to make an image if you don't need it!
I had looked quickly at Verify but didn't think to uncheck the "Verify image" box--now I see what you are saying! Running a Verify (Against Image File: No) right now using ImgBurn!
Yeah I knew about the "bad sectors" thing but am glad you mentioned it again. I really appreciate your response to this LUK!
-
Alot of times I buy a commercial DVD or BD disc and then don't watch it for a while. I would like to unwrap the disc when I get it and then test it to make sure it is fully "readable" so that, if not, I can exchange it at the place-of-purchase. There are at least 3 programs I already have on my PC that appear to be able to do this:
1. Read with ImgBurn i.e. try to copy the disc to my hard drive and see if there are any errors in doing so
2. Perform a ScanDisc with Nero DiscSpeed 5 (the latest, I think)
3. Use DVDInfoPro and select the CRC Read Errors test
Does anyone here know the difference(s) between these programs' methods of reading the discs? Is any "test method" superior to any other? Is there a better way, or better program, than any of the above?
-
Another ImgBurn capability I didn't know about. Thank you--amazing program!
Do you determine the exact number of sectors that your files will need, and then put-in to that setting "total disk sectors minus file sectors needed"?Yup.
Use the the 'Calculate' button to get the normal size (in sectors) of the entire image (with that setting on 0), then adjust the value to suit.
-
This was all I could find about this:
File System PaddingAnything that's not divisible by 16 (sectors) will be padded by the drive when you burn to DVD+ media.
The default setting is '0'.
So how is the OP's interest fulfilled? Do you determine the exact number of sectors that your files will need, and then put-in to that setting "total disk sectors minus file sectors needed"?
-
Plays-back perfectly, so all SEEMS ok with the disc but it does make me wonder about the media. :wringshands:
-
Opinions please.
Hmmm doesn't anyone know what those "squigglies" denote?
Problem in Burning Ritek SO 4 Write Error
in ImgBurn Support
Posted
FWIW I have been using that Ritek media with very good success at 4x (it's 8x media but my drive only supports 2.4x and 4x). But I think it might be relatively new so you should start by updating yr drive's firmware. If it appears to be supported media (look at Supported Write Speeds under ImgBurn's Device tab) then try every speed. If none works you are SOL with that drive.