27 Nov
2008
27 Nov
'08
9:01 a.m.
Am Friday 21 November 2008 23:30:00 schrieb Preston C.:
Preston,
I have to admit I am having some trouble here myself which I could not yet
solve reliably, that is why I respond so late...
It might have to do with the sound device that is selected in kmix (I wrote
about that issue some other day a while ago).
There are several variables/applications involved that want examination so I
guess it will take me some time until I can give further details on that.
The problem that I have is that like You I cannot receive MIDI data from an
external USB device, but in this case kmon showed me that sometimes there is
a short number of MIDI messages I get and then it all stops and I do not see
any more messages, and sometimes I get no MIDI messages at all.
As I said a while ago I wrote about this problem and noticed that it could
have to do with the sound device to which kmix is set to. When You run kmix
(open it from the task bar) and You have several sound devices for sound
output then kmix offers a popup menu from which to choose which one You want
to adjust. I have noticed that I get these hangups when the internal onboard
sound of my notebook is selected here, and it is all just fine when the USB
sound device is selected, but now I am not so sure here anymore.
I also had some problems to get qjackctl running properly when there are
several sound devices available. It seemed the problem could be fixed when
setting qjackctl to output do "default" device and input from
"default"
device and apart from that set the sound device with the single menu at the
top menu called "interface". But still I have problems with that and get no
MIDI data, so I have to have a closer look at what is happening here.
BTW, do You have no MIDI data even when not running a RT kernel? It could also
be a kernel related problem, as I had no problems with an older RT kernel.
Possible solutions for me:
Run jackd via command line (only), so I can see exactly what jackd gets when
run.
Regards,
Crypto.
Thank you
Crypto. I will try what you said about using kmidimon and
then get back with you. Thanks again. I hope I didn't send this to
your private email. It seems that when I hit reply in Gmail it sends
it to people's private address?
I tried Kmidimon and got no signal. I attached a screenshot of my
desktop and setup. 
27 Nov
27 Nov
6:43 p.m.
New subject: no connection...
On Thu, Nov 27, 2008 at 8:01 AM, Crypto <crypto(a)online.de> wrote:
Am Friday 21 November 2008 23:30:00 schrieb Preston
C.:
Preston,
I have to admit I am having some trouble here myself which I could not yet
solve reliably, that is why I respond so late...
It might have to do with the sound device that is selected in kmix (I wrote
about that issue some other day a while ago).
There are several variables/applications involved that want examination so I
guess it will take me some time until I can give further details on that.
The problem that I have is that like You I cannot receive MIDI data from an
external USB device, but in this case kmon showed me that sometimes there is
a short number of MIDI messages I get and then it all stops and I do not see
any more messages, and sometimes I get no MIDI messages at all.
As I said a while ago I wrote about this problem and noticed that it could
have to do with the sound device to which kmix is set to. When You run kmix
(open it from the task bar) and You have several sound devices for sound
output then kmix offers a popup menu from which to choose which one You want
to adjust. I have noticed that I get these hangups when the internal onboard
sound of my notebook is selected here, and it is all just fine when the USB
sound device is selected, but now I am not so sure here anymore.
I also had some problems to get qjackctl running properly when there are
several sound devices available. It seemed the problem could be fixed when
setting qjackctl to output do "default" device and input from
"default"
device and apart from that set the sound device with the single menu at the
top menu called "interface". But still I have problems with that and get no
MIDI data, so I have to have a closer look at what is happening here.
BTW, do You have no MIDI data even when not running a RT kernel? It could also
be a kernel related problem, as I had no problems with an older RT kernel.
Possible solutions for me:
Run jackd via command line (only), so I can see exactly what jackd gets when
run.
Regards,
Crypto.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
Crypto, you are right! I tried it with a non-RT kernel and everything
worked... except for the major popping sounds. Is there anyway for me
to update my RT kernel, I use CCRMA, and then try it? Thanks a lot.
Thank you
Crypto. I will try what you said about using kmidimon and
then get back with you. Thanks again. I hope I didn't send this to
your private email. It seems that when I hit reply in Gmail it sends
it to people's private address?
I tried Kmidimon and got no signal. I attached a screenshot of my
desktop and setup. 
8 p.m.
New subject: no connection...
On Thu, 2008-11-27 at 17:43 -0500, Preston C. wrote:
On Thu, Nov 27, 2008 at 8:01 AM, Crypto
<crypto(a)online.de> wrote:
If you need to use 2.6.26.x there is no fix available (AFAIK). MIDI i/o
from external devices in the alsa sequencer is broken. I got a partial
solution that gets midi input going but the internal timer in the alsa
sequencer is broken anyway.
What to do depends on which Fedora you are running, if < 9 then you
could use the older 2.6.24.x rt kernel, if on 9 or 10 there is nothing
you can do until some kernel guru steps in and fixes the problem
(2.6.24.x is too old for the X server that runs on Fedora 9 - if you try
you will get X segfaults every once in a while and your session will
just die).
I have had good enough results running the stock Fedora kernel on Fedora
9. Make sure that jackd is running with realtime priority...
Sorry to not have better news.
-- Fernando
Am Friday 21 November 2008 23:30:00 schrieb
Preston C.:
Preston,
I have to admit I am having some trouble here myself which I could not yet
solve reliably, that is why I respond so late...
It might have to do with the sound device that is selected in kmix (I wrote
about that issue some other day a while ago).
There are several variables/applications involved that want examination so I
guess it will take me some time until I can give further details on that.
The problem that I have is that like You I cannot receive MIDI data from an
external USB device, but in this case kmon showed me that sometimes there is
a short number of MIDI messages I get and then it all stops and I do not see
any more messages, and sometimes I get no MIDI messages at all.
As I said a while ago I wrote about this problem and noticed that it could
have to do with the sound device to which kmix is set to. When You run kmix
(open it from the task bar) and You have several sound devices for sound
output then kmix offers a popup menu from which to choose which one You want
to adjust. I have noticed that I get these hangups when the internal onboard
sound of my notebook is selected here, and it is all just fine when the USB
sound device is selected, but now I am not so sure here anymore.
I also had some problems to get qjackctl running properly when there are
several sound devices available. It seemed the problem could be fixed when
setting qjackctl to output do "default" device and input from
"default"
device and apart from that set the sound device with the single menu at the
top menu called "interface". But still I have problems with that and get no
MIDI data, so I have to have a closer look at what is happening here.
BTW, do You have no MIDI data even when not running a RT kernel? It could also
be a kernel related problem, as I had no problems with an older RT kernel.
Possible solutions for me:
Run jackd via command line (only), so I can see exactly what jackd gets when
run.
Crypto, you are right! I tried it with a non-RT kernel and everything
worked... except for the major popping sounds. Is there anyway for me
to update my RT kernel, I use CCRMA, and then try it? Thanks a lot. Thank you
Crypto. I will try what you said about using kmidimon and
then get back with you. Thanks again. I hope I didn't send this to
your private email. It seems that when I hit reply in Gmail it sends
it to people's private address?
I tried Kmidimon and got no signal. I attached a screenshot of my
desktop and setup.
9:33 p.m.
New subject: no connection...
If you need to use 2.6.26.x there is no fix available
(AFAIK). MIDI i/o
from external devices in the alsa sequencer is broken. I got a partial
solution that gets midi input going but the internal timer in the alsa
sequencer is broken anyway.
What to do depends on which Fedora you are running, if < 9 then you
could use the older 2.6.24.x rt kernel, if on 9 or 10 there is nothing
you can do until some kernel guru steps in and fixes the problem
(2.6.24.x is too old for the X server that runs on Fedora 9 - if you try
you will get X segfaults every once in a while and your session will
just die).
I have had good enough results running the stock Fedora kernel on Fedora
9. Make sure that jackd is running with realtime priority...
Sorry to not have better news.
-- Fernando
I am using F8 but am thinking about using F10. Fernando, do you think
that it would be a good idea to use F10 instead of F8 for the problem
I am having?
9:56 p.m.
New subject: no connection...
On Thu, 2008-11-27 at 20:33 -0500, Preston C. wrote:
Which kernel are you booting? ("uname -r" to find out). Fedora 8 should
not exhibit the problem I was talking about, I have only seen it happen
in linux >= 2.6.26 (and perhaps 25 as well).
It may be a problem in the particular Audigy alsa driver you have to use
for your card...
-- Fernando
If you need to
use 2.6.26.x there is no fix available (AFAIK). MIDI i/o
from external devices in the alsa sequencer is broken. I got a partial
solution that gets midi input going but the internal timer in the alsa
sequencer is broken anyway.
What to do depends on which Fedora you are running, if < 9 then you
could use the older 2.6.24.x rt kernel, if on 9 or 10 there is nothing
you can do until some kernel guru steps in and fixes the problem
(2.6.24.x is too old for the X server that runs on Fedora 9 - if you try
you will get X segfaults every once in a while and your session will
just die).
I have had good enough results running the stock Fedora kernel on Fedora
9. Make sure that jackd is running with realtime priority...
Sorry to not have better news.
I am using F8 but am thinking about using F10. Fernando, do you think
that it would be a good idea to use F10 instead of F8 for the problem
I am having?
10:06 p.m.
New subject: no connection...
Which kernel are you booting? ("uname -r" to
find out). Fedora 8 should
not exhibit the problem I was talking about, I have only seen it happen
in linux >= 2.6.26 (and perhaps 25 as well).
It may be a problem in the particular Audigy alsa driver you have to use
for your card...
-- Fernando
2.6.24- I don't see how it could be a problem with the sound card
driver when it works with a standard kernel? Then again you know more
than me.
10:12 p.m.
New subject: no connection...
On Thu, 2008-11-27 at 21:06 -0500, Preston C. wrote:
(not necessarily :-)
If it works with the standard kernel (and it is also 2.6.24) then it is
probably an interaction between the realtime preemption patch and that
particular alsa driver.
[but if the kernel base versions are not exactly the same for the
standard and realtime kernels then it could also be a problem in the
particular alsa driver - something that changed between versions]
-- Fernando
Which kernel
are you booting? ("uname -r" to find out). Fedora 8 should
not exhibit the problem I was talking about, I have only seen it happen
in linux >= 2.6.26 (and perhaps 25 as well).
It may be a problem in the particular Audigy alsa driver you have to use
for your card...
2.6.24- I don't see how it could be a problem with the sound card
driver when it works with a standard kernel? Then again you know more
than me.
10:16 p.m.
New subject: no connection...
(not necessarily :-)
If it works with the standard kernel (and it is also 2.6.24) then it is
probably an interaction between the realtime preemption patch and that
particular alsa driver.
[but if the kernel base versions are not exactly the same for the
standard and realtime kernels then it could also be a problem in the
particular alsa driver - something that changed between versions]
-- Fernando
So what should I do you think? I don't know all to much about Linux
but would the base versions have to do with my Nvidia graphics card
not working with the RT kernel?
10:36 p.m.
New subject: no connection...
On Thu, 2008-11-27 at 21:16 -0500, Preston C. wrote:
That is a different issue. The binary nvidia kernel blob needs some glue
code to be rebuilt for each different kernel you install, how to do that
depends on how you installed the nvidia driver originally.
-- Fernando
(not
necessarily :-)
If it works with the standard kernel (and it is also 2.6.24) then it is
probably an interaction between the realtime preemption patch and that
particular alsa driver.
[but if the kernel base versions are not exactly the same for the
standard and realtime kernels then it could also be a problem in the
particular alsa driver - something that changed between versions]
So what should I do you think? I don't know all to much about Linux
but would the base versions have to do with my Nvidia graphics card
not working with the RT kernel?
5641
days inactive
5641
days old
linux-audio-user@lists.linuxaudio.org
8 comments
3 participants
participants (3)
-
Crypto -
Fernando Lopez-Lezcano -
Preston C.