Skip to content
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

Broadcast Disconnect #8459

Closed
mixxxbot opened this issue Aug 22, 2022 · 20 comments
Closed

Broadcast Disconnect #8459

mixxxbot opened this issue Aug 22, 2022 · 20 comments

Comments

@mixxxbot
Copy link
Collaborator

Reported by: jharveysxm
Date: 2016-01-28T15:06:30Z
Status: Expired
Importance: High
Launchpad Issue: lp1539119
Tags: broadcast
Attachments: mixxx.log.1


While broadcast Mixxx disconnects... and when you try to reconnected it says "Mixxx successfully connect to server", but it is not connected. Go to your stream server and you see no client is connected, try it connect again and nothing happens, no status messages as if to say "already connected", "successfully connected", "fail to connect", or "disconnected"

The only wait to back broadcasting again is to close and reopen MIxxx and reconnect then it works.

@mixxxbot
Copy link
Collaborator Author

Commented by: jharveysxm
Date: 2016-01-28T15:08:12Z


Windows 10 64bit Intel core 3 with 4 gig of memory

@mixxxbot
Copy link
Collaborator Author

Commented by: jharveysxm
Date: 2016-01-28T15:08:51Z


sorry for Mixxx 2.0 64 bit

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2016-01-28T15:20:15Z


please post the mixxx.log file from a faulty run.

%APPDATA%\Mixxx\mixxx.log

If it is not your recent run, it may has a suffix like mixxx.log.5

@mixxxbot
Copy link
Collaborator Author

Commented by: jharveysxm
Date: 2016-01-28T23:29:48Z
Attachments: mixxx.log.1


See Attached

@mixxxbot
Copy link
Collaborator Author

Commented by: jharveysxm
Date: 2016-01-28T23:30:58Z


Not sure it is correct one, I had to restart to do my show

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2016-01-29T06:55:01Z


Thank you, it was the right one

...
Debug [EngineShoutcast 1]: shout_queuelen 364 
...
Debug [EngineShoutcast 1]: shout_queuelen 303031 
Debug [EngineShoutcast 1]: EngineShoutcast::write() header error: -4 Socket error 
...
Debug [EngineShoutcast 1]: EngineShoutcast::write() header error: -4 Socket error 
Debug [EngineShoutcast 1]: EngineShoutcast::processDisconnect() 
...
Debug [EngineShoutcast 1]: Connection pending. Waiting... 
Debug [EngineShoutcast 1]: Streaming server made error: No error 
Debug [EngineShoutcast 1]: EngineShoutcast::processConnect() socket error. Is socket already in use? 

It looks like Mixxx does not release the socket after the socket error

@mixxxbot
Copy link
Collaborator Author

Commented by: jharveysxm
Date: 2016-02-23T13:48:36Z


Will their be resolution to this soon? I really need it Guys

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2016-02-24T22:35:33Z


I am afraid not, sorry.
I have just digged through the Mixxx and the libshout 2.4.0 code, but I have not found anything suspicious.
Unfortunately I cannot reproduce this issue on Windows and I have no access to a windows machine to test this.
We need a Windows based contributor, who is able to reproduce the issue.

@mixxxbot
Copy link
Collaborator Author

Commented by: darrenitu
Date: 2016-03-08T10:50:13Z


Hi- yes this is what happens to us- see my report https://bugs.launchpad.net/mixxx/+bug/1552312

Identical! It looks like a buffer overload due to a conflict with the latest update of Windows 10 and Mixxx V2. We are about to go 24/7 and were planning on using Mixxxx so please please please advise on a fix!!!

(64bit, 320kbps streaming, recording shows, 3 different laptops and configs but all W10)

@mixxxbot
Copy link
Collaborator Author

Commented by: jharveysxm
Date: 2016-04-19T23:28:37Z


This is also true for Linux. I changed all my systems from Windows and now I am using Linux Mint and The results are the same. If Mixxx disconnects while streaming, when you try to reconnect it prompts that you were reconnected, but when you check your streaming server you realize that Mixxx never reconnected and no matter how much times you try to reconnect from there on, it will never connect, until you restart Mixxx.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2016-04-20T05:46:14Z


Hi Jay,

please provide the mixxx.log file from a run, where reconnecting has failed.
you will find it at ~/.mixxx/mixxx.log.x where ix is the number of Mixxx runs since then.

I have also prepared a Mixxx 2.1 alpha version that has additional debug messages.
https://launchpad.net/~nschloe/+archive/ubuntu/mixxx-nightly

If the issue still happens with this build, please post the mixxx.log as well.

Thank you.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2016-04-20T05:47:40Z


By the way: we have currently issues with our build server so we cannot provide a Windows 2.1 build.
If one can provide one, it would be great.

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2016-07-04T22:03:13Z


We have a new alpha build now:
http://downloads.mixxx.org/builds/master/release/mixxx-2.1.0-alpha-pre-master-git5868-release-x64.exe

@mixxxbot
Copy link
Collaborator Author

Commented by: sblaisot
Date: 2016-07-05T17:22:46Z


the alpha build Daniel linked to has a bug and doesn't install in the right place. please use this new one instead: http://downloads.mixxx.org/builds/master/release/mixxx-2.1.0-alpha-pre-master-git5869-release-x64.exe

@mixxxbot
Copy link
Collaborator Author

Commented by: gedmarc
Date: 2017-07-30T20:11:25Z


Hi There,

Is there any update? I'll be installing the 2.1 alpha now with pretty much the same environment.
Will post updates

@mixxxbot
Copy link
Collaborator Author

Commented by: jharveysxm
Date: 2017-07-30T20:55:19Z


on my last test with 2.1 I no such issue, but it never disconnected either

@mixxxbot
Copy link
Collaborator Author

Commented by: daschuer
Date: 2017-07-31T05:20:40Z


Does this mean you have an other issue now?
Please describe it in a now bug. Thank you.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2018-09-21T19:02:42Z


Any luck with 2.1.4 or 2.2.0 beta?

@mixxxbot
Copy link
Collaborator Author

Commented by: janitor
Date: 2018-11-21T04:17:32Z


[Expired for Mixxx because there has been no activity for 60 days.]

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Expired.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant