SBE: No episodes listed.

[awaldram]

When connecting to a slave backend you get no episodes listed under the series title.

For films etc that are listed you just get - nothing selecting play HLS and 'Unfortunate, Myth Android front-end has stopped' for 'play recording'

Parsing recordings the slave has from a browser shows all episodes in the .xml
and indeed mythtvgo operates without issue form the same back-end.
Did notice when trying to fix that sometimes when connected to the master back-end a refresh results in two of every episode listed might be related.

In my case this makes the program unusable as my master-backend does not have enough power to handle trans-codes and actually segfaults mythbackend as resources are exhausted , whereas the quad xeon slave woudl be perfect.

Also there are no upcoming recordings listed yet if you go into program guide the upcoming recordings are indicated with green borders so MAF is aware of the upcoming recordings.

[billmeek]

@awaldram, Thanks for the comments. Would you please take a look at issue
#130. I've been testing it for the 1.20.0 release, and believe it's now working.

At this point, we're not doing enhancements (Feature Freeze in MythTV speak.)
So, I'll label this as an enhancement. Although I don't like the 'stopped error'.

If you respond, please add your MythTV version (just 0.2X) would be fine. I'm assuming
you're running on the app's 1.10.1 version.

[awaldram]

@billmeek Thanks for replying, #130 pretty much sums up the issue.
look forward to 1.20 :)
I suspect the Stop may be resolved as if the MAF was delivering wrong/unparsable host-name to the play stream then maybe that’s the segfault.

MythTv .26+fixes (debian) shared SG (inc Streaming) central stores, 2 backends (1 with capture cards), Many frontends.
Some custom mods to mythweb video.php to fix video streaming (passed upstream)

Agree on label pity there isn't a 'paused' option as most all isssue may be resolved in 1.20.0

[dmfrey]

if #130 resolves this issue, should we close this issue?

[billmeek]

@dmfrey, I'd prefer to leave this open. The enhancement asks for MAF
to directly access the slave BE. At present, we do everything through the
MBE. @awaldram's, SBE has more housepower then his MBE, so he'd
like to have the transcoding done there. That's not done now (and not
tested at all.)

[dmfrey]

but isn't this configurable on the backend to perform all jobs on the
backend where the recording resides?

On Thu, Oct 3, 2013 at 4:44 PM, billmeek [email protected] wrote:

@dmfrey https://github.com/dmfrey, I'd prefer to leave this open. The
enhancement asks for MAF
to directly access the slave BE. At present, we do everything through the
MBE. @awaldram https://github.com/awaldram's, SBE has more housepower
then his MBE, so he'd
like to have the transcoding done there. That's not done now (and not
tested at all.)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/198#issuecomment-25656434
.

My Google Profile http://www.google.com/profiles/dmfrey

[billmeek]

130 addresses the initial issue of missing SBE recordings.

Yes, the MySQL setting is JobsRunOnRecordHost and mine is
set to 1 (e.g. do it on the recording host.) Unfortunately, it only
seems to apply to jobs done by recording rules, not by the Services
API. I guess I could argue that it's an upstream bug. When my
'pretend' slave was running, I did test this and the transcode ran
on the MBE. The initial post here cites 'mythtvgo' as being able
to do this. Bottom line, it's a design choice. I put the milestone
to 1.30.0, oops, thought I'd already done that.