Errors With Toast

[TheConfuzed1]

I am running Mac OS X 10.3.7 on an 867MHz Quicksilver G4 with 1.12 GB of RAM.

I searched around a bit earlier today to see if I could find a solution for ripping some stubborn DVDs when I created this thread. It was while reading your forum earlier today that I discovered Mac the Ripper, and I was hoping that it would save me from having to using my Formac Studio TVR to copy these DVDs.

The programs that I am using are DVDBackup 1.3, DVD2oneX 1.1.0, Toast Titanium 6.0, and now Mac the Ripper 2.6.1.

I have always used the DVDBackup-DVD2oneX-Toast-combination in the past with fair success, although I would occasionally get an error with some movies in DVDBackup.

After reading some old threads earlier today, I decided to try Mac the Ripper with one of my DVDBackup-proof movies to see what would happen. I used it on The Forgotten, and I was happy to see that although I did get the "bad sector" error, the movie copied just fine.

I'm a bit reluctant to try burning the result however, after having burned four coasters in a row! I have a couple of VIDEO_TS folders sitting on my hard drive that I have never gotten around to burning (I created these with my previously successful three-program cocktail). I tried burning them in Toast and I keep getting this error:



Does anyone have any clue as to why I would suddenly get this error when I have never seen it before? I have tried burning several movies and gotten the same frustrating error four times in a row without fail!

[Frobozz]

Are you using Toast 6.0.7? If not, get the free update from Roxio. Also, you can try Save as Disc Image from the Toast File menu and then burning the disc image using the Toast Copy window. That should eliminate any verification error.

[chikanakan]

Sector 0 verification error means the disc is bad. Sector 0 is the TOC file. This happens when a DVD-RW/+RW goes bad. It could be bad media also.

[TheConfuzed1]

The media is Memorex 8x DVD-R that I bought in a 30 pack spindle. It seems unlikely that I would have four bad DVDs in a row, considering that I have used other DVDs from this spindle just fine.

[davefx]

i got this same error with a bunch of maxell CD-R's i bought. not related to your dvd's but the same error nonetheless.

turns out the discs were "almost" fine in my case, but i will not buy them again. "almost" fine means the data was all still there on the data cd-r's but the audio cd's i burned have TOC problems in cd players.

i'd try different media, like the yellow top maxell dvd's. i've had extremely good luck with those. my experience with memorex dvd media has been mixed.

[chikanakan]

Memorex is bad media. It looks like you'll have 26 more coasters. I suggest updating the drive firmware to see if it will help.

[WiseWeasel]

I've had some reports of users having this same exact problem. They were able to fix it by setting up the DVD to burn in Toast, except instead of selecting "Record", they select "Save as Disk Image" in the File menu, and make a disk image of the DVD. Then, they change Toast to Copy mode, Image File mode, drag the newly created disk image to Toast's window, and then record to DVD-R. They have to do this or verification will fail each time. Also, some users have been having problems with Toast 6.0.3 - 6.0.7 that are fixed by reverting to version 6.0. Myself, I have stuck with version 6.0, as it's been working well for me, and the versions after that gave me trouble.

[terryj]

I run Toast 6.07, and the only problems I have are with suck
media like Memorex and Sony. Stay away from those brands,
and use reputable brands like TDK, Maxell, Apple, and Tayio Yuden.

Here's a simple way to test if it is your Memorex discs..
Go out and buy ONE piece of TDK or Maxell media.
Burn the same movie with that media.
If it passes verification, congrats its the Memroex discs, return
them for a refund. If it fails on the new piece of
media, then you know it is something else, like your app.

[TheConfuzed1]

I just thought that I would tune in to say that Memorex sucks. It was the media. Memorex has made my list of things to never buy again.

[sjk]

Memorex CD-Rs are the only media to ever get stuck in my CD/DVD burners.

There's no "perfect" media; even the most reputable occasionally fails. Yep, that's obvious but occasionally it seems worth repeating when people are liberally making different recommendations.

[WiseWeasel]

Ritek/RiData are the bomb (both CD-R and DVD-R), and pretty cheap too...

[sjk]

I've had excellent results with Ritek/Ridata G04 media. I'd call it affordable or inexpensive, but not cheap.

Since upgrading my Pioneer DVR-107D firmware I've wanted to try some of their 8x G05 media... once I find a cost-effective way to ship it here.

