Re: [PD] Data structures: no object for freeing pointers?
One approach is to assign a variable for active/unactive scalars. And then use that variable to render the scalar visible/invisible. After a work session, the user can hide the active scalars, display the inactive ones, and select + delete these. It's still far from ideal, but a compromise. Envoyé: Mardi 11 Juin 2013 11:25:23 Objet: Re: [PD] Data structures: no object for freeing pointers? On Die, 2013-06-11 at 11:00 +0200, Jan Baumgart wrote: I've been building a sequencer with data structs. But now I've come to a dead end, because there seems to be no object, that let's you remove structs. The only way seems to be deleting them in the gui. It's still possible to put only one pointer and then arrays on it, then you can add or delete at the last array item, or it's possible to put an id at each array element and then remove the element id to delete, then it's possible to have undo's. pc ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] l2ork externals install
Hi All, Hi Ivica, I've reinstalled my box and I'm reinstalling l2ork and I'm having a hard time getting all the externals I need in place. Is it possible that some externals are built with ./tar_em_up.sh -F but not installed with make install? I got to admit I'm a bit confused (about which ones) because I've already built and installed moonlib and miXed manually, but now that I've arrived to iem* I see the binaries are in the build folder but not in /usr/lib/pd-l2ork/extra. I'd appreciate some guidance... Thanks! András ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] compiling pix_opencv on debian (lmde)
thanks for this
I just tested your patch with a fresh install of Ubuntu and it doesn't work
pix_opencv still depends both on opencv 1.5 and 2.3
it's a shame but I'll fix this later
the svn version works on ubuntu after installing legacy packages :
sudo apt-get install libopencv-dev libcv-dev libhighgui-dev libcvaux-dev
libopencv-dev is version 2.3.1
the others are legacy and install among others cv.h
concerning, pix_opencv_blobtrack, which version of opencv are you using ?
check it with : echo $(pkg-config --modversion opencv)
cheers
a
--
do it yourself
http://antoine.villeret.free.fr
2013/6/19 yvan volochine yvan...@gmail.com
FYI it does not build on archlinux (with opencv2).
I fixed some of it with the following patch:
https://gist.github.com/**gusano/5814205https://gist.github.com/gusano/5814205
and now all externals build fine except for `pix_opencv_blobtrack` which
gives the following error:
blobtrack.h: In function ‘CvFGDetector* cvCreateFGDetector1()’:
blobtrack.h:20:113: warning: control reaches end of non-void function
[-Wreturn-type]
static CvFGDetector* cvCreateFGDetector1 () { return
cvCreateFGDetectorBase(CV_BG_**MODEL_MOG,NULL); }
^
blobtrack.h: In function ‘CvFGDetector* cvCreateFGDetector0Simple()’:
blobtrack.h:19:113: warning: control reaches end of non-void function
[-Wreturn-type]
static CvFGDetector* cvCreateFGDetector0Simple() { return
cvCreateFGDetectorBase(CV_BG_**MODEL_FGD_SIMPLE, NULL); }
^
blobtrack.h: In function ‘CvFGDetector* cvCreateFGDetector0()’:
blobtrack.h:18:113: warning: control reaches end of non-void function
[-Wreturn-type]
static CvFGDetector* cvCreateFGDetector0 () { return
cvCreateFGDetectorBase(CV_BG_**MODEL_FGD,NULL); }
^
make: *** [pix_opencv_blobtrack.o] Error 1
ciao,
y
--
http://yvanvolochine.com
http://soundcloud.com/**yvanvolochinehttp://soundcloud.com/yvanvolochine
http://soundcloud.com/**elgusanorojo http://soundcloud.com/elgusanorojo
http://vimeo.com/yv
__**_
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - http://lists.puredata.info/**
listinfo/pd-list http://lists.puredata.info/listinfo/pd-list
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -
http://lists.puredata.info/listinfo/pd-list
Re: [PD] compiling pix_opencv on debian (lmde)
On 20/06/13 15:04, Antoine Villeret wrote: thanks for this I just tested your patch with a fresh install of Ubuntu and it doesn't work pix_opencv still depends both on opencv 1.5 and 2.3 it's a shame but I'll fix this later yep, I thought that this might be archlinux specific, that's why I didn't officialy submit my patch =) libopencv-dev is version 2.3.1 the others are legacy and install among others cv.h concerning, pix_opencv_blobtrack, which version of opencv are you using ? check it with : echo $(pkg-config --modversion opencv) 2.4.5 ciao, y -- http://yvanvolochine.com http://soundcloud.com/yvanvolochine http://soundcloud.com/elgusanorojo http://vimeo.com/yv ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] l2ork externals install
I am still in the process of cleaning up externals to make sure they are stable and robust enough to be included. This is a time-consuming process. Some of the work was already started by a colleague Stephen Carl but a lot more work remains. If you (or anyone else) would like to contribute to this process, we do have a google doc up that goes through each external and annotates what needs to be done (e.g. is it stable, does it have robust documentation, like the one Jonathan has been working on, is it a GUI object that needs additional changes to make it accelerated within pd-l2ork etc.). That said, I think iem lib should be included as far as I can tell (but may be wrong as well). extra folder does have a collection of iem* subfolders, but I am not sure which specific object is missing. If you can send me specific list of objects missing I can investigate further. HTH Best wishes, Ico On 06/20/2013 08:43 AM, András Murányi wrote: Hi All, Hi Ivica, I've reinstalled my box and I'm reinstalling l2ork and I'm having a hard time getting all the externals I need in place. Is it possible that some externals are built with ./tar_em_up.sh -F but not installed with make install? I got to admit I'm a bit confused (about which ones) because I've already built and installed moonlib and miXed manually, but now that I've arrived to iem* I see the binaries are in the build folder but not in /usr/lib/pd-l2ork/extra. I'd appreciate some guidance... Thanks! András ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list -- Ivica Ico Bukvic, D.M.A Composition, Music Technology Director, DISIS Interactive Sound Intermedia Studio Director, L2Ork Linux Laptop Orchestra Head, ICAT IMPACT Studio Virginia Tech Department of Music Blacksburg, VA 24061-0240 (540) 231-6139 (540) 231-5034 (fax) disis.music.vt.edu l2ork.music.vt.edu ico.bukvic.net ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Data structures: no object for freeing pointers?
Yes with visibility setting we can access an element of an array only, so each state can be stored, retrieved, replaced at will by accessing an element of te array... The matter is how accessing an element, idealy it would be a [nbx] where max value is the number of array elements, or a scalar but I don't how it's possible to fix limits to [drawnumber] De: João Pais jmmmp...@googlemail.com À: pd-list pd-list@iem.at, Patrice Colet colet.patr...@free.fr Envoyé: Jeudi 20 Juin 2013 11:09:26 Objet: Re: [PD] Data structures: no object for freeing pointers? One approach is to assign a variable for active/unactive scalars. And then use that variable to render the scalar visible/invisible. After a work session, the user can hide the active scalars, display the inactive ones, and select + delete these. It's still far from ideal, but a compromise. Envoyé: Mardi 11 Juin 2013 11:25:23 Objet: Re: [PD] Data structures: no object for freeing pointers? On Die, 2013-06-11 at 11:00 +0200, Jan Baumgart wrote: I've been building a sequencer with data structs. But now I've come to a dead end, because there seems to be no object, that let's you remove structs. The only way seems to be deleting them in the gui. It's still possible to put only one pointer and then arrays on it, then you can add or delete at the last array item, or it's possible to put an id at each array element and then remove the element id to delete, then it's possible to have undo's. pc ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] l2ork externals install
On Thu, Jun 20, 2013 at 3:56 PM, Ivica Ico Bukvic i...@vt.edu wrote: I am still in the process of cleaning up externals to make sure they are stable and robust enough to be included. This is a time-consuming process. Some of the work was already started by a colleague Stephen Carl but a lot more work remains. If you (or anyone else) would like to contribute to this process, we do have a google doc up that goes through each external and annotates what needs to be done (e.g. is it stable, does it have robust documentation, like the one Jonathan has been working on, is it a GUI object that needs additional changes to make it accelerated within pd-l2ork etc.). That said, I think iem lib should be included as far as I can tell (but may be wrong as well). extra folder does have a collection of iem* subfolders, but I am not sure which specific object is missing. If you can send me specific list of objects missing I can investigate further. Well, not a definite list, but: - moonlib and flatspace: are in the sources, not compiled by default, but added to LIB_TARGETS in externals/Makefile can be compiled, installed and they do work, - loaders(/libdir): in the sources, not compiled by default, I compiled and installed it manually, and it works, - miXed(/toxy): in the sources, not compiled by default, I compiled it manually and installed it even more manually (ie make install doesn't work), and I only tested 'widget', which party works. I need it badly though, and 'widget popop', which I use, happens to work. Definitely needs some massaging to be included. - iem*: are in the sources, seem to be not compiled by default - and this is where I chose to write to the list so cannot yet tell about compile/install. András On 06/20/2013 08:43 AM, András Murányi wrote: Hi All, Hi Ivica, I've reinstalled my box and I'm reinstalling l2ork and I'm having a hard time getting all the externals I need in place. Is it possible that some externals are built with ./tar_em_up.sh -F but not installed with make install? I got to admit I'm a bit confused (about which ones) because I've already built and installed moonlib and miXed manually, but now that I've arrived to iem* I see the binaries are in the build folder but not in /usr/lib/pd-l2ork/extra. I'd appreciate some guidance... Thanks! András ___pd-l...@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] [PD-announce] JOB: Post-doc on Sound-Producing Actions (Oslo)
Post-Doctoral Research Fellowship (up to 3 years) Sound-Producing Actions University of Oslo, Department of Musicology, fourMs lab http://uio.easycruit.com/vacancy/982967/62048?iso=no ## Description ## One postdoctoral research fellowship is available at the Department of Musicology for work within the fourMs research project. fourMs is an interdisciplinary research project with participation of the Departments of Musicology, Informatics and Psychology at the University of Oslo. As suggested by the acronym of the four M’s, Music, Mind, Motion, and Machines, the project is focused on the relationships between body motion, mind and technology in music, and is strongly interdisciplinary in its approach and activities. See the fourMs website for more information: http://www.fourms.uio.no The fellowship is within the area of sound-producing actions, broadly defined as body motion that produces sound in interaction with various instruments and/or by the human vocal apparatus. Applicants should have competence within one or more relevant areas for research on sound producing actions such as motion capture, processing and classification of motion capture data, biomechanics, motor control, and, more generally, embodied music cognition. Familiarity with basics of musical acoustics and sound synthesis would be an additional advantage in view of modeling the links between sound-producing actions and the resultant sound. The postdoctoral fellow shall work closely together with the other researchers in the fourMs group, taking part in joint studies, experiments, publications and dissemination efforts, including both scientific and more artistic and practice-related sub-projects. The main purpose of the post-doctoral research fellowship is to qualify for work in top academic positions within their disciplines. The postdoctoral fellowship period is three years. The position entails a 10% compulsory workload per year of teaching and supervision duties. Please see regulations concerning other conditions of employment for research fellowship positions. The proposed starting date for the fellowship is fall 2013. ## Qualifications and Personal Skills ## In assessing the applications, special emphasis will be placed on the quality and extent of previous research, relevance of scientific qualifications for the announced fellowship position and personal qualifications for team-work and international collaboration, the quality of the project description, and on the assumed academic and personal ability on the part of the candidates to complete the project within the given time frame. ## Requirements ## - A PhD degree in an area of relevance for research on sound-producing actions. - The doctoral dissertation must have been submitted for evaluation by the closing date of the application. ## We offer ## - salary level 57 - 64 (NOK 473 400 - 538 700, depending on level of expertise) - Broad training possibilities within a stimulating academic environment - Attractive welfare arrangements - Favorable pension arrangement ## Submissions ## Applicants must submit the following attachments with the electronic application, preferably in pdf format: - letter of application - Curriculum Vitae - list of publications - project description of 3 - 5 pages, including a schedule of activities. The project description must clarify how the applicant will approach the post-doctoral project theme theoretically and methodically, and specify how the project will be completed within the given time frame Applicants who graduated at a foreign higher education institution are expected to submit an explanation of their institution’s grading system. Please be aware that all documents should be in English or a Scandinavian language. Please also refer to the Regulations concerning Post-Doctoral Research Fellowships. Qualified and short-listed applicants will be invited for an interview. The University of Oslo has an agreement for all employees, aiming to secure rights to research results. According to the Norwegian Freedom of Information Act, information about an applicant may be included in the public list of applicants, even if non-disclosure has been requested. The University of Oslo aims to achieve a balanced gender composition in the workforce and to recruit people with ethnic minority backgrounds. ## General ## Application deadline: 5 August 2013 Expected Start Date: Fall 2013 Reference number: 2013/6355 Contacts: Administrative Head of Department Ellen Wingerei Telephone: +47 22 84 44 28 fourMs project leader Professor Rolf Inge Godøy Telephone: +47 22 85 40 64 Head of Department Alexander Refsum Jensenius Telephone: +47 22 84 48 34 http://uio.easycruit.com/vacancy/982967/62048?iso=no -- Alexander Refsum Jensenius, Ph.D. Head of Department Department of Musicology University of Oslo http://www.hf.uio.no/imv/english/ ___
Re: [PD] compiling pix_opencv on debian (lmde)
2013/6/20 yvan volochine yvan...@gmail.com On 20/06/13 15:04, Antoine Villeret wrote: thanks for this I just tested your patch with a fresh install of Ubuntu and it doesn't work pix_opencv still depends both on opencv 1.5 and 2.3 it's a shame but I'll fix this later yep, I thought that this might be archlinux specific, that's why I didn't officialy submit my patch =) afaik not this is related to opencv 2.4.5... libopencv-dev is version 2.3.1 the others are legacy and install among others cv.h concerning, pix_opencv_blobtrack, which version of opencv are you using ? check it with : echo $(pkg-config --modversion opencv) 2.4.5 i've just build it and yes it breaks compatibility... I've push a fixed version to svn it should work with both version could you please test it with 2.4.5 ? thanks for pointing that a ciao, y -- http://yvanvolochine.com http://soundcloud.com/**yvanvolochinehttp://soundcloud.com/yvanvolochine http://soundcloud.com/**elgusanorojo http://soundcloud.com/elgusanorojo http://vimeo.com/yv __**_ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/** listinfo/pd-list http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] l2ork externals install
On 06/20/2013 11:35 AM, András Murányi wrote: On Thu, Jun 20, 2013 at 3:56 PM, Ivica Ico Bukvic i...@vt.edu mailto:i...@vt.edu wrote: I am still in the process of cleaning up externals to make sure they are stable and robust enough to be included. This is a time-consuming process. Some of the work was already started by a colleague Stephen Carl but a lot more work remains. If you (or anyone else) would like to contribute to this process, we do have a google doc up that goes through each external and annotates what needs to be done (e.g. is it stable, does it have robust documentation, like the one Jonathan has been working on, is it a GUI object that needs additional changes to make it accelerated within pd-l2ork etc.). That said, I think iem lib should be included as far as I can tell (but may be wrong as well). extra folder does have a collection of iem* subfolders, but I am not sure which specific object is missing. If you can send me specific list of objects missing I can investigate further. Well, not a definite list, but: - moonlib and flatspace: are in the sources, not compiled by default, but added to LIB_TARGETS in externals/Makefile can be compiled, installed and they do work, Those have been disabled in pd-l2ork as they have way too many problems or are redundant. Please correct me if I am missing something. - loaders(/libdir): in the sources, not compiled by default, I compiled and installed it manually, and it works, I have that one just fine. - miXed(/toxy): in the sources, not compiled by default, I compiled it manually and installed it even more manually (ie make install doesn't work), and I only tested 'widget', which party works. I need it badly though, and 'widget popop', which I use, happens to work. Definitely needs some massaging to be included. Ditto for these just like flatspace and moonlib. - iem*: are in the sources, seem to be not compiled by default - and this is where I chose to write to the list so cannot yet tell about compile/install. What about all the iem* folders inside the extra/ folder? What objects exactly are missing? I have: iem16 iem_adaptfilt iem_ambi iem_bin_ambi iem_delay iemgui iemguts iemlib iemmatrix iem_roomsim iem_spec2 iem_tab iemxmlrpc Are you by any chance running a self-built deb? If so, have you made sure to install all the dev libs? Seems to me if you've built your own binaries that you may have not successfully built all the libs and that something has silently failed. Checking the build log may shed some light as to what is going on. András On 06/20/2013 08:43 AM, András Murányi wrote: Hi All, Hi Ivica, I've reinstalled my box and I'm reinstalling l2ork and I'm having a hard time getting all the externals I need in place. Is it possible that some externals are built with ./tar_em_up.sh -F but not installed with make install? I got to admit I'm a bit confused (about which ones) because I've already built and installed moonlib and miXed manually, but now that I've arrived to iem* I see the binaries are in the build folder but not in /usr/lib/pd-l2ork/extra. I'd appreciate some guidance... Thanks! András ___ Pd-list@iem.at mailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -http://lists.puredata.info/listinfo/pd-list -- Ivica Ico Bukvic, D.M.A Composition, Music Technology Director, DISIS Interactive Sound Intermedia Studio Director, L2Ork Linux Laptop Orchestra Head, ICAT IMPACT Studio Virginia Tech Department of Music Blacksburg, VA 24061-0240 (540) 231-6139 (540) 231-5034 (fax) disis.music.vt.edu l2ork.music.vt.edu ico.bukvic.net ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] l2ork externals install
On Fri, Jun 21, 2013 at 12:36 AM, Ivica Ico Bukvic i...@vt.edu wrote: On 06/20/2013 11:35 AM, András Murányi wrote: On Thu, Jun 20, 2013 at 3:56 PM, Ivica Ico Bukvic i...@vt.edu wrote: I am still in the process of cleaning up externals to make sure they are stable and robust enough to be included. This is a time-consuming process. Some of the work was already started by a colleague Stephen Carl but a lot more work remains. If you (or anyone else) would like to contribute to this process, we do have a google doc up that goes through each external and annotates what needs to be done (e.g. is it stable, does it have robust documentation, like the one Jonathan has been working on, is it a GUI object that needs additional changes to make it accelerated within pd-l2ork etc.). That said, I think iem lib should be included as far as I can tell (but may be wrong as well). extra folder does have a collection of iem* subfolders, but I am not sure which specific object is missing. If you can send me specific list of objects missing I can investigate further. Well, not a definite list, but: - moonlib and flatspace: are in the sources, not compiled by default, but added to LIB_TARGETS in externals/Makefile can be compiled, installed and they do work, Those have been disabled in pd-l2ork as they have way too many problems or are redundant. Please correct me if I am missing something. I use moonlib/mknob which is unique because you can set its characteristics, which is the way it reacts to mouse movements. The flatspace/knob object is more simplistic, but without either, there's only vslider and hslider. There's also flatspace/comport, I'm not aware if there is a better alternative. - loaders(/libdir): in the sources, not compiled by default, I compiled and installed it manually, and it works, I have that one just fine. I didn't! - miXed(/toxy): in the sources, not compiled by default, I compiled it manually and installed it even more manually (ie make install doesn't work), and I only tested 'widget', which party works. I need it badly though, and 'widget popop', which I use, happens to work. Definitely needs some massaging to be included. Ditto for these just like flatspace and moonlib. Yeah they are in a bad shape but 'miXed/toxy/widget popup' is the last fully functioning dropdown combo box I can get. - iem*: are in the sources, seem to be not compiled by default - and this is where I chose to write to the list so cannot yet tell about compile/install. What about all the iem* folders inside the extra/ folder? What objects exactly are missing? I have: iem16 iem_adaptfilt iem_ambi iem_bin_ambi iem_delay iemgui iemguts iemlib iemmatrix iem_roomsim iem_spec2 iem_tab iemxmlrpc I don't have these. Are you by any chance running a self-built deb? If so, have you made sure to install all the dev libs? Seems to me if you've built your own binaries that you may have not successfully built all the libs and that something has silently failed. Checking the build log may shed some light as to what is going on. I used tar_em_up.sh -F (then untar and make install) which produced the following in /usr/local/lib/pd-l2ork (I've removed the manually built ones from the list): adaptive expr~ parazit-help.pd array2list.pd expr~.pd_linuxparazit.pd arrayreset.pd expr.pd_linux patch_name-help.pd arraysize ext13 patch_name.pd_linux bassemu~ fexpr~.pd_linux pd~ boids fiddle~ pd-wavelet bonk~pique bsaylorGem pixeltango choice hilbert~-help.pd purepd complex-mod~-help.pd hilbert~.pd README.txt complex-mod~.pdjmmmp rev1-final.pd comportK12 rev1~-help.pd controctopus la-kitchenrev1~.pd creb rev1-stage.pd cxclist-abs rev2~-help.pd cycloneloop~ rev2~.pd disis_netreceive-help.pd lrshift~ rev3~-help.pd disis_netreceive.pd_linux Makefile.am rev3~.pd disis_netsend-help.pd makefile.subdir rradical disis_netsend.pd_linux memento rtc disis_phasor~-help.pd memento-p sfruit disis_phasor~.pd_linux sigmund~ disis_wiimote-help.pdspectdelay~-help.pd disis_wiimote.pd_linux nsend spectdelay~.pd_linux earplug~ output~-help.pd stdout ekext output~.pdtimestretch btw the original LIB_TARGETS = adaptive arraysize bassemu boids bsaylor comport creb cxc cyclone earplug ekext ext13 freeverb ggee hcs iem_ambi iem_bin_ambi iemlib iemgui iemguts iem_adaptfilt iemmatrix iemxmlrpc iem_delay
Re: [PD] l2ork externals install
On 06/20/2013 08:20 PM, András Murányi wrote: I used tar_em_up.sh -F (then untar and make install) which produced the following in /usr/local/lib/pd-l2ork (I've removed the manually built ones from the list): adaptive expr~ parazit-help.pd array2list.pd expr~.pd_linuxparazit.pd arrayreset.pd expr.pd_linux patch_name-help.pd arraysize ext13 patch_name.pd_linux bassemu~ fexpr~.pd_linux pd~ boids fiddle~ pd-wavelet bonk~pique bsaylorGem pixeltango choice hilbert~-help.pd purepd complex-mod~-help.pd hilbert~.pd README.txt complex-mod~.pdjmmmp rev1-final.pd comportK12 rev1~-help.pd controctopus la-kitchenrev1~.pd creb rev1-stage.pd cxclist-abs rev2~-help.pd cycloneloop~ rev2~.pd disis_netreceive-help.pd lrshift~ rev3~-help.pd disis_netreceive.pd_linux Makefile.am rev3~.pd disis_netsend-help.pd makefile.subdir rradical disis_netsend.pd_linux memento rtc disis_phasor~-help.pd memento-p sfruit disis_phasor~.pd_linux sigmund~ disis_wiimote-help.pd spectdelay~-help.pd disis_wiimote.pd_linux nsend spectdelay~.pd_linux earplug~ output~-help.pd stdout ekext output~.pdtimestretch The dev libs were installed according to the l2ork web page, and none of them were unavailable. As for the build log, is there one? Or you meant the console output? Sorry, I meant console output redirect. I haven't tried -F in a while since it is pretty much all but deprecated (particularly since now pd-l2ork only conflicts with one optional pd-extended package). Perhaps there is something in -F build format that fails when -B doesn't. It is unlikely but nonetheless possible. Can you try -B (deb)? Also, please send me build log off-list with -F so that I can investigate further. Thanks! ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
