3 Apr
2009
3 Apr
'09
5:30 p.m.
Am Freitag, den 03.04.2009, 20:57 +0200 schrieb Stéphane Letz:
I will do that, but dont get me wrong, speak about a posible bug in my
code, not in your's. Jackdmp is realy nice, fast and light, that why I
wont be able to run it with my app.
And sorry, it will posible take some day's, my work try to eat me . . .
thanks hermann
Now, it work
with jackdmp, great,
So the Question comes in mind, why need I to register the midi port as
first one ? Anyone experience the same behaviour ? Or is it just a
effekt from a hidden bug ? mmm
regards hermann
_
Maybe, but could you extract the "crashing" code in a simpler test
client? It would help.
Thanks
Stephane
4 Apr
4 Apr
3:28 a.m.
New subject: jack_midi in jackd and jackdmp
Am Freitag, den 03.04.2009, 20:38 +0200 schrieb hermann meyer:
Am Freitag, den 03.04.2009, 20:57 +0200 schrieb
Stéphane Letz:
I will do that, but dont get me wrong, speak about a posible bug in my
code, not in your's. Jackdmp is realy nice, fast and light, that why I
wont be able to run it with my app.
And sorry, it will posible take some day's, my work try to eat me . . .
thanks hermann
I have try to reproduce this behaviour with the midiseq example client,
he here it work, no matter witch port I register at first or how many
clients I open.
So the errror is definity in my Code. I will let you know when I found
the real bug.
regards hermann
Now, it
work with jackdmp, great,
So the Question comes in mind, why need I to register the midi port as
first one ? Anyone experience the same behaviour ? Or is it just a
effekt from a hidden bug ? mmm
regards hermann
_
Maybe, but could you extract the "crashing" code in a simpler test
client? It would help.
Thanks
Stephane
6058
days inactive
6059
days old
linux-audio-dev@lists.linuxaudio.org
1 comments
1 participants
participants (1)
-
hermann meyer