This file will include the majority of the known issues we're aware of with AzuraCast and that are in the stages of review / investigation / fixing. We don't provide a date on the fixes but rest assured we're aware of them.
-
When some live DJ broadcasting software connects to stream, only the first metadata update is received, rather than the initial metadata when the client connects. This is often reported as AzuraCast "missing" the first song that a DJ broadcasts. This is an upstream issue with Liquidsoap that we are continuing to follow. The easy workaround for most users is to connect while playing a very short track (such as an intro or station ID), then immediately transition to another song after connecting, which triggers a second metadata update and fixes the issue.
-
The WebDJ feature, on some browsers and in some situations, can broadcast sound that seems "crackly" and intermittent to stream listeners. This is a known issue, but the cause of it is currently unknown. #5116
-
Many users have requested the ability for Liquidsoap to skip to the next song automatically after a DJ disconnects. This is also an upstream issue with Liquidsoap that we are continuing to follow.
We class bugs as 'high priority' when it impacts a large amount of users, related to CPU and Memory usages or security bugs. These bugs can be complex to debug and requires a large amount of investigation and reviewing by our team.
-
Playlists not always following the schedule
-
Ansible users not being able to install on Ubuntu 18.04 due to ocaml-ffmpeg being unsupported #5007
-
Deleting a station can fail to remove it from supervisord (very limited users impacted) #4898
-
Remote Album Art can't find artwork that exists on Last.FM #5103
-
No metadata for FLAC mount point (Upstream issue) - #5008
- Song playback bar can continue to play despite audio being stopped. #5031