Star Wars Episode 2 Problem Ifoupdate to blame?

[Elbart0-]

After doing the Big3 guide for the first time on region 2 Star Wars Episode 2 everything went well. Or so I thought as it played perfecly in powerdvd I burnt it and now going to watch it on my standalone it refuses to load. All that comes up is "2" on LCD. I'm pretty sure this is a ifoupdate problem at first I used the version in the guide (6.7) but this causes a chapter problem. Now using version 7.8 it all apears to be fine untill trying it on a standalone. I also tried get vts sectors in ifoedit after I did it in ifoupdate and although this did change a few things it still didn't fix the problem. There are some options in 7.8 not shown in the guide is it likely any of these should have been ticked? Any help would be greatly appreciated.

Thanks Elbart0.

[jel]

hmmm...you have been around the forums long enough for there to be no need to mention media ... but ... my first thought would be bad media ;) or the burning program?

second thought, is that you may have stripped something that has messed up the navigational structure, which powerdvd ignores but your stand alone (being more sensitive to these things) will not.

third thought is that you may have incorrectly updated a ifo that was not encoded/re-authored.

have you tried playing the burnt disc in your pc?

in my experience if you have used ifoupdate correctly then any playing issues are usually a result of another factor but if you can provide further details we may be able to find a solution

hope that helps

j

ps i know other forum members have sucessfully backed up this movie, and may be able to help with particular issues/solutions they encountered.

[Eyes`Only]

My guess is the burning app...

[Chubmeister]

This won't be much comfort, but in defense of ifoupdate, I suspect it will not be to blame.

I often edit things so that the DVD loads up the root menu and skips those annoying warnings or intros (using 2cools cheat sheets), however if I have messed with the structure in any way then I burn onto a RW first because I have noticed that it may play perfectly well in ifoedit or pc playing software but wont load onto a standalone.

Take a fresh rip of original ifo's, bups and VOB_X_0's again to your final directory and try ifoupdate again, you shouldn't need to make any changes to the default settings.

I guess I'm saying use a rw disk first, whats another 30mins if you've spent all day encoding a great quality back-up?

Chubs

Oh, one more thing to try, although the disk won't play in your standalone, can you make it load if you press menu? If it does then it probably was a mistake you made with ifoupdate, if it still won't fire up then it is more likely down to the burning software as suggested.

[influenza]

I'm curious if this is maybe an infamous pause (black screen waiting for you to press play/fast forward on the remote). If the disc does continue when doing this search the knowledge base on the dif4u hompage, keyword pause

[Elbart0-]

I've ruled out the media (datasafe dvdrw) as I put another movie on it and that works fine. Also ruled out the burning app (prassi) as the problem. I even tried copying the original exacly and just removed the last 3 main movie vobs so it would fit on the disc. Although the hole dvd isn't on the disc it is to my understanding that the dvd should still work and load up the menus etc. Which is doesn't and gives the same problem. :confused: Before anyone asks yes the original dvd plays pefectly fine. :) As for pressing play/menu etc I've tried that and it doesn't do anything.

[Eyes`Only]

try imgtool and dvddecrypter

[kheops]

my r2 dvd is multiangle (for the well known star wars scrolling at the beginning, text is english or french)
make sure this part of your rip is ok

my 0.02 :)

[Elbart0-]

In the end I just gave up and changed the pre command to load the menu first and this seems to have fixed it. Thanks to all for your help I'll know what to do in future if it happens again. :)

[influenza]

That certainly sounds like a restricted cell problem

[Eyes`Only]

yeah i kind of does, but really the 'symptom' is described too vaguely to do anything with