blutach

Almost all PAL players and TVs can handle native NTSC OK (patch or no patch). It's not true NTSC but is rather 60Hz PAL (which sounds a bit like an oxymoron, but is really the best way to describe it). But the display is as good as perfect (well, as perfect as NTSC can be I guess - it really is quite inferior ... but that's another discussion). Regards

Why? The VOB's mastering should point to whether this flag should be set. Regards

Just cos it's up on Digital Digest, which I obviously respect very much, does not make it technically true (although the descrption you have quoted above about interlacing and speed up is correct - anyway PC monitors could not care less about framerate). And professional studios, ensure the audio is slowed. If you are interested in the technincal details of DVD, get Jim Taylor's book, DVD Demystified. There is also a real good online reference - http://www.dvddemystified.com/dvdfaq.html Sometimes, the patch method can work for PAL-NTSC. But what I said before about framerates and resolutions is a technical fact. If you want to do this correct, you need to alter the FR and res in the VOBs, not just the IFOs - the MPEG stream needs to be correct. Techo boffins may like to use avisynth scripts (bilinear resize will get the resolution right), but there are olots of progs out there which do the job pretty well - DVD Flick and SUPER come to mind (although Procoder seems to tick every technical box every time - pricey though). Regards

Shamus' job's better - he gets to sit round and drink beer all day I'm OK and of course, Firey is giving me shit all day How's your batting? Regards

The only things I can guarantee (other than death and taxes) is that the sun will come up in the East tomorrow. What I can say, is it is highly superior to the media you are using and I've never had a bad burn with it. Regards

If that is computed with an MD5 tool, it is exactly the same at that reported on the website. So the download is OK. As corny says, check for viruses. Regards

We can't answer any questions about decryption. DVD43 (although horribly outdated) is a decrypting tool. Please refrain from discussing decrypting on this forum!!! ImgBurn is a burning tool - it is not meant to be used a decrypter. Find something else. Regards

Most, if not all, car nav disks are written PTP and not OTP (like all dual layer media is). They can't be copied. Get a Tom Tom or a phone with a nav built in (for some reason I have both - it gets confusing when they don't agree which route to take!!!). Regards

A little bit of searching would have found the media we all recommend - Verbatim 2.4x MKM-001s. ALso, when you post a log, please post the full log of the burn, not just bits. Regards

There's no reason not to have ISO+UDF on your CD. Wondering why you only have ISO ticked. Regards

Sorry mworthngton. The patch method (as it is known) just won't cut the mustard. It alters the framerates in the VOBs not one iota. To truly convert, you need to adjust the VOBs framerates and resolutions. Regards

Get better media (Verbatim or Taiyo Yuden) and ensure your burns are verified. If you are already doing this, ensure your player's laser is clean. Regards

This is a function of really crappy basic authoring programs built into recorders/cameras. They often have redundant data. So don't expect them to be professionally authored like a commercial DVD which uses Scenarist or the like. Now if the data is the same in VTS_02_1.VOB as VTS_03_1.VOB, they are in 2 different titlesets. There's nothing that can be done other than reauthoring the redundant data out. You can't point the files at different data - this will screw up the structure of the DVD. And, as you have observed, the video might be the same, but one VTS might be full D1 (720x576 for PAL), the other half D1 (352x576). This is not the same data! (although it may appear to be so). And each VTS can only have one resolution and aspect ratio. So, right now, your choices are: 1. Author out redundant data (blanking unwanted titlesets) - VobBlanker can help you. If you decide to do this, ensure you know which data is the one you don't want. A trace in PgcEdit can help here. 2. Just burn what you have. Regards

corny, you are mistaken. That was a way to make CRC errors (basically, to take a stanley knife and etch the disk as hard as you can). Funny, they didn't grant me a patent on that one. How are you Jack - got over getting so near to the Rugger Cup yet? Regards

And audio CDs is coming in the next release. Regards

It would be considered spyware. No-one wants that for this app. If you got problems, this is exactly what this forum is for. Regards

And since when have I been helpful? Doesn't anyone read my custom user title? That is my REAL personna!!! Regards

Then buy some new DVDs. We recommend Verbatim or Taiyo Yuden. Regards

LUK! = "dude" =)) Regards

You do have the log. See the Help menu. The guides explain how to set the layer break. As for your original question, it seems the ISO has been mastered incorrectly. Contrary to your thoughts, if you had have gone ahead, I expect a coaster would have been the result. The message (which you refuse to explicitly say, nor provide a log so we can actually determine what it really was), was probably (hazarding a guess now) that there is no cell that obeys the DVD specs for setting a layer break. You may google what they are. Regards

All the more reason to use build mode (assuming the transcoders don't load up VIDEO_TS.IFO with a bit of advertising) Regards

It's a normal Ritek W01. Size 4.38Gb. And yes, something's screwed with the FS to give it a reported size like that. Regards

Yes, it always seemed a sus move for Verbatim to use MBI to make disks for it. Sad. Regards

donta asked because DVD Shrink can mess up the LB. Regards

Who said this is a democracy, Irfan? This is LUK!'s program, which he provides for free. Enough of these stupid challenges. Open the bloody log window (it stays open for the next burn, too). Regards