Shoot Em Up + 3:10 to Yuma

Lol. A major rule to remember,

"The less a man makes declarative statements, the less apt he is to look foolish in retrospect.

 

I'm a newb to posting, but have found great useful info here.
I have been trouble burning the last few movies, haven't really had issues before. I was able to burn Shoot Em UP, but had to download the DVDDecrypter. I usually just use AnyDvd, DvDShrink, and Nero7; that has worked.
Now I have read the 5 pages here on burning 3:10 to yuma and read the guide section, but no where is it saying how to shrink the main movie down since it is 2 hour 2 mins long. It is like 5250 mb and I need it down. I have never dragged a title before over to the left as the guide illustrates, that is all new to me. I usually can by custom ratio and what not, but the main movie is at 98% and I can't shrink it down from that.
Any help would be appreciated.
Thanks for the previous words of wisdom from this board!

 

With this movie, after ripping with DVD HD FAB Decrypter, before using Shrink, you must run it through FixVTS. Then Shrink will shrink it. Why...I don't know. Must be the encryption in 3:10 to Yuma. I did notice that DVD HD Fab Decrypter has a later version, 4.0.5.0 just released today. Maybe that fixes this issue. Don't know.

 

I am sorry, I forgot to mention I did try running through Fixvts.
However, when I go to the folder to open up the Video_TS file, it isn't not there. The VOB file isn't, but the IFO file shows up in the folder.
I've run it through DvdDecrypter like 5 times to see if I can get the Video_TS.vob file, but it doesn't show in the folder that is on the HD. I can view it when I open the disc in Fixvts, but not the folder on the HD I copied 3:10 to Yuma in.

In this guide it says to use the Video_TS.VOB, but I can't see it:
http://webpages.charter.net/bacitup/TheGuides/Back up DVD w fab,vixvts,shrink,imageburn.pdf

However, in this guide it shows to use the VTS_01_0.VOB file:
http://forums.afterdawn.com/thread_view.cfm/494836

**Well I read the later one again, and tried that. It seems Fixvts is working this time.**
I'll give shrink a go and try Nero to burn, if not I'll try ImgBurn for the first time.
Thanks for all the comments and links that allowed me to read up and gain more knowledge that I wish I had previously known.

 

I tried dvdfab decryptor but it was terribly slow and got hung at 14% complete. While searching for dvdfab hd decryptor beta (todays version) I came across DVDFab Platinum v4.0.4.0 Beta instead. This got me through the process flawlessly. Tested on dvd player and saw no problems. Hope this helps



edit** the movie Im referring to is 3:10 to Yuma

 

I was able to burn it. Just was hung up with Fixvts for some reason. But coming here and doing more research I figured it out.

 

@nemesees and escapest

glad you guys got it.

Rip, burn, and conquer!

 

Regarding 3:10, this is what I have learnt from info supplied to posts at another Forum. RipIt4Me will work but apparently, unless you are like me & create a folder with the movies initials before rip & use that as your destination target, it will fail because of the label, (I think shades of "Blades of Glory). The new version of DvdFab HD Decrypter apparently solves the Dvd Shrink problem, which apparently wasn't a problem because if you used deep analysis, you could carry on with Dvd Shrink as normal. I won't name the people responsible for this info, but I still credit them with it & hopefully they know who they are.

 

For Ripit4me,
Use Wizard mode, I used Movie only
Also, be patient. In Ri4m, the create PSL step takes awhile.
Skip Step 3B.
When you get to shrink, in reauthor, you get 3 main movies, select Movie 1 (2:02)

 

dont understand the process - I ripped it with DVD fab to my harddrive by opening up and hitting start. Then with fixtvs I dragged the video TS folder on top of the fix icon. and hit run - and I get this error "couldnt open input file" - what am i doing wrong?

 

Open the Video_TS folder double click or drage the first VOB file into FixVts, then select Full Dvd.

http://www.afterdawn.com/guides/archive/fixvts_guide.cfm

 

OK - how do I open it up in shrink then? does fixtvs make other files somewhere?

 

When FixVts gets done doing it's thing it stores the backup copy in the DvdFab folder. It should be labeled FixVts Backup or something to that nature. Just open that file in Shrink, and continue as normal.

 

I have done all of that and I still have the same problem in shrink. when I try to reauthor and drag the main movie I get it still in the red and I cant get it compressed. Did I suppossed to do more if fixtvs?

 

blakeas, Try running your FixVTS folder back through FixVTS again and try to shrink the results, maybe that will work. I seem to have read that someone has done that before.

 

Remove the additional languages, and pointless extras as you own the orignial. Do a deep analysis on it first. Then you should have no problem compressing it.

 

I am having an issue with 3:10 to Yuma. I am using DVDFab 4.0.3.6 beta and it burns the disc but for some reason leaves out the first chapter. The movie starts at the second chapter. Anyone got any clue what's happening?

 

Update to beta version 4.0.5.0 Jan. 10th 2008. And try ripping main movie only.

 

as another poster said:

When using Shrink with anydvd I get a red bar at the top of the capacity area and a 98% compression number. When I try to re author I still get a red bar and a 98% compression number plus get a message saying there is not enough room, to check for automatic (which is how it's set) or reduce audio stream (which doesn't help). When I try rtipit4me I get a message (couldn't create target rip target). No problems with Death Sentence, Georgia Rule, or Resident Evil, just 3:10 to Yuma.

I just did not explain it correctly - even after all of that I did with dvd fab and fixtvs, I have my original problem as stated above.

What is going on?

 

I was having the same issue, but I downloaded the new release of FabDVD HD (4.0.5.0) and ripped it again (only movie) and Shrink is back to normal. It's correctly sized now. Try 4.0.5.0.