Hi all,
just committed code to svn that will build (provided dbus and dbus-glib and the corresponding dev packages are present) a program xvidcap-dbus-client which allows you to remote control xvidcap.
You can run "xvidcap-dbus-client --action start" to start a capture session. Other actions are "stop" or "pause" (toggles paused on/off). Those commands can also be bound to specific keys as your window manager permits. If xvidcap is not started, when you run xvidcap-dbus-client, it will be started automatically.
Code cleanup and documentation is still pending, but feedback is welcome.
Karl.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
btw. if you try dbus activation of xvidcap, i. e. autostarting an unstarted instance through "xvidcap-dbus-client --action start" make sure you have saved a target filename for your capture to your preferences including absolute path. If you don't (i. e. use smth. like "test.avi"), xvidcap will try to write /test.avi because dbus starts xvidcap with pwd = /. And xvidcap doesn't handle that gracefully atm.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
just committed code to svn that will build (provided dbus and dbus-glib and the corresponding dev packages are present) a program xvidcap-dbus-client which allows you to remote control xvidcap.
You can run "xvidcap-dbus-client --action start" to start a capture session. Other actions are "stop" or "pause" (toggles paused on/off). Those commands can also be bound to specific keys as your window manager permits. If xvidcap is not started, when you run xvidcap-dbus-client, it will be started automatically.
Code cleanup and documentation is still pending, but feedback is welcome.
Karl.
btw. if you try dbus activation of xvidcap, i. e. autostarting an unstarted instance through "xvidcap-dbus-client --action start" make sure you have saved a target filename for your capture to your preferences including absolute path. If you don't (i. e. use smth. like "test.avi"), xvidcap will try to write /test.avi because dbus starts xvidcap with pwd = /. And xvidcap doesn't handle that gracefully atm.