Having problems with MIDI in recording on Ubuntu
I have a Yamaha P-120 model with a USB to MIDI interface that looks like this.

USB to MIDI interface
I've decided to use LMMS because it seems like the easiest MIDI sequencer available. I'm having a lot of difficulties getting this to work.
What I am trying to do
Record input from my keyboard onto LMMS
What is working
I can get my output to work, so I can control my keyboard via my computer.
What is not working
My computer isn't reading the input from the keyboard. I can't record any songs.
What have I tried
A lot.
Ports/Any other Information
Port Client name Port name
14:0 Midi Through Midi Through Port-0
24:0 USB Midi USB Midi MIDI 1
128:1 LMMS Default preset
128:2 LMMS Default preset
128:4 LMMS Default preset
129:0 Client-129 qjackctl
Let me know if you need anything else to help. I am really trying hard to fix this problem as I would love to use my MIDI keyboard.
drivers keyboard music midi lmms
add a comment |
I have a Yamaha P-120 model with a USB to MIDI interface that looks like this.

USB to MIDI interface
I've decided to use LMMS because it seems like the easiest MIDI sequencer available. I'm having a lot of difficulties getting this to work.
What I am trying to do
Record input from my keyboard onto LMMS
What is working
I can get my output to work, so I can control my keyboard via my computer.
What is not working
My computer isn't reading the input from the keyboard. I can't record any songs.
What have I tried
A lot.
Ports/Any other Information
Port Client name Port name
14:0 Midi Through Midi Through Port-0
24:0 USB Midi USB Midi MIDI 1
128:1 LMMS Default preset
128:2 LMMS Default preset
128:4 LMMS Default preset
129:0 Client-129 qjackctl
Let me know if you need anything else to help. I am really trying hard to fix this problem as I would love to use my MIDI keyboard.
drivers keyboard music midi lmms
Doesaseqdump -p "USB Midi"work?
– CL.
Mar 18 '14 at 8:35
yes. my output reads:24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop
– and0rsk
Mar 18 '14 at 11:22
Found out some things more with my interface:aconnect -i client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' 'andaconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' client 128: 'FLUID Synth (3237)' [type=user] 0 'Synth input port (3237:0)'
– and0rsk
Mar 18 '14 at 12:25
Also, I am following this tutorial now and so far I am still having problems with the MIDI tedfelix.com/linux/linux-midi.html
– and0rsk
Mar 18 '14 at 12:27
add a comment |
I have a Yamaha P-120 model with a USB to MIDI interface that looks like this.

USB to MIDI interface
I've decided to use LMMS because it seems like the easiest MIDI sequencer available. I'm having a lot of difficulties getting this to work.
What I am trying to do
Record input from my keyboard onto LMMS
What is working
I can get my output to work, so I can control my keyboard via my computer.
What is not working
My computer isn't reading the input from the keyboard. I can't record any songs.
What have I tried
A lot.
Ports/Any other Information
Port Client name Port name
14:0 Midi Through Midi Through Port-0
24:0 USB Midi USB Midi MIDI 1
128:1 LMMS Default preset
128:2 LMMS Default preset
128:4 LMMS Default preset
129:0 Client-129 qjackctl
Let me know if you need anything else to help. I am really trying hard to fix this problem as I would love to use my MIDI keyboard.
drivers keyboard music midi lmms
I have a Yamaha P-120 model with a USB to MIDI interface that looks like this.

