Hi toots..,

Yeah, I ended up re-dvd2avi'ing. My movie "Blue Streak" was one of them
too. But, unfortunately, it took a while to do. I don't know why it takes me
forever to:

* DVD Rip - - - now @ 3.6k (instead of my past ~9k)
* DVD2AVI - - - this one takes me about an hour for each movie (or more)

All in all, I would have to wait 2 hours for a complete project. And,
that just plains sucks !! hehe..

But, I don't know what else to do. I remember my older Intel 233mhz
setup. that game me faster DVD rips - - same setup, but newer and
faster MOBO and CPU - - I'm really sumpped, and

I think my K7S52A sucks for DVD riping and DVD2AVI'ing projects !!

But, I now need to re-do "Matrix" to test again in CQM.. as you've read
above, how my faulty dvd2avi cause incorrect CQM finalization
This NEEDS to be done again, so that I can give the developer his singing
praises, I mean, glory, I mean, better results hehe hehe..
Just having fun

However, my first attempt at "Blue Streak" was a rather successful one,
I thought.. but the real test is the ENCODE the whole movie now.. so you
understand my and my 'ness decision ?

Well, let me see what decisions I have to make, and what else I want to do.
Oh, did I mention, I'm making spagetti
-vhelp

vhelp wrote:
"dvd2avi - this one takes me about an hour for each movie (or more) "

i understand


you need an hour or more to make one project with dvd2avi

hi Jorel..

Yeah, I'm w/ ya.

Oh, @ toots..
I used DVD2AVI v1.76 ( I won't use anything else !!! )

- Now, a thought has ben brewing in the back of my mind..
"Why not encode a bunch of DVD rips to divX yikes !!"
Well, why not ??
If the encode is done right, and maximum as possible, why not do this, for
testing ideas and things ie, CQM !!
I haven't tested this, but just HOW MANY movies can we encode to divX
(and w/ great quality, ie near dvd) and use those to test CQM with ??
For example, if we have a 30gig hard drive, how many whole divX encodes
can we have ?? ..5 movies, 10 movies 20 movies ??

anyone divX gurus, w/ knowledge and skills to share w/ us for divX encodes ??

Anyways, it was just an idea

-vhelp

is too much time vhelp!
i need ~5 minutes to do one project with dvd2avi176

when ripping,you wrote that got 3,6k...
better is check your aspi!
something is wrong in your system!


convert to divx from dvds
for me is not a good idea (only my opinion)
you can got space but will loose quality.

hi jorel..

yeah, hard drive space and divXing and all that stuff was just an idea,
that's all.

Anyways, as far as ASPI and all, I've never touched it. So, I don't think
it should be changed.. actually, I've never seen it

But, what really knocks me out, is the dvd2avi'ing to a .d2v file. That is
a LONG process. I remember it being MUCH faster too. And, as far as
my project needing to be in YUV for faster processing, is a lot of nonsense.
It's the same basic speed.. no improvements weather it's YUV or RGB, as
it doesn't matter. Anyways..

-vhelp

ok, I've decided to go with the encoding project.

TMPG's time estimates are 6 hours for.. here's the specs, case anyone wants
to compare w/ their projects of this same movie:

* Time index: ~6 hours
* Movie: "Blue Steal"
* Length: 94 min
* Frames: 135,430
* Audio: 112k
* Encode: MPEG-2 / 16x9 / 704x480 / CQM's CQ(89, max2000 ave995 min567)
* CDR: 1 cd @ 800mb size, for this project

I used vcalc (latest version) for the bitrate values, and let CQM v1.1.12a
to all the rest

Does anyone think it will make the 1 cdr game plan ?? CQ 89 is a rather
high value, but I'm resting in the hands of CQM for this to succeed.
Place your bets hehe..

Note, its really too bad we windows 98 users can't get a snap shot of what
the file size of our encode is during encoding, like NT and XP does

We are now passing the first 10 minute of encoding, with 5h 34m to go

-vhelp

@ all..

HAY all.. another just lit up.. I got a fabulous idea about
obtaining the filesize of the encoding project, as it is running !!

I wrote this Delphi app that computes the HD space left on EACH hd (a
project I was working on for something similar) anyways..

In short, I calculate the HD space for each drive, pending on which drive
is selected for computations

I found, that if I encode to my capture (networked) hd, that being the
only file that gets writeen to we could calculate the running jobs
filesize buy subtracting the actual hd's size. ie, 54g - 4,674,551,808
Well, anyways, I could modify my app (fmem.exe) to some degree and make
it more user friendly. In fact, I could add some features like a grid
of values ie, incremental filesize and times vs. encoding times etc.
and let it iterate in 1 minute intervals to update the grid. This could
give us windows 98 users the ability to peek inside the filesize !!
Note, this would not work under a setup if you are encoding to your Swap
file drive, cause this drive get constantly updated w/ other files and
things being writen to.

This way, we all benefit CQM in one way or another

Any windows 98 users like this idea ??
A great tool indeed!!

-vhelp

vhelp,
6~hours to do this job with athlon1800+ seems good!
but
that with CQ89, 704x480 with 94 minutes source
will give you a big final file size!

Hay Jorel..

Tell that to Kwag.. this is his prediction not mine

Note, my system is acting really caka. So, I'm getting a little worried,
but I'll hang on.

-vhelp

Kwag,
this will be big!


vhelp,
it's done!

Ok, I've ben testing this out (earlier)

And, here is what I have so far:


"Movie position" is the same as TMPG's.. letting you know how deep into
the movie you are.

The above was based on a rought estimate, because I did not start this
idea till project was encoding. So, I guessed an estimated filesize to start
with, and added 12mb to it. It's ben calculating ever since.

Now, I REALLY can't wait for this to finish, because I'll know if this works
or not

Note, I had to stop TMPG from encoding a few times (but I clicked on NO, to
resume encoding)

@ Jorel..
The 6+hours is based on my XP 1700+ ( not my other 1800+ )

@ Jorel..
Tell me, after looking at the above, what do you think about the filesize
so far ??
* too big (oh my hehe)
* too small (even worse hehe)
* just right (great)

--> <--

-vhelp

like posted,you got ~184mb for 20 minutes encoded!

after i start my "nuclear calculator" i got:
target=800mb, 94 minutes!
movie position 20 minutes=184mb!
then...

for 4 minutes=184/20*4=36,8mb
for 10 minutes=184/2=92mb
for 80 minutes=184*4=736mb

4minutes+10minutes+80minutes=94minutes
36,8+92+736= ~864,8mb final size
without audio!


vhelp,
this will be too big or my "nuclear calculator" is mad!
well,you can cut the credits and burn without audio!

(just kidding,you know)

Hi Jorel..

Sorry, I lost internet connect a few hours ago.

That pretty much sums it up for ONE HOUR though !!
So, your NUCLEAR CALC is off a bit.

Here's the final 60 MINUTE encode (I knew I'd have to stop, so I decided
to stop at 60 minutes)

