You are not logged in.
I've used jack w/ qtractor and some synths off and on for years on this pc. This time I'm trying to use jack2-dbus and the jack2 server itself seems to be working just fine. I can start jack server with jack_control, connect keyboard, qtractor, ardor, synths, meterbridge etc together in qjackctl and all seems happy. Rendered output files play fine later with jack server down. For the life of me though, I can't figure out where the jack -> alsa audio connection is "off" resulting in no speaker output while the jack server is up. Looks normal in the qjackctl connections dialog. Hardware is simply an akai usb mini-keyboard and the onboard hda intel audio processor.
Pulseaudio is not installed and Master, PCM and Front levels are high in alsamixer. Audio works fine with jack server down and browser / other apps sending direct to alsa. I see the output of "jack_control dp" below with jack server up and yoshimi receiving midi events and output meter flashing shows the playback ports not set (there are ports in connection dialog of qjackctl, however).
Any tips / pointers greatly appreciated.
==========================
[lefty@localhost ~]$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xfebfc000 irq 44
[lefty@localhost ~]$ lsmod |grep snd
snd_hda_codec_idt 32804 1
snd_hda_intel 29956 0
snd_hda_codec 126979 2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep 4746 1 snd_hda_codec
snd_pcm 63876 2 snd_hda_codec,snd_hda_intel
snd_page_alloc 5974 2 snd_pcm,snd_hda_intel
snd_timer 14942 1 snd_pcm
snd 44383 6 snd_hwdep,snd_timer,snd_hda_codec_idt,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 4386 1 snd my .asoundrc:
------------------
pcm.!default {
type hw
card Intel
}
ctl.!default {
type hw
card Intel
}my jack launching script:
-------------------------------
#!/bin/bash
jack_control start
sudo schedtool -R -p 20 `pidof jackdbus`
jack_control ds alsa
jack_control dps device hw:Intel
jack_control dps rate 48000
jack_control dps nperiods 2
jack_control dps period 64
jack_control eps realtime true
sleep 10
/usr/bin/a2jmidid -e &
sleep 10
sudo schedtool -R -p 20 `pidof a2jmidid`[lefty@localhost bin]$ jack_control dp
--- get driver parameters (type:isset:default:value)
device: ALSA device name (str:set:hw:0:hw:Intel)
capture: Provide capture ports. Optionally set device (str:notset:none:none)
playback: Provide playback ports. Optionally set device (str:notset:none:none)
rate: Sample rate (uint:set:48000:48000)
period: Frames per period (uint:set:1024:64)
nperiods: Number of periods of playback latency (uint:set:2:2)
hwmon: Hardware monitoring, if available (bool:notset:False:False)
hwmeter: Hardware metering, if available (bool:notset:False:False)
duplex: Provide both capture and playback ports (bool:notset:True:True)
softmode: Soft-mode, no xrun handling (bool:notset:False:False)
monitor: Provide monitor ports for the output (bool:notset:False:False)
dither: Dithering mode (char:notset:n:n)
inchannels: Number of capture channels (defaults to hardware max) (uint:notset:0:0)
outchannels: Number of playback channels (defaults to hardware max) (uint:notset:0:0)
shorts: Try 16-bit samples before 32-bit (bool:notset:False:False)
input-latency: Extra input latency (frames) (uint:notset:0:0)
output-latency: Extra output latency (frames) (uint:notset:0:0)
midi-driver: ALSA device name (str:notset:none:none)Last edited by badmusician (2013-08-16 22:29:52)
Offline
When pasting configs, code or command output, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode
like thisIt makes the code more readable and - in case of longer listings - more convenient to scroll through.
Offline
Sorry...edited now
Offline
Still don't know why jack apps' pcm output connected to system playback does not make it through to speakers, but as a workaround I find that if I launch zita-j2a from the zita-ajbridge aur package, I can connect my jack apps to it's playback ports and output DOES make it to speakers.
Offline