[mythtv-users] Remote Secondary Backend

[Toby Mills]

>Raymond gave you the answer: by default it streams from the backend
>where the recording was done. Seems to me this will be sufficient to
>avoid multiple hops, provided your backends all host their own
>storage.

Yes, this kind of works, except often a scheduled program will be recorded on the master on behalf of the slave (because the slave is busy etc).
In this case the recording is saved down to the slave storage using storage groups.
It would make sense to stream these from the slave not the master.

Unless there is another way of controlling the logic of which backend or input is the preferred server for recording, at the moment I've been using storage groups to control the logic of what is recorded where, perhaps there is another way.

If a client at the guesthouse schedules a recording, then it should be recorded by preference on the guesthouse backend. Is there away of choosing your preferred recording backend when scheduling a recording. I haven't seen one, but if there was, this would solve that problem.

Toby







__________ Information from ESET NOD32 Antivirus, version of virus signature database 5202 (20100616) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com