hello,

thanks all for your answer. i fact, i've got only 1 /dev/midi* device when i plug my interface. so the problem does not really come from pd.

did anyone succesfully using multiple in / out usb/midi interface under linux (ubuntu)?

thx Cyrille

patco a écrit :

hello, you might want to try to create a symlink to your other midi ports?

http://lists.puredata.info/pipermail/pd-list/2007-08/052968.html

Le mercredi 29 octobre 2008 à 20:02 +0100, cyrille henry a écrit :

...

hello,

i've got a usb / midi device with 2 in and 2 out (bcf2000 by example, but i've got the same problem with other hardware). With pd/linux (ubuntu), i can't use the 2nd in / out : just the 1st one is usable.

does anyone know how to use device with multiple midi in / out?

thanks Cyrille

---

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

hello,

IOhannes m zmoelnig a écrit :

cyrille henry wrote:

...

hello,

thanks all for your answer. i fact, i've got only 1 /dev/midi* device when i plug my interface. so the problem does not really come from pd.

did anyone succesfully using multiple in / out usb/midi interface under linux (ubuntu)?

yes i am (i think)

my solution is:

• use alsa-midi (forget about /dev/midi*)

ok. aconnect -o and -i can see both output and input of my BCF, so it's certainly the way to go.

• open 2 alsa-midi ports from Pd

i don't really understand. did you mean that i should create 2 virtual midi device, and open them with pd? or should i have something in my pd midi configuration.

• connect your 2 hw-devices to the Pd's 2 alsa-midi ports (i usually

conveniently use qjackctl for this; but you can do so by using [aconnect] as well)

ok

• access the device connected to Pd's 1st port via channel1-16 and the

device connected to the 2nd port via channel17-32

• scale at will

ok

thanks a lot Cyrille

fgmasdr IOhannes

IOhannes m zmoelnig wrote:

the latter. starting Pd with "pd -alsamidi 1,1" (apologies for the weird syntax), should give you 2 midi-in ports and 2 midi-out ports. you can also select "alsamidi" via the media-menu, and chose the number of ports you want.

btw, i've updated the "aconnectgui" patch in externals/iem/aconnect that provides a graphical interface to change connections (from within Pd). you can now modify the number of midi-ports Pd provides from within this patch. (it doesn't set the midi-API to ALSA by itself though)

fg,adsr IOhannes

cyrille henry wrote:

IOhannes m zmoelnig a écrit : ...

...

the latter. starting Pd with "pd -alsamidi 1,1" (apologies for the weird syntax), should give you 2 midi-in ports and 2 midi-out ports.

-alsamidi did not work here (got same result than pd -help)

...

you can also select "alsamidi" via the media-menu, and chose the number of ports you want.

i don't have this choice in the media menu. i'm using vanillia pd 0.41.4.

you need alsa-headers in order to have alsamidi.

fgmasdr IOhannes

Hello,

Is is possible in Pd to produce exactly the same envelope again and again? If I send the same message to vline and use this to cut an envelope out of noise or a sine wave, it always changes a bit (if you listen carefully). (The phase is always reset, that's not the problem.) I recorded the sounds, had a look at the soundfiles in an edit program and noticed that all the envelopes were slightly different. Then I used line~ in a subpatch with blocksize 1 and did the same thing. This sounds better and if I looked at the recorded sound files they were more identical (although the release changes a bit, there seems to be a very small inaccuracy in the delay... but you can't hear this with the sine sound. The noise sound is always a bit different, I guess because it are randomly generated frequencies?). Anyway I thought that vline~ was more precise than line~ but this doesn't seem to be true...? Have a look at the file in attach.

Hans R