On Mon, February 28, 2011 01:15, Harrie Hoogeveen wrote: > Hello, > > First, thank you for the tip for duplicating clip sets, it works > perfectly. > I have some issues using the vloopback settings. > I upgraded to 1.4.0 as you suggested, I used the same ebuild (gentoo) with > just a version number upgrade and every ting seems to work fine. 1.4.1 > does > not compile doh, but I did not have the time to look in to that. Saw some > issues passing in the list, so I will wait for those to be resolved. > > I load the vloopback module with 5 pipes: options vloopback pipes=5 > So I get 10 video devices: > ls /dev/video* > /dev/video0 /dev/video2 /dev/video4 /dev/video6 /dev/video8 > /dev/video1 /dev/video3 /dev/video5 /dev/video7 /dev/video9 >>From which the even numbers are input devices and the odd numbers are >> output > devices. > For example /dev/video1 gives the output for /dev/video0. > > If I select the vloopback output and to the advanced options, first minor > issue is that the advanced option dialog always appears on my second > screen > instead of the first screen as the other dialogs.
OK, should be fixed in subversion now. > The major issue is that it only shows /dev/video8 (the last input device) > as > an option in the list box. It misses all the other video devices. > The most bizar part is after selecting this one it just seems to take the > first video device available on play. So I can only configure only number > 8 > and then it still plays on 0. The second instants of LiVES I launch will > take the next. Which with different load times, will give very unexpected > results in which instants maps to which device. > Should also be fixed in subversion now. > Also I am missing the vpp_defaults file in the .lives-dir which used to > hold > the settings, if I copy the old one there, LiVES will give me a warning > that > the video settings are changed and remove the file. > That is correct, because the video device parameter changed from a string to a string list. The old vpp_defaults file will not work with the current version of LiVES. > Nevertheless my patch has come a far way. The basis is there and after the > video device mapping is resolved I can record a first show case. (I had > good > fun decorating my living room with video mapped 3d shapes. :) > > Also I wanted to ask if you have plans implementing the loop and ping pong > loop boolean's for the OSCP interface. It's the only part I need the > interface for now, except for pre configuring the set. > As you requested, I have implemented them in OSC, I added: /video/loop/set /video/loop/get /video/pingpong/set /video/pingpong/get Loop takes a bitmap of LIVES_LOOP_NONE (0), LIVES_LOOP_CONT (1) and LIVES_LOOP_FIT (2) - the latter will loop the video to fit the audio. You can also look up the values of these constants with: /lives/constant/value/get - but this is probably more advanced than you need. So, I suggest you checkout and compile from subversion. This will also be useful for me for testing the fixes and new functionality. Regards, Gabriel. ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Lives-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lives-users
