Add shoutcast status indicator to skins.

Bug #1101329 reported by Brook Smith
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Wishlist
Unassigned

Bug Description

It would be nice to have a widget to toggle/enable broadcasting and show the status of the enabled encoder(s). Basic functionality would be as follows.

RED STEADY: Disabled

RED FLASHING: Enabled but disconnected.

YELLOW (FLASHING): Buffer/Connection Issue but still connected.

GREEN: Enabled and functioning properly.

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

Bug #664610 added the relevant control that indicates shoutcast status. See examples in that bug for how to add it to the skins. I'm leaving this bug as a tracking bug for specifically adding broadcasting indicators.

summary: - Wishlist: Broadcast Status/Toggle Widget
+ Add shoutcast status indicator to skins.
Changed in mixxx:
status: New → Confirmed
importance: Undecided → Wishlist
jus (jus)
Changed in mixxx:
milestone: none → 1.12.0
assignee: nobody → jus (jus)
status: Confirmed → In Progress
RJ Skerry-Ryan (rryan)
tags: added: shoutcast
removed: wishlist
Revision history for this message
Daniel Schürmann (daschuer) wrote :

https://github.com/mixxxdj/mixxx/pull/665

contains a status button for Shade. It has:
* UNCONNECTED
* CONNECTING
* CONNECTED
* FAILURE

It does not include the buffering warning. Currently it will flush the buffer and reconnect after 10 s of 192 kbit/s mp3.
Buffering is a "normal" condition using a http protocol. So what should be the threshold for a warning and what is the action the user can take?
An other issue is that there a some weak clients out there, that do not reconnect if their own buffer is consumed or are not able to sync the sample rate variations. So it is hard to predict which buffer level is critical.

For now, I would go without a buffering state.

Any ideas?

jus (jus)
Changed in mixxx:
assignee: jus (jus) → nobody
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

I believe this is fixed now.

Changed in mixxx:
status: In Progress → Fix Released
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/6858

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

Related blueprints

Remote bug watches

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