Bug 13475 - Volume goes to "0" when "muting" is activated on player synced with a player set to fixed volume
: Volume goes to "0" when "muting" is activated on player synced with a player ...
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Sync
: 7.4.0
: PC Other
: P3 normal (vote)
: 7.5.0
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-19 02:15 UTC by Joerg Schwieder
Modified: 2009-10-30 15:44 UTC (History)
2 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Schwieder 2009-08-19 02:15:51 UTC
When you sync two players and one of them has it's volume set to a fixed 100% level, when you mute the players the one without a fixed volume will get it's volume set to "0" instead of "-volume"
Comment 1 Joerg Schwieder 2009-08-19 06:54:52 UTC
Additional Info:
No longer sure whether it's limited to syncing with a player that is set to fixed volume, however, it's very reproducible this way.

But I do also see random occasions with other players. The scenario is always the following:

I have several synced players. Volume is NOT synced, I do however modify it "simultaneously", that is, all players in a sync group receive the same command one after another.
Occasionally a player does go to 100% when being muted or unmuted.
Comment 2 Michael Herger 2009-08-20 07:31:40 UTC
Jörg - could you please add a control.command/queries=debug log from when you're seeing this? Also: what kind of players are you using? Classic/Boom only or some SqueezePlay too?
Comment 3 Joerg Schwieder 2009-08-20 07:36:29 UTC
Here's some stuff I have right now, does this help. I don't know if the issue happened when I did these logs, but they show what I do. I can't fully reproduce it.

It seems to happen more often when the server is busy (e.g. sending cache data to iPeng, or while browsing things) but that'S just an impression.

Plus it makes logging a bit more difficult :-)

All my tests wehere I saw this were indeed with a Classic and a Boom, I'm not completely sure but it could be that it was always the Classic going to "0".

[{"clientId":null,"id":"35","channel":"/slim/request","successful":true}]
[09-08-18 23:57:17.0261] Slim::Web::Cometd::handler (143) Cometd request: [
  {
    channel => "/slim/request",
    data => {
          request  => ["00:04:20:10:11:0d", ["mixer", "muting", 0]],
          response => "/bbe8fab6/slim/request",
        },
    id => 34,
  },
]
[09-08-18 23:57:17.0286] Slim::Web::Cometd::handleRequest (816) Request for /bbe8fab6/slim/request / 34 is not async
[09-08-18 23:57:17.0301] Slim::Web::Cometd::Manager::deliver_events (215) Sending event on channel /bbe8fab6/slim/request to bbe8fab6
[09-08-18 23:57:17.0326] Slim::Web::Cometd::Manager::deliver_events (229) Delivering events to bbe8fab6:
[
  {
    channel => "/bbe8fab6/slim/request",
    data => {},
    ext => { priority => "" },
    id => 34,
  },
]
[09-08-18 23:57:17.0342] Slim::Web::Cometd::sendHTTPResponse (669) Sending Cometd chunk:
[{"data":{},"id":"34","channel":"/bbe8fab6/slim/request","ext":{"priority":""}}]
[09-08-18 23:57:17.0369] Slim::Web::Cometd::sendHTTPResponse (662) Sending Cometd Response:
HTTP/1.1 200 OK
Cache-Control: no-cache
Connection: keep-alive
Pragma: no-cache
Content-Length: 73
Content-Type: application/json
Expires: -1

[{"clientId":null,"id":"34","channel":"/slim/request","successful":true}]
[09-08-18 23:57:17.0500] Slim::Web::Cometd::handler (143) Cometd request: [
  {
    channel => "/slim/request",
    data => {
          request  => ["00:04:20:10:11:0d", ["mixer", "muting", 0]],
          response => "/bbe8fab6/slim/request",
        },
    id => 36,
  },
]
[09-08-18 23:57:17.0523] Slim::Web::Cometd::handleRequest (816) Request for /bbe8fab6/slim/request / 36 is not async
[09-08-18 23:57:17.0537] Slim::Web::Cometd::Manager::deliver_events (215) Sending event on channel /bbe8fab6/slim/request to bbe8fab6
[09-08-18 23:57:17.0564] Slim::Web::Cometd::Manager::deliver_events (229) Delivering events to bbe8fab6:
[
  {
    channel => "/bbe8fab6/slim/request",
    data => {},
    ext => { priority => "" },
    id => 36,
  },
]
[09-08-18 23:57:17.0581] Slim::Web::Cometd::sendHTTPResponse (669) Sending Cometd chunk:
[{"data":{},"id":"36","channel":"/bbe8fab6/slim/request","ext":{"priority":""}}]
[09-08-18 23:57:17.0606] Slim::Web::Cometd::sendHTTPResponse (662) Sending Cometd Response:
HTTP/1.1 200 OK
Cache-Control: no-cache
Connection: keep-alive
Pragma: no-cache
Content-Length: 73
Content-Type: application/json
Expires: -1

