|
VP3 and VP6 Video Codec Configuration
Guide
|
Home
|
General notes for encoding video in both the VP3 and VP6 formats.
Winamp stops playing during stream.
You must encode all video files using the same exact encoder settings.
You must also enable the "Resize to" and "Drop/Repeat Frames" options in the
NSV encoder.
Video loosing synch with audio.
You need to Force Framerate to a whole number. ( For example - 18 or 24 )
You need to check Auto Key Frame.
Make Threshold 2X the frame rate. 40 - ( 2 x 20)
Make Minimum Distance 2 X the frame rate. 40 - ( 2 x 20 )
Make Maximum Distance 4 X the frame rate. 80 ( 4 x 20 )
VP3
The VP3 video codec is a open source codec sponsored by the ON2 corporation.
It comes as a standard package with NSV Tools.
Choose the VP3 codec for encoding in the configuration settings of
the NSV Live capture software or NSV GUI.
Optimized VP3 configuration for low bandwidth streaming
Submitted by
www.pcmovieman.com
NSV Format options
Audio send-ahead ms : 0
Min / max sync frame interval : 19 / 19
TOC Size : 1024
|
VP3 Encoding Options
Bitrate : 110 kbs
Keyfram Bitrate : 110
Check Allow dropped frames (Enable CBR)
Quality (63=|50=h) : 50
|
Check Auto Keyframe
Threshold : 90
Minimum distance : 8
Maximum distance : 120
Noise sensitivity : 1
Sharpness : 1
|
VP3 VfW encoding guide
bloomd.home.mchsi.com/vp3
VP6.2
The VP6.2 video codec is a closed source codec developed by the ON2 corporation.
Choose the VP6 codec for encoding in the configuration settings of
the NSV Live capture software or the NSV GUI.
- VFW encoding guide
After you install the VP6.2 Plugin, look on your hard drive in the ON2
Technologies directory :
C:\Program Files\On2 Technologies\VP6 VFW Codec
You will find these documents published by ON2 regarding the use and configuration
of the VP6.2 video codec :
-VP6VFW_Release_Notes.txt -VP6 VFW User Guide ( PDF document )
-Note for VP6.2 encoding When using two pass encoding, you
must encode in two stages. In the first stage you select "Two pass - first pass"
and then encode. In the second stage, you must encode with "Two pass - Best quality".
Optimized VP6 configuration for low bandwidth streaming

Bitrate : (Kilobytes per second) 106
Mode : Encoding video - Two pass, best quality
Mode : Live video - Real Time / Live Encoding
End usage : Stream From A Server
|
Material : Progressive
Noise Reduction : 1
Sharpness : 1
Key Frames Auto keyframe : check
Max frames Btw keys : 90 |
Information submitted by
Marsman2k
Technical Details: The pre-made VP6.2
configurations range from 80 kbps @ 20 fps, to 200 kbps @ 30 fps. As 30
fps is the highest fps rate used, it was chosen as the starting point
for adjustments. 24 kbps mono audio was used in all settings.
Given a 100 kbps target, 80 kbps was
the target for video information. That combined with 24 kbps of audio
results in 104 kbps total – the figure the configuration is designed to
peak out at. This is the same for all configuration rates @ 30 fps – in
that the video target is
approximately 20k below the desired output.
When dealing with 20 fps for the same
output
rate, the primary adjustment made was to the video target bitrate and
was increased to bring the output rate up to match the desired output.
Since 10 fps of information are missing, the video quality specifically
was used to fill the gap. Thus 20 fps configurations look better than
their 30 fps counterparts as the video quality was increased to make up
the difference.
Specific adjustments to the VP6 codec started from the following chart:
|
Bitrate |
size |
fps |
Max Btw Keys |
Quantizer |
Temporal |
Spatial |
Peak Bitrate |
Buffer |
|
|
- |
- |
- |
- |
- |
- |
- |
- |
- |
|
|
30 |
320x240 |
15 |
600 |
12/56 |
20 |
40/60 |
95 |
5/5/5 |
|
|
- |
- |
- |
- |
- |
- |
- |
- |
- |
|
|
40 |
160x120 |
15 |
600 |
12/56 |
20 |
40/60 |
85 |
5/5/5 |
|
|
- |
- |
- |
- |
- |
- |
- |
- |
- |
|
|
80 |
320x240 |
20 |
500 |
11/54 |
20 |
37/55 |
90 |
5/5/6 |
|
|
- |
- |
- |
- |
- |
-- |
- |
- |
- |
|
|
100 |
320x240 |
30 |
450 |
10/52 |
20 |
35/50 |
95 |
5/5/6 |
|
|
- |
- |
- |
- |
- |
-- |
- |
- |
- |
|
|
150 |
320x240 |
30 |
350 |
9/50 |
20 |
32/45 |
95 |
5/6/6 |
|
|
- |
- |
- |
- |
- |
- |
- |
- |
- |
|
|
250 |
320x240 |
24-30 |
300 |
8/48 |
20 |
30/40 |
100 |
6/6/6 |
|
|
- |
- |
- |
- |
- |
- |
- |
- |
- |
|
|
300 |
320x240 |
30 |
255 |
7/46 |
20 |
29/39 |
100 |
6/6/6 |
|
|
- |
- |
- |
- |
- |
- |
- |
- |
- |
|
|
500 |
" |
30 |
210 |
6/44 |
20 |
25/37 |
100-125 |
6/6/6 |
|
|
- |
- |
- |
- |
- |
- |
- |
- |
- |
|
|
750 |
" |
30 |
165 |
5/42 |
20 |
22/36 |
100-125 |
6/6/6 |
|
|
- |
- |
- |
- |
- |
- |
- |
- |
- |
|
|
1000 |
480x368 |
24-30 |
120 |
4/40 |
20 |
20/35 |
100-150 |
6/6/6 |
|
The rows in italic are taken
directly from the On2 Technologies documentation. From these general
guidelines, and my own experiments, I filled in some values in between
these examples. Using this as a guideline, I experimented with various
rates and compression.
|