~WORKAROUND!~Mixxx Not pushing Metadata to Shoutcast 1.x+2.x server (windows 10)

[unknownpedestrian]

Bug Description

When streaming to the latest version of shoutcast (selfhost)

when using mixxx as a source the title information is not being sent to the server, it updates the title as follows:
Push to YP: " "
for the song name every time the song changes

I've tried toggling UTF-8 and OGG dynamic updating and no dice at all

it seems all my DJs that use mixxx are having this issue where the title field in the shoutcast server is just left blank! and when I go to try and display the metadata manually it just returns a blank page! HELP!

UPDATE:
I found out this issue is related to special characters being in the password!! (Ex. $#%@_-+)
once i removed the special characters from the password titles started pushing through like normal!

still a bug with mixxx that is a nice work around for now!~

Version

2.4.1, 2.5.0

OS

Windows 10, windows 11, Ubuntu 22.04

[acolombier]

@daschuer I'm wondering if this is something that the libshoutcast update could fix.

[daschuer]

I am not aware that something has changed, but it is worth a try.

[daschuer]

I have pushed a new build. It will appear here:
https://github.com/mixxxdj/mixxx/actions/runs/10980988560?pr=4723
You need to login to GitHub to see the windows installer link at the bottom of the page. Please check.

[daschuer]

It is probably here:

mixxx/lib/libshout-idjc/src/proto_icy.c

Line 43 in 067792b

if (shout_queue_printf(self, "%s\n", self->password))

In this place, user and password is base64 encoded:

mixxx/lib/libshout-idjc/src/proto_http.c

Line 51 in 067792b

out = _shout_util_base64_encode(in);

This could be a reason why steaming work, but not metadata.

@unknownpedestrian
are you able to use Wireshark to compare a working implementation with the special Characters with the Mixxx implementation? I think it should be possible to escape the password appropriate.

There is anyway an issue when sending a plain text password. Is both solved with this branch:
#13285 ?

[CGillen]

I'm looking at this w/ @unknownpedestrian. I haven't found another piece of software that works w/ special chars yet, so we can't compare packets. Actually, the only other free software I could find and get working is PlayIt Live. If you have any other free software suggestions I can try those too.

PlayIt Live did give me a bit of insight though. It allows streaming through SHOUTcast V1 and V2. V1 didn't work with special characters (even with only + since that's technically in the base64 allowed chars list), but it did work without special characters.
V2 on the other hand did work with special characters and not.
I'm still learning about these protocols and how this all works, so I don't know if that's helpful information.

It very well could be our server software too. I don't know if there's another SHOUTcast V1 server software you can point us to, but the official shoutcast server (sc_serv) could be mangling accepting url encoded passwords. I'm seeing plain text passwords as a query string to the server instead of the Authorization header like you linked to.

[acolombier]

There is anyway an issue when sending a plain text password. Is both solved with this branch:
#13285 ?

I believe it is. During my tests, I did try with tracks containing Emojis on an Icecast 2 servers and metadata were sent correctly. I haven't tried with a password containing special character but I'll try that if time allows it.