libshout-1:2.4.2-1 breaks live broadcasting mixxx 2.2.1

[Remy]

Hey, libshout version 1:2.4.2-1 seems to break the broadcasting. I can't connect to the server at all.

When I downgrade to libshout-1:2.4.1-4 the broadcast works again.

I'm using Manjaro stable, this uses the latest 1:2.4.2-1 version.

I'm not sure if this a problem on Mixxx's side or on the libshout side.

More info on this forum post https://www.mixxx.org/forums/viewtopic.php?f=3&t=12781

Thanks!

UPDATE: I also tested the newest libshout version 2.4.3 from git. This version is also broken. https://aur.archlinux.org/packages/libshout-git/

[Daniel Schürmann (daschuer)]

What exactly happens when you cannot connect.
Does the mixxx.log file looks different?

[Remy (remyjo)]

I pasted the error from the log below. But I don't think it logs the libshout problem. Also the full log is attached.

I noticed there were 2 other people on the libshout github who also had this problem. https://github.com/xiph/Icecast-libshout/issues/14

That's why I opened this issue also on there. https://github.com/xiph/Icecast-libshout/issues/15

Debug [Main]: DlgPrefBroadcast - broadcastEnabledChanged() 1
Debug [ShoutOutput 'Connection 1']: ShoutConnection - run: Starting thread
Debug [ShoutOutput 'Connection 1']: ShoutConnection - processConnect
Debug [ShoutOutput 'Connection 1']: ShoutConnection - "Connection 1" : updating from preferences
Debug [ShoutOutput 'Connection 1']: ShoutConnection - Using server URL: QUrl("//source@178.157.91.98:8000/mount")
Debug [ShoutOutput 'Connection 1']: Successfully loaded encoder library "mp3lame"
Debug [ShoutOutput 'Connection 1']: Loaded libmp3lame version 3.100
Debug [ShoutOutput 'Connection 1']: lame_set_VBR_quality: "present" lame_encode_buffer_interleaved_ieee_float: "present" id3tag_add_v2: "present"
Debug [ShoutOutput 'Connection 1']: CBR mode with bitrate: 160
Warning [ShoutOutput 'Connection 1']: ShoutConnection - 1 / 3 Streaming server failed connect. Failures: "Please retry current operation."
Warning [ShoutOutput 'Connection 1']: ShoutConnection - 2 / 3 Streaming server failed connect. Failures: "Please retry current operation."
Warning [ShoutOutput 'Connection 1']: ShoutConnection - 3 / 3 Streaming server failed connect. Failures: "Please retry current operation."
Debug [ShoutOutput 'Connection 1']: Unloaded libmp3lame
Debug [ShoutOutput 'Connection 1']: ShoutConnection - processConnect() returning false
Warning [ShoutOutput 'Connection 1']: Streaming error: "Please retry current operation.\nPlease check your connection to the Internet and verify that your username and password are correct."

[Remy (remyjo)]

UPDATE: This issue on libshout GitHub got moved to their GitLab page: https://gitlab.xiph.org/xiph/icecast-libshout/issues/2308

[Remy (remyjo)]

UPDATE: The problem is fixed! I just build the GitLab version and it works, no problems anymore.

https://gitlab.xiph.org/xiph/icecast-libshout/

[Daniel Schürmann (daschuer)]

But what does this mean for Mixxx and Linux users still using the faulty version?
Can we detect this and warn the users?
Or should we ship our own libshout build.
We can then also use the aac enabled version.

So I think this bug is still in progress.

[Remy (remyjo)]

It really depends on the distribution. Ubuntu and Debian based distributions still ship with libshout 2.4.1 and that version doesn't have the bug.

Arch based distributions ship with 2.4.3 which has this bug. So Arch based distribution users, can install the AUR version "libshout-git". This builds it straight from the GitLab source. https://aur.archlinux.org/packages/libshout-git/

I agree that the bug is still in progress until the commit get pushed in the next release.

[Uwe Klotz (uklotzde-deactivatedaccount)]

Fedora is shipping libshoutcast 2.2.2 (all releases). This is what I use as a dependency for the RPM Fusions builds

Should I switch/upgrade to iceast 2.4.4?

[Uwe Klotz (uklotzde-deactivatedaccount)]

Ok, so icecast is just the server? I only see libshout-devel 2.2.2.

[Daniel Schürmann (daschuer)]

The patch is not released yet:
https://gitlab.xiph.org/xiph/icecast-libshout/-/tags
I guess we need at least > 2.4.3

[Daniel Schürmann (daschuer)]

A PR for Mixxx is here:
https://github.com/mixxxdj/mixxx/pull/2040
It reverts libshout to 2.4.1

[Remy (remyjo)]

Thanks for fixing the bug! I just build from source and can confirm it works. I really appreciate the work you guys do, thank you :)

[Daniel Schürmann (daschuer)]

Unfortunately the fix has not managed to go to 2.4.3 see:
https://gitlab.xiph.org/xiph/icecast-libshout/issues/2308
It was finally fixed here https://gitlab.xiph.org/xiph/icecast-libshout/commit/0ac7ed9e84c3871d4427acc1ce59dca5e4af21ef after the 2.4.3 release.

[Daniel Schürmann (daschuer)]

https://github.com/mixxxdj/mixxx/pull/2438 rejects now 2.4.2 and 2.4.3

[Fabzgy (fabzgy)]

I just did the Ubuntu release upgrade from 19.10 to 20.04 this morning and now I am stuck with this bug. Probably there are going to be more people facing this problem.
What is the best way to get out of this situation? Is there an apt repository for the 2.2.4 version?

[Daniel Schürmann (daschuer)]

Unfortunately there is no binary available for 2.2.4 yet.

I think the easiest way is to downgrade libshout:
By luck the eoan dep package can be installed
https://packages.ubuntu.com/eoan/libshout3

If you are not afraid for installing a lot of dev packages,you can build your own 2.2.4 alpha.
https://www.mixxx.org/wiki/doku.php/compiling_on_linux

If you are interested in bleeding edge features and like to help us towards the 2.3 release,
you can install:
https://launchpad.net/~mixxx/+archive/ubuntu/nightlies
But please backup your .mixxx folder first and test all your use cases before going live

[hackerb9 (hackerb9)]

Thank you, @daschuer! It seems to be working. I helped a DJ install the following on his Debian laptop:

    http://ppa.launchpad.net/mixxx/nightlies/ubuntu/pool/main/m/mixxx/mixxx_2.4.0~alpha~pre-0ubuntu1~master~git7378~bionic_amd64.deb

and finally Mixxx works again for going Live! Hurray! Just in time for his show tonight.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/9681