Midi

[Master of Reality]

herm... i cant seem to play midi... Kmidi says error cannot open output device. /dev/midi is chmodded to 777 and links to /dev/midi00 which is r/w by everyone. Is there something else im missing?

[Tux]

Use Kmid instead.

[Master of Reality]

"couldnt open /dev/sequencer"
squencer is set to rw to all and nothing is using it.

[Tux]

modprobe snd-seq-device?

[Master of Reality]

still doesnt work.. same error

[Master of Reality]

if anyone else cares... i sitll havent fixed it but... I have found that programs dont think /dev/sequencer exists. kmidi which uses /dev/snd/seq crashes now after i fixed the permissions. Kmidi will only use artsd works with artsd but sound horrific.

[Calum]

i get this when trying to play a midi file with kmidi in slack. i run kmidi, get the gui, and try to open a file. it exits this way:

Code: Select all

aRts init failed: loading the aRts backend "/opt/kde/lib/libartscbackend.la" failed
error writing to dsp device: No such file or directory
Kmidi:Problem with PIPE_INT_WRITE due to:Broken pipe



which makes me think of that odd "invalid output device" error i get with audacity when using /dev/dsp (which still works fine for audacity, mplayer and xmms). here's what i get when trying to play the same file with timidity. it also exits:

Code: Select all

bash-2.05b$ timidity -Od ~/midi/fairylullaby.mid
aRts init failed: loading the aRts backend "/opt/kde/lib/libartscbackend.la" failed
Couldn't open Arts device


same error, hmm? something wrong with aRts then? not sure. also:

Code: Select all

bash-2.05b$ ls -l /opt/kde/lib/libartscbackend.la
-rwxr-xr-x    1 root     root         1483 Sep 14 15:06 /opt/kde/lib/libartscbackend.la


in case it makes a difference...
don't know what's going on here, and i get that exactsame error when i try to output to a wave file as when i try to output to /dev/dsp
maybe not much help, but i'd be curious to fix this too actually, now i am aware of it. if i find anything i'll post here again.

[Master of Reality]

do you have artsd running though?

[Master of Reality]

The only errors timidity gives to not working are in the syslog, they are...:

Code: Select all

Nov 25 15:51:26 xen modprobe: modprobe: Can't locate module snd-card-1
Nov 25 15:51:26 xen modprobe: modprobe: Can't locate module snd-card-2
Nov 25 15:51:26 xen modprobe: modprobe: Can't locate module snd-card-3
Nov 25 15:51:26 xen modprobe: modprobe: Can't locate module snd-card-4
Nov 25 15:51:26 xen modprobe: modprobe: Can't locate module snd-card-5
Nov 25 15:51:26 xen modprobe: modprobe: Can't locate module snd-card-6
Nov 25 15:51:26 xen modprobe: modprobe: Can't locate module snd-card-7

and i have no idea why its looking for a snd-card module?

[Calum]

do you have artsd running though?

looks like i'm not:

Code: Select all

calum@claudia:~$ artsd
artsd: error while loading shared libraries: libmad.so.0: cannot open shared object file: No such file or directory



[Calum]

ok, i installed artsd via slapt-get and have got it running (even though it's crap), and now i can play my midi file using kmidi and timidity, but i get an odd crunching noise every 3/4 of a second or so. like if it was a 78 rpm record and there was a bunch of scratches only on one part of the record.

does this help?

[Master of Reality]

thats what i get with kmidi. Apparently this is how linux is supposed to play midi files?

[Calum]

once i get my power supply, i can try it on RH9 and see if it works. if it does, it's the slackpacks at fault, and it'll be as simple as a recompile of whatever the bottleneck is, i hope.