blutach
Beta Team Members-
Posts
5,124 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by blutach
-
Sounds like there's 16 sectors of padding. According to the log, it breaks at 2,027,968 Note - there is no need to specify an L0 landing zone for +R disks. Regards
-
Verifying recorded disc - why high CPU priority ?
blutach replied to Annoynimous's topic in ImgBurn Suggestions
I'd support this suggestion, too. Let's see what LUK says. Regards -
Ensure the MID code is MCC. Pop a blank in and fire up ImgBurn. Open the write window and look at the info in the top right. Regards
-
@Neil Wilkes If your authoring package allows, try padding L0 so it is greater than L1. Your AUDIO_TS.IFO and ATS_0X_0.IFOs will need amending in the same way that a VIDEO_TS.IFO is for padding. Regards
-
Sadly, as prices of drives have come down to meet mass market demand, the quality of them has, too. More and more, I am seeing reports of crappy drives. It's a vexing problem. Regards
-
Show MUX rate in layer break selection windows
blutach replied to fordman's topic in ImgBurn Suggestions
Tests have shown the mux rate is not that important - we initially thought it was, but clearly, it isn't as superbit DVDs use high mux rate. But, do test for seamless layer break - don't go burning 10 DLs in a row and wonder why they ALL don't work. Do one and then see. From my guide on the PgcEdit site: Regards -
L0 is the first layer L1 is the second layer the layer break occurs on the last LBA of L0 or in the example it's at 1810190. As far as a JACKET_P directory goes just copy it like any other directory into the same subdirectory as where the VIDEO_TS directory is located and it will put them both into the image when you select that directory as your source. Just to add - DVD Rom files, like Jacket_P folder should be at the end of the image. Regards
-
Great to hear. Thanks for getting back to us. Regards
-
Welcome to ImgBurn Forum! It's obviously not loading the GUI - mine shows about 18Mb. Try disabling your startup programs and then re-try. That will ID the rogue prog that is stopping ImgBurn from starting. Ensure Windoze's Data Execution Prevention is not on. Regards
-
Sounds like Little Britain - same thing happened on that one. Regards
-
Welcome to ImgBurn Forum! The cell is obviously repeated in different PGCs. Since the LB occurs at the end of a cell (ie at a physical point like a cell boundary and not a logical one like a PGC), it is quite feasible that the same cell is represented many times. However, it represents the same physical position in each of the 4 cases. The Very Good choice pertains to its quality wrt to that PGC. The others do not satisfy the same criteria in their PGCs but of course, the break is at the same spot. I hope this rubbish I am writing makes some sense. Regards
-
That is the funniest thing I have read this am !! Except for your perfomance appraisal!!! =)) Regards
-
True, but his verify errors start at 4.2 Gb and even an CMC should burn to there. Regards
-
Disc erase not done when ImgBurn 2.1.0.0 says it is
blutach replied to Relentence's topic in ImgBurn Bugs
Bugger cruley - we're supposed to find them! (Skulks away in embarrassment!) Regards -
Welcome to ImgBurn Forum! Your drive is not reading the sectors it has just written to. This is happening near the outer edge of the disk, where the media is most susceptible. Get better media - Verbatims or Taiyo Yudens. Perhaps slow your burn down as well (your max write rate was 6.3x, which is higher than your burner is rated for this media and this is right at the edge of the disk). Make it 4x. Regards
-
Welcome to ImgBurn Forum! There's lots wrong here. Your firmware is outa date - update it to 1.29 here. But that is not gunna cure all. The media you are using is not considered real good. We recommend Verbatim (MCC dye, preferably Made In Singapore) or (genuine) Taiyo Yudens. And even they are not gunna cure all if you try to burn at MAX speed on a USB drive. Slow it down - way down - 2.4X or even 1x Regards
-
Img wont finish writing - incompatible format?
blutach replied to fnbdave's topic in ImgBurn Support
Dunno how old your PC is, but USB burning has its own challenges. Burn slower - 1x or better still, bring the drive onto an IDE channel. Regards -
Of course I am! Regards
-
@LUK! Yes - I never seen one and IIRC, the spec is for them to be OTP to minimise disruption to the viewing. Lemme check and revert. EDIT: According to Taylor, PTP can be used but really only where there are 2 versions of the movie on the disk (WS/FS) (or where it is full of extras and the main flick does not cross the LB). He says, sequential playback demands OTP. For PTP, we need 2 leadins (I guess it's like 2 SL DVDs packed on top of each other). This doesn't mean that in an episodic DVD, for example, where sequential playback across the LB is usually not a consideration, the physical layout of a DVD could not be PTP. All the more reason to have files and not an ISO, IMHO. Regards