16 Aug
2015
16 Aug
'15
4:04 p.m.
Hey hey everyone,
I've got problems connecting Midish to Yoshimi. Keyboards with and without
active sensing from the mid 80s to the past year work fine. But when I try to
connect Yoshimi from within Midish, I get no sound. LinuxSampler works though.
The midish procedure
dnew 4 "yoshimi" wo # Add Yoshimi to Midish device list
onew "Yoshimi" {4 0} # name first channel Yoshimi
Create a filter to route all events from my keyboard to Yoshimi.
Typos aren't possible, since it's all done by Midish procedures and has been
tested about 10 times.
Does Yoshimi need any special MIDI input beyond noteon/noteoff perhaps?
Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter: http://twitter.com/ffanci_silvain
* GitHub: https://github.com/fsilvain
16 Aug
16 Aug
4:51 p.m.
On Sun, 16 Aug 2015 16:04:28 +0200 (CEST), F. Silvain wrote:
Does Yoshimi need any special MIDI input beyond
noteon/noteoff perhaps?
All MIDI devices, including Yoshimi, don't need anything more than note
on events to play a note. Note off could be two different kinds of
events, but that doesn't matter. Active sensing should protect against
hanging notes, assumed that a MIDI cable e.g. should get disconnected,
but you can't rely on it. All channel related MIDI events could
"suffer" from running status. Briefly worded, no you don't need
anything more than note on events to hear something. Active sensing,
running status and note off events don't matter here. If you can't here
something after sending note on events from one app to another app
inside Linux, something is fishy, since it doesn't need more than a
note on event.
5:20 p.m.
On Sun, 16 Aug 2015 16:04:28 +0200 (CEST)
"F. Silvain" <silvain(a)freeshell.de> wrote:
Hey hey everyone,
I've got problems connecting Midish to Yoshimi. Keyboards with and without
active sensing from the mid 80s to the past year work fine. But when I try to
connect Yoshimi from within Midish, I get no sound. LinuxSampler works though.
The midish procedure
dnew 4 "yoshimi" wo # Add Yoshimi to Midish device list
onew "Yoshimi" {4 0} # name first channel Yoshimi
Create a filter to route all events from my keyboard to Yoshimi.
Typos aren't possible, since it's all done by Midish procedures and has been
tested about 10 times.
Does Yoshimi need any special MIDI input beyond noteon/noteoff perhaps?
No. This seems more like a connection issue.
Have you compiled yoshimi yourself, or are you getting it from a distro?
What's the version number - the latest is 1.3.5.2
I've not used Midish. Does it expect alsa or jack midi? If working from a
command line you can set yoshimi to match what you have.
yoshimi -a -A will set alsa for both midi and audio.
yoshimi -a -J -K will give you alsa midi and jack audio with the L & R outs
auto-connected.
yoshimi -? lists all the options.
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
17 Aug
17 Aug
1:02 a.m.
Will Godfrey, Aug 16 2015:
Hey hey Will!
...
Have you compiled yoshimi yourself, or are you getting
it from a distro?
I've compiled it myself.
What's the version number - the latest is 1.3.5.2
It is the latest.
I've not used Midish. Does it expect alsa or jack
midi? If working from a
command line you can set yoshimi to match what you have.
It expects ALSA and my
audio driver is JACK. From the shell the connetions work fine, both JACK - automatically
and ALSA through aconnect. But from Midish it doesn't work. Yoshimi sees the
successful MIDI connections through ALSA sequencer, but somehow doesn't accept
Midish's input. So I guess it's Midish somehow. I've made sure:
aconnect hardware synth -> yoshimi = OK
aplaymidi -> yoshimi = OK
hardware -> hardware through Midish = OK
hardware -> LinuxSampler through Midish = OK
hardware -> Yoshimi through Midish = no sound/transmission
...
Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter: http://twitter.com/ffanci_silvain
* GitHub: https://github.com/fsilvain
8:10 p.m.
Hey hey Will,
I worked around the issue using a2jmidi_bridge. Still it is a baffling
mystery. :_
Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter: http://twitter.com/ffanci_silvain
* GitHub: https://github.com/fsilvain
8:44 p.m.
On Mon, 17 Aug 2015 20:10:49 +0200 (CEST)
"F. Silvain" <silvain(a)freeshell.de> wrote:
Hey hey Will,
I worked around the issue using a2jmidi_bridge. Still it is a baffling
mystery. :_
Ta-ta
Ah! Got it :)
By default yoshimi complies for jack midi.
In CMakeLists.txt near line 60 look for:
set (DefaultMidi jack CACHE STRING "Default midi driver - alsa or jack")
and change it to:
set (DefaultMidi alsa CACHE STRING "Default midi driver - alsa or jack")
However it should have worked using yoshimi -a
If this is run via Midish then maybe it is stripping off the '-a' argument
--
It wasn't me! (Well actually, it probably was)
... the hard part is not dodging what life throws at you,
but trying to catch the good bits.
8:50 p.m.
Will J Godfrey, Aug 17 2015:
...
By default yoshimi complies for jack midi.
I
changed that, when I compiled it. I don't use JACK MIDI anywhere, if I can avoid it.
:)
...
However it should have worked using yoshimi -a
If this is run via Midish then maybe it is stripping off the '-a' argument
No I'm running yoshimi from a different tty and it works fine if connected to a
hardware device via aconnect or even, when fed by aplaymidi. I have to assume, it's
somethig in Midish, though I can't understand, what it could be.
Thank you for caring for your users!
...
Ta-ta
----
Ffanci
* Homepage: https://freeshell.de/~silvain
* Twitter: http://twitter.com/ffanci_silvain
* GitHub: https://github.com/fsilvain
3389
days inactive
3390
days old
linux-audio-user@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
F. Silvain -
Ralf Mardorf -
Will Godfrey -
Will J Godfrey