What this posting comes down to really is really a do-I-need-to-get-a-new-video-card? one. The opening post back in July http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=769723here[/link] gives you the full specs of my current card and general situation I'm in. But below are just the specs themselves plus basic system setup which are probably sufficient.
From that thread and an other on this general video card subject, it seems that I don't really need one in terms of Vegas. But I'm wondering if it would help with Fraps.
I've sent a tech support Q to them but I'm also needing Vegas user input, hence this thread. I use Fraps mainly with NASA World Wind (to make faux fly-overs using satellite images. Since one can tilt and so on much like in Google Earth, there is a certain realism that beats just doing a Ken Burns pan over a 2-D sattelite image.
At this point, I have not figured out how to adjust the speed of "flight" in the new Java version of WW, so this is default speed, and in this case I simply spun around over the San Francisco bay (download the no-audio 960x480 32 Mb. WMV test render at link below; it has some minor FX added via Color Curves, Color Correction, Color Balance, 0.3 Sharpen
As you will see, I captured at 60fps and at 29.27, both at Fraps "Full Size" as uncompressed .AVI. Then rendered out in Vegas together at 0.50 playback for I know I end up doing some slow mo with such captures.
The problem is that both the 60 and 29.97 "jitter" - the first is in smaller increments which a bit smoother yet blurry too, the second sharper but the jitters are naturally twice as long in duration.
There will always be some glitter-type artifacts with Fraps in such captures especially towards the horizon line when the satellite image is tilted to give it a 3-D perspective, but those can be washed out a bit with some tweaking in Vegas.
But it's these jitters that make the captures un-usable.
Q:
As always, thanks for you input.
~ Philip
http://www.compassionsensuality.net/Other/VEGAS_Forum_Q/FRAPS_60+29.9fps_at_0.5_speed.wmvFRAPS_60+29.9fps_at_0.5_speed.WMV[/link]
_____________
System Specs
Windows Version:7 64-bit
RAM:16 Gb. DDR3
Processor:AMD X6 1090T Phenom II Black Edition 6x3.2 Ghz - no overclocking
Hard Drives: SATA2 7200 Rpm.
Video Card:nVidia GeForce 6800 XT
Sound Card:M-Audio Delta Audiophile (Analog I/O)
Video Capture:Onboard and TI chip IEEE PCI card
CD Burner:Asus DRW 24B1ST
DVD Burner:Asus DRW 24B1ST
Camera:Canon HV30 HD
nVidia GeForce 6800 XT[b][/b] XFX version
Series: GeForce 6
GPU: NV41
Release Date: 2005-09-30
Interface: PCI-E x16
Core Clock: 325 MHz
Memory Clock: 350 MHz (700 DDR)
Memory Bandwidth: 22.4 GB/sec
Shader Operations: 2600 MOperations/sec
Pixel Fill Rate: 2600 MPixels/sec
Texture Fill Rate: 2600 MTexels/sec
Vertex Operations: 325 MVertices/sec
Framebuffer: 128,256,512 MB
Memory Type: DDR
Memory Bus Type: 64x4 (256 bit)
DirectX Compliance: 9.0c
OpenGL Compliance: 2.0
PS/VS Version: 3.0/3.0
Process: 130 nm
Fragment Pipelines: 8 (12)
Vertex Pipelines: 4 (6)
Texture Units: 8 (12)
Raster Operators 8
From that thread and an other on this general video card subject, it seems that I don't really need one in terms of Vegas. But I'm wondering if it would help with Fraps.
I've sent a tech support Q to them but I'm also needing Vegas user input, hence this thread. I use Fraps mainly with NASA World Wind (to make faux fly-overs using satellite images. Since one can tilt and so on much like in Google Earth, there is a certain realism that beats just doing a Ken Burns pan over a 2-D sattelite image.
At this point, I have not figured out how to adjust the speed of "flight" in the new Java version of WW, so this is default speed, and in this case I simply spun around over the San Francisco bay (download the no-audio 960x480 32 Mb. WMV test render at link below; it has some minor FX added via Color Curves, Color Correction, Color Balance, 0.3 Sharpen
As you will see, I captured at 60fps and at 29.27, both at Fraps "Full Size" as uncompressed .AVI. Then rendered out in Vegas together at 0.50 playback for I know I end up doing some slow mo with such captures.
The problem is that both the 60 and 29.97 "jitter" - the first is in smaller increments which a bit smoother yet blurry too, the second sharper but the jitters are naturally twice as long in duration.
There will always be some glitter-type artifacts with Fraps in such captures especially towards the horizon line when the satellite image is tilted to give it a 3-D perspective, but those can be washed out a bit with some tweaking in Vegas.
But it's these jitters that make the captures un-usable.
Q:
As always, thanks for you input.
~ Philip
http://www.compassionsensuality.net/Other/VEGAS_Forum_Q/FRAPS_60+29.9fps_at_0.5_speed.wmvFRAPS_60+29.9fps_at_0.5_speed.WMV[/link]
_____________
System Specs
Windows Version:7 64-bit
RAM:16 Gb. DDR3
Processor:AMD X6 1090T Phenom II Black Edition 6x3.2 Ghz - no overclocking
Hard Drives: SATA2 7200 Rpm.
Video Card:nVidia GeForce 6800 XT
Sound Card:M-Audio Delta Audiophile (Analog I/O)
Video Capture:Onboard and TI chip IEEE PCI card
CD Burner:Asus DRW 24B1ST
DVD Burner:Asus DRW 24B1ST
Camera:Canon HV30 HD
nVidia GeForce 6800 XT[b][/b] XFX version
Series: GeForce 6
GPU: NV41
Release Date: 2005-09-30
Interface: PCI-E x16
Core Clock: 325 MHz
Memory Clock: 350 MHz (700 DDR)
Memory Bandwidth: 22.4 GB/sec
Shader Operations: 2600 MOperations/sec
Pixel Fill Rate: 2600 MPixels/sec
Texture Fill Rate: 2600 MTexels/sec
Vertex Operations: 325 MVertices/sec
Framebuffer: 128,256,512 MB
Memory Type: DDR
Memory Bus Type: 64x4 (256 bit)
DirectX Compliance: 9.0c
OpenGL Compliance: 2.0
PS/VS Version: 3.0/3.0
Process: 130 nm
Fragment Pipelines: 8 (12)
Vertex Pipelines: 4 (6)
Texture Units: 8 (12)
Raster Operators 8