Trying to send midi audio to Discord on Xubuntu
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have a casio keyboard which doubles as a midi controller, and I want its audio to go through a discord voice call. I don't have an audio-in jack, or else this would be trivial, so I'm going the usb midi route.
My setup so far is Xubuntu 18.04 with qjackctl and qsynth. The keyboard shows up under the ALSA tab in the JACK connections window, and it connects to qsynth just fine. I can hear it through headphones. But now I don't know how to pipe this audio through to discord. Looking into virtual audio cables didn't go very far either.
audio pulseaudio alsa xubuntu jack
asked Nov 18 at 7:04
Daffy
1434
add a comment |
up vote
0
down vote
favorite
I have a casio keyboard which doubles as a midi controller, and I want its audio to go through a discord voice call. I don't have an audio-in jack, or else this would be trivial, so I'm going the usb midi route.
My setup so far is Xubuntu 18.04 with qjackctl and qsynth. The keyboard shows up under the ALSA tab in the JACK connections window, and it connects to qsynth just fine. I can hear it through headphones. But now I don't know how to pipe this audio through to discord. Looking into virtual audio cables didn't go very far either.
audio pulseaudio alsa xubuntu jack
asked Nov 18 at 7:04
Daffy
1434
Crossposting this from askubuntu since that question has gone 2 days with absolutely no interaction.
– Daffy
Nov 18 at 7:05
You tagged withpulseaudio, but you only mention jack and ALSA. Does your system run Pulseaudio? My advice would be not to unnecessarily mix audio systems. Routing in ALSA will require eitheralsa_loopor an application, routing in Jack should work if discord shows up under Jack (don't know that) or can be made to show up with a plugin. Routing in Pulseaudio should also be easy. Ifqsynthrequires Jack (don't remember), you can usetimidityinstead (though it will eat more CPU). In any case, decide on a method, and edit question with more information about how stuff shows up.
– dirkt
2 days ago
@dirkt I'm under the impression that Xubuntu 18.04 uses pulseaudio, though I could be wrong, linux audio systems are doing my head in. I think I figured out a way to cut jack out of the picture. I now have qsynth using ALSA exclusively, and the "monitor of stereo output" input is working in discord and audacity. The new problem is that the pitch is shifted lower for some reason. Maybe due to a 44100/48000hz mismatch?
– Daffy
yesterday
Runpavucontroland see if both discord and qsynth show up as sources/sinks to test if you run Pulseaudio. "Monitor of stereo output" strongly suggest you do, because ALSA doesn't have "monitors", but Pulseaudio does. Pulseaudio has an ALSA compatibility layer, which is probably used by one or both of the programs. Pulseaudio does resampling, so if there is a mismatch, one or both applications gave wrong ALSA information, or they are doing something funny. If it's indeed Pulseaudio, first step is to usepacmdwith the variouslist-*commands, and see what the configuration is.
– dirkt
yesterday
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a casio keyboard which doubles as a midi controller, and I want its audio to go through a discord voice call. I don't have an audio-in jack, or else this would be trivial, so I'm going the usb midi route.
My setup so far is Xubuntu 18.04 with qjackctl and qsynth. The keyboard shows up under the ALSA tab in the JACK connections window, and it connects to qsynth just fine. I can hear it through headphones. But now I don't know how to pipe this audio through to discord. Looking into virtual audio cables didn't go very far either.
audio pulseaudio alsa xubuntu jack
asked Nov 18 at 7:04
Daffy
1434
I have a casio keyboard which doubles as a midi controller, and I want its audio to go through a discord voice call. I don't have an audio-in jack, or else this would be trivial, so I'm going the usb midi route.
My setup so far is Xubuntu 18.04 with qjackctl and qsynth. The keyboard shows up under the ALSA tab in the JACK connections window, and it connects to qsynth just fine. I can hear it through headphones. But now I don't know how to pipe this audio through to discord. Looking into virtual audio cables didn't go very far either.
audio pulseaudio alsa xubuntu jack
audio pulseaudio alsa xubuntu jack
asked Nov 18 at 7:04
Daffy
1434
asked Nov 18 at 7:04
Daffy
1434
asked Nov 18 at 7:04
Daffy
1434
asked Nov 18 at 7:04
Daffy
1434
asked Nov 18 at 7:04
Daffy
1434
1434
Crossposting this from askubuntu since that question has gone 2 days with absolutely no interaction.
– Daffy
Nov 18 at 7:05
You tagged withpulseaudio, but you only mention jack and ALSA. Does your system run Pulseaudio? My advice would be not to unnecessarily mix audio systems. Routing in ALSA will require eitheralsa_loopor an application, routing in Jack should work if discord shows up under Jack (don't know that) or can be made to show up with a plugin. Routing in Pulseaudio should also be easy. Ifqsynthrequires Jack (don't remember), you can usetimidityinstead (though it will eat more CPU). In any case, decide on a method, and edit question with more information about how stuff shows up.
– dirkt
2 days ago
@dirkt I'm under the impression that Xubuntu 18.04 uses pulseaudio, though I could be wrong, linux audio systems are doing my head in. I think I figured out a way to cut jack out of the picture. I now have qsynth using ALSA exclusively, and the "monitor of stereo output" input is working in discord and audacity. The new problem is that the pitch is shifted lower for some reason. Maybe due to a 44100/48000hz mismatch?
– Daffy
yesterday
Runpavucontroland see if both discord and qsynth show up as sources/sinks to test if you run Pulseaudio. "Monitor of stereo output" strongly suggest you do, because ALSA doesn't have "monitors", but Pulseaudio does. Pulseaudio has an ALSA compatibility layer, which is probably used by one or both of the programs. Pulseaudio does resampling, so if there is a mismatch, one or both applications gave wrong ALSA information, or they are doing something funny. If it's indeed Pulseaudio, first step is to usepacmdwith the variouslist-*commands, and see what the configuration is.
– dirkt
yesterday
add a comment |
Crossposting this from askubuntu since that question has gone 2 days with absolutely no interaction.
– Daffy
Nov 18 at 7:05
You tagged withpulseaudio, but you only mention jack and ALSA. Does your system run Pulseaudio? My advice would be not to unnecessarily mix audio systems. Routing in ALSA will require eitheralsa_loopor an application, routing in Jack should work if discord shows up under Jack (don't know that) or can be made to show up with a plugin. Routing in Pulseaudio should also be easy. Ifqsynthrequires Jack (don't remember), you can usetimidityinstead (though it will eat more CPU). In any case, decide on a method, and edit question with more information about how stuff shows up.
– dirkt
2 days ago
@dirkt I'm under the impression that Xubuntu 18.04 uses pulseaudio, though I could be wrong, linux audio systems are doing my head in. I think I figured out a way to cut jack out of the picture. I now have qsynth using ALSA exclusively, and the "monitor of stereo output" input is working in discord and audacity. The new problem is that the pitch is shifted lower for some reason. Maybe due to a 44100/48000hz mismatch?
– Daffy
yesterday
Runpavucontroland see if both discord and qsynth show up as sources/sinks to test if you run Pulseaudio. "Monitor of stereo output" strongly suggest you do, because ALSA doesn't have "monitors", but Pulseaudio does. Pulseaudio has an ALSA compatibility layer, which is probably used by one or both of the programs. Pulseaudio does resampling, so if there is a mismatch, one or both applications gave wrong ALSA information, or they are doing something funny. If it's indeed Pulseaudio, first step is to usepacmdwith the variouslist-*commands, and see what the configuration is.
– dirkt
yesterday
Crossposting this from askubuntu since that question has gone 2 days with absolutely no interaction.
– Daffy
Nov 18 at 7:05
Crossposting this from askubuntu since that question has gone 2 days with absolutely no interaction.
– Daffy
Nov 18 at 7:05
You tagged with
pulseaudio, but you only mention jack and ALSA. Does your system run Pulseaudio? My advice would be not to unnecessarily mix audio systems. Routing in ALSA will require either alsa_loop or an application, routing in Jack should work if discord shows up under Jack (don't know that) or can be made to show up with a plugin. Routing in Pulseaudio should also be easy. If qsynth requires Jack (don't remember), you can use timidity instead (though it will eat more CPU). In any case, decide on a method, and edit question with more information about how stuff shows up.– dirkt
2 days ago
You tagged with
pulseaudio, but you only mention jack and ALSA. Does your system run Pulseaudio? My advice would be not to unnecessarily mix audio systems. Routing in ALSA will require either alsa_loop or an application, routing in Jack should work if discord shows up under Jack (don't know that) or can be made to show up with a plugin. Routing in Pulseaudio should also be easy. If qsynth requires Jack (don't remember), you can use timidity instead (though it will eat more CPU). In any case, decide on a method, and edit question with more information about how stuff shows up.– dirkt
2 days ago
@dirkt I'm under the impression that Xubuntu 18.04 uses pulseaudio, though I could be wrong, linux audio systems are doing my head in. I think I figured out a way to cut jack out of the picture. I now have qsynth using ALSA exclusively, and the "monitor of stereo output" input is working in discord and audacity. The new problem is that the pitch is shifted lower for some reason. Maybe due to a 44100/48000hz mismatch?
– Daffy
yesterday
@dirkt I'm under the impression that Xubuntu 18.04 uses pulseaudio, though I could be wrong, linux audio systems are doing my head in. I think I figured out a way to cut jack out of the picture. I now have qsynth using ALSA exclusively, and the "monitor of stereo output" input is working in discord and audacity. The new problem is that the pitch is shifted lower for some reason. Maybe due to a 44100/48000hz mismatch?
– Daffy
yesterday
Run
pavucontrol and see if both discord and qsynth show up as sources/sinks to test if you run Pulseaudio. "Monitor of stereo output" strongly suggest you do, because ALSA doesn't have "monitors", but Pulseaudio does. Pulseaudio has an ALSA compatibility layer, which is probably used by one or both of the programs. Pulseaudio does resampling, so if there is a mismatch, one or both applications gave wrong ALSA information, or they are doing something funny. If it's indeed Pulseaudio, first step is to use pacmd with the various list-* commands, and see what the configuration is.– dirkt
yesterday
Run
pavucontrol and see if both discord and qsynth show up as sources/sinks to test if you run Pulseaudio. "Monitor of stereo output" strongly suggest you do, because ALSA doesn't have "monitors", but Pulseaudio does. Pulseaudio has an ALSA compatibility layer, which is probably used by one or both of the programs. Pulseaudio does resampling, so if there is a mismatch, one or both applications gave wrong ALSA information, or they are doing something funny. If it's indeed Pulseaudio, first step is to use pacmd with the various list-* commands, and see what the configuration is.– dirkt
yesterday
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f482482%2ftrying-to-send-midi-audio-to-discord-on-xubuntu%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Crossposting this from askubuntu since that question has gone 2 days with absolutely no interaction.
– Daffy
Nov 18 at 7:05
You tagged with
pulseaudio, but you only mention jack and ALSA. Does your system run Pulseaudio? My advice would be not to unnecessarily mix audio systems. Routing in ALSA will require eitheralsa_loopor an application, routing in Jack should work if discord shows up under Jack (don't know that) or can be made to show up with a plugin. Routing in Pulseaudio should also be easy. Ifqsynthrequires Jack (don't remember), you can usetimidityinstead (though it will eat more CPU). In any case, decide on a method, and edit question with more information about how stuff shows up.– dirkt
2 days ago
@dirkt I'm under the impression that Xubuntu 18.04 uses pulseaudio, though I could be wrong, linux audio systems are doing my head in. I think I figured out a way to cut jack out of the picture. I now have qsynth using ALSA exclusively, and the "monitor of stereo output" input is working in discord and audacity. The new problem is that the pitch is shifted lower for some reason. Maybe due to a 44100/48000hz mismatch?
– Daffy
yesterday
Run
pavucontroland see if both discord and qsynth show up as sources/sinks to test if you run Pulseaudio. "Monitor of stereo output" strongly suggest you do, because ALSA doesn't have "monitors", but Pulseaudio does. Pulseaudio has an ALSA compatibility layer, which is probably used by one or both of the programs. Pulseaudio does resampling, so if there is a mismatch, one or both applications gave wrong ALSA information, or they are doing something funny. If it's indeed Pulseaudio, first step is to usepacmdwith the variouslist-*commands, and see what the configuration is.– dirkt
yesterday