[mythtv-users] Intel Atom 330 as a backend
kungfujesus06 at gmail.com
Thu Mar 12 12:45:01 UTC 2009
On Thu, Mar 12, 2009 at 08:41:00AM -0400, Michael T. Dean wrote:
> On 03/12/2009 08:36 AM, Adam Stylinski wrote:
>> On Wed, Mar 11, 2009 at 10:41:53PM +0100, Philippe Cherel wrote:
>>> Le mercredi 11 mars 2009 21:59:11, Raymond Wagner a ??crit :
>>>> LiveTV does not get commflagged anyway. Recorded TV may not finish
>>>> commflagging until several hours after the recording has finished.
>>>> Assuming your playback machine will be considerably more powerful, you
>>>> may consider turning off jobs on the backend, and running mythjobqueue
>>>> on your frontend.
>>> Ok, i see. Usually the only job i use is transcoding, then i edit the
>>> file with avidemux and encode it in x264 to save some space, but I do
>>> that with my main computer so it's not a problem.
>> Wait, you transcode and then you put it through avidemux? That doesn't
>> sound like a good idea, I would think that would get really lossy due to
>> compression, and cause many artifacts. In any case, the transcode job
>> that myth does in mpeg4 would probably take all day if you left it to the
>> atom processor. You're going to have to defer your jobs to a different
>> myth back/front end, especially for high def content.
> I'm guessing he means he does a /lossless/ MPEG-2->MPEG-2 transcode with
> mythtranscode to remove commercials, then he transcodes with avidemux.
> mythtv-users mailing list
> mythtv-users at mythtv.org
Either way, unless he defers his jobs somewhere else, he's going to spend an eternity for the flagging, rendering the transcode part useless.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: not available
More information about the mythtv-users