Alright, so I got into the competitive tf2 scene only late 2013, and so far I've really enjoyed it. During this time I've seen plenty of demos of other people on YouTube, and recently wanted to post a demo of my own. I recorded the demo and then had the grim realization that .dem files aren't recognized by anything besides tf2. I then looked around on forums and such and found out about te=he Lawena Recording Tool, and I tried it out. It worked great until, but then I had to compress the TGA files into a .avi file. In VirtualDub I (attempted to) synced up the audio and video (I have no idea if that worked because the finished product is weird), and then I went to file - Save as AVI. It seemed to render alright and then I closed out VirtualDub. Here's the problem, my now compressed 4-5 second test clip that I recorded in Lawena is now a jittering slo-mo'd mess. The audio and video both keep stuttering and freezing up. Any help? Is it a VirtualDub codec that I need or something?
The files that you are looking at are fully uncompressed and hard to work with. You can have TF2 output compressed h.264 video which is easier to work with but it's not as high quality. However if you do want the highest quality possible, just put those files into your editor and make aggressive use of prerendering.
At this point you are highly limited on the amount of memory you have in your pc. The more memory you have, the longer footage you can prerender without issue.
At this point you are highly limited on the amount of memory you have in your pc. The more memory you have, the longer footage you can prerender without issue.
AndKennethThe files that you are looking at are fully uncompressed and hard to work with. You can have TF2 output compressed h.264 video which is easier to work with but it's not as high quality. However if you do want the highest quality possible, just put those files into your editor and make aggressive use of prerendering.
At this point you are highly limited on the amount of memory you have in your pc. The more memory you have, the longer footage you can prerender without issue.
Well, quality/size isn't really a problem here, it's more the actual file itself. After it's exported from VirtualDub, it seems to be all jittery and freezey, while the actual quality of the video is fine. That is what I need help with.
At this point you are highly limited on the amount of memory you have in your pc. The more memory you have, the longer footage you can prerender without issue.[/quote]
Well, quality/size isn't really a problem here, it's more the actual file itself. After it's exported from VirtualDub, it seems to be all jittery and freezey, while the actual quality of the video is fine. That is what I need help with.
AyRwhen you exported it from vdub, did you end up with a file that was huge? the uncompressed file tends to work poorly with media players afaik
so you gotta run it through something like sony vegas or a program called easy h264 (google it) and that should output a like 40mb file and that one should work ok
Thanks, I used h264 and it worked great. I wasn't aware of the file size problems in the media player
so you gotta run it through something like sony vegas or a program called easy h264 (google it) and that should output a like 40mb file and that one should work ok[/quote]
Thanks, I used h264 and it worked great. I wasn't aware of the file size problems in the media player
We are talking files on the order of gigabytes per second. They can get real big real quick and fill up your memory like no tomorrow.
If you're wondering the math, each frame is about 40 mb in a tga sequence. If you're recording at 1080p 60 fps you're looking at 2.4 gigabytes per second. Using lagarith which is a lossless codec, it's a bit better but still quite large.
If you're wondering the math, each frame is about 40 mb in a tga sequence. If you're recording at 1080p 60 fps you're looking at 2.4 gigabytes per second. Using lagarith which is a lossless codec, it's a bit better but still quite large.
If you use the huge files, computers tend to struggle playing them back (just consider how many GBs per second it has to load, show, and then discard again to load the next). You can still use them while editing though in most cases, and the final render shouldn't have the problem. Or you could do as AyR said and just encode them.