New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Known Issue: Blank metadata when first connecting as a DJ using BUTT, etc. #867
Comments
hey there @CodeSteele , I am using "butt" for live streaming, is this the reason the metadata info shown below isn't displayed either? |
@macbroadcast as far as I know, the metadata should be good after a single song plays. Does it not correct after the first song completes? If not, likely a different issue (and I would suggest using Mixxx for now if you need that functionality, being as it may likely be BUTT). |
it does not change @CodeSteele so its useless for live DJs, what should i do ? Open an issue ?, buster seems always busy with less important stuff 😄 |
Thanks for your reply @CodeSteele , this works just with butt on ubuntu for me, will check settings on osx again and checking Mixx aswell!, but where is the other information in BUTT for ? Description, URL Genre, IRC |
Yeah not sure if BUTT supports that, you may have to reach out to the BUTT devs -- I can't find anything in their docs. |
its seems its not capturing the information from butt on OSX https://stream.iradio.guru/public/iradio and works fine on ubuntu any idea ? @CodeSteele @SlvrEagle23 |
I'm having same problem with BUTT on live DJ streams, no metadata updating at all. |
I am using butt for a long time, but never cared much about the metadata, I informed the author about the issue, because all my music stuff is of course on mac and therefore i need a working solution, as well, but its mostly just a question of time. But I don't know what your problem with traktor is?https://traktorbible.com/en/t2_broadcasting_part_1.aspx#step2 |
@macbroadcast as far as AzuraCast is concerned, it won't care if you're streaming from OSX or Ubuntu. If BUTT acts different between the two platforms I'd be really tempted to blame BUTT for that (it's not something like a browser issue where I have to worry about how Safari for OSX renders things differently, it's just a TCP protocol). Sadly right now neither of us have the ability to reproduce issues on OSX (complain to Apple about their EULA and vendor lock-in that doesn't allow us to spin up OSX VMs for testing, we do a lot of our testing in VMs instead of having a ton of physical machines sitting around, which gets expensive fast). Considering how slow BUTT development seems I should probably spend some time seeing if I can find a replacement, it has been a pain in our butt (heh) for awhile at this point due to a lot of odd behaviors/bugs. As far as this bug issue is concerned, it's about delays internal to LiquidSoap and AzuraCast's integrations that make metadata take awhile to populate on first song play -- it shouldn't entirely prevent metadata from displaying at all, but bug appears present on all players where as general random metadata issues seem to plague BUTT regardless. |
OK, no idea was it the cause but I now run latest AzuraCast in a docker and BUTT metadata works just fine sending from windows 10. Should know later if it works on OSX |
I've tested this on macOS High Sierra 10.13.6 (17G65) with Butt and Mixx and could only reproduce this bug with Butt. Also for me this Bug consistently occurs when starting Butt for the first time and then connecting. Butt sets the metadata to I've looked at the station logs when this happens and there I found this:
The problem most likely stems from an illegal char in the string that Butt sends to AzuraCast and that the |
You can use Liquidsoap to capture the meta and change it if you like. The way I had it on aerial was to do the following - feel free to adapt it for Azura:
Some ogg encoders send a dead hunk at the beginning of a connection and this results in bad metadata being sent through LS and Icecast. Back in 2012 when I wrote this, it was to stop IceCast from segfaulting and crashing the station. It's a simple fix that just sits in the script out of the way and fixes any bad meta. Call it after the DJ live functions on the LS script. with : |
It appears that in the absence of any metadata, this just sets a placeholder value with the station name or other text. While we could implement this into the LS config, I'd prefer something a little more interactive, like triggering a metadata update upon successful DJ authentication that actually includes the DJ's name in the metadata. The LS documentation suggests this is possible via a Telnet connection, which I may take advantage of. |
While we can't do anything on the AzuraCast end about clients that connect to stream not sending an immediate metadata update, we can trigger one on our end when a DJ successfully authenticates, which overrides the existing metadata to show the DJ's "display name" and the station name. That's exactly what the latest change accomplishes; it will flush the metadata upon a successful DJ connection, ensuring that your listeners are aware of the presence of a live DJ in the interstitial time between their connection and the first metadata push. Hopefully this helps mitigate the issue! |
Reopening after having reverted the previous quick fix, as it causes the DJ name to show up in the song playback timeline and other places. |
Hi everyone, do you have an update on this? We have a perhaps related issue where Azuracast's JSON API shows inconsistent data after a live DJ connects via Butt. What I fail to see if it's a) an issue with Butt not sending certain data or sending wrong data to Azuracast or b) Azuracast not handling connection events properly (although I see that a) and b) are related). Our problem is that Azurcast seems to "remember" metadata accross different Butt sessions (carried out by different Butt clients). Thanks |
Hello, i am having this problem with the latest version of Azuracast on Docker (Debian 10 KVM). I am streaming from Sam Broadcaster to Azuracast (SHOUTcast DNAS/posix(linux x64) v2.5.5.733 ) The streaming happends on a "LAN" network so there is no firewall, etc. The stream is playing but on Azura web interface it shows it offline and from time to time it goes again online for 2-3 seconds. Is there a way to fix this issue? Thank you, |
Hello again, i have figured it out: the problem was that i had 2 mount points. I have deleted the relay mount point and now it display the station online and the song tile and artist are being displayed. Sorry for the comment above. Thank you! |
If anyone interested a new verison of Butt is available (v0.1.19). I could only test it on Windows, the Mac version would not start for me due to some error. I see no difference compared to v0.1.18 in terms of the issue at hand. For me the behavior is deterministic:
(Although it's deterministic behavior, it's not really what we want. For us it would be great if it was configurable whether or not Butt automatically sends metadata or only "on demand".) |
I know this is old post, but this is the only clue that got me to fix same "Stream Offline". The clue is match streaming software with relay name! |
Apparently this is caused by LiquidSoap not firing the metadata change event that we expect to be fired.
Going to see what I can do about this...
The text was updated successfully, but these errors were encountered: