2 Dec
2017
2 Dec
'17
5:28 p.m.
Thanks David. Now I'm having a problem with the USB over MIDI connecting
properly to the computer. When I click on a piano key in the Pianoteq
application it plays fine, but somehow I have the USB over midi configured
wrong. I'm running a2 J m i d i d - e, but then I don't remember what to
connect with what, on midi or alsa qjackctl tabs, to get it to work. And
I'm no longer sure whether I need the midi translation to be set to
sequential or raw or none. Thanks again for the help.
On Dec 2, 2017 8:14 AM, "David Kastrup" <dak(a)gnu.org> wrote:
john gibby <johnalan.gibby(a)gmail.com> writes:
Hi All. I am just reading the responses, and I
am going to study them
after sending this email. But I want to share this - I got it work. Got
up at 4:30am, just now got it working. I don't really understand
completely what I've done, but here it is. Maybe y'all can help me
better
understand why all this works.
BTW, I apologize that my email last night was unpleasant; I was really
upset, but should have moderated the email better. And - maybe I will
consider getting rid of PA, but the thing is, it "comes with" AV Linux
and
so it was more convenient for me to try and live
with it. As for using a
Mac for all this; had never thought of that. Interesting idea. (Can one
purchase and load MAC OS on my tower PC?)
What I did:
1. Turned off "autospawn" in PA client.conf. I don't know yet if I need
to implement a way to make this temporary.
I find that a good choice on a computer used for serious audio work.
It's sometimes inconvenient when you forgot to start it in time (like
having to kill and restart applications that chose to grab ALSA
exclusively instead) but it's good _not_ to have to worry about it
restarting when actually doing DAW/audio work.
--
David Kastrup