Opened 12 years ago

Closed 3 years ago

#11453 closed Bug Report - General (Trac EOL)

Frontend Services API doesn't playback recording when frontend isn't in "Watch Recordings"

Reported by: thomas@… Owned by: Bill Meek
Priority: minor Milestone: needs_triage
Component: MythTV - Services API - Frontend Version: 0.26-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description

When using the frontend services API to start playback of a recording on a frontend, the frontend will not start playback unless it is already on the "Watch Recordings" screen.

What is expected to happen: When using the PlayRecording? service on the frontend, it should start playback of the recording regardless of what menu the frontend is currently displaying.

What actually happens: If the frontend is displaying a screen other than "Watch Recordings" the frontend will switch to the "Watch Recordings" screen and stay there without playing back the recording.

Extra Notes: If after reproducing this bug, you immediately send another "PlayRecording?" for a different recording (after the frontend has already switched to the "Watch Recordings" screen), it will play the recording that was initially requested. When exiting the initially requested recording, it well then start playback of the second requested recording.

This appears to only be an issue with recordings. Using PlayVideo? when the frontend is on any screen works as expected.

Attachments (1)

frontendversion (824 bytes) - added by thomas@… 12 years ago.
frontend version information

Download all attachments as: .zip

Change History (7)

Changed 12 years ago by thomas@…

Attachment: frontendversion added

frontend version information

comment:1 Changed 12 years ago by Thomas Mashos <thomas@…>

Per conversation with sphery, I also tested it from the main menu. It fails in exactly the same way (so it's not related to bug #10407 )

comment:2 Changed 11 years ago by cpinkham

Component: MythTV - GeneralMythTV - Services API - Frontend

comment:3 Changed 10 years ago by pkendall64@…

I have the same problem and I have worked around it by first sending a SendAction? command with the action set to "TV Recording Playback". My application first calls GetStatus? and only send the action if it's not already in the recording screen "playbackbox". After sending the action I wait 1 second before starting the recording playback. I'm not sure if the 1 second wait depends on the number of recordings or not, but it works for me.

Still it would be good to have this problem fixed so the workaround is not required.

comment:4 in reply to:  3 Changed 6 years ago by Justin Randall

Replying to pkendall64@…:

I have the same problem and I have worked around it by first sending a SendAction? command with the action set to "TV Recording Playback". My application first calls GetStatus? and only send the action if it's not already in the recording screen "playbackbox". After sending the action I wait 1 second before starting the recording playback. I'm not sure if the 1 second wait depends on the number of recordings or not, but it works for me.

Still it would be good to have this problem fixed so the workaround is not required.

I know this issue is relatively ancient, but I had the exact same issue and implemented a similar "workaround" although after digging into it I believe that the intention of SendAction? is not necessarily to change the page displayed on the frontend, but rather to change the context of subsequent commands being sent. It would be great if SendAction? supported the old "jump" commands like the NetworkControl? plain text interface does.

comment:5 Changed 4 years ago by Stuart Auchterlonie

Milestone: unknownneeds_triage
Owner: set to Bill Meek
Status: newassigned

Bill, can you review please?

comment:6 Changed 3 years ago by Stuart Auchterlonie

Resolution: Trac EOL
Status: assignedclosed

We have moved all bug tracking to github [1]

If you continue to have this issue, please open a new issue at github, referencing this ticket.

[1] - https://github.com/MythTV/mythtv/issues

Note: See TracTickets for help on using tickets.