Re: midish and virtual alsa midi ports

From: RaphaŽl Mouneyres <rmouneyres_at_free.fr>
Date: Sun May 26 2013 - 17:45:40 CEST
yes i need to connect port, but as for testing, i do it with visually in the jack patchbay, so it's easy to connect.
I confirm that i'm unable to receive messages in jack when routing from midish to virtual ports (activated with modprobe snd-virmidi)

I used gmidimonitor to check the received messages and :
 with alsa midi through 14:0 it is OK
 with QjackMMC 130:0 it is OK (which is the one i really need to use)
 with Virtual RAW midi 20:0 i just receive nothing, although the ports are correctly listed in alsa

this is an archlinux x86 box, may you try to reproduce the problem on your system (openbsd?) ?

RaphaŽl


Le 26 mai 2013 ŗ 17:12, Alexandre Ratchov a ťcrit :

> On Sat, May 25, 2013 at 11:03:04PM +0200, gorest wrote:
>> hello,
>> 
>> Working config :
>> midish > alsa midi through 14:0 > a2jmidid > qjackmmc
>> here jack transport is responding to MMC messages
>> 	rmidish
>> 	dnew 2 "14:0" wo
>> 	dmmctx {2}
>> 	import "mymidifile.mid"
>> 	t 86
>> 	p
>> 
>> Not working config
>> midish > alsa virtual midi ports 20:0 > a2jmidid > qjackmmc
>> 	rmidish
>> 	dnew 3 "20:0" wo
>> 	dmmctx {3}
>> 	import "mymidifile.mid"
>> 	t 86
>> 	p
>> now jack transport is not responding
>> 
>> did you already tried with those alsa virtual midi ports ? should
>> they work as is in midish ?
> 
> Hi,
> 
> midish doesn't make the difference between different types of midi
> ports, so virtual midi ports are not special and should work as
> others.
> 
> Does your setup requires connecting ports? IIRC, virtual midi ports
> used to need tweaks with aconnect utility
> 
> -- Alexandre
> 
Received on Sun, 26 May 2013 17:45:40 +0200

This archive was generated by hypermail 2.1.8 : Wed Nov 08 2017 - 16:32:25 CET