Renoise LOG> ALSA: Opening ALSA Playback Device 'hw:1,0 (Audio Kontrol 1)'...
Renoise LOG> ALSA: Open ALSA Output Device OK
Renoise LOG> ALSA: Max channels is 2 for Playback...
Renoise LOG> ALSA: Using 2 channels (2 requested) for Playback...
Renoise LOG> ALSA: Using access format RW_INTERLEAVED (requested RW_INTERLEAVED) for Playback...
Renoise LOG> ALSA: Failed to set format S32_LE for Playback: Invalid argument...
Renoise LOG> ALSA: Failed to set format S24_3LE for Playback: Invalid argument...
Renoise LOG> ALSA: Failed to set format S16_LE for Playback: Invalid argument...
Renoise LOG> ALSA: No supported sample format was accepted for Playback. Bailing out..
Renoise LOG> ALSA: ALSA Output FAILED (HW parameters)!
Renoise LOG> Error Message: Failed to open the ALSA device 'hw:1,0 (Audio Kontrol 1)' (SetupHWParameters failed).
Renoise LOG> Error Message: ALSA failed to open. Trying to open JACK instead...
I’m on Arch 32bit Renoise 2.8b7 but believe this has existed with this card before the latest round of betas.
Alsa works fine through other applications and I can get 2 channel out in Renoise through jack.
My USB NI Audio Kontrol 1 presents itself as 2 stereo outs on [edit]hw:1,0,0 and hw:1,0,1[/edit]
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: AudioKontrol1 [Audio Kontrol 1], device 0: Audio Kontrol 1 [Audio Kontrol 1]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
I’m pretty clueless about ALSA so I’ve just been using my desktop’s built in card, which isn’t really ideal. The card does with fine with xwax via ALSA though so it’s not completely useless.
Yes, JACK works fine, I can still use renoise happily that way but most the time I’m too lazy to launch JACK and just use my computers internal interface. I’m not mixing or mastering or anything so the slight audio quality hit doesn’t really matter.
I just thought I’d report the problem I’m having with ALSA. Gotta report them bugs and problems!
if you are too lazy to launch jack, you can write a startup script, where you are launching jack and renoise, so every time you are booting up, you are just ready to go (or put it on shortcuts of your window manager)
Renoise won’t natively see the subdevices or the setup in my ~/.asoundrc and falls back to Jack (as I mention in the incredibly old thread title)
I don’t have a problem using Jack. It does not work out of the box though.
Here is a suitable, hardcoded ~/.asoundrc for a 2x4 audio interface that works with Jack.
Use jack2x4 in the interface section in qjackctl, and watch for you device moving to hw:1 if you hot plug it (it probably has a friendly name like hw:audiokontrol1 you could use instead)
# create a device called multi to combine the separate devices
pcm.multi {
type multi;
# bind the 'separate' Kore hardware devices
slaves.a.pcm "hw:0,0,0"
slaves.a.channels 2
slaves.b.pcm "hw:0,0,1"
slaves.b.channels 2
# bind channels to virtual device
bindings.0.slave a
bindings.0.channel 0
bindings.1.slave a
bindings.1.channel 1
bindings.2.slave b
bindings.2.channel 0
bindings.3.slave b
bindings.3.channel 1
}
# JACK needs to 'see' a mixer defined for a device
# even when there isn't a software mixer as is the case with this device
ctl.multi {
type hw
card 0
}
# this is the bit of magic... defining the 'card' we're going to use!
pcm.jack2x4 {
# "asym" allows for different handling of in/out devices
type asym
playback.pcm {
# route for mmap workaround
type route
slave.pcm "multi"
ttable.0.0 1
ttable.1.1 1
ttable.2.2 1
ttable.3.3 1
}
capture.pcm {
# 2 channels only
type hw
card 0
}
}
# define a non-functioning mixer for jack2x4 for JACK's benefit
ctl.jack2x4 {
type hw
card 0
}
yes exactly /> (are there still so many of them?) i apologize for my poor knowledge on that topic.
all mine soundsapps run smoothly thru jack (i love to patch my own environment)
kindest regs
./h