Terenius
29th November 2001, 07:32
I think someone asked for some numbers in regards to AthlonXP cpu and realtime DiVX capture. Well, here are the results from some quick tests I did.
Source: Satellite feed (MPEG-2 stream)
System:
AthlonXP 1600+
512 MB DDR-Ram
Windows 2000 Server Ed
40GB Maxtor Diamond+ on dedicated IDE channel
Hauppauge WinTV-Theather capture card
Test:
Capture 5:30 from preview channel
VirtualDub 1.4.7
DiVX 4.11 Codec
640x480 resolution, 29.97 fps, YUV2
Results:
For Reference (HuffYUV)
Frames captured: 9897
Compression 2.9:1
Frames dropped: 1
Total size: 2.1 GB
DiVX (Slowest encoding setting, 1500 kb/s bitrate)
Frames captured: 9819
Compression 80.8:1
Frames dropped: 87
Total size: 126.8 MB
DiVX (Slowest encoding setting, 1000 kb/s bitrate)
Frames captured: 9821
Compression 100.1:1
Frames dropped: 80
Total size: 57.5 MB
DiVX (Slow encoding setting, 1500 kb/s bitrate)
Frames captured: 9882
Compression 68.7:1
Frames dropped: 8
Total size: 139.9 MB
DiVX (Medium encoding setting, 1500 kb/s bitrate)
Frames captured: 9885
Compression 71.5:1
Frames dropped: 4
Total size: 136.5 MB
DiVX (Internal De-interlace, slow, 1500 kb/s)
Frames captured: 9849
Compression 87.3:1
Frames dropped: 49
Total size: 121.7 MB
DiVX (Internal De-interlace, medium, 1500 kb/s)
Frames captured: 9885
Compression 87.3:1
Frames dropped: 6
Total size: 121.7 MB
My Conclusion:
AthlonXP 1600+ is certainly up to the task of real-time encoding. I would use (1500, slow), or (1500, medium, de-interlace). If you're just planning to use it to capture the occasional missed show then I'd highly recommend using this method. Beats capturing to MPEG-1 hands down in my opinion.
Hope that answers your question (whoever was asking)
Source: Satellite feed (MPEG-2 stream)
System:
AthlonXP 1600+
512 MB DDR-Ram
Windows 2000 Server Ed
40GB Maxtor Diamond+ on dedicated IDE channel
Hauppauge WinTV-Theather capture card
Test:
Capture 5:30 from preview channel
VirtualDub 1.4.7
DiVX 4.11 Codec
640x480 resolution, 29.97 fps, YUV2
Results:
For Reference (HuffYUV)
Frames captured: 9897
Compression 2.9:1
Frames dropped: 1
Total size: 2.1 GB
DiVX (Slowest encoding setting, 1500 kb/s bitrate)
Frames captured: 9819
Compression 80.8:1
Frames dropped: 87
Total size: 126.8 MB
DiVX (Slowest encoding setting, 1000 kb/s bitrate)
Frames captured: 9821
Compression 100.1:1
Frames dropped: 80
Total size: 57.5 MB
DiVX (Slow encoding setting, 1500 kb/s bitrate)
Frames captured: 9882
Compression 68.7:1
Frames dropped: 8
Total size: 139.9 MB
DiVX (Medium encoding setting, 1500 kb/s bitrate)
Frames captured: 9885
Compression 71.5:1
Frames dropped: 4
Total size: 136.5 MB
DiVX (Internal De-interlace, slow, 1500 kb/s)
Frames captured: 9849
Compression 87.3:1
Frames dropped: 49
Total size: 121.7 MB
DiVX (Internal De-interlace, medium, 1500 kb/s)
Frames captured: 9885
Compression 87.3:1
Frames dropped: 6
Total size: 121.7 MB
My Conclusion:
AthlonXP 1600+ is certainly up to the task of real-time encoding. I would use (1500, slow), or (1500, medium, de-interlace). If you're just planning to use it to capture the occasional missed show then I'd highly recommend using this method. Beats capturing to MPEG-1 hands down in my opinion.
Hope that answers your question (whoever was asking)