| Summary: | usb midi configuration | ||
|---|---|---|---|
| Product: | [I don't know] kde | Reporter: | Evan Mundy <Evan> |
| Component: | general | Assignee: | Unassigned bugs <unassigned-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 4.14.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
I have had some trouble getting a setup for off-line music established, and my current setup is going fairly well, except for the problem in the bug report, so I would prefer to implement some solution on the current desktop, if it is available! please close this bug report: thank you. Sincerely, Evan@mundy.xyz "Simon Grundy" (Evan Mundy) |
To the bug report section: Hello. I use KDE to run Skype and MuseScore 2.02. I am using Pulse/Alsa/Jack, but these do not provide midi note input into MuseScore. I prefer to use a midi keyboard, rather than a computer keyboard for MuseScore note input. I have a "USB2.0-midi" device: midi in and out din-to-din at the midi keyboard, to a usb port on the computer. In an attempt to use the USB midi device, I first used "Configuration/hardware Devices/USB Sound device, and used an "enable" section, where I first called the device a "USB Audio" device. This did not work. Only when I changed the MuseScore audio driver to Alsa, and re-enabled the usb midi device, calling it "USB 2.0-midi" would it provide note input with my midi keyboard into MuseScore. After checking the midi input, I used Skype, but the mike input did not work until I changed the MuseScore audio driver to "Jack". However, the cable for the USB midi device would not reach to the location I normally place my computer. Therefore, I then attached a 10-foot usb extension to the usb midi usb cable. After I did so, and went to enable the usb midi device, I found that it was reassigned as an "other device". There is no configuration sub-section, and the module is listed as "unknown". No midi input is currently available. The usb midi device instructions ask you to use the same usb port all the time, so my assumption is that the usb extension was interpreted as a second midi port. Under the circumstances, I decided to try two other usb ports, but the response was exactly the same. Would you say that if I want to again use the device, that I would have to run another KDE installation or overwrite my current installation if I expect to use this device again? I now know that I should use the device without the usb cable extension; that I should use the Alsa driver,and that I should name the device "USB2.0-midi" in the enable section of Configuration. Is there some tactic or approach I could use within the current KDE installation that would restore my ability to use the USB2.0-midi device, or is bug-report support of the opinion that my assessment is condidered correct or accurate, and that I can only now use the USB2.0-midi device with a new replacement KDE installation? Or do you recommend that other sections such as Vendor ID ("vid") also be used along with the "enable" section to complete the process that makes the device available for use? Sincerely, Evan Mundy Reproducible: Always Steps to Reproduce: 1.added usb cable extension 2. no midi input 3. tried another midi port: no midi input Actual Results: (no midi input) Expected Results: remove usb cable extension; process should return to prior established midi input on the same usb port.