Thanks. This should likely be the default configuration (for jack?)
then. Default configs for these packages install both daemons as I
listed them.
In any case, I gave up on it and went back to using Windows to do music
production, far too many problems with too many tools for me still. I'll
c
Some additional notes follwing more testing (takes a reboot between
tests)...
The problem seems to be isolated to pulseaudio running when an alsa
reload is performed. If pulseaudio has not been stopped, sudo alsa
reload will not properly initalize the card. If pulseaudio is stopepd
and restarted e
** Attachment added: "pulseaudio log generated via "pulseaudio -""
http://launchpadlibrarian.net/35704756/pulseverbose.log
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/35704757/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.
Public bug reported:
Binary package hint: pulseaudio
This bug report being filed per request by one of the bug team (dtchen).
In simple terms, upon an initial boot and login, ALSA will not pass MIDI
data from a supported interface until it is forcibly restarted without
pulseaudio respawning.
Thi
Confirming this bug, and the solution to getting the card driver to
properly load being as documented above. I have a different interface
(TASCAM US-122L) but the same exact issues and errors. Creating
~/.pulse/client.conf with the line "autospawn = no", stopping JACK and
issuing a "sudo alsa reloa
