On Sun, March 6, 2011 00:23, Harrie Hoogeveen wrote: > On Sat, Mar 5, 2011 at 11:29 PM, <[email protected]> wrote: > >> On Sat, March 5, 2011 22:18, Harrie Hoogeveen wrote: >> > Hello, >> > >> > I have build version 1.4.2-svn, I have attached the ebuild. >> > It seems to be working fine, but no change for the video device >> selection: >> > Starting... >> > *** Using vloopback plugin for fs playback, agreed to use palette type >> 519 >> > ( >> > UYVY:Y'CbCr (clamped) ). *** >> > Successfully loaded 59 Weed filters >> > Loading default keymap from >> /home/mivz/.lives-dir/default.keymap...done. >> > Started jack audio subsystem. >> > >> > Checking optional >> > >> dependencies:mplayer...detected...convert...detected...composite...detected...sox...detected >> > cdda2wav...detected...jackd...detected...pulse audio...NOT >> > DETECTED...python...detected...dvgrab...detected...xwininfo...detected... >> > >> > Window manager reports as "compiz"; number of monitors detected: 1 >> > Temp directory is /tmp/livestmp/ >> > Compiled with jack support, good ! >> > Welcome to LiVES version 1.4.2-svn. >> > >> > But not much seems to have changed for the vloopback settings. I still >> > just >> > see /dev/video8 in the selection list. When closing it does create the >> new >> > vpp_defaults file. >> > Also the option dialog still appears on the second workspace. >> >
OK, I checked in another possible fix for this. It may be working OK now. >> > The OSC commands for loop and pingpong are working perfect. >> > >> > Can I provide you with any debugging information some how? >> > >> > Regards, >> > Harrie >> > >> >> Yes, please edit lives/lives-plugins/plugins/playback/video/vloopback.c >> and uncomment the line: >> >> //fprintf(stderr,"got %s\n",devname); >> >> Then re-install and start from a terminal, see what output you get. >> >> >> Gabriel. >> >> > That seems to give all the devices: > LiVES 1.4.2-svn > Copyright 2002-2010 Gabriel Finch ([email protected]) and others. > LiVES comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details. > > got /dev/video0 > got /dev/video2 > got /dev/video4 > got /dev/video6 > got /dev/video8 > Hmm that is strange. Just to make sure you are running the correct version of the plugin, I bumped the version number. When you restart LiVES you should see a message now about the plugin being updated. Also please check the version number in Advanced settings, it should be 1.0.2 Something else I would like you to try, in the vloopback. file, add the following line: while (vdevs[i]!=NULL) { snprintf(devstr+slen,30000-slen,"%s|",vdevs[i]); fprintf(stderr,"devstr is now %s\n",devstr); // <<<<<<<<<<<< new slen+=strlen(vdevs[i])+1; free(vdevs[i++]); } free( vdevs ); > But every time I hit the video dev select list it also gives a warning: > (lives:23495): GLib-GObject-WARNING **: gsignal.c:3079: signal name > `depressed' is invalid for instance `0x7f4c2001a560' > Yes, I see this too. It seems to be a bug in gtk+ or maybe gtk+ and compiz. > Another minor thing I got, if I run make with -j12, which will make it use > many cpu's at the same time during compile it will give an error when I > execute lives: lives: error while loading shared libraries: > libweed_slice.so.0: cannot open shared object file: No such file or > directory > When I just run make, on one cpu, every thing will be fine. > Not sure what the problem is there - when I run with -j4 it works fine. What happens when you type ldd /usr/bin/lives-exe | grep libweed 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
