Timeline for Cast devices freeze when casting audio streams
Current License: CC BY-SA 3.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 27, 2017 at 7:38 | vote | accept | Roy Solberg | ||
Mar 23, 2017 at 20:48 | comment | added | Roy Solberg | @AliNaddaf I found a solution/workaround as described below. The issue issuetracker.google.com/issues/36191282 is marked as fixed, but I'm not sure if it is directly related and/or if the fix has been released to the Cast firmware versions I mention here..? | |
Mar 23, 2017 at 20:45 | answer | added | Roy Solberg | timeline score: 3 | |
Mar 21, 2017 at 15:49 | comment | added | Ali Naddaf | Nothing jumps at me | |
Mar 21, 2017 at 14:05 | comment | added | Roy Solberg | Thank you, @AliNaddaf. I'll do that. I'm just trying to get verified that the server software is up to date and should be able to work and that everything is set up as it should be. However, I have now added more header and body info. You don't happen see anything suspect, do you? | |
Mar 21, 2017 at 14:01 | history | edited | Roy Solberg | CC BY-SA 3.0 |
Added headers and body of requests.
|
Mar 20, 2017 at 21:11 | comment | added | Ali Naddaf | I suggests you open a ticket on our sdk issue tracker and include a sample stream that can produce the result. | |
Mar 20, 2017 at 20:04 | comment | added | Roy Solberg | Actually, with a styled media receiver I only get the log statement "[cast.receiver.MediaManager] Load metadata error: [object Object] cast_receiver.js:67". According to the network tab in Chrome dev tools there's only one network call towards the stream and it returns HTTP 200. The receiver does not play anything, but it does not freeze and it still lets me disconnect. | |
Mar 20, 2017 at 15:42 | comment | added | Ali Naddaf | Does that happen with a Styled or the Default receiver, too? | |
Mar 20, 2017 at 11:17 | history | edited | Roy Solberg |
edited tags
|
|
Mar 20, 2017 at 10:59 | history | asked | Roy Solberg | CC BY-SA 3.0 |