On Thu, March 10, 2011 20:23, Harrie Hoogeveen wrote: > On Wed, Mar 9, 2011 at 5:07 AM, <[email protected]> wrote: > >> On Wed, March 9, 2011 02:24, [email protected] wrote: >> > On Sun, March 6, 2011 22:58, Harrie Hoogeveen wrote: >> >> On Sun, Mar 6, 2011 at 6:02 PM, <[email protected]> wrote: >> >> >> >>> 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. >> >> >> >> >> >> To bad, it is still the same. The window pops up at the second >> desktop. >> >> I >> >> also noticed how there are not other popup windows in the settings >> >> dialog. >> >> Only at the vj effects parameters. they popup on the correct desktop. >> >> >> >> >> > >> > OK, I made another fix for this, now it should force the settings onto >> the >> > gui screen. Would you mind testing this ? >> > >> > >> > I am working on an option to save settings to an alternate file and >> then >> > reload them on startup. >> > >> >> OK, that is done also now. You can save the settings from the advanced >> window, and then load them on startup with the -vppdefaults <file> >> option. >> Note that this will only set the settings for the current plugin, it >> won't >> set the value of the plugin itself (although maybe in a future version >> it >> will). >> >> This means you no longer have to mess around with copying the >> vpp_defaults >> file. >> >> Gabriel. >> > > I have been testing. The settings dialog still appears on my second work > space.
Hmm then I am going to need to test this myself and find a solution that works. It may be that it is simply not possible to show one dialog box over another on the same screen. However you will have to wait until I get round to plugin in my TV (second monitor). > Also I think it stores the number of the selected video device in the > vpp_defaults but video devices that are taken don't appear in the list. So > say selection 0 is video /dev/video0 when I launce the first instance. > Then > the first instance will take the first video device, then the second > instance I launch won't see /dev/video0 and will have /dev/video2 as > selection 0. Which also means that if I just make one vpp_defaults file > with > selection 0 and launch them in order with an appropriate amount of time in > between. They will nicely open in order, which is fine for me. Yes I think your analysis is correct. > I think the > v4l api works this way. This also means that complexer selections have > issues. Selection option X will vary in meaning depending on which video > device is in use. This could be solved by storing the device string > instead > of the selection int in the vpp_defaults file. > The problem is the way LiVES handles parameters - either you have a string, or you have a string list. For the latter only the index in the list is stored. But for string you don't get the drop down list. And yes the list changes each time because it doesnt include devices which are already in use. > I also see that some user have over a 100 weed filters where I only have > around 50. Is this a compile/build issues at my side? Or do they have > custom > added effects? > Probably you are missing frei0r effects. Check the downloads page for instructions or install the packages before compiling. There are also libvisual generators which are sometimes packaged. Regards, Gabriel. ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Lives-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lives-users
