Reply to thread

Message

<blockquote data-quote="samuel337" data-source="post: 63324" data-attributes="member: 10347">I'm not sure if this is on the cards yet, but I thought I'd give some insight on how mythTV works in this respect (I've defected a bit recently, but quickly returned when I realised how many more features MP has&nbsp; :lol: ).mythTV has what's called a master backend and slave backends. The master backend controls all the slave backends, and the frontends connect to the master backend. It is assumed that each slave backend has one or more tv cards attached to it. When a TV show is required to be recorded, the master backend locates a free TV card and tells it to record. The file is then stored locally on that computer (I think) and it is then responsible for com-skipping and transcoding of that file. The master backend is designed so that these tasks are spread out over the various backends and that they are only undertaken during idle times.This is my understanding of it anyway, and while it may not be the best setup, it might give people some ideas to work with. I have a single master backend and frontend system so I can't comment extensively on how the whole slave backend system works.Sam</blockquote>

[QUOTE="samuel337, post: 63324, member: 10347"] I'm not sure if this is on the cards yet, but I thought I'd give some insight on how mythTV works in this respect (I've defected a bit recently, but quickly returned when I realised how many more features MP has :lol: ). mythTV has what's called a master backend and slave backends. The master backend controls all the slave backends, and the frontends connect to the master backend. It is assumed that each slave backend has one or more tv cards attached to it. When a TV show is required to be recorded, the master backend locates a free TV card and tells it to record. The file is then stored locally on that computer (I think) and it is then responsible for com-skipping and transcoding of that file. The master backend is designed so that these tasks are spread out over the various backends and that they are only undertaken during idle times. This is my understanding of it anyway, and while it may not be the best setup, it might give people some ideas to work with. I have a single master backend and frontend system so I can't comment extensively on how the whole slave backend system works. Sam [/QUOTE]

Verification