On Fri, Feb 10, 2012 at 8:07 PM, Liviu Andronic <email@example.com>
Thanks for the pointers.
On Fri, 10 Feb 2012 12:08:57 +0100, Iwan Gabovitch <firstname.lastname@example.org> wrote:
I installed 'glc' easily using apt, and it seems to support my card, but it is just too jerky. I've followed  and tried several options that did improve the speed of the recording
glc-capture --compression=none --colorspace=bgr --disable-audio /usr/local/build/trigger/data/trigger
but it is still unbearably jerky. I guess that my laptop is simply not withstanding the load.
I'm not sure I follow this 2nd guide. Do I really need PulseAudio? I got rid of it, and am loathe to isntall it back. Would ALSA suffice?
Also, step 3 says 'start game', but if I start Trigger then I can no longer switch to a terminal for the 'wmctrl' and 'ffmpeg' calls.
You should be able to use ALSA by replacing "pulse" with "hw:0,2" or something like that. It might not work if your sound card/driver are annoying.
You can start recording before starting trigger or use a `sleep 4 &&` timer at the start of the line or edit the trigger config so it runs in a window.
The lower the resolution of the game, the smoother the recording should be. What resolution do you use in Trigger?
I'll gladly help if there are problems!
On Fri, Feb 10, 2012 at 12:05 PM, Liviu Andronic <email@example.com
I was wondering how should one approach recording a Trigger race? I tried
using , but as a result my laptop became unbearably slow when playing
the race. What do you use to record the races?