[{"clientId":null,"id":"36","channel":"/slim/request","successful":true}]
[09-08-18 23:57:17.0745] Slim::Web::Cometd::handler (143) Cometd request: [
  {
    channel => "/slim/request",
    data => {
          request  => ["00:04:20:10:11:0d", ["mixer", "muting", "?"]],
          response => "/bbe8fab6/slim/request",
        },
    id => 37,
  },
]
[09-08-18 23:57:17.0768] Slim::Web::Cometd::handleRequest (816) Request for /bbe8fab6/slim/request / 37 is not async
[09-08-18 23:57:17.0783] Slim::Web::Cometd::Manager::deliver_events (215) Sending event on channel /bbe8fab6/slim/request to bbe8fab6
[09-08-18 23:57:17.0810] Slim::Web::Cometd::Manager::deliver_events (229) Delivering events to bbe8fab6:
[
  {
    channel => "/bbe8fab6/slim/request",
    data => { _muting => 0 },
    ext => { priority => "" },
    id => 37,
  },
]
[09-08-18 23:57:17.0826] Slim::Web::Cometd::sendHTTPResponse (669) Sending Cometd chunk:
[{"data":{"_muting":"0"},"id":"37","channel":"/bbe8fab6/slim/request","ext":{"priority":""}}]
[09-08-18 23:57:17.0851] Slim::Web::Cometd::sendHTTPResponse (662) Sending Cometd Response:
HTTP/1.1 200 OK
Cache-Control: no-cache
Connection: keep-alive
Pragma: no-cache
Content-Length: 73
Content-Type: application/json
Expires: -1

[{"clientId":null,"id":"37","channel":"/slim/request","successful":true}]
[09-08-18 23:57:17.4832] Slim::Web::Cometd::requestCallback (837) requestCallback got results for /bbe8fab6/slim/playerstatus/00:04:20:10:11:0d / 7
[09-08-18 23:57:17.4847] Slim::Web::Cometd::Manager::deliver_events (215) Sending event on channel /bbe8fab6/slim/playerstatus/00:04:20:10:11:0d to bbe8fab6
[09-08-18 23:57:17.4924] Slim::Web::Cometd::Manager::deliver_events (229) Delivering events to bbe8fab6:
[
  {
    channel => "/bbe8fab6/slim/playerstatus/00:04:20:10:11:0d",
    data => {
          can_seek => 1,
          current_title => undef,
          duration => "168.071",
          "mixer volume" => 0,
          mode => "stop",
          player_connected => 1,
          player_ip => "192.168.0.113:33028",
          player_name => "Transporter",
          "playlist mode" => "disabled",
          "playlist repeat" => 0,
          "playlist shuffle" => 0,
          playlist_cur_index => 39,
          playlist_loop => [
                {
                  # tied Tie::IxHash
                  album => "Dancing The Whole Way Home",
                  artist => "Miss Li",
                  artwork_url => "http://images.napster.com/mp3s/2434/resources/185/729/files/185729917.jpg",
                  id => 8910,
                  "playlist index" => 39,
                  remote => 1,
                  title => "Bourgeois Shangri-La",
                  url => "napster://track:28287866.wma",
                },
              ],
          playlist_timestamp => "1250548013.71032",
          playlist_tracks => 40,
          power => 1,
          rate => 1,
          remote => 1,
          signalstrength => 0,
          "time" => "168.071",
        },
    ext => { priority => "" },
    id => 7,
  },
]
Comment 4 Joerg Schwieder 2009-08-20 07:37:27 UTC
Oh, and the "mixer muting ?" query is in  there for debugging purposes only, I since removed it and still saw the issue.
Comment 5 Ben Klaas 2009-08-26 07:52:40 UTC
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Comment 6 Michael Herger 2009-09-03 04:03:23 UTC
I'm sorry, but I can't reproduce this issue:

- 2 player synced: Boom & Touch
- Touch set to 100% volume

Whenever I send a mute command, only the player defined in the command will be muted, it's volume going to volume*-1.

QA - can you reproduce?
Comment 7 Joerg Schwieder 2009-09-03 04:07:03 UTC
Meanwhile I also see this without syncing, but mainly with my Touch.
Comment 8 Ross Levine 2009-10-07 15:02:18 UTC
(In reply to comment #7)
> Meanwhile I also see this without syncing, but mainly with my Touch.

How do you see this with out syncing?
Comment 9 James Richardson 2009-10-30 15:44:03 UTC
Joerg:

QA is unable to replicate this with 7.5 and the latest firmware for SP devices.  Please re-test with that version.  If you are still able to replicate the issue, attach a new log and reopen the bug.