danomatika / ofxMidi

(maintained) Midi addon for openFrameworks
Other
262 stars 73 forks source link

/dev/snd/seq failed: no such file or directory #74

Closed batchku closed 3 years ago

batchku commented 5 years ago

I have built an OF app with ofxmidi, and when I try to run the app I get this error:

ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory

MidiInAlsa::initialize: error creating ALSA sequencer client object.

terminate called after throwing an instance of 'RtMidiError'
  what():  MidiInAlsa::initialize: error creating ALSA sequencer client object.
Aborted (core dumped)

Any ideas what may be causing that @danomatika ?

danomatika commented 5 years ago

It's most likely a configuration issue with your system and not something with ofxMidi.

danomatika commented 5 years ago

ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory

ie. You might not have the ALSA sequencer module loaded, etc...

batchku commented 5 years ago

Thanks @danomatika I suspect as much; I have been googling around and not finding the way to do it. Unfortunately some key ASLA pages are not loading: https://www.alsa-project.org/~tiwai/lk2k/lk2k.html

Can you point me to where I can learn about how to load asla modules manually?

batchku commented 5 years ago

Here is what I see:

ali@ali-nono:~$  sudo modprobe snd-seq
modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() could not find module by name='snd_seq'
modprobe: ERROR: could not insert 'snd_seq': Unknown symbol in module, or unknown parameter (see dmesg)
modprobe: ERROR: ../libkmod/libkmod-module.c:979 command_do() Error running install command for snd_seq
modprobe: ERROR: could not insert 'snd_seq': Operation not permitted
danomatika commented 3 years ago

Closing for now as this is a system config issue and not necessarily an issue with ofxMidi.

cyphunk commented 1 year ago

@batchku by chance did you find a solution? I'm testing this addon now on raspberry pi and debugging similar system issues. for what it is worth aplay for also works fine for playing sound.

Update: I resolved this. If anyone stumbles here, modprobe snd_seq. If your pi fails, maybe check that you rebooted the pi since recent kernel update. This was the case with me which I confirmed by checking runtime kernel version uname with where snd_req module was found in /lib/modules

btw helpful for debugging was: aplay -l shows the mididevice but aplaymidi -l was failing wiht the same snd_seq error

danomatika commented 1 year ago

This might good to add to the readme under the known issues section, if you have time.

enohp ym morf tnes

Dan Wilcox danomatika.com robotcowboy.com

On Feb 2, 2023, at 5:41 PM, Nathan Fain @.***> wrote:

 @batchku by chance did you find a solution? I'm testing this addon now on raspberry pi and debugging similar system issues

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.

olawalejuwonm commented 1 year ago

@danomatika how did you resolve this issue please?

danomatika commented 1 year ago

Judging from batchku's previous post, you just need to reboot after a kernel update for the Alsa dev endpoints to be regenerated.

Update: I resolved this. If anyone stumbles here, modprobe snd_seq. If your pi fails, maybe check that you rebooted the pi since recent kernel update. This was the case with me which I confirmed by checking runtime kernel version uname with where snd_req module was found in /lib/modules

btw helpful for debugging was: aplay -l shows the mididevice but aplaymidi -l was failing wiht the same snd_seq error

olawalejuwonm commented 1 year ago

I'm running on wsl how do I do that?

On Tue, Aug 8, 2023, 10:30 Dan Wilcox @.***> wrote:

Judging from batchku's previous post, you just need to reboot after a kernel update for the Alsa dev endpoints to be regenerated.

Update: I resolved this. If anyone stumbles here, modprobe snd_seq. If your pi fails, maybe check that you rebooted the pi since recent kernel update. This was the case with me which I confirmed by checking runtime kernel version uname with where snd_req module was found in /lib/modules

btw helpful for debugging was: aplay -l shows the mididevice but aplaymidi -l was failing wiht the same snd_seq error

— Reply to this email directly, view it on GitHub https://github.com/danomatika/ofxMidi/issues/74#issuecomment-1669257114, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMSQ2BHHYMEPFXGJLCOMC6LXUIBK5ANCNFSM4HIQZJRQ . You are receiving this because you commented.Message ID: @.***>

danomatika commented 1 year ago

I'm running on wsl how do I do that?

Ok, now that we know what system you are on, Google turns up a Github issue on the WSL repo: it's not possible as MIDI hardware is not currently exposed to the Linux layer: https://github.com/Microsoft/WSL/issues/237

UPDTAE: To clarify, it seems you need to either compile for native Windows or Linux.