USB to MIDI interface
I've decided to use LMMS because it seems like the easiest MIDI sequencer available. I'm having a lot of difficulties getting this to work.
What I am trying to do
Record input from my keyboard onto LMMS
What is working
I can get my output to work, so I can control my keyboard via my computer.
What is not working
My computer isn't reading the input from the keyboard. I can't record any songs.
What have I tried
A lot.
Ports/Any other Information
Port Client name Port name
14:0 Midi Through Midi Through Port-0
24:0 USB Midi USB Midi MIDI 1
128:1 LMMS Default preset
128:2 LMMS Default preset
128:4 LMMS Default preset
129:0 Client-129 qjackctl
Let me know if you need anything else to help. I am really trying hard to fix this problem as I would love to use my MIDI keyboard.
drivers keyboard music midi lmms
drivers keyboard music midi lmms
edited Jan 8 at 3:21
karel
58.1k12128146
58.1k12128146
asked Mar 18 '14 at 5:22
and0rskand0rsk
1586
1586
Doesaseqdump -p "USB Midi"work?
– CL.
Mar 18 '14 at 8:35
yes. my output reads:24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop
– and0rsk
Mar 18 '14 at 11:22
Found out some things more with my interface:aconnect -i client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' 'andaconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' client 128: 'FLUID Synth (3237)' [type=user] 0 'Synth input port (3237:0)'
– and0rsk
Mar 18 '14 at 12:25
Also, I am following this tutorial now and so far I am still having problems with the MIDI tedfelix.com/linux/linux-midi.html
– and0rsk
Mar 18 '14 at 12:27
add a comment |
Doesaseqdump -p "USB Midi"work?
– CL.
Mar 18 '14 at 8:35
yes. my output reads:24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop
– and0rsk
Mar 18 '14 at 11:22
Found out some things more with my interface:aconnect -i client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' 'andaconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' client 128: 'FLUID Synth (3237)' [type=user] 0 'Synth input port (3237:0)'
– and0rsk
Mar 18 '14 at 12:25
Also, I am following this tutorial now and so far I am still having problems with the MIDI tedfelix.com/linux/linux-midi.html
– and0rsk
Mar 18 '14 at 12:27
Does
aseqdump -p "USB Midi" work?– CL.
Mar 18 '14 at 8:35
Does
aseqdump -p "USB Midi" work?– CL.
Mar 18 '14 at 8:35
yes. my output reads:
24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop– and0rsk
Mar 18 '14 at 11:22
yes. my output reads:
24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop– and0rsk
Mar 18 '14 at 11:22
Found out some things more with my interface:
aconnect -i client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' ' and aconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' client 128: 'FLUID Synth (3237)' [type=user] 0 'Synth input port (3237:0)' – and0rsk
Mar 18 '14 at 12:25
Found out some things more with my interface:
aconnect -i client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' ' and aconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' client 128: 'FLUID Synth (3237)' [type=user] 0 'Synth input port (3237:0)' – and0rsk
Mar 18 '14 at 12:25
Also, I am following this tutorial now and so far I am still having problems with the MIDI tedfelix.com/linux/linux-midi.html
– and0rsk
Mar 18 '14 at 12:27
Also, I am following this tutorial now and so far I am still having problems with the MIDI tedfelix.com/linux/linux-midi.html
– and0rsk
Mar 18 '14 at 12:27
add a comment |
2 Answers
2
active
oldest
votes
The MIDI command bytes for Clock, Stop, and Active Sensing are F8, FC, and FE.
In binary, this would be 11111000, 11111100, and 11111110.
The MIDI protocol has no synchronization or error correction; this looks like noise on the MIDI data line, i.e., there is no actual MIDI signal.
Reasons for this could be:
- the MIDI input cable is broken;
- the keyboard's MIDI output is broken; or
- the "HOST SELECT" switch is not set to "MIDI".
It is possible the MIDI cable is broken, except that I was getting output to the keyboard through my computer (So I think that it would mean that MIDI IN would have to be the only cord broken). Host select switch is set to MIDI. I hope its not a hardware failure. The only way I can think of making sure it isn't a hardware failure is to make sure there isn't some weird driver/problem with Yamaha keyboards and MIDI connections. (I've found stuff online saying Yamaha is special).
– and0rsk
Mar 18 '14 at 12:42
I might just purchase another cable and see if that works. I'll be able to tell you if it was hardware failure after I see how a new cable reacts to the connection (unless the hardware failure is on the keyboard itself like you suggested).
– and0rsk
Mar 18 '14 at 12:48
add a comment |
Change the in and out cables on your synthesizer and it will work
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2faskubuntu.com%2fquestions%2f435745%2fhaving-problems-with-midi-in-recording-on-ubuntu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The MIDI command bytes for Clock, Stop, and Active Sensing are F8, FC, and FE.
In binary, this would be 11111000, 11111100, and 11111110.
The MIDI protocol has no synchronization or error correction; this looks like noise on the MIDI data line, i.e., there is no actual MIDI signal.
Reasons for this could be:
- the MIDI input cable is broken;
- the keyboard's MIDI output is broken; or
- the "HOST SELECT" switch is not set to "MIDI".
It is possible the MIDI cable is broken, except that I was getting output to the keyboard through my computer (So I think that it would mean that MIDI IN would have to be the only cord broken). Host select switch is set to MIDI. I hope its not a hardware failure. The only way I can think of making sure it isn't a hardware failure is to make sure there isn't some weird driver/problem with Yamaha keyboards and MIDI connections. (I've found stuff online saying Yamaha is special).
– and0rsk
Mar 18 '14 at 12:42
I might just purchase another cable and see if that works. I'll be able to tell you if it was hardware failure after I see how a new cable reacts to the connection (unless the hardware failure is on the keyboard itself like you suggested).
– and0rsk
Mar 18 '14 at 12:48
add a comment |
The MIDI command bytes for Clock, Stop, and Active Sensing are F8, FC, and FE.
In binary, this would be 11111000, 11111100, and 11111110.
The MIDI protocol has no synchronization or error correction; this looks like noise on the MIDI data line, i.e., there is no actual MIDI signal.
Reasons for this could be:
- the MIDI input cable is broken;
- the keyboard's MIDI output is broken; or
- the "HOST SELECT" switch is not set to "MIDI".
It is possible the MIDI cable is broken, except that I was getting output to the keyboard through my computer (So I think that it would mean that MIDI IN would have to be the only cord broken). Host select switch is set to MIDI. I hope its not a hardware failure. The only way I can think of making sure it isn't a hardware failure is to make sure there isn't some weird driver/problem with Yamaha keyboards and MIDI connections. (I've found stuff online saying Yamaha is special).
– and0rsk
Mar 18 '14 at 12:42
I might just purchase another cable and see if that works. I'll be able to tell you if it was hardware failure after I see how a new cable reacts to the connection (unless the hardware failure is on the keyboard itself like you suggested).
– and0rsk
Mar 18 '14 at 12:48
add a comment |
The MIDI command bytes for Clock, Stop, and Active Sensing are F8, FC, and FE.
In binary, this would be 11111000, 11111100, and 11111110.
The MIDI protocol has no synchronization or error correction; this looks like noise on the MIDI data line, i.e., there is no actual MIDI signal.
Reasons for this could be:
- the MIDI input cable is broken;
- the keyboard's MIDI output is broken; or
- the "HOST SELECT" switch is not set to "MIDI".
The MIDI command bytes for Clock, Stop, and Active Sensing are F8, FC, and FE.
In binary, this would be 11111000, 11111100, and 11111110.
The MIDI protocol has no synchronization or error correction; this looks like noise on the MIDI data line, i.e., there is no actual MIDI signal.
Reasons for this could be:
- the MIDI input cable is broken;
- the keyboard's MIDI output is broken; or
- the "HOST SELECT" switch is not set to "MIDI".
edited Mar 18 '14 at 13:12
answered Mar 18 '14 at 12:14
CL.CL.
1,42911112
1,42911112
It is possible the MIDI cable is broken, except that I was getting output to the keyboard through my computer (So I think that it would mean that MIDI IN would have to be the only cord broken). Host select switch is set to MIDI. I hope its not a hardware failure. The only way I can think of making sure it isn't a hardware failure is to make sure there isn't some weird driver/problem with Yamaha keyboards and MIDI connections. (I've found stuff online saying Yamaha is special).
– and0rsk
Mar 18 '14 at 12:42
I might just purchase another cable and see if that works. I'll be able to tell you if it was hardware failure after I see how a new cable reacts to the connection (unless the hardware failure is on the keyboard itself like you suggested).
– and0rsk
Mar 18 '14 at 12:48
add a comment |
It is possible the MIDI cable is broken, except that I was getting output to the keyboard through my computer (So I think that it would mean that MIDI IN would have to be the only cord broken). Host select switch is set to MIDI. I hope its not a hardware failure. The only way I can think of making sure it isn't a hardware failure is to make sure there isn't some weird driver/problem with Yamaha keyboards and MIDI connections. (I've found stuff online saying Yamaha is special).
– and0rsk
Mar 18 '14 at 12:42
I might just purchase another cable and see if that works. I'll be able to tell you if it was hardware failure after I see how a new cable reacts to the connection (unless the hardware failure is on the keyboard itself like you suggested).
– and0rsk
Mar 18 '14 at 12:48
It is possible the MIDI cable is broken, except that I was getting output to the keyboard through my computer (So I think that it would mean that MIDI IN would have to be the only cord broken). Host select switch is set to MIDI. I hope its not a hardware failure. The only way I can think of making sure it isn't a hardware failure is to make sure there isn't some weird driver/problem with Yamaha keyboards and MIDI connections. (I've found stuff online saying Yamaha is special).
– and0rsk
Mar 18 '14 at 12:42
It is possible the MIDI cable is broken, except that I was getting output to the keyboard through my computer (So I think that it would mean that MIDI IN would have to be the only cord broken). Host select switch is set to MIDI. I hope its not a hardware failure. The only way I can think of making sure it isn't a hardware failure is to make sure there isn't some weird driver/problem with Yamaha keyboards and MIDI connections. (I've found stuff online saying Yamaha is special).
– and0rsk
Mar 18 '14 at 12:42
I might just purchase another cable and see if that works. I'll be able to tell you if it was hardware failure after I see how a new cable reacts to the connection (unless the hardware failure is on the keyboard itself like you suggested).
– and0rsk
Mar 18 '14 at 12:48
I might just purchase another cable and see if that works. I'll be able to tell you if it was hardware failure after I see how a new cable reacts to the connection (unless the hardware failure is on the keyboard itself like you suggested).
– and0rsk
Mar 18 '14 at 12:48
add a comment |
Change the in and out cables on your synthesizer and it will work
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Change the in and out cables on your synthesizer and it will work
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Change the in and out cables on your synthesizer and it will work
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Change the in and out cables on your synthesizer and it will work
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 16 mins ago
JackJack
1
1
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jack is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2faskubuntu.com%2fquestions%2f435745%2fhaving-problems-with-midi-in-recording-on-ubuntu%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
Does
aseqdump -p "USB Midi"work?– CL.
Mar 18 '14 at 8:35
yes. my output reads:
24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Active Sensing 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Clock 24:0 Stop– and0rsk
Mar 18 '14 at 11:22
Found out some things more with my interface:
aconnect -i client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' 'andaconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 28: 'USB Midi' [type=kernel] 0 'USB Midi MIDI 1 ' client 128: 'FLUID Synth (3237)' [type=user] 0 'Synth input port (3237:0)'– and0rsk
Mar 18 '14 at 12:25
Also, I am following this tutorial now and so far I am still having problems with the MIDI tedfelix.com/linux/linux-midi.html
– and0rsk
Mar 18 '14 at 12:27