Jonathan Pentecost
Jonathan Pentecost
Cheers, got it. I believe that plex is not adhering to the `relative` time when we send the seek command, since this is implemented by each chromecast application: ``` {"type":"SEEK","requestId":5,"mediaSessionId":1,"currentTime":0,"relativeTime":30,"resumeState":"PLAYBACK_START"}...
Appreciate that, will dig into these logs. Did the seek-to command work?
Cool, thanks for that! I'll take a look into those logs.
I am unable to determine from the logs how `plex` is seeking. One approach we can take is to check to see if this is the `plex` chromecast app (id...
I have merged the changes in. It looks to be working for me, but I don't have Plex to try it out on. Let me know if it doesn't work.
Awesome! Feel free to raise an issue for anything else that doesn't seem to work on Plex :)
I am not sure I follow regarding : ```go fmt.Println("state", status.PlayerState, "status.IdleReason", status.IdleReason) ``` I can't see this line in application.go? I am not opposed to removing logrus from most...
Is the stream coming from go-chromecast or from an external service? Do you have a code snippet of where you have the debug statement being printed? I don't know why...
Hello @oliverpool, Oh cool, I'll check that out, thanks! What did you have in mind for a more robust client/library? I have been wanting to re-write the current implementation of...
I can see having a more robust library for the chromecast being useful, I am happy to attempt to make this library more robust, or did you want to do...