vob files compresser disappointment !

  • Thread starter Thread starter RJK
  • Start date Start date
R

RJK

XP Home ed.SP2 all up to date ....
Running ancient DVD2ONE, (handy little "all in one" *.vob file
compresser/authoring utility), it used to scan and reduce a ripped dvd's
*.vob files down to 4.7gb's, and create the necessary *ifo and *.bup files,
all ready for Nero, in about 15 to twenty minutes on my old Socket A
non-dual channel mobo / XP2600 Barton 512kb L2 cache-1.917ghzCPU / 768mb's
ddr333/166mhz system box.

Recently pushed that box to one side and have for a couple of weeks been
tweaking up software in my "new" (older/cheaper generation stuff!)
Conroe865PE / Intel P935 2 x 3.2ghz (2x2mb L2cache), 2 x 512mb's Crucial
DDR400/200mhz 184 pin memory running dual channel, just ran ran a DVD2ONE
sweep on a ripped film (*.vob's=6.36gb's) and it took 16 minutes ! I was
hoping for, like ...2 or 3 minutes :-) !!!!!

....old DVD2ONE utility fixed software timings/clockbound ????

....any ideas on why it took the same time on both PC's, or what I can do to
speed it up. ...have never and WILL NOT overclock anything anywhere !

TIA

regards, Richard
 
RJK said:
XP Home ed.SP2 all up to date ....
Running ancient DVD2ONE, (handy little "all in one" *.vob file
compresser/authoring utility), it used to scan and reduce a ripped dvd's
*.vob files down to 4.7gb's, and create the necessary *ifo and *.bup
files, all ready for Nero, in about 15 to twenty minutes on my old Socket
A non-dual channel mobo / XP2600 Barton 512kb L2 cache-1.917ghzCPU /
768mb's ddr333/166mhz system box.

Recently pushed that box to one side and have for a couple of weeks been
tweaking up software in my "new" (older/cheaper generation stuff!)
Conroe865PE / Intel P935 2 x 3.2ghz (2x2mb L2cache), 2 x 512mb's Crucial
DDR400/200mhz 184 pin memory running dual channel, just ran ran a DVD2ONE
sweep on a ripped film (*.vob's=6.36gb's) and it took 16 minutes ! I was
hoping for, like ...2 or 3 minutes :-) !!!!!

...old DVD2ONE utility fixed software timings/clockbound ????

...any ideas on why it took the same time on both PC's, or what I can do
to speed it up. ...have never and WILL NOT overclock anything anywhere !
Click to expand...

The bottle neck is the speed of the interface with your hard disk drive(s).
Tapping a few buttons on my trusty calculator and assuming that you have a
SATA150 drive interface suggests a best time of around 12 minutes, but life
is rarely that simple and longer is likely. Also performing the actual
compression for the .vob files is an incredibly processor intensive activity
(the video is uncompressed and then compressed again. 16 minutes is
actually quite impressive and suggests that the output quality is a bit
under par.
 
Thanks M.I.5¾,

I think you've hit the nail on the head "bottleneck," I haven't made use of
SATA - I use 2 x IDE hd's, and when I put the new motherboard, cpu and
memory in my box, I put in as primary hd a new Maxtor 160gb STM3160215A and
kept the slave Maxtor 80gb 6Y080L0
....I noticed, in the bios auto-detected hd specs. that where the much older
80gb 6Y080L0 hd, (among the rest of the specs.),
is showing "UDMA 6," the new 160gb STM3160215A is showing "UDMA 5," so
perhaps I bought a "new" OLD 160gb hd. ...and I notice it only has a 2mb
buffer, rather than the 8mb I usually hold out for !

re: the "quality" - the quality of the *.vobs / screen image, after
running a DVD2one pass on ripped *.vob's is simply VERY good, even comparing
dark sequences between the orginal factory pressed dvd and my own burnt one,
I can't see any degradation. I often wondered how DVD2one does it, and mine
is a really old version ! I like it because it does the *.vob files the
"size reduction," it also authors the thing / produces the *.ifo and *.bup
files, which saves me having to fight with IFO edit etc.

regards, Richard
 
Back
Top