The transcoder needs to write out a new file and it does that directly rather than through the backend, so running the transcoder on anything but the server that did the original recording isn't something that was part of the original design of the transcoder. It might work and it might not. If Geoffrey sees this, he would know better than I would.
With that said, here's a link to how I answered a similar question recently.
http://www.gossamer-threads.com/lists/mythtv/users/108054?search_string=allow%20commercial;#108054
Great -- appreciate it. Hopefully the next person to ask something similar will be able to find it a bit easier.
Note that I'm in the opposite position of the original poster - my backend is a nice powerful box (P4 3.2ghz), but I've moved all my tuners except the DVB card off to separate boxes (one dedicated slave backend which is a P3-866, and one of my frontends which is a P4 3ghz, but is also a HDTV frontend), so I'd like to make sure the flagging takes place on the relatively idle backend. :) All the storage is on the backend (NFS-mounted on the boxes with the tuners), so running the jobs there will also prevent the network overhead.
It'd be nice to have a "generic" job scheduler option where you can say "Run all jobs of this type on this box", and other similar options, but that may not be as trivial as I'd wish. :)
------------------------------------------------------------------------ | nate carlson | [EMAIL PROTECTED] | http://www.natecarlson.com | | depriving some poor village of its idiot since 1981 | ------------------------------------------------------------------------
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
