-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I've started playing with PD, and so far I am really enjoying it.
I'm using the Debian Sid package (0.40.2-2) on an amd64 (Intel Core 2 Duo) system, using JACK. Everything seems to work perfectly. In fact, PD is the only music language that works at all out-of-the-box on this 64-bit hardware.
So far I'm finding what I need in the docs and via Google. A couple things still evade me though:
1) PD doesn't seem to run in realtime mode when using the -rt flag. The docs say that this requires "root mode", but that doesn't make any sense. JACK and dozens of softsynths work in RT mode as a non-root user, using PAM (new method) or capabilities module. But I'm not sure how to get PD to do that.
2) I'm confused by the Debian puredata package versus pd-externals and pd-extended. I found an ancient package of pd-externals, but it seems that some (vu, for example) of those are now in the main puredata package. However others (cheby~, for example) aren't. The only one I really need is the ladspa~ external, but I'm not sure where to find it or how to install it without clobbering or interfering with the main puredata package.
3) I found the source to OSCx on SourceForge, but it looks ancient (i.e. from 2002), which includes it's own statically-linked (and very old) version of libosc. Is that really the latest release? I'm thrilled that PD makes working with MIDI so easy, but I am going to want to use OSC too.
4) I can't seem to figure out how to save audio settings such that pd starts up JACK and ALSA MIDI upon startup. Every time I start it, I have to manually go into the Media menu, and select JACK, and tell it how many audio ports (it doesn't remember), and select the ALSA-MIDI dialog box and tell it how many MIDI ports (it *does* remember that), before it opens the ALSA port. I'd like both to happen automatically at startup. I'm using "pd -rt -jack -alsamidi" but it seems to disregard those.
5) I was able to locate and run the flext and py sources (separately from all of the above), and build and install them. So far PD has been straightforward enough that I haven't had any need to mess around with embedded python, but it was nice to be able to build an external with no trouble.
Thanks!
- -ken
Hi!
Glad you are enjoying Pd.
- I found the source to OSCx on SourceForge, but it looks ancient (i.e. from 2002), which includes it's own statically-linked (and very old) version of libosc. Is that really the latest release? I'm thrilled that PD makes working with MIDI so easy, but I am going to want to use OSC too.
This part of your post really confuses me. The OSCx stuff works quite well. Why is it a problem that the code is "old"? By the way there is a "new" OSC implementation in the "mrpeach" folder, take a look if you are worried about OSCx. For the record though, I've been using sendOSC and dumpOSC for quite some time now and they work very well.
Steve
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Aug 27, 2007 at 09:45:27PM -0400, Stephen Sinclair wrote:
Hi!
Glad you are enjoying Pd.
Right now I am devouring every sample patch I can get my hands on. It seems to be really easy to modify them to suit my purposes.
A few of them require libraries for which there doesn't seem to be source available, just binaries (for i386, which I don't have). But that's probably related to the other questions in my original (snipped) post.
- I found the source to OSCx on SourceForge, but it looks ancient (i.e. from 2002), which includes it's own statically-linked (and very old) version of libosc. Is that really the latest release? I'm thrilled that PD makes working with MIDI so easy, but I am going to want to use OSC too.
This part of your post really confuses me. The OSCx stuff works quite well. Why is it a problem that the code is "old"? By the way there is a "new" OSC implementation in the "mrpeach" folder, take a look if you are worried about OSCx. For the record though, I've been using sendOSC and dumpOSC for quite some time now and they work very well.
Cool!
I wanted to make sure I wasn't going to end up installing something that has since been deprecated or superceded.
Thanks for the reply. As long as that one works, I'll be glad to install and use it. I'm off to go OSC now.
- -ken
On Aug 27, 2007, at 9:45 PM, Stephen Sinclair wrote:
Hi!
Glad you are enjoying Pd.
- I found the source to OSCx on SourceForge, but it looks ancient
(i.e. from 2002), which includes it's own statically-linked (and very old) version of libosc. Is that really the latest release? I'm thrilled that PD makes working with MIDI so easy, but I am going to want to use OSC too.
This part of your post really confuses me. The OSCx stuff works quite well. Why is it a problem that the code is "old"? By the way there is a "new" OSC implementation in the "mrpeach" folder, take a look if you are worried about OSCx. For the record though, I've been using sendOSC and dumpOSC for quite some time now and they work very well.
Hey,
I am curious, does OSCx implement time tagging at all? IIRC, that's one of the advantages of mrpeach's OSC objects.
.hc
Steve
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------ ----
I have the audacity to believe that peoples everywhere can have three meals a day for their bodies, education and culture for their minds, and dignity, equality and freedom for their spirits. - Martin Luther King, Jr.
Hans-Christoph Steiner wrote:
- I found the source to OSCx on SourceForge, but it looks ancient
(i.e. from 2002), which includes it's own statically-linked (and very old) version of libosc. Is that really the latest release? I'm thrilled that PD makes working with MIDI so easy, but I am going to want to use OSC too.
This part of your post really confuses me. The OSCx stuff works quite well. Why is it a problem that the code is "old"?
probably because it is not maintained but buggy?
By the way there is a "new" OSC implementation in the "mrpeach" folder, take a look if you are worried about OSCx. For the record though, I've been using sendOSC and dumpOSC for quite some time now and they work very well.
i was fine with the OSCx objects, until i tried to send a big (not a _really big_ message, just _big_) message and it crashed. see my bug report on this.
Hey,
I am curious, does OSCx implement time tagging at all? IIRC, that's one of the advantages of mrpeach's OSC objects.
and that is another reason why mrpeach's objects are more interesting.
mgfa.frt IOhannes
Hi Ken,
4) I can't seem to figure out how to save audio settings such that pd starts
up JACK and ALSA MIDI upon startup. Every time I start it, I have to manually go into the Media menu, and select JACK, and tell it how many audio ports (it doesn't remember), and select the ALSA-MIDI dialog box and tell it how many MIDI ports (it *does* remember that), before it opens the ALSA port. I'd like both to happen automatically at startup. I'm using "pd -rt -jack -alsamidi" but it seems to disregard those.
In Montreal I was having a problem like this, and with a little help from Iohannes, found that the following arguments worked for me:
# start jack jackd -d alsa -d hw:0 -r 44100 -p 512
# start pd pd -jack -audiodev 0 -channels 2 (without the "-channels 2" flag, it would segfault, and without the "-audiodev 0" flag it would ignore the -jack flag)
I just tried this, and it did what you're trying to do: pd -jack -audiodev 0 -channels 2 -alsamidi
hope that helps, -David M.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Aug 27, 2007 at 11:10:13PM -0400, David Merrill wrote:
Hi Ken,
- I can't seem to figure out how to save audio settings such that pd starts
up JACK and ALSA MIDI upon startup. Every time I start it, I have to manually go into the Media menu, and select JACK, and tell it how many audio ports (it doesn't remember), and select the ALSA-MIDI dialog box and tell it how many MIDI ports (it *does* remember that), before it opens the ALSA port. I'd like both to happen automatically at startup. I'm using "pd -rt -jack -alsamidi" but it seems to disregard those.
In Montreal I was having a problem like this, and with a little help from Iohannes, found that the following arguments worked for me:
# start jack jackd -d alsa -d hw:0 -r 44100 -p 512
# start pd pd -jack -audiodev 0 -channels 2 (without the "-channels 2" flag, it would segfault, and without the "-audiodev 0" flag it would ignore the -jack flag)
I just tried this, and it did what you're trying to do: pd -jack -audiodev 0 -channels 2 -alsamidi
hope that helps,
Yes! That worked perfectly. Thanks!
- -ken
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, Aug 27, 2007 at 11:10:13PM -0400, David Merrill wrote:
Hi Ken,
- I can't seem to figure out how to save audio settings such that pd starts
up JACK and ALSA MIDI upon startup. Every time I start it, I have to manually go into the Media menu, and select JACK, and tell it how many audio ports (it doesn't remember), and select the ALSA-MIDI dialog box and tell it how many MIDI ports (it *does* remember that), before it opens the ALSA port. I'd like both to happen automatically at startup. I'm using "pd -rt -jack -alsamidi" but it seems to disregard those.
In Montreal I was having a problem like this, and with a little help from Iohannes, found that the following arguments worked for me:
# start jack jackd -d alsa -d hw:0 -r 44100 -p 512
# start pd pd -jack -audiodev 0 -channels 2 (without the "-channels 2" flag, it would segfault, and without the "-audiodev 0" flag it would ignore the -jack flag)
I just tried this, and it did what you're trying to do: pd -jack -audiodev 0 -channels 2 -alsamidi
I just realized that it *almost* works.
The JACK devices are definitely created at the time that PD starts up.
But no sound comes out until I choose the "Test Audio and MIDI" window, and click on -20 or -40, and get a tone, and then click OFF.
Only *then* will audio come out of any other patches that might be loaded, even if I can see from number boxes that the patches are definitely running.
- -ken
Ken Restivo wrote:
I just realized that it *almost* works.
The JACK devices are definitely created at the time that PD starts up.
But no sound comes out until I choose the "Test Audio and MIDI" window, and click on -20 or -40, and get a tone, and then click OFF.
Only *then* will audio come out of any other patches that might be loaded, even if I can see from number boxes that the patches are definitely running.
you hae to turn the audio-engine on in order to hear something. there is a little checkbox in the main pd-window that says "compute audio", try enabling that... btw, this should be explained in the docs (if it is not, i think it is a serious omission)
fms.dr IOhannes
PS: i think it would be nicer to limit each email to just one (group of) question(s); as you can see by the answers so far, people seem to split it up anyhow, but the subjects and bureaucratic organization completely screws up. and pd-dev vs pd-list and...
-ken
_______________________________________________ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Hallo, Ken Restivo hat gesagt: // Ken Restivo wrote:
I just realized that it *almost* works.
The JACK devices are definitely created at the time that PD starts up.
But no sound comes out until I choose the "Test Audio and MIDI" window, and click on -20 or -40, and get a tone, and then click OFF.
Only *then* will audio come out of any other patches that might be loaded, even if I can see from number boxes that the patches are definitely running.
Watch the main Pd window and check, if the "compute audio" button is switched on. Pd will only compute audio if that is enabled. (The "Test Audio and MIDI" patch switches on audio/dsp calculation automatically.) This also is described in the fine HTML manual which is available through the Help-menu or online here: http://www-crca.ucsd.edu/~msp/Pd_documentation/x2.htm Everyone should read it at least once every year for the first three years of using Pd and more often during the first year.
Ciao
-
David Merrill -
Frank Barknecht -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
Ken Restivo -
Stephen Sinclair