Compress .MOV ?

ggspencer wrote on 5/18/2005, 4:27 PM
Using Vegas 5, I have rendered a 3 minute and 45 second video to .MOV format (QT) for streaming to the WEB - I have read DSE's training on VASST but the size of my file is 90MB using a size of 240 X 196 (Video Format = Sorenson Video 3) Streaming = Hinted

My question: Is this a compressed file or do I have to buy QT Pro or another codec to perform compression and how much compression can I expect ?



Or is there a way to compress in Vegas for .MOV (Quick Time 6) ?

If anyone can share their experience with this, thanking you in advance !



Comments

B_JM wrote on 5/18/2005, 4:54 PM
you dont have to buy anything and the answer to this was just printed here in the last week or less ..

that is a compressed file ... you can reduce the frame rate to get the file smaller yet ..

hinted streaming (btw) is only if you are going to stream the video via a server set up to do this ... generally speaking ..



Coursedesign wrote on 5/18/2005, 5:30 PM
90MB for 3m45s at 240x196 is not good.

Be sure your keyframes are set to 300, that's the biggest step for most people.

For the rest (there is certainly more to fiddle with), look for earlier posts per BJ_M's suggestion.

I got a 5m12s, 500x384 resolution (yes, vertical), 30P video down from 90MB to 17MB without excessive quality reduction in QT. That took a significant amount of testing (for me) though, and it's difficult to offer simple cookbook recipes.
B_JM wrote on 5/18/2005, 5:53 PM
i thought he said 9meg , not 90 meg

doesnt sound like sorenson was used
Chienworks wrote on 5/18/2005, 6:05 PM
File size is determined by the length of the video and the bitrate used for encoding. The frame size and frame rate don't matter when calculating file size. To get 90MB from 225 seconds you must have encoded at 3Mbps (3000Kbps). This is very high for web delivery. Many web videos are encoded at 256Kbps or thereabouts. At this rate, with no other changes at all, your file size would drop to around 8MB which is a good size for web delivery. You should also be able to get away with a frame size of 320x240 and still have a semi-decent looking picture.
Coursedesign wrote on 5/18/2005, 6:20 PM
"The frame size and frame rate don't matter when calculating file size."

Both of these do matter for a given quality, i.e. if you reduce the frame rate or the frame size you can increase the bit rate for a given file size, which increases the video quality.
Chienworks wrote on 5/18/2005, 6:31 PM
No you can't. If you render 320x240 30fps at 256Kbps you will use 256K bits per second. If you render 160x120 10fps at 256Kbps, you will still use 256K bits per second. The resulting file size will still be essentially identical.

The frames of the 160x120 10fps video will be sharper and clearer than the 320x240 30fps video. This is because there are more bits available for each frame and the image won't be compressed as much.

Using a smaller frame size or lower frame rate will let you use a lower bit rate to maintain the same quality. However, to get a different file size, just changing the frame size or frame rate won't make any difference. You have to use a lower bit rate to get a smaller file size.

True, the frame size and frame rate matter a lot for quality. If you want a small file size then you'll have to use smaller frames and slower rates to get better quality images ... because you will be using a lower bitrate to get a smaller file. Just changing the frame size or rate alone won't alter the finished file size at all.

For compressed video, file size is determined only by the length of the video and the bitrate used.
ggspencer wrote on 5/18/2005, 6:33 PM
Thank you for your help everyone - this is where Im at:

I have got the size down to 7MB with the following settings
REnder Quality=Good
Frame Size = 240 X 196
Frame rate = 15 Field Order = None Aspect Ratio = 1
Video Format = Sorenson Video 3
Compressed Depth = 24 bpp Quality = 50% Data Rate = Basic
Target Rate = 28
Key Frame every 300
Streaming = Fast Start with Compressed Header

Do these sound ok ? Not sure about the target rate.
Chienworks wrote on 5/18/2005, 6:36 PM
Quicktime uses bytes per second for the rate instead of bits per second, so 28KBps = 224Kbps, which is a probably good for that frame size. 15 frames per second is a good choice too since that lets each frame have twice as many bits for a clearer image. You might be able to get away with a 320x240 frame, but you would just have to try it and see how it looks.
B_JM wrote on 5/18/2005, 8:06 PM
you are right chienworks - I should have said reduce the frame rate AND data rate ..

I just assumed that this was a given .....




this why 24p w/ pulldown mpeg encoding is more efficient for dvd --
jlafferty wrote on 5/18/2005, 9:36 PM
Why is the 320x240 frame dimension preferred over 360x240? Aren't the black bars prohibitive? Wouldn't I rather have more of my original DV frame where they are?

Incidentally, I just did an 8:17 piece that looks nice and it's "only" 31mb:

http://ideaspora.net/breadstuy.mov

Settings are: target bitrate of 100kBps, 360x240, 15fps progressive PAR .9091 sorenson 3 | 16 bit, 22050khz mono audio, QDesign Music 2

- jim
Coursedesign wrote on 5/18/2005, 9:50 PM
Chienworks,

It sounds like we are talking about two different things.

Your math is impeccable, but as you yourself said, "Using a smaller frame size or lower frame rate will let you use a lower bit rate to maintain the same quality."

That's all I was talking about.

I look at it first from a viewer's standpoint, and what he or she might perceive as a reasonable compromise between subjective quality and download time, given what exactly I am trying to communicate. The upper limit on the file size is then usually determined by the web site owner (who is paying for the bandwidth bills).

Related subject:
The WM9 player is supposed to be able to do frame interpolation so you can feed it say 15fps and have it play back at a 30 fps rate with the action at normal speed. I never spent much time on this, because I couldn't get any useful improvement from it. Anybody have good experience with this?
B_JM wrote on 5/19/2005, 5:59 AM
it does a terrible job at it
B_JM wrote on 5/19/2005, 6:00 AM
should use 1:1 PAR
jlafferty wrote on 5/19/2005, 12:39 PM
Yes, you're right. Sorry about that.