phawind111 / google-cast-sdk

Automatically exported from code.google.com/p/google-cast-sdk
0 stars 0 forks source link

GCKMediaStatus's queueItemCount and currentItemId are 0 after first item in queue plays #677

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Load a list of items with queueLoadItems.
2. Observe mediaControlChannelDidUpdateQueue is called.
3. Use GCKMediaControlChannel to get GCKMediaStatus.
4. Verify status's queueItemCount and currentItemId shows the number of loaded 
items and a current ID.
5. Wait for the first queue item to finish playing.
6. When mediaControlChannelDidUpdateQueue is called again, check the 
queueItemCount and currentItemId

What is the expected output? What do you see instead?
Expected: The queue item count should match the initial number of loaded items. 
The currentItemId should update to the next item's ID.
Actual: The queueItemCount and currentItemId are 0. The queue continues to play.

What version of the product are you using? On what operating system?
iOS Cast SDK v2.10.0
Custom receiver with SDK version 2.0.0, media player 1.0.0
Android Play Services Cast version v8.1.0, CCL v2.5.1

Please provide any additional information below.

The Android sender and receiver still show the correct queue size and current 
item ID. The receiver continues playing items in the queue.

Original issue reported on code.google.com by ca...@doubleencore.com on 23 Oct 2015 at 10:59

GoogleCodeExporter commented 8 years ago
We're looking into it.

Original comment by jonathan...@google.com on 26 Oct 2015 at 10:55

GoogleCodeExporter commented 8 years ago
What Chromecast firmware version are you using?
Can you reproduce the issue, capture the logs, and provide them here as a text 
file?

Original comment by jonathan...@google.com on 27 Oct 2015 at 9:09

GoogleCodeExporter commented 8 years ago
Firmware version: 1.16.44433

Log is attached.

Original comment by ca...@doubleencore.com on 28 Oct 2015 at 12:50

Attachments:

GoogleCodeExporter commented 8 years ago
Hi, mediaControlChannelDidUpdateQueue would not be called unless the queue is 
updated. If the item just finishes and moves to next one, it is not considered 
to be that the queue has updated. In this scenario, I think you should only get 
the callback when the queue finishes, and that is when currentItemId and 
queueItemCount would both be 0.
But I would appreciate if you could also attach logs from iOS side.

Original comment by jieh...@google.com on 29 Oct 2015 at 11:44

GoogleCodeExporter commented 8 years ago
On iOS the queue updated callback is triggered after the first item in the 
queue completes playing. After that it is not triggered between the remainder 
of the items. Please see the attached log.

On Android the queue updated callback is triggered after every item in the 
queue completes.

Original comment by ca...@doubleencore.com on 30 Oct 2015 at 4:55

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by jonathan...@google.com on 2 Nov 2015 at 7:33

GoogleCodeExporter commented 8 years ago
Hi Caleb, can you use the same repro steps and provide the equivalent receiver 
logs for Android (which should work correctly)?

Original comment by jonathan...@google.com on 5 Dec 2015 at 12:56

GoogleCodeExporter commented 8 years ago
We were not able to reproduce this with the default player.  There may be 
something that your custom receiver application does to trigger this, i.e. 
forcing a media status to be sent when it is not expected.

Original comment by jonathan...@google.com on 15 Dec 2015 at 1:00