mikebrady / shairport-sync

AirPlay and AirPlay 2 audio player
Other
7.27k stars 573 forks source link

Error -19 getting dac_delay in buffer_get_frame. (IQaudIO and/or android AirAudio) #292

Closed TermeHansen closed 8 years ago

TermeHansen commented 8 years ago

I have problems getting shairport-sync working on my raspberry with an IQaudIO from my android using AirAudio. I have looked in the other open issue on android and tried the sync suggestions, but it seems unrelated to that. As soon as I connect the AirAudio I get a lot of: "Error -19 getting dac_delay in buffer_get_frame."

Looking for the configuration file "/etc/shairport-sync.conf".
Output device name is "hw:0,0".
Lowest dB value is a mute.
Can't get dB value corresponding to a "volume" of 1.
Hardware mixer has dB volume from -103.000000 to 0.000000.
Has mute ability.
Version: "2.8.3-openssl-Avahi-ALSA-soxr-metadata"
statistics_requester status is 0.
daemon status is 0.
rtsp listening port is 5000.
udp base port is 6001.
udp port range is 100.
Shairport Sync player name is "TermoPlayer".
Audio Output name is "(null)".
on-start action is "(null)".
on-stop action is "(null)".
wait-cmd status is 0.
mdns backend "(null)".
stuffing option is "0".
resync time is 0.
allow a session to be interrupted: 0.
busy timeout time is 120.
drift tolerance is 2200 frames.
password is "(null)".
ignore_volume_control is 0.
disable_synchronization is 1.
audio backend desired buffer length is 6615.
audio backend latency offset is 0.
volume range in dB (zero means use the range specified by the mixer): 0.
zeroconf regtype is "_raop._tcp".
configuration file name "/etc/shairport-sync.conf" resolves to "/etc/shairport-sync.conf".
metdata enabled is 0.
metadata pipename is "(null)".
get-coverart is 0.
avahi: avahi_register.
avahi: register_service.
avahi: request to add "_raop._tcp" service without metadata
avahi: service '8520C1FA2F90@TermoPlayer' successfully added.
avahi: address advertised is: "192.168.1.117".
New RTSP connection on port 5000
Play connection from user agent "iTunes/11.3.1 (Macintosh; OS X 10.9.4) AppleWebKit/537.77.4".
Connection from IPv4: 192.168.1.241:35680
Error -19 getting dac_delay in buffer_get_frame.
Error -19 getting dac_delay in buffer_get_frame.
Error -19 getting dac_delay in buffer_get_frame.
Error -19 getting dac_delay in buffer_get_frame.
Error -19 getting dac_delay in buffer_get_frame.
Error -19 getting dac_delay in buffer_get_frame.
Error -19 getting dac_delay in buffer_get_frame.
Error -19 getting dac_delay in buffer_get_frame.

Update: Just tried with our Ipad 3 and same issue.

Update 2: compiled --without-soxr, and now it seems to work?!?

mikebrady commented 8 years ago

Many thanks for the report. The error message is coming from the part of the software that communicates with the DAC. Could you check what output devices are visible with, say, alsamixer? Did you use the correct overlay for enabling the IQaudIO device?

TermeHansen commented 8 years ago

As stated in latest update, "--without-soxr" it works for some reason, same config file and everything.

**** List of PLAYBACK Hardware Devices ****
card 0: IQaudIODAC [IQaudIODAC], device 0: IQaudIO DAC HiFi pcm512x-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

output_device = "hw:0,0"; //

mikebrady commented 8 years ago

Thanks. That's really bizarre. I'll see what I can check out. What's your system? Latest Raspbian? Which type of Pi? Just a really odd suggestion -- try it with an output device hw:0. I can't imagine why it might make a difference, but it's what I normally write...

TermeHansen commented 8 years ago

Hi Mike. I turned off the internal jack off with dtparam=audio=off in /boot/config.txt. With your suggestion I activated it again, and then everything worked. Returning back to no jack output and it still works o_O

Bottomline - Everything works now with no hickups, so consider this issue as "solved" for now. Still don't know what happened before, as I am using same binaries and config?!?

Thks for your time and coding skills!

mikebrady commented 8 years ago

Thanks for the update. It might help someone in the future. I'll close the issue for now. Feel free to reopen it if needed.

gramss commented 7 years ago

I had the same issue.. changed my hostname during installation.

A simple restart solved the issue

kabakaev commented 4 years ago

I came to this issue because of the same error message. This error is printed on ubuntu-18.04 when pulseaudio is using the alsa card. Try killall /usr/bin/pulseaudio to test it it's actually the case.