If i could at least get a hint about what these programs do, i might be able to test them out and document them - or is this a case of "go read the source, its documented there"?
I am currently planning to write a small gui for ivtv using GTK and Java (gcj) or python - probably Java (as i don't know python, and i don't want to do it in C(++)) - a small and simple controll app that should be able to act as a frontend to ivtv-tune and ivtvctrl, including loading settings from disk etc, searching from channels (using ivtv's built-in signal detect), lanch mplayer and record. Or is that already done (ptune-ui doesn't count - its ugly, dysfunctional, require a ton of non-standard deps, and generally leaves a lot to be desired) -- Kyrre søn, 26.03.2006 kl. 21.03 skrev Kyrre Ness Sjobak: > Hello. > > There are many ivtv* commands, but not all of them are documented. What > are: > > ivtv-detect > ivtv-encoder > ivtv-mpegindex > ivtvplay > ivtv-radio > > Some of them are quite obivious - but not all of theme are easy to > understand how to use. And none of them are documented on > http://ivtvdriver.org/index.php/Documentation > (or on the wiki at all) > > --- Kyrre > > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
