If a connection to a streaming server fails, the [Shoutcast],status CO remains in wrong status, potentially displaying a misleading icon

Bug #1520768 reported by jus
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Low
Unassigned

Bug Description

Latest 2.0.0-rc1

The following PR adds a status indicator for the live broadcasting feature:
https://github.com/mixxxdj/mixxx/pull/665/files
https://bugs.launchpad.net/mixxx/+bug/1101329/comments/2

If you try to connect to a streaming server and the connection failed, the
[Shoutcast],status
control remains at the ``failure`` status, while it should return to the ``unconnected`` status when clicking away the obligatory modal window.
This can be observed best with the Shade skin, where you always have the ``failure``icon below the clock, after the first unsuccessful attempt to start live broadcasting.

I`d expect the following:
* Connect to the streaming server
* Error occurs -> ``[Shoutcast],status`` changes to ``failure`` and the password/connection hint modal window appears.
* Click away modal window -> ``[Shoutcast],status`` resets to default ``unconnected``

Tags: broadcast
Revision history for this message
Daniel Schürmann (daschuer) wrote :

This behaviour is by design. I think it is correct to show the ``failure``icon until you connect successful live broadcasting works as desired. The configuration / connection was proven as wrong / failure. Keeping the failure until proving the opposite seems to be not bad.

IMHO with the proposed behaviour the failure icon is redundant, since the pop up is displayed at the same time anyway.

Revision history for this message
jus (jus) wrote :

The attempt to connect was not successful -> We notify the user about the failure (modal + icon), and about the possible reason (modal). User is notified that action has to be taken, and confirms modal box. We are back in the unconnected state. End of interaction.

Why bother with an failure message afterwards, even if its an icon? This would be exclusive to other error notifications in the application.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

(in mixxx 2.0)

Changed in mixxx:
status: New → Incomplete
milestone: none → 2.0.0
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

BTW I agree with Jus in post 2 -- for reliability Mixxx should behave like a state machine from a user's mental model perspective.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Nevermind -- the bug was filed after the PR was merged :)

Changed in mixxx:
status: Incomplete → Confirmed
milestone: 2.0.0 → 2.0.1
Revision history for this message
Be (be.ing) wrote :
Changed in mixxx:
milestone: 2.0.1 → none
Revision history for this message
Daniel Schürmann (daschuer) wrote :

We can consider this bug again after it is merged.
The state icon should work as expected, but I do not agree with the original bug as outlined in #1.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Is this still an issue? PR #1300 has merged.

Changed in mixxx:
importance: Undecided → Low
tags: added: broadcast
removed: shoutcast
Revision history for this message
ronso0 (ronso0) wrote (last edit ):
Changed in mixxx:
status: Confirmed → Fix Released
milestone: none → 2.3.2
Changed in mixxx:
milestone: 2.3.2 → 2.3.0
Revision history for this message
Swiftb0y (swiftb0y) wrote :

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

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.