Movie: "Blue Streak"
MPEG-2 / 704x480 / 16x9
Audio: 112k
Length: 94 minutes - - - (encoded only 60 min worth for this test)
Encode Mode: ES (Video + Audio)
CQ: 89
-------------------------
* Final FileSize video: 868,040mb
* Final FileSize audio: 49,309mb

Oh well, I wonder what went wrong w/ CQM v1.1.12a for this test ??
-vhelp

============================================
Getting closer. Now 2% over
Will test with .57 min bitrate

file: DVD 94 min 16:9
============================================
mp2 from headac3he: 88,462
abr 1283 = (1820 / 8) * 60 * 94
tmpgenc max/min 5000/300
Detect Screen Change OFF
Padding ON
KDVD 720 x 480
============================================
target m2v size: 1,283,000
m2v size: 1,308,837
m2vsample: 26,948
CQ: 67.16

bbmpeg muxed as dvd
video: 1,366,028
audio: 89,826
---------
1,455,854
(1,431,200 max allowed on 80 CD's)

MPEG2Source("h:\hunt\1.1.12a\hunt.d2v")
telecide()
decimate()
LegalClip()
unfilter(50,50)
GripCrop( 720,480 )
GripSize(resizer="BicubicResize")
STMedianFilter(8, 32, 0, 0, 8, 32)
temporalsmoother(1,2)
mergechroma(blur(1.50))
mergeluma(blur(0.1))
GripBorders()
LegalClip()

Well, what can I say kwag... I just finished encoding "The Time Machine" (PAL) using CQMatic 1.1.11. Wanted file size 800 MB (what else ). Finished, multiplexed file size turned out 799.26 MB. AMAZING Talk about precise prediction. Once again, thank you for this excellent program.

__________________
AudioSlave

Thanks audioslave

Try 1.1.12a, and just run prediction to see if the CQ found matches closely the one 1.1.11 did.

-kwag

hi audioslave,

I'm new to the Wanted and don'tWants

But, what was your actual Video size ??
-vhelp

Ok, for those curious..

I've finished last nights 2nd encoding test of "Blue Streak" - 94min. movie.

I'm still learning things like how to balance out video/audio and things.

This morning, after 5h:34m of encoding above movie, it was 810mb. I'm
going to assume that it was just TOO big still. But, the CQ was MUCH lower
I used 50, instead of 89, and it was still too big - just the video part. The
audio is perfect for this mins. @ 77.2mb - - 810+77 = 887mb that's
not gonna fit an 800mb cdr. I was surprised, because the movie is only
94 minutes long.

And, anything undre CQ of 50 is tipically blocky as anything, but I've only
done a few tests in this area.

I'm still wondering why CQM v1.1.12a choose CQ of 89, in the first place

So, I'm stumped

-vhelp

@vhelp,

You are encoding as "ES Video Only" and not as "System (Video+Audio)", right

-kwag

Hi Kwag..

Incorrect

I chose ES (Video + Audio) for two reason:

A - because memory serve me that you (after testing) found that v2.520
......was ok w/ this mode and ES (unless I miss-read you )

B - because I want to save time, and not have to encode audio separately.
......if its already there, why not.. right ?

Ok, let me have it

Tell me, that I have to re-do again, w/ same CQ's ??

-vhelp