Conversation
There was a problem hiding this comment.
There are a number of things I'd change/add to this guide:
-
Screenshots. Describing the connections in QjackCtl without screenshots is painfully confusing.
-
I really can't see the need to launch QjackCtl and a2jmidid from the command line. It's much less confusing for a new user (that's who I gather this guide is intended for) to launch it from the menu or a toolbar shortcut and have QjackCtl automatically launch a2jmidid by adding a line in "Execute script after Startup" in the 'Options' tab:
a2jmidid -e &. That way you never have to worry about launching it again.
Agree
In fact, the official documentation sometimes also does this. Not sure how many linux users don't use the command line. But of course we should add both. @ignotus666, you can add a few of these changes. I haven't tested the guide myself, but I will try it (should work since it seems to be ok). |
|
Verified it. It does work (but you need to start jack before doing anything else). But why can't we use ALSA MIDI? |
Because Jamulus uses JACK MIDI |
I'm all for using the command line when it makes sense or an application doesn't provide a launcher, but cluttering up your desktop screen with terminal windows when there's no need isn't practical IMHO. I can add the info and the screenshots; I don't have a MIDI keyboard but I can change the aliases in QjackCtl to rename the MIDI gear I do have so it matches the gear described in the guide. Not sure when I'll have time though. |
Ok. Not sure how all this works (I don't usually connect my digital piano to my PC), but I thought that we only need to connect the Audio? Which kind of MIDI signal does Jamulus support (except for the mixing desk commands).
Agree. We could say something like "you can also open it in your terminal with [command]".
But I do. Let me take a few screenshots. |
Duh, you're right... I haven't tried it but I assume it's the synth that uses JACK MIDI then.
Ok cool. |
Yes. I think so and it worked for me. These are my screenshots: @niebert could you please explain why we need the midi through etc? Edit @ignotus666 they say that although ALSA midi is possible, they recommend JACK midi: pantherb/setBfree#28 |
|
What MIDI tab does the synth appear in? I'm obviously missing something so maybe the MIDI through bit does have an explantation. |
|
Not sure, but I assume JACK midi. Can test tomorrow evening |
|
I just installed setBfree and I see what happens: setBfree auto-connects to 'Midi Through' in the JACK MIDI tab, so @niebert's instructions do make sense. You can connect your MIDI keyboard directly to setBfree in the JACK MIDI tab though, without going through 'Midi Through'. |
|
Ok. So should we merge it then? Any thoughts/changes needed? Especially from @niebert |
|
Added pictures now and I think we can merge it after the translation progress if finished |
|
Sorry to be a pest, but - in the last step, when connecting setBfree to Jamulus, it would be advisable to disconnect setBfree's outputs from the 'system' inputs in order to comply with Rule Number 1: do not listen to your local audio. Otherwise it would also lead to a flanger/echo effect. Other than that small detail, it's much better with the screenshots. |
|
Can you change it please? I have to work on the german translation and fix a few things. |
|
Ok - I'll add that advice. |
|
Done. I also corrected a couple of things. |
|
I think we can merge it, after @ignotus666 you've rechecked these additions? |
|
Looks good. |
|
Merged |









In this PR we should discuss how to restructure the Software Synth page since it’s now at a completely different spot.
@niebert should comment on this since he's the author.