I've compiled Pd-0.46-4 from source, but I'd like to install some libraries. Will apt-get work, or do I have to compile them as well?
On 01/23/2015 10:06 AM, Alexandros Drymonitis wrote:
I've compiled Pd-0.46-4 from source, but I'd like to install some libraries. Will apt-get work, or do I have to compile them as well?
Pd goes to some length to stay binary compatible, so you can use the "pd-*" packages without a problem.
the main obstacle will be the search path: your self-compiled Pd will most likely search the libraries in /usr/local/lib/pd/extra whereas the pd-* packages install to /usr/lib/pd/extra/
simply adding /usr/lib/pd/extra to your search path should fix that.
gfmrdsa IOhannes
On Fri, Jan 23, 2015 at 1:46 PM, IOhannes m zmölnig zmoelnig@iem.at wrote:
On 01/23/2015 10:06 AM, Alexandros Drymonitis wrote:
I've compiled Pd-0.46-4 from source, but I'd like to install some libraries. Will apt-get work, or do I have to compile them as well?
Pd goes to some length to stay binary compatible, so you can use the "pd-*" packages without a problem.
the main obstacle will be the search path: your self-compiled Pd will most likely search the libraries in /usr/local/lib/pd/extra whereas the pd-* packages install to /usr/lib/pd/extra/
I had something like that in mind, but the Pd compiled from source didn't create a /usr/local/lib/pd directory. Everything is lying in it's own directory (in this case /home/pi/applications/pd-0.46-4/ ). Should I create the /usr/local/lib directory? Forgot to mention that I haven't installed Pd with apt-get, so there's no /usr/lib/pd either..
simply adding /usr/lib/pd/extra to your search path should fix that.
gfmrdsa IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Le 23/01/2015 13:18, Alexandros Drymonitis a écrit :
On Fri, Jan 23, 2015 at 1:46 PM, IOhannes m zmölnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> wrote:
On 01/23/2015 10:06 AM, Alexandros Drymonitis wrote: > I've compiled Pd-0.46-4 from source, but I'd like to install some > libraries. Will apt-get work, or do I have to compile them as well? Pd goes to some length to stay binary compatible, so you can use the "pd-*" packages without a problem. the main obstacle will be the search path: your self-compiled Pd will most likely search the libraries in /usr/local/lib/pd/extra whereas the pd-* packages install to /usr/lib/pd/extra/
I had something like that in mind, but the Pd compiled from source didn't create a /usr/local/lib/pd directory. Everything is lying in it's own directory (in this case /home/pi/applications/pd-0.46-4/ ).
make is only compiling pd. if you want to install pd, use make install (this require root privilege, so "sudo make install" will create the dir etc)
cheers c
Should I create the /usr/local/lib directory? Forgot to mention that I haven't installed Pd with apt-get, so there's no /usr/lib/pd either..
simply adding /usr/lib/pd/extra to your search path should fix that. gfmrdsa IOhannes _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Personally, I never use root to install - instead, I configure with, say, --prefix=/tmp/pd-test/ (after making the directory /tmp/pd-test) and then make and make install as a plain user. (If you want that version to stay around put it in your home directory somewhere, e.g., /home/msp/pdinstall or something like that).
Installing as root will do fine until you compile some other version of Pd and can't figure out how to keep them apart. - then you will end up badly confused, as I have :)
Miller
On Fri, Jan 23, 2015 at 01:30:21PM +0100, Cyrille Henry wrote:
Le 23/01/2015 13:18, Alexandros Drymonitis a écrit :
On Fri, Jan 23, 2015 at 1:46 PM, IOhannes m zmölnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> wrote:
On 01/23/2015 10:06 AM, Alexandros Drymonitis wrote:
I've compiled Pd-0.46-4 from source, but I'd like to install some libraries. Will apt-get work, or do I have to compile them as well?
Pd goes to some length to stay binary compatible, so you can use the "pd-*" packages without a problem.
the main obstacle will be the search path: your self-compiled Pd will most likely search the libraries in /usr/local/lib/pd/extra whereas the pd-* packages install to /usr/lib/pd/extra/
I had something like that in mind, but the Pd compiled from source didn't create a /usr/local/lib/pd directory. Everything is lying in it's own directory (in this case /home/pi/applications/pd-0.46-4/ ).
make is only compiling pd. if you want to install pd, use make install (this require root privilege, so "sudo make install" will create the dir etc)
cheers c
Should I create the /usr/local/lib directory? Forgot to mention that I haven't installed Pd with apt-get, so there's no /usr/lib/pd either..
simply adding /usr/lib/pd/extra to your search path should fix that.
gfmrdsa IOhannes
Pd-list@lists.iem.at mailto:Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 01/23/2015 05:43 PM, Miller Puckette wrote:
Personally, I never use root to install - instead, I configure with, say, --prefix=/tmp/pd-test/ (after making the directory /tmp/pd-test) and then make and make install as a plain user. (If you want that version to stay around put it in your home directory somewhere, e.g., /home/msp/pdinstall or something like that).
Installing as root will do fine until you compile some other version of Pd and can't figure out how to keep them apart.
like
/usr/bin/pd /usr/local/bin/pd /home/msp/pdinstall/bin/pd
?
gfamds IOhannes
Le 23/01/2015 17:43, Miller Puckette a écrit :
Personally, I never use root to install - instead, I configure with, say, --prefix=/tmp/pd-test/ (after making the directory /tmp/pd-test) and then make and make install as a plain user. (If you want that version to stay around put it in your home directory somewhere, e.g., /home/msp/pdinstall or something like that).
Installing as root will do fine until you compile some other version of Pd and can't figure out how to keep them apart. - then you will end up badly confused, as I have :)
i have only 1 pd, so i never have problem!
cheers c
Miller
On Fri, Jan 23, 2015 at 01:30:21PM +0100, Cyrille Henry wrote:
Le 23/01/2015 13:18, Alexandros Drymonitis a écrit :
On Fri, Jan 23, 2015 at 1:46 PM, IOhannes m zmölnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> wrote:
On 01/23/2015 10:06 AM, Alexandros Drymonitis wrote: > I've compiled Pd-0.46-4 from source, but I'd like to install some > libraries. Will apt-get work, or do I have to compile them as well? Pd goes to some length to stay binary compatible, so you can use the "pd-*" packages without a problem. the main obstacle will be the search path: your self-compiled Pd will most likely search the libraries in /usr/local/lib/pd/extra whereas the pd-* packages install to /usr/lib/pd/extra/
I had something like that in mind, but the Pd compiled from source didn't create a /usr/local/lib/pd directory. Everything is lying in it's own directory (in this case /home/pi/applications/pd-0.46-4/ ).
make is only compiling pd. if you want to install pd, use make install (this require root privilege, so "sudo make install" will create the dir etc)
cheers c
Should I create the /usr/local/lib directory? Forgot to mention that I haven't installed Pd with apt-get, so there's no /usr/lib/pd either..
simply adding /usr/lib/pd/extra to your search path should fix that. gfmrdsa IOhannes _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Fri, Jan 23, 2015 at 2:30 PM, Cyrille Henry ch@chnry.net wrote:
Le 23/01/2015 13:18, Alexandros Drymonitis a écrit :
On Fri, Jan 23, 2015 at 1:46 PM, IOhannes m zmölnig <zmoelnig@iem.at mailto:zmoelnig@iem.at> wrote:
On 01/23/2015 10:06 AM, Alexandros Drymonitis wrote: > I've compiled Pd-0.46-4 from source, but I'd like to install some > libraries. Will apt-get work, or do I have to compile them as well? Pd goes to some length to stay binary compatible, so you can use the "pd-*" packages without a problem. the main obstacle will be the search path: your self-compiled Pd will most likely search the libraries in /usr/local/lib/pd/extra whereas
the pd-* packages install to /usr/lib/pd/extra/
I had something like that in mind, but the Pd compiled from source didn't create a /usr/local/lib/pd directory. Everything is lying in it's own directory (in this case /home/pi/applications/pd-0.46-4/ ).
make is only compiling pd. if you want to install pd, use make install (this require root privilege, so "sudo make install" will create the dir etc)
Did that and got this at the end:
/usr/bin/install: omitting directory ./doc/7.stuff/soundfile-tools' /usr/bin/install: omitting directory
./doc/7.stuff/synth'
/usr/bin/install: omitting directory `./doc/7.stuff/tools'
Makefile:795: recipe for target 'install-nobase_dist_libpdDATA' failed
make[3]: *** [install-nobase_dist_libpdDATA] Error 1
make[3]: Leaving directory '/home/pi/applications/pd-0.46-4'
Makefile:1178: recipe for target 'install-am' failed
make[2]: *** [install-am] Error 2
make[2]: Leaving directory '/home/pi/applications/pd-0.46-4'
Makefile:847: recipe for target 'install-recursive' failed
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory '/home/pi/applications/pd-0.46-4'
Makefile:1172: recipe for target 'install' failed
make: *** [install] Error 2
/usr/local/bin/pd now exists, as well as /usr/local/lib/pd, but there were some stuff missing from the latter. doc/7.stuff/ had only the synth/ directory (I copied all the missing stuff from /home/pi/applications/pd-0.46-4/doc/7/stuff) and 4.data.structures/ was missing altogether. Also bin/ had only pd and pd-watchdog, but no pdsend and pdreceive (also copied from /home/pi/applications/pd-0.46-4/bin).
Pd launches, but doesn't really work. I get this message in Pd's console when it starts :API 1 not supported, reverting to 2 (OSS) and opening testtone.pd, results in these messages: /dev/dsp (read/write): No such file or directory (now will try write-only...) /dev/dsp (writeonly): No such file or directory /dev/dsp (readonly): No such file or directory audio I/O stuck... closing audio
and the audio won't work...
Still, if I launch Pd from /home/pi/applications/pd-0.46-4/bin/pd everything works fine, except that it crashes with some externals I tried to use..
cheers c
Should I create the /usr/local/lib directory?
Forgot to mention that I haven't installed Pd with apt-get, so there's no /usr/lib/pd either..
simply adding /usr/lib/pd/extra to your search path should fix that. gfmrdsa IOhannes _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/
listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
when there is some problem with sudo make install, i use sudo make install -k, so that the problem is skiped, but everything else is still installed... cheers c
Le 24/01/2015 11:16, Alexandros Drymonitis a écrit :
On Fri, Jan 23, 2015 at 2:30 PM, Cyrille Henry <ch@chnry.net mailto:ch@chnry.net> wrote:
Le 23/01/2015 13:18, Alexandros Drymonitis a écrit : On Fri, Jan 23, 2015 at 1:46 PM, IOhannes m zmölnig <zmoelnig@iem.at <mailto:zmoelnig@iem.at> <mailto:zmoelnig@iem.at <mailto:zmoelnig@iem.at>>> wrote: On 01/23/2015 10:06 AM, Alexandros Drymonitis wrote: > I've compiled Pd-0.46-4 from source, but I'd like to install some > libraries. Will apt-get work, or do I have to compile them as well? Pd goes to some length to stay binary compatible, so you can use the "pd-*" packages without a problem. the main obstacle will be the search path: your self-compiled Pd will most likely search the libraries in /usr/local/lib/pd/extra whereas the pd-* packages install to /usr/lib/pd/extra/ I had something like that in mind, but the Pd compiled from source didn't create a /usr/local/lib/pd directory. Everything is lying in it's own directory (in this case /home/pi/applications/pd-0.46-__4/ ). make is only compiling pd. if you want to install pd, use make install (this require root privilege, so "sudo make install" will create the dir etc)
Did that and got this at the end: /usr/bin/install: omitting directory
./doc/7.stuff/soundfile-tools' /usr/bin/install: omitting directory
./doc/7.stuff/synth' /usr/bin/install: omitting directory `./doc/7.stuff/tools' Makefile:795: recipe for target 'install-nobase_dist_libpdDATA' failed make[3]: *** [install-nobase_dist_libpdDATA] Error 1 make[3]: Leaving directory '/home/pi/applications/pd-0.46-4' Makefile:1178: recipe for target 'install-am' failed make[2]: *** [install-am] Error 2 make[2]: Leaving directory '/home/pi/applications/pd-0.46-4' Makefile:847: recipe for target 'install-recursive' failed make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory '/home/pi/applications/pd-0.46-4' Makefile:1172: recipe for target 'install' failed make: *** [install] Error 2/usr/local/bin/pd now exists, as well as /usr/local/lib/pd, but there were some stuff missing from the latter. doc/7.stuff/ had only the synth/ directory (I copied all the missing stuff from /home/pi/applications/pd-0.46-4/doc/7/stuff) and 4.data.structures/ was missing altogether. Also bin/ had only pd and pd-watchdog, but no pdsend and pdreceive (also copied from /home/pi/applications/pd-0.46-4/bin).
Pd launches, but doesn't really work. I get this message in Pd's console when it starts :API 1 not supported, reverting to 2 (OSS) and opening testtone.pd, results in these messages: /dev/dsp (read/write): No such file or directory (now will try write-only...) /dev/dsp (writeonly): No such file or directory /dev/dsp (readonly): No such file or directory audio I/O stuck... closing audio
and the audio won't work...
Still, if I launch Pd from /home/pi/applications/pd-0.46-4/bin/pd everything works fine, except that it crashes with some externals I tried to use..
cheers c Should I create the /usr/local/lib directory? Forgot to mention that I haven't installed Pd with apt-get, so there's no /usr/lib/pd either.. simply adding /usr/lib/pd/extra to your search path should fix that. gfmrdsa IOhannes _________________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> <mailto:Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at>> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/__listinfo/pd-list <http://lists.puredata.info/listinfo/pd-list> _________________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/__listinfo/pd-list <http://lists.puredata.info/listinfo/pd-list>
On Sat, Jan 24, 2015 at 12:22 PM, Cyrille Henry ch@chnry.net wrote:
when there is some problem with sudo make install, i use sudo make install -k, so that the problem is skiped, but everything else is still installed... cheers c
Did that too. Again had some stuff missing in /usr/local/lib/pd/doc, but copied them from ~/applications/pd-0.46-4/doc. Wrongly I thought that pdsend and pdreceive should lie in /usr/local/lib/bin, I realised they're in /usr/local/bin.
Pd now launches, but as soon as I turn the DSP on I get this: /dev/dsp (read/write): No such file or directory (now will try write-only...) /dev/dsp (writeonly): No such file or directory /dev/dsp (readonly): No such file or directory audio I/O stuck... closing audio
and obviously there's no /dev/dsp Is this file supposed to be created by the Makefile? Can I create this manually - copy it from somewhere?
Le 25/01/2015 11:18, Alexandros Drymonitis a écrit :
On Sat, Jan 24, 2015 at 12:22 PM, Cyrille Henry <ch@chnry.net mailto:ch@chnry.net> wrote:
when there is some problem with sudo make install, i use sudo make install -k, so that the problem is skiped, but everything else is still installed... cheers c
Did that too. Again had some stuff missing in /usr/local/lib/pd/doc, but copied them from ~/applications/pd-0.46-4/doc. Wrongly I thought that pdsend and pdreceive should lie in /usr/local/lib/bin, I realised they're in /usr/local/bin.
Pd now launches, but as soon as I turn the DSP on I get this: /dev/dsp (read/write): No such file or directory (now will try write-only...) /dev/dsp (writeonly): No such file or directory /dev/dsp (readonly): No such file or directory audio I/O stuck... closing audio
and obviously there's no /dev/dsp Is this file supposed to be created by the Makefile? Can I create this manually - copy it from somewhere?
no, this is supposed to be your soundcard. this "file" should be create by oss driver. try starting pd with -alsa flag. cheers c
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 25/01/15 10:18, Alexandros Drymonitis wrote:
and obviously there's no /dev/dsp
Depends on the specific versions on your rPi, but try:
add 'snd_pcm_oss' to '/etc/modules' to make it work after reboot 'modprobe snd_pcm_oss' to make it work before rebooting http://www.raspberrypi.org/forums/viewtopic.php?f=38&t=15253
or try:
install 'alsa-oss' if you haven't already got it run 'aoss pd' instead of 'pd' https://help.ubuntu.com/community/alsa-oss
Note: I have no rPi, so I haven't tested these suggestions...
On Sun, Jan 25, 2015 at 12:33 PM, Claude Heiland-Allen claude@mathr.co.uk wrote:
On 25/01/15 10:18, Alexandros Drymonitis wrote:
and obviously there's no /dev/dsp
Depends on the specific versions on your rPi, but try:
add 'snd_pcm_oss' to '/etc/modules' to make it work after reboot 'modprobe snd_pcm_oss' to make it work before rebooting http://www.raspberrypi.org/forums/viewtopic.php?f=38&t=15253
or try:
install 'alsa-oss' if you haven't already got it run 'aoss pd' instead of 'pd' https://help.ubuntu.com/community/alsa-oss
This last one did it! Launching Pd with -oss won't work (it can't find /dev/dsp), but launching it like you suggest "aoss /usr/local/bin/pd" outputs audio properly.
Thanks
On 01/25/2015 12:08 PM, Alexandros Drymonitis wrote:
On Sun, Jan 25, 2015 at 12:33 PM, Claude Heiland-Allen claude@mathr.co.uk wrote:
On 25/01/15 10:18, Alexandros Drymonitis wrote:
and obviously there's no /dev/dsp
Depends on the specific versions on your rPi, but try:
add 'snd_pcm_oss' to '/etc/modules' to make it work after reboot 'modprobe snd_pcm_oss' to make it work before rebooting http://www.raspberrypi.org/forums/viewtopic.php?f=38&t=15253
or try:
install 'alsa-oss' if you haven't already got it run 'aoss pd' instead of 'pd' https://help.ubuntu.com/community/alsa-oss
This last one did it! Launching Pd with -oss won't work (it can't find
obviously, since "pd -oss" does the same as "pd": it tries using the OSS-drivers. but...
/dev/dsp), but launching it like you suggest "aoss /usr/local/bin/pd" outputs audio properly.
you really should avoid using OSS (unless forced to, because your soundcard only has OSSv4 drivers). use "pd -alsa" to use ALSA directly. (the hacks mentioned in the other mail really emulate the OSS layer on top of ALSA...)
the debian packages usually modify Pd so that ALSA is the default (which is probably the reason why you haven't run into this problem before).
gfamdsr IOhannes
On Sun, Jan 25, 2015 at 6:28 PM, IOhannes m zmölnig zmoelnig@iem.at wrote:
install 'alsa-oss' if you haven't already got it run 'aoss pd' instead of 'pd' https://help.ubuntu.com/community/alsa-oss
This last one did it! Launching Pd with -oss won't work (it can't find
obviously, since "pd -oss" does the same as "pd": it tries using the OSS-drivers. but...
/dev/dsp), but launching it like you suggest "aoss /usr/local/bin/pd" outputs audio properly.
you really should avoid using OSS (unless forced to, because your soundcard only has OSSv4 drivers). use "pd -alsa" to use ALSA directly. (the hacks mentioned in the other mail really emulate the OSS layer on top of ALSA...)
The thing is that when I launch Pd with the -alsa flag, I get a prompt of the available flags, and Pd doesn't launch (and -alsa and -jack is not there, even though I configured Pd with --enable-jack). Do you have to configure Pd with ALSA explicitly when compiling from source?
Aha - Pd somehow got compiled without ALSA support - perhaps, when you compiled Pd, you had not yet installed alsa-devel. Install alsa-devel and recompile Pd.
cheers Miller
On Sun, Jan 25, 2015 at 07:05:41PM +0200, Alexandros Drymonitis wrote:
On Sun, Jan 25, 2015 at 6:28 PM, IOhannes m zmölnig zmoelnig@iem.at wrote:
install 'alsa-oss' if you haven't already got it run 'aoss pd' instead of 'pd' https://help.ubuntu.com/community/alsa-oss
This last one did it! Launching Pd with -oss won't work (it can't find
obviously, since "pd -oss" does the same as "pd": it tries using the OSS-drivers. but...
/dev/dsp), but launching it like you suggest "aoss /usr/local/bin/pd" outputs audio properly.
you really should avoid using OSS (unless forced to, because your soundcard only has OSSv4 drivers). use "pd -alsa" to use ALSA directly. (the hacks mentioned in the other mail really emulate the OSS layer on top of ALSA...)
The thing is that when I launch Pd with the -alsa flag, I get a prompt of the available flags, and Pd doesn't launch (and -alsa and -jack is not there, even though I configured Pd with --enable-jack). Do you have to configure Pd with ALSA explicitly when compiling from source?
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Sun, Jan 25, 2015 at 7:57 PM, Miller Puckette msp@ucsd.edu wrote:
Aha - Pd somehow got compiled without ALSA support - perhaps, when you compiled Pd, you had not yet installed alsa-devel. Install alsa-devel and recompile Pd.
Do I have to delete all the Pd files to recompile, or can I keep them?
I'd delete the Pd source tree - I think all the auxilliary stuff can stay. But it wouldn't hurt to start over altogether - that way you'd know exactly what you have :)
M
On Sun, Jan 25, 2015 at 08:28:30PM +0200, Alexandros Drymonitis wrote:
On Sun, Jan 25, 2015 at 7:57 PM, Miller Puckette msp@ucsd.edu wrote:
Aha - Pd somehow got compiled without ALSA support - perhaps, when you compiled Pd, you had not yet installed alsa-devel. Install alsa-devel and recompile Pd.
Do I have to delete all the Pd files to recompile, or can I keep them?
Am Sonntag, 25. Januar 2015 19:58 CET, Miller Puckette msp@ucsd.edu schrieb:
I'd delete the Pd source tree - I think all the auxilliary stuff can stay. But it wouldn't hurt to start over altogether - that way you'd know exactly what you have :)
Hmm,
./config.status --recheck
should do the trick. If not, the automake build is broken and should be fixed. If you want to change the configuration parameters
make clean ./configure
should work.
Cheers, Ralf Mattes
M
On Sun, Jan 25, 2015 at 08:28:30PM +0200, Alexandros Drymonitis wrote:
On Sun, Jan 25, 2015 at 7:57 PM, Miller Puckette msp@ucsd.edu wrote:
Aha - Pd somehow got compiled without ALSA support - perhaps, when you compiled Pd, you had not yet installed alsa-devel. Install alsa-devel and recompile Pd.
Do I have to delete all the Pd files to recompile, or can I keep them?
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Sun, Jan 25, 2015 at 7:57 PM, Miller Puckette msp@ucsd.edu wrote:
Aha - Pd somehow got compiled without ALSA support - perhaps, when you compiled Pd, you had not yet installed alsa-devel. Install alsa-devel and recompile Pd.
apt-get can't find any alsa-devel...
apt-cache search "^alsa-" gave this: alsa-base - ALSA driver configuration files alsa-firmware-loaders - ALSA software loaders for specific hardware alsa-oss - ALSA wrapper for OSS applications alsa-source - ALSA driver sources alsa-tools - Console based ALSA utilities for specific hardware alsa-tools-gui - GUI based ALSA utilities for specific hardware alsa-utils - Utilities for configuring and using ALSA
maybe alsa-utils?
cheers Miller
On Sun, Jan 25, 2015 at 07:05:41PM +0200, Alexandros Drymonitis wrote:
On Sun, Jan 25, 2015 at 6:28 PM, IOhannes m zmölnig zmoelnig@iem.at
wrote:
install 'alsa-oss' if you haven't already got it run 'aoss pd' instead of 'pd' https://help.ubuntu.com/community/alsa-oss
This last one did it! Launching Pd with -oss won't work (it can't
find
obviously, since "pd -oss" does the same as "pd": it tries using the OSS-drivers. but...
/dev/dsp), but launching it like you suggest "aoss /usr/local/bin/pd" outputs audio properly.
you really should avoid using OSS (unless forced to, because your soundcard only has OSSv4 drivers). use "pd -alsa" to use ALSA directly. (the hacks mentioned in the other mail really emulate the OSS layer on top of ALSA...)
The thing is that when I launch Pd with the -alsa flag, I get a prompt of the available flags, and Pd doesn't launch (and -alsa and -jack is not there, even though I configured Pd with --enable-jack). Do you have to configure Pd with ALSA explicitly when compiling from source?
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->
Sorry, my bad - I think on apt-get it's 'alsa-dev' (but 'alsa-devel' on RPM... go figure)
M
On Sun, Jan 25, 2015 at 09:28:25PM +0200, Alexandros Drymonitis wrote:
On Sun, Jan 25, 2015 at 7:57 PM, Miller Puckette msp@ucsd.edu wrote:
Aha - Pd somehow got compiled without ALSA support - perhaps, when you compiled Pd, you had not yet installed alsa-devel. Install alsa-devel and recompile Pd.
apt-get can't find any alsa-devel...
apt-cache search "^alsa-" gave this: alsa-base - ALSA driver configuration files alsa-firmware-loaders - ALSA software loaders for specific hardware alsa-oss - ALSA wrapper for OSS applications alsa-source - ALSA driver sources alsa-tools - Console based ALSA utilities for specific hardware alsa-tools-gui - GUI based ALSA utilities for specific hardware alsa-utils - Utilities for configuring and using ALSA
maybe alsa-utils?
cheers Miller
On 25/01/15 19:28, Alexandros Drymonitis wrote:
apt-get can't find any alsa-devel...
apt-get install libasound2-dev
or to save time when you forget yet another thing:
apt-get build-dep puredata
note: this last command might do weird things with libjack-dev (at least it does here), so run with -s ("simulate") first to avoid trashing your system accidentally...
Am Sonntag, 25. Januar 2015 20:28 CET, Alexandros Drymonitis adrcki@gmail.com schrieb:
On Sun, Jan 25, 2015 at 7:57 PM, Miller Puckette msp@ucsd.edu wrote:
Aha - Pd somehow got compiled without ALSA support - perhaps, when you compiled Pd, you had not yet installed alsa-devel. Install alsa-devel and recompile Pd.
apt-get can't find any alsa-devel...
You want to look for the development package for libasound (that's how alsa's client library is called in Debian).
$ apt-cache search libasound-dev libasound2-dev - shared library for ALSA applications -- development files
HTH Ralf Mattes
Am Sonntag, 25. Januar 2015 20:46 CET, "Mattes" r.mattes@mh-freiburg.de schrieb:
Am Sonntag, 25. Januar 2015 20:28 CET, Alexandros Drymonitis adrcki@gmail.com schrieb:
On Sun, Jan 25, 2015 at 7:57 PM, Miller Puckette msp@ucsd.edu wrote:
$ apt-cache search libasound-dev libasound2-dev - shared library for ALSA applications -- development files
In general, if you want to compile on Debian I suggest downloading the debian sources
apt-get source puredata
In the downloaded nad extracted source you'll find a direcetory 'debian' that contains a file 'conrol'. That file will list all packages that need to be installed to successfully build the package.
cat debian/control ... Build-Depends: debhelper (>= 7.0.50~), dh-autoreconf, dpkg-dev (>= 1.16.1~), gettext, libasound2-dev [linux-any], portaudio19-dev, libjack-dev ...
I would _not_ recomend 'apt-get build-dep since I might install all sorts of stuff you don't want or need (for a self-compiled puredata you don't need dh-aoutreconf, dpkg-dev etc).
Cheers, RalfD
Hi,
I did build puredata from Raspbian jessie source on Raspberry Pi following directives from IOhannes and described here:
http://lists.puredata.info/pipermail/pd-list/2014-11/108543.html
It was a smooth process with good result. This is about puredata 0.46-2 however, the latest on Raspbian repository.
Katja
On Sun, Jan 25, 2015 at 8:53 PM, Mattes r.mattes@mh-freiburg.de wrote:
Am Sonntag, 25. Januar 2015 20:46 CET, "Mattes" r.mattes@mh-freiburg.de schrieb:
Am Sonntag, 25. Januar 2015 20:28 CET, Alexandros Drymonitis adrcki@gmail.com schrieb:
On Sun, Jan 25, 2015 at 7:57 PM, Miller Puckette msp@ucsd.edu wrote:
$ apt-cache search libasound-dev libasound2-dev - shared library for ALSA applications -- development files
In general, if you want to compile on Debian I suggest downloading the debian sources
apt-get source puredata
In the downloaded nad extracted source you'll find a direcetory 'debian' that contains a file 'conrol'. That file will list all packages that need to be installed to successfully build the package.
cat debian/control ... Build-Depends: debhelper (>= 7.0.50~), dh-autoreconf, dpkg-dev (>= 1.16.1~), gettext, libasound2-dev [linux-any], portaudio19-dev, libjack-dev ...
I would _not_ recomend 'apt-get build-dep since I might install all sorts of stuff you don't want or need (for a self-compiled puredata you don't need dh-aoutreconf, dpkg-dev etc).
Cheers, RalfD
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Am Sonntag, 25. Januar 2015 21:25 CET, katja katjavetter@gmail.com schrieb:
Hi,
I did build puredata from Raspbian jessie source on Raspberry Pi following directives from IOhannes and described here:
http://lists.puredata.info/pipermail/pd-list/2014-11/108543.html
It was a smooth process with good result. This is about puredata 0.46-2 however, the latest on Raspbian repository.
Katja
N.B.: if you want to compile/build the debian package then 'apt-get build-dep' is of course the way to go. If you want to compile the upstream source than some of the dependencies aren't neccessary (and often install a lot of unneeded stuff - esp. on a limited system like the Rasberry Pi).
Cheers, RalfD
On Sun, Jan 25, 2015 at 12:33 PM, Claude Heiland-Allen claude@mathr.co.uk wrote:
On 25/01/15 10:18, Alexandros Drymonitis wrote:
and obviously there's no /dev/dsp
Depends on the specific versions on your rPi, but try:
add 'snd_pcm_oss' to '/etc/modules' to make it work after reboot 'modprobe snd_pcm_oss' to make it work before rebooting http://www.raspberrypi.org/forums/viewtopic.php?f=38&t=15253
Coming back after a few days. adding 'snd_pcm_oss' to /etc/modules also did it. I don't need to launch Pd via aoss anymore, I launch it properly (/usr/local/bin/pd) and audio works fine. Thanks!
or try:
install 'alsa-oss' if you haven't already got it run 'aoss pd' instead of 'pd' https://help.ubuntu.com/community/alsa-oss
Am 23. Jänner 2015 13:18:27 MEZ, schrieb Alexandros Drymonitis adrcki@gmail.com:
Forgot to mention that I haven't installed Pd with apt-get, so there's no /usr/lib/pd either..
Installing any external via pd-* package will
mfg.ugd.fhj IOhannes
-- Sent from my pdp-11