Hello,
My HiFiBerry DAC sounds good when using aplay , but I cannot use JACK, I get an error:
$ jackd -d alsa -d hw:sndrpihifiberry -P
jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:sndrpihifiberry|-|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: mmap-based access is not possible for the playback stream of this audio interface
ALSA: cannot configure playback channel
cannot load driver module alsa
Are there any solution for using HiFiBerry and JACK?
Thank you.
Date
Votes
17 comments
-
HiFiBerry team Looking at this thread, it looks like jackd has some problems in general with the Raspberry Pi and a patched version is needed:
http://stackoverflow.com/questions/12144972/jack-audio-connection-kit-jackd-daemon-fails-to-start-on-raspberrypi -
Rafael S Yes, I use the jackd1 patched version (Jack1 0.121.3 git commit 75e3e20b) as explained by AutoStatic on http://wiki.linuxaudio.org/wiki/raspberrypi
$ dpkg-query -W jackd1
jackd1 1:0.121.3+20120418git75e3e20b-2.1+fixed1~raspbian1
I’ve been using my UCA202 USB card succesfully, but my new HiFiBerry shows this mmap error :-( -
Rafael S
It seems that MMAP ALSA driver support is needed for JACK, as explained here
http://wiki.linuxaudio.org/wiki/raspberrypi#running_jack
Could it be possible to support mmap access on HiFiBerry driver? -
HiFiBerry team Hi Rafael,
I don't think this can be done easily. Our HiFiBerry driver is using the Raspberry Pi I2S subsystem, which seems not to support mmap. This would need somebody who can work on the I2S sound subsystem. Most likely this will need major changes. Therefore there is only a minimal chance to change this.
Best regards
Daniel -
Rafael S Hi Daniel,
Some work has been done for provide MMAP to the internal audio here:
http://martinezjavier.wordpress.com/2013/04/27/mmap-support-for-raspberry-pi-bcm2835-alsa-driver/
Code is published here:
https://github.com/raspberrypi/linux/commit/bad49c21520ddc40d512a0d424cbc94f20068e6c
Maybe it could help for I2S scenario :-)
It would be a great improvement if you can advance to this, specialy if you can develope a new multichannel DAC that we are awaiting for doing some FIR xover filtering using RPI :-)
I must say that I am very impressed with the sound of HiFiberry DAC. I use Brutefir 32K taps mixed IIR and FIR filter for doing respectively DRC and Bass linearization. 75% CPU is reached so I think multichannel xover could be possible if I2S 4 channel sound card were available :-)
Thank you and congratulations for your projects!
BR
Rafael -
Stephan S. Any news on this? Same situation here "mmap-based access is not possible for the playback stream of this audio interface".
Thanks,
Stephan. -
HiFiBerry team Dear Stephan,
as far as I know no one is working on this at the moment. The developer of the I2S sound subsystem is still maintaining the driver, but not working on new functionalities.
Best regards
Daniel -
Jorma Unfortunately I only found this topic after purchasing the DAC+.
My intention is to create a headless soft synth based on the Pi 2. The DAC+ is a nice unit and getting it to work with Arch Linux was easy enough. It makes a compact package with the Pi and not using a USB bus also sounds like a good idea.
Due to the lack of mmap support it is not suitable for this kind of use. Even not being able to use jackd is not a show stopper. It also seems that some soft synths that I tried require mmap when accessing ALSA direcly.
Daniel - is there any longer term plan on including mmap support? This would make the unit much more versatile... -
HiFiBerry team At this time, there are no plans for this. However as the whole Linux kernel is Open Source, it might be interesting for other developers to work on this. If somebody wants to work on this, we will support him.
Best regards
Daniel -
Konstantin Kozhedub For those who have found this topic after buying, I can recommend the use alsa_out for jackd. Not very elegant, but it works.
alsa_out -dhw: sndrpihifiberry -p1024 -n4 -r48000 - always consumes 35% of CPU. -
Roman Spychala Try (poorly documented)mmap_emulALSA plugin:pcm.mmapmyberry {
type mmap_emul;
slave {
pcm "hw:0";
}
}pcm.!default {
type plug;
slave {
pcm mmapmyberry;
}
} -
HiFiBerry team With Linux 4.x the mmap() functionality can be enabled by a device-tree overlay:
dtoverlay=i2s-mmap
(see https://github.com/raspberrypi/firmware/tree/master/boot/overlays for more information)
Best regards
Daniel -
Florian Koch Can somebody confirm that jackd is now working using this overlay?
-
HiFiBerry team Hi Florian,
we have feedback that some HiFiBerry users use it this way.
Best regards
Daniel -
busa Hi
Somebody managed to get Jackd Running with RPI + HifiBerry Digi+? It seams that the mmap-overlay works, but Jackd keeps crashing after a few seconds. Would like to use it for BruteFir :-)
jackd -R -p16 -v -d alsa -dhw:0 -p 256 -n 3 -r 44100 -s
jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
getting driver descriptor from /usr/lib/arm-linux-gnueabihf/jack/jack_dummy.so
getting driver descriptor from /usr/lib/arm-linux-gnueabihf/jack/jack_alsa.so
getting driver descriptor from /usr/lib/arm-linux-gnueabihf/jack/jack_net.so
getting driver descriptor from /usr/lib/arm-linux-gnueabihf/jack/jack_oss.so
JACK compiled with System V SHM support.
server `default' registered
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
loading driver ..
start poll on 3 fd's
apparent rate = 44100
new client: alsa_pcm, id = 1 type 1 @ 0x1a2e5a8 fd = -1
creating alsa driver ... hw:0|hw:0|256|3|44100|0|0|nomon|swmeter|soft-mode|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames (5.8 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 3 periods for playback
new buffer size 256
resizing port buffer segment for type 0, one buffer = 1024 bytes
resizing port buffer segment for type 1, one buffer = 1024 bytes
registered port system:capture_1, offset = 1024
registered port system:capture_2, offset = 2048
registered port system:playback_1, offset = 0
registered port system:playback_2, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
-- jack_rechain_graph()
-- jack_sort_graph
2876 waiting for signals
ALSA: poll time out, polled for 8706051 usecs
DRIVER NT: could not run driver cycle
stopping driver
detaching driver
jack main caught signal 12
starting server engine shutdown
freeing shared port segments
server thread back from poll
stopping server thread
stopping watchdog thread
last xrun delay: 0.000 usecs
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
cleaning up shared memory
cleaning up files
unregistering server `default'Best Regards
busa
-
Kristján Valur Jónsson dtoverlay=i2s-mmap
is doing the trick, dmixer now works.
I suggest updating the user guides and suggest that this overlay be added for those needing advanced ALSA configuration. Also, are there any drawbacks to doing this?
-
Luc PANNETRAT I can confirm "dtoverlay=i2s-mmap" works here with jackd and alsa_out (Hifiberry DAC+ pro)
Please sign in to leave a comment.