Perform a wireshark trace on working Mixxx and search HTTP POST and GET packets for the password. I know the track metadata follows password. Work out the syntax.
Use curl -v --header to inject legal packets to shoutcast.
I will look for a Mixxx flow chart. I will have a go at reading the source code. My thoughts are:
Repeat on working and broken machines:
Which module sends the metadata to libshout? How it does it? Exactly what it is sending?
Is libshout actually getting the metadata? How it does it? Exactly what is it looking for?
Thanks Daniel.
tez@U18042:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
tez@U18042: ~/.mixxx$ head mixxx.log profiler= 0 profiling=0 qt_sqlite_plugin=0 qtkeychain=0 shoutcast=1 shoutcast_ internal= 1 test=False tsan=0 ubsan=0 verbose=1 vinylcontrol=1 wv=0)" is starting...
Debug [Main]: "Mixxx" "2.3.0-alpha-pre" "(git 2.2 r6739; built on: Feb 28 2019 @ 13:48:58; flags: asan=0 battery=1 buildtime=1 bulk=1 color=0 coreaudio=0 faad=0 ffmpeg=0 hid=1 hss1394=0 lilv=1 localecompare=1 macappstore=0 mad=1 mediafoundation=0 modplug=0 opengles=0 optimize=native opus=1 perftools=0 perftools_
Debug [Main]: Compile time library versions:
Debug [Main]: Qt: 5.9.5
Debug [Main]: libshout: 2.4.1
No metadata is being sent to Shoutcast.
My tasks:
Perform a wireshark trace on working Mixxx and search HTTP POST and GET packets for the password. I know the track metadata follows password. Work out the syntax.
Use curl -v --header to inject legal packets to shoutcast.
I will look for a Mixxx flow chart. I will have a go at reading the source code. My thoughts are:
Repeat on working and broken machines:
Which module sends the metadata to libshout? How it does it? Exactly what it is sending?
Is libshout actually getting the metadata? How it does it? Exactly what is it looking for?
Find the mismatch!