search

yoyz / amsynth

Automatically exported from code.google.com/p/amsynth
GNU General Public License v2.0
1 stars 0 forks source link

second instance does not respond to alsa midi events #31

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Start amSynth
2. Start new instance
3. connect outputs and amSynth MIDI IN, select different midi channels
4. play midi notes on midi channel of 2nd instance -> no response

What is the expected output? What do you see instead?
Second instance also responds to alsa midi "amSynth MIDI IN"

What version of the product are you using? On what operating system?
Arch linux, 1.3.0

Please provide any additional information below.
You can reach me through jelle at plantenberg dot nl.

Original issue reported on code.google.com by yell...@gmail.com on 27 Dec 2011 at 10:15

GoogleCodeExporter commented 9 years ago 
The newly spawned instance of amsynth creates its own alsa midi port but does 
not recreate any connections from the first instance.

After connecting something to the new port, I find that the new instance of 
amsynth does respond to alsa midi events.

The ports are named identically though which makes it hard to associate the 
port with the instance of amsynth.

Original comment by nickdowell on 8 Jan 2012 at 11:47

GoogleCodeExporter commented 9 years ago 
Could not reproduce the reported problem

Original comment by nickdowell on 27 Jun 2013 at 7:40