[Ladd]

FWIW:

Toast went to version 6.0.9 earlier this month ...

[Wender]

Hi, I'm still having problems like those described here. For a long time, I have not used the "verification" option in Toast but done a full "Compare" (from the "Utilities" menu" instead, and got some interesting results. Have been using only top notch media (Ritek and Taiyo Yuden Pro):

(FIY: Compare does a full comparison of all the files on the disc).

I have two systems - one working and one apparently not:

1) 17" PowerBook with Toast 6.0.9 and OSX 10.3.8 never had any problems, all disks burn and "Compare" as identical clones. Never had ONE single error message from Toast. Exceptions are some .ifo and .bup files that Toast alters slightly if they have the wrong offsets, so this is normal I've been told.

2) A 17" iMac G4 with a Pioneer DVR-108 installed as a replacement to the Sony superdrive that died on me. Same Toast and OS. With this system I get errors with one or more .vob files that have errors - or should I say differ from the original folder on the hard drive. I have burned the same discs from the same sources off the same external HD to both systems - the PowerBook burns fine and the iMac does too, but 50% of the time there are errors during "compare".

This is scary - because you would never know this unless you bothered with a comparison of the files. No errors EVER during burning.

So get this: I used my iMac and saved as disk image instead, like WizeWeasel said. And did a "compare" of the disk mounted and the source files. Same thing: One of the .vob files (different one this time, seems to be random) had an error!! And I haven't even burned anything yet!

So what's this? Bad RAM? Bad Toast? I'm speechless... Please help!

Wender

[terryj]

try bad rip?
It is possible to get a bad rip..I had one recently with MTR
2.65 on a HEAVILY scratched PVT Copy of Ju-On i got from the local Snatchbuster. Had to take it back and go across town to another one to get a decent copy.

and yes, I did try Master Galactica's infamous soap trick
on the disc before giving up and returning it.


At this point, I would trash the disc image, re-rip,
then disc image and test again. I also assume this isn't
the "generic 2 file error" that happens sometimes
with using the Comparison option in toast.
if so, you know you can skip over that, the disc should
be fine....

[pixeljammedia]

try bad rip?
It is possible to get a bad rip..I had one recently with MTR
2.65 on a HEAVILY scratched PVT Copy of Ju-On i got from the local Snatchbuster.

Now Terryj, you know better than to rip rented discs. Shame on you. But on another note, is it better without Buffy the Social Worker? Actually, now that I think of it, you could have easily bought the disc from B@llbuster rather than rented it. Never mind.

[Wender]

Thanks for the reply, but I don't get it. Why would a bad rip show as an error between ripped files and the created disc or image?

I mean - Toast would just copy them exactly the way they are, or do you mean Toast tries to "correct" badly ripped .vob files and then they show up as different?

One more note: Third try - success. This varies even with the same source files so I don't think that's it. Some of these filesets are MD5 verified downloads of unprotected region free music DVDs.

Still puzzled...

[terryj]

try bad rip?
It is possible to get a bad rip..I had one recently with MTR
2.65 on a HEAVILY scratched PVT Copy of Ju-On i got from the local Snatchbuster.

Now Terryj, you know better than to rip rented discs. Shame on you.

And you PJ, no better than to read than to insert both feet in your mouth without any mustard...


Again, for the benefit of those who didn't read it the first time...

I had one recently with MTR
2.65 on a HEAVILY scratched PVT Copy of Ju-On i got from the local Snatchbuster.

again slowly for the class:

HEAVILY
SCRATCHED
PVT ( as in Previously Viewed Tape/DVD, bought and paid for)
Copy of ju-On.

And as for Japanese vs. American remakes, I always seek out/prefer
the originals to our shoddy attempts at cashing in on the coattails
of far superior beings.

but, I have to admidt, Naomi Watts in The Ring is comparable to
the original Ringu, but not quite.

As for SMG, what's up with her choices in movies since Buffy ended?
It makes me wonder did we all just imagine she could act for 7 seasons
on BTVS?

[terryj]

Thanks for the reply, but I don't get it. Why would a bad rip show as an error between ripped files and the created disc or image?

I mean - Toast would just copy them exactly the way they are, or do you mean Toast tries to "correct" badly ripped .vob files and then they show up as different?

Still puzzled...

