New GW Movie Released
Excel
Thanks for the heads-up Dreamsmith
Armaio
Quote:
|
Originally Posted by Dreamsmith
Uh, this thread is barely a week old, and has had someone post in it nearly every day it's been up. Continuing an ongoing discussion is not "bringing back old threads".
BTW, are you a moderator for this forum, or are you just impersonating a moderator? |
Kityn
Good video Excel This is one I haven't seen yet.Too bad I missed the end of BWE,but I'll be there this time around. 
This is one I haven't seen yet.Too bad I missed the end of BWE,but I'll be there this time around.
Excel
Quote:
|
Originally Posted by Armaio
Well the movie is old, therefore so is the thread. I was expecting to see something new and realized it was something I had saw a week ago. Thats why I considered it "old".
|
that's what this is all about
Armaio
Quote:
|
Originally Posted by Excel
My movie is 12hours old
that's what this is all about |
Orbit
This is an excellent video, well done Excel!
Brett Kuntz
Oops, thought this was about the original post's official GW movie, I haven't watched Excel's.
-You were the encoder? Single pass will sink you fast
-Cutting out high camera movement is always a start.
-XviD is a DivX encoder, only instead of using the DivX encoder which has most of its options unchangeable and hardcoded, XviD lets you change around anything you want for that perfect encode.
-Frame rate doesn't matter in final size, as neither DivX or XviD saves information in "frames" (in laymens terms anyways). FPS will matter if you say; capture at 15 fps, but then change it to 30 fps so the movie plays twice as fast, then encode that. But, if you say encode a real 30 fps movie, then have the encoder 'drop' every 2nd frame, therefor making it 15fps but still the same playback speed, you'll notice the resulting video stream has roughly the same (slightly less) bitrate as the original.
-If you notice H.263 blocking, delete and restart the encoding, up the bitrate by about 10% and try that out. H.263 will first appear during camera movement, if it's really low bitrate, it'll appear all the time even if the camera is still.
Quote:
|
Originally Posted by Excel
What do you mean 60mb for 2,5minutes. Actually it's ~17,7mb/m
how would you have encoded it then?I just used single pass 2400 bitrate, should I have switched the focus a bit to use more space on fast motion? Lemme guess, Xvid never played around with that :-/Critical feedback is always good, no way to better yourself otherwise EDIT/ you can't compare the size of your movie directly to mine because you only used 15fps when I used 30... (yes I know the real frame rate is not 30 in the end) |
-Cutting out high camera movement is always a start.
-XviD is a DivX encoder, only instead of using the DivX encoder which has most of its options unchangeable and hardcoded, XviD lets you change around anything you want for that perfect encode.
-Frame rate doesn't matter in final size, as neither DivX or XviD saves information in "frames" (in laymens terms anyways). FPS will matter if you say; capture at 15 fps, but then change it to 30 fps so the movie plays twice as fast, then encode that. But, if you say encode a real 30 fps movie, then have the encoder 'drop' every 2nd frame, therefor making it 15fps but still the same playback speed, you'll notice the resulting video stream has roughly the same (slightly less) bitrate as the original.
-If you notice H.263 blocking, delete and restart the encoding, up the bitrate by about 10% and try that out. H.263 will first appear during camera movement, if it's really low bitrate, it'll appear all the time even if the camera is still.