Hi list,I got a little AKM320 usb midi keyboard for $40. Hooked it up, fired up Pd, and we're back to 2005:http://article.gmane.org/gmane.comp.multimedia.puredata.general/14675 Just change UM-1 to AKM320 and you have my error report. Well, aside from the fact that my laptop doesn't have a modem on it (though I bet if it did it'd show up in Pd's audio device list...) Any clue what's going on here, and how to fix Pd to do the right thing _without_ touching any of the state on my machine (save for the Pd binary, of course)?
Thanks,Jonathan
A fun challenge....
Does anything see it? (In particular, does the qjackctl MIDI patch bay see it?) Not that that's scientific, but that's the way I check around for whether the so-called ALSA MIDI driver can find it.
cheers Miller
On Thu, Apr 21, 2016 at 02:08:29AM +0000, Jonathan Wilkes via Pd-list wrote:
Hi list,I got a little AKM320 usb midi keyboard for $40. Hooked it up, fired up Pd, and we're back to 2005:http://article.gmane.org/gmane.comp.multimedia.puredata.general/14675 Just change UM-1 to AKM320 and you have my error report. Well, aside from the fact that my laptop doesn't have a modem on it (though I bet if it did it'd show up in Pd's audio device list...) Any clue what's going on here, and how to fix Pd to do the right thing _without_ touching any of the state on my machine (save for the Pd binary, of course)?
Thanks,Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
qjackctl has three tabs: Audio, Midi, and ALSA. The device shows up in the ALSA tab. lmms has a drop down list for midi in and midi out. It shows up on those lists, I can select it, and then I'm off making sounds. And that is using ALSA as the backend, so I know this can be done.
aconnect -o sees it:client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 20: 'AKM320' [type=kernel] 0 'AKM320 MIDI 1 '
Neither Pd nor Pd-l2ork see it or list it with --listdev. I can symlink /dev/snd/midiwhatevs to /dev/midi and it will get found and work in pd-0.46-7 (but not in Pd-l2ork-- maybe something with the 0.43 changes? not sure). But that requires me to go buy clothes from 2005 off of ebay. I don't want to do that, I want *AKM320* to show up in a dropdown list in Pd. -Jonathan On Wednesday, April 20, 2016 11:14 PM, Miller Puckette msp@ucsd.edu wrote:
A fun challenge....
Does anything see it? (In particular, does the qjackctl MIDI patch bay see it?) Not that that's scientific, but that's the way I check around for whether the so-called ALSA MIDI driver can find it.
cheers Miller
On Thu, Apr 21, 2016 at 02:08:29AM +0000, Jonathan Wilkes via Pd-list wrote:
Hi list,I got a little AKM320 usb midi keyboard for $40. Hooked it up, fired up Pd, and we're back to 2005:http://article.gmane.org/gmane.comp.multimedia.puredata.general/14675 Just change UM-1 to AKM320 and you have my error report. Well, aside from the fact that my laptop doesn't have a modem on it (though I bet if it did it'd show up in Pd's audio device list...) Any clue what's going on here, and how to fix Pd to do the right thing _without_ touching any of the state on my machine (save for the Pd binary, of course)?
Thanks,Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
BTW-- On OSX I get the correct device string "AKM320", and when I set that device everything looks to be working correctly there. I only tested with the GUI port of Pd-l2ork, but I'd assume Pd Vanilla also works there.
-Jonathan
On Wednesday, April 20, 2016 11:31 PM, Jonathan Wilkes via Pd-list <pd-list@lists.iem.at> wrote:
qjackctl has three tabs: Audio, Midi, and ALSA. The device shows up in the ALSA tab. lmms has a drop down list for midi in and midi out. It shows up on those lists, I can select it, and then I'm off making sounds. And that is using ALSA as the backend, so I know this can be done.
aconnect -o sees it:client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 20: 'AKM320' [type=kernel] 0 'AKM320 MIDI 1 '
Neither Pd nor Pd-l2ork see it or list it with --listdev. I can symlink /dev/snd/midiwhatevs to /dev/midi and it will get found and work in pd-0.46-7 (but not in Pd-l2ork-- maybe something with the 0.43 changes? not sure). But that requires me to go buy clothes from 2005 off of ebay. I don't want to do that, I want *AKM320* to show up in a dropdown list in Pd. -Jonathan On Wednesday, April 20, 2016 11:14 PM, Miller Puckette msp@ucsd.edu wrote:
A fun challenge....
Does anything see it? (In particular, does the qjackctl MIDI patch bay see it?) Not that that's scientific, but that's the way I check around for whether the so-called ALSA MIDI driver can find it.
cheers Miller
On Thu, Apr 21, 2016 at 02:08:29AM +0000, Jonathan Wilkes via Pd-list wrote:
Hi list,I got a little AKM320 usb midi keyboard for $40. Hooked it up, fired up Pd, and we're back to 2005:http://article.gmane.org/gmane.comp.multimedia.puredata.general/14675 Just change UM-1 to AKM320 and you have my error report. Well, aside from the fact that my laptop doesn't have a modem on it (though I bet if it did it'd show up in Pd's audio device list...) Any clue what's going on here, and how to fix Pd to do the right thing _without_ touching any of the state on my machine (save for the Pd binary, of course)?
Thanks,Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
So... last time I used 'alsa midi' I think It worked to start up Pd with -alsamidi, then use aconnect to make Pd's input listen to whatever source aconnect will allow it to be connected to.
But that was years ago... I'm happy to say I don't have to use MIDI very frequently.
cheers Miller
On Thu, Apr 21, 2016 at 04:04:19AM +0000, Jonathan Wilkes wrote:
BTW-- On OSX I get the correct device string "AKM320", and when I set that device everything looks to be working correctly there. I only tested with the GUI port of Pd-l2ork, but I'd assume Pd Vanilla also works there.
-Jonathan
On Wednesday, April 20, 2016 11:31 PM, Jonathan Wilkes via Pd-list <pd-list@lists.iem.at> wrote:qjackctl has three tabs: Audio, Midi, and ALSA. The device shows up in the ALSA tab. lmms has a drop down list for midi in and midi out. It shows up on those lists, I can select it, and then I'm off making sounds. And that is using ALSA as the backend, so I know this can be done.
aconnect -o sees it:client 0: 'System' [type=kernel]    0 'Timer          '    1 'Announce       ' client 14: 'Midi Through' [type=kernel]    0 'Midi Through Port-0' client 20: 'AKM320' [type=kernel]    0 'AKM320 MIDI 1  '
Neither Pd nor Pd-l2ork see it or list it with --listdev. I can symlink /dev/snd/midiwhatevs to /dev/midi and it will get found and work in pd-0.46-7 (but not in Pd-l2ork-- maybe something with the 0.43 changes? not sure). But that requires me to go buy clothes from 2005 off of ebay. I don't want to do that, I want *AKM320* to show up in a dropdown list in Pd. -Jonathan On Wednesday, April 20, 2016 11:14 PM, Miller Puckette msp@ucsd.edu wrote:
A fun challenge....
Does anything see it? (In particular, does the qjackctl MIDI patch bay see it?) Not that that's scientific, but that's the way I check around for whether the so-called ALSA MIDI driver can find it.
cheers Miller
On Thu, Apr 21, 2016 at 02:08:29AM +0000, Jonathan Wilkes via Pd-list wrote:
Hi list,I got a little AKM320 usb midi keyboard for $40. Hooked it up, fired up Pd, and we're back to 2005:http://article.gmane.org/gmane.comp.multimedia.puredata.general/14675 Just change UM-1 to AKM320 and you have my error report. Well, aside from the fact that my laptop doesn't have a modem on it (though I bet if it did it'd show up in Pd's audio device list...) Any clue what's going on here, and how to fix Pd to do the right thing _without_ touching any of the state on my machine (save for the Pd binary, of course)?
Thanks,Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
I can confirm that is still the case… J
On Apr 21, 2016, at 12:11 AM, Miller Puckette msp@ucsd.edu wrote:
So... last time I used 'alsa midi' I think It worked to start up Pd with -alsamidi, then use aconnect to make Pd's input listen to whatever source aconnect will allow it to be connected to.
But that was years ago... I'm happy to say I don't have to use MIDI very frequently.
cheers Miller
On Thu, Apr 21, 2016 at 04:04:19AM +0000, Jonathan Wilkes wrote:
BTW-- On OSX I get the correct device string "AKM320", and when I set that device everything looks to be working correctly there. I only tested with the GUI port of Pd-l2ork, but I'd assume Pd Vanilla also works there.
-Jonathan
On Wednesday, April 20, 2016 11:31 PM, Jonathan Wilkes via Pd-list pd-list@lists.iem.at wrote:
qjackctl has three tabs: Audio, Midi, and ALSA. The device shows up in the ALSA tab. lmms has a drop down list for midi in and midi out. It shows up on those lists, I can select it, and then I'm off making sounds. And that is using ALSA as the backend, so I know this can be done.
aconnect -o sees it:client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 20: 'AKM320' [type=kernel] 0 'AKM320 MIDI 1 '
Neither Pd nor Pd-l2ork see it or list it with --listdev. I can symlink /dev/snd/midiwhatevs to /dev/midi and it will get found and work in pd-0.46-7 (but not in Pd-l2ork-- maybe something with the 0.43 changes? not sure). But that requires me to go buy clothes from 2005 off of ebay. I don't want to do that, I want *AKM320* to show up in a dropdown list in Pd. -Jonathan On Wednesday, April 20, 2016 11:14 PM, Miller Puckette msp@ucsd.edu wrote:
A fun challenge....
Does anything see it? (In particular, does the qjackctl MIDI patch bay see it?) Not that that's scientific, but that's the way I check around for whether the so-called ALSA MIDI driver can find it.
cheers Miller
On Thu, Apr 21, 2016 at 02:08:29AM +0000, Jonathan Wilkes via Pd-list wrote:
Hi list,I got a little AKM320 usb midi keyboard for $40. Hooked it up, fired up Pd, and we're back to 2005:http://article.gmane.org/gmane.comp.multimedia.puredata.general/14675 Just change UM-1 to AKM320 and you have my error report. Well, aside from the fact that my laptop doesn't have a modem on it (though I bet if it did it'd show up in Pd's audio device list...) Any clue what's going on here, and how to fix Pd to do the right thing _without_ touching any of the state on my machine (save for the Pd binary, of course)?
Thanks,Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Why can't alsa midi report "connectable" devices inside Pd, to be displayed in a dropdown?
-Jonathan On Thursday, April 21, 2016 12:24 AM, Jaime Oliver jaime.oliver2@gmail.com wrote:
I can confirm that is still the case… J
On Apr 21, 2016, at 12:11 AM, Miller Puckette msp@ucsd.edu wrote:
So... last time I used 'alsa midi' I think It worked to start up Pd with -alsamidi, then use aconnect to make Pd's input listen to whatever source aconnect will allow it to be connected to.
But that was years ago... I'm happy to say I don't have to use MIDI very frequently.
cheers Miller
On Thu, Apr 21, 2016 at 04:04:19AM +0000, Jonathan Wilkes wrote:
BTW-- On OSX I get the correct device string "AKM320", and when I set that device everything looks to be working correctly there. I only tested with the GUI port of Pd-l2ork, but I'd assume Pd Vanilla also works there.
-Jonathan
On Wednesday, April 20, 2016 11:31 PM, Jonathan Wilkes via Pd-list pd-list@lists.iem.at wrote:
qjackctl has three tabs: Audio, Midi, and ALSA. The device shows up in the ALSA tab. lmms has a drop down list for midi in and midi out. It shows up on those lists, I can select it, and then I'm off making sounds. And that is using ALSA as the backend, so I know this can be done.
aconnect -o sees it:client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 20: 'AKM320' [type=kernel] 0 'AKM320 MIDI 1 '
Neither Pd nor Pd-l2ork see it or list it with --listdev. I can symlink /dev/snd/midiwhatevs to /dev/midi and it will get found and work in pd-0.46-7 (but not in Pd-l2ork-- maybe something with the 0.43 changes? not sure). But that requires me to go buy clothes from 2005 off of ebay. I don't want to do that, I want *AKM320* to show up in a dropdown list in Pd. -Jonathan On Wednesday, April 20, 2016 11:14 PM, Miller Puckette msp@ucsd.edu wrote:
A fun challenge....
Does anything see it? (In particular, does the qjackctl MIDI patch bay see it?) Not that that's scientific, but that's the way I check around for whether the so-called ALSA MIDI driver can find it.
cheers Miller
On Thu, Apr 21, 2016 at 02:08:29AM +0000, Jonathan Wilkes via Pd-list wrote:
Hi list,I got a little AKM320 usb midi keyboard for $40. Hooked it up, fired up Pd, and we're back to 2005:http://article.gmane.org/gmane.comp.multimedia.puredata.general/14675 Just change UM-1 to AKM320 and you have my error report. Well, aside from the fact that my laptop doesn't have a modem on it (though I bet if it did it'd show up in Pd's audio device list...) Any clue what's going on here, and how to fix Pd to do the right thing _without_ touching any of the state on my machine (save for the Pd binary, of course)?
Thanks,Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 2016-04-21 06:38, Jonathan Wilkes via Pd-list wrote:
Why can't alsa midi report "connectable" devices inside Pd, to be displayed in a dropdown?
because nobody has implemeted it.
personally i find that it preferable to use a specialised software for the patching¹. Pd doesn't necessarily need to poll the available MIDI devices every know and then to discover newly connected devices. otoh, applications like qjackctl can (and will) do this for you, and you can easily configure it to automatically connect your AKM320 and your UM-1 to Pd whenever you plug them in, while reserving your BCM2000 for the use with ardour.
i also find it preferable to be able to route multiple MIDI devices to the same MIDI port within Pd e.g. if I use ch#1 on my MIDI keyboard and ch#10 on my drum-sequencer, and i want to hook both into Pd, there is little use to open up two MIDI ports and reserve ch1-16 for the keyboard and ch17-32 for the drum sequencer; instead i want MIDI merge functionality. otoh, if i want to drive Pd with two independent multi-channel MIDI sequencers, it might very well make sense to be able to separate them on a patch level.
the alsa-midi implementation *used* to auto-connect to all available MIDI-ports (in special circumstances). this was disabled because:
- it was unclear how to turn off this behaviour (e.g. for those who
wanted their MIDI-devices to be connected to multiple ports in Pd)
- it would also automatically connect with the MIDI-thru virtual device
that get's automatically loaded, and *this* is rather annoying. at that time there was noobvious way to programmatically exclude the MIDI-thru device (or e.g. any non-hardware devices), short of hardcoding their name into a blacklist, which is not seem particularily appealing.
anyhow. the main challenge is to make the system flexible for power-users and at the same time allow plug-and-play setup when the flexibility is not needed. the current implementation favours flexibility. if someone can come-up with a scheme that allows both, we should of course go that route. if somebody comes up with a solution that favours plug-and-play at the expense of flexibility, i'd like to veto.
cfg,dasdr IOhannes
¹ fwiiw, there are even some people who very much prefer JACK audio applications to *not* automatically connect to the "system" output - or any other output for that matter (unfortunately this is an option that Pd currently does not offer)
On 21/04/2016 09:36, IOhannes m zmoelnig wrote:
On 2016-04-21 06:38, Jonathan Wilkes via Pd-list wrote:
Why can't alsa midi report "connectable" devices inside Pd, to be displayed in a dropdown?
because nobody has implemeted it.
personally i find that it preferable to use a specialised software for the patching¹.
+1
On Thursday, April 21, 2016 3:39 AM, IOhannes m zmoelnig <zmoelnig@iem.at> wrote:
On 2016-04-21 06:38, Jonathan Wilkes via Pd-list wrote:
Why can't alsa midi report "connectable" devices inside Pd, to be displayed in a dropdown?
because nobody has implemeted it.
I'm mainly fishing for any potential alsa api limitations that would make doing what I want very difficult or impossible. Like "it garbles the device names", or "crashes every Tuesday", etc. -Jonathan
I don't know of any reason this can't be done. The main alsa api limitation that has stopped me is: Not Worth the Hassle. That, however, is subjective - if you indeed want to attack it I'll be glad to see it (and perhaps even borrow it into vanilla if you're game).
cheers Miller On Thu, Apr 21, 2016 at 02:25:26PM +0000, Jonathan Wilkes via Pd-list wrote:
On Thursday, April 21, 2016 3:39 AM, IOhannes m zmoelnig <zmoelnig@iem.at> wrote:On 2016-04-21 06:38, Jonathan Wilkes via Pd-list wrote:
Why can't alsa midi report "connectable" devices inside Pd, to be displayed in a dropdown?
because nobody has implemeted it.
I'm mainly fishing for any potential alsa api limitations that would make doing what I want very difficult or impossible. Like "it garbles the device names", or "crashes every Tuesday", etc. -Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
I should say that while aconnect works fine mostly, there are a lot of issues with running it. The main one is that it doesn’t seem to show current connections, just available devices, also, often it will stop working (with no apparent reason) and the device needs to be unplugged and plugged in again. I don’t know if connecting from Pd would solve these issues, but that would be a reason to bother. I however, don’t know either if this is an issue for anybody else… best, J
On Apr 21, 2016, at 11:09 AM, Miller Puckette msp@ucsd.edu wrote:
I don't know of any reason this can't be done. The main alsa api limitation that has stopped me is: Not Worth the Hassle. That, however, is subjective - if you indeed want to attack it I'll be glad to see it (and perhaps even borrow it into vanilla if you're game).
cheers Miller On Thu, Apr 21, 2016 at 02:25:26PM +0000, Jonathan Wilkes via Pd-list wrote:
On Thursday, April 21, 2016 3:39 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2016-04-21 06:38, Jonathan Wilkes via Pd-list wrote:
Why can't alsa midi report "connectable" devices inside Pd, to be displayed in a dropdown?
because nobody has implemeted it.
I'm mainly fishing for any potential alsa api limitations that would make doing what I want very difficult or impossible. Like "it garbles the device names", or "crashes every Tuesday", etc. -Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
IOhannes m zmoelnig -
Jaime Oliver -
Jonathan Wilkes -
Lorenzo Sutton -
Miller Puckette