The "correction" could come either between your shrinking software
(DVD2ONEX or Popcorn) and what it does to the files it CAN'T read.
Surely it's not hard to theorize that, if you rip a DVD, and the DVD
has bad sectors, that MTR is still going to try and rip the disc complete
bad sectors and all, and that Popcorn or DTOX would ignore the bad sectors, making the disc structure not as complete as the bad MTR rip,
and thus cause your verification to fail?

Have you tried a very clean disc just make sure?
Try something new or something that hasn't got played as much,
and follow all steps through to see if it happens thus.

Other things that might be possible:

Time to clean the lens on the Burner, too much dust
Time to switch media, you could have a bad batch

Stop burning internet Downloads, and try authoring
something to see if it happens on self-authored projects.
IF it does, then it may point to hardware, rather than software.

If your rips aren't being ran through DTOX or Popcorn before
going to Toast, then it more than likely points to either
media or your burner as the culprit that's causing the verification to fail.

[Wender]

If your rips aren't being ran through DTOX or Popcorn before
going to Toast, then it more than likely points to either
media or your burner as the culprit that's causing the verification to fail.

Well - it's neither and that's exactly the problem. Not running anything through DTOX or Popcorn and NOT BURNING AT ALL makes the same errors appear.

VIDEO_TS folder verified with .md5 checksum, saving as Disc Image in Toast, mounting that image and then doing Compare of the two VIDEO_TS folders. Data mismatch with some .VOB files 50% of the time. Repeating the exact procedure may not generate any errors. It's not the burner because I haven't even burned it yet!

Where's the ghost in my machine???

[terryj]

ok, your still not following me:

I'll quote myself so hopefully we can get to the bottom of this:

Stop burning internet Downloads, and try authoring
something to see if it happens on self-authored projects.
IF it does, then it may point to hardware, rather than software.

I believe there is NO GHOST IN YOUR MACHINE,
UNLESS YOU COUNT THE ONE YOU DOWNLOADED.

Does that make it clear enough for you?


To weed out the problem, you have to be willing to
take the necessary steps to find the "ghost in the machine".

You say you are not burning: So that rules out Toast
( for the most part), it also rules out DTOX and popcorn.

You are not ripping these files, so that rules out MTR, your DVD burner, and possibly your oS.

What's left?

Some of these filesets are MD5 verified downloads of unprotected region free music DVDs.

Create something NEW and by mean NEW I mean NOT DOWNLOADED, on your mac. use iDVD, Toast,
whatever to author it. Then do the compare in Toast.
I bet you find that they match on the dollar.

So the problem will then be your DOWNLOADED MOVIE
TS folders.

How to fix: numerous ways, but the easiest :
RE-AUTHOR them.

[Wender]

Hi,

Thanks for taking your time and effort to reply. I seriously think I can get to the bottom of this.

Maybe I haven't made myself clearly enough: This happens to VIDEO_TS folders I have downloaded, yes. Maybe not authored correctly, yes. Still doesn't make sense they compare OK after copying (making Disk Image I mean) and sometimes they don't compare OK.

Second, I have authored 10+ VIDEO_TS folders myself in iDVD starting out from iMovie and added menues etc in iDVD. Same thing happens, and repeating it makes these errors. However, it may be error free on first attempts sometimes.

Secondly: Doing all these things, including from downloaded VIDEO_TS folders, have yet to produce ONE error while doing the exact same thing on my 17" 1,5Ghz PowerBook. Now that's strange don't you think?

Additionally - I have quite a few audio files as .shn and .flac files. Verifying these doing .md5 checksum with xAct or just veryfying the .flac file sets will report errors maybe half the time using my iMac. Running the same test again may produce errors with some other files than the first run, then the third time doing the exact same thing, it finally checks out OK.

Doing these verifications using xAct on my PowerBook NEVER fails. Haven't seen it once.

Now that's why I'm suggesting a ghost in the machine...

I have done every described maintenence routine I know about on my iMac. Now I am actually backing up 200+ GB of stuff from my HD just to do a full zero all data and reinstalling my system. Did run Tech Tool Pro but it could not find one single error. So that's why I'm doing this now.

Being a Mac user since 1987, this is the worst and most annoying problem I have ever encountered.

Wender

[chikanakan]

Toast must fix the offsets of the VIDEO_TS folder. If you create an image in Toast and then mount it and compare the original, they will will not be the same. The Toast image is correct. MD5 check sums are worthless in this cause.