-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
libshout-1:2.4.2-1 breaks live broadcasting mixxx 2.2.1 #9681
Comments
Commented by: daschuer What exactly happens when you cannot connect. |
Commented by: 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. xiph/Icecast-libshout#14 That's why I opened this issue also on there. xiph/Icecast-libshout#15
|
Commented by: remyjo UPDATE: This issue on libshout GitHub got moved to their GitLab page: https://gitlab.xiph.org/xiph/icecast-libshout/issues/2308 |
Commented by: remyjo UPDATE: The problem is fixed! I just build the GitLab version and it works, no problems anymore. |
Commented by: daschuer But what does this mean for Mixxx and Linux users still using the faulty version? So I think this bug is still in progress. |
Commented by: 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. |
Commented by: uklotzde 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? |
Commented by: uklotzde Ok, so icecast is just the server? I only see libshout-devel 2.2.2. |
Commented by: daschuer The patch is not released yet: |
Commented by: 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 :) |
Commented by: daschuer Unfortunately the fix has not managed to go to 2.4.3 see: |
Commented by: 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. |
Commented by: daschuer Unfortunately there is no binary available for 2.2.4 yet. I think the easiest way is to downgrade libshout: If you are not afraid for installing a lot of dev packages,you can build your own 2.2.4 alpha. If you are interested in bleeding edge features and like to help us towards the 2.3 release, |
Commented by: hackerb9 Thank you, @daschuer! It seems to be working. I helped a DJ install the following on his Debian laptop:
and finally Mixxx works again for going Live! Hurray! Just in time for his show tonight. |
Issue closed with status Fix Released. |
Reported by: remyjo
Date: 2019-06-18T12:00:42Z
Status: Fix Released
Importance: High
Launchpad Issue: lp1833225
Tags: broadcast
Attachments: mixxx.log
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/
The text was updated successfully, but these errors were encountered: