MythTV Official Community Forum

Following happens on a single ATSC tuner system (Mythtv light 0.29): On one of the retro channels they show three episodes in a row. To avoid having back to back recordings with that single tuner I programmed a Manual Schedule form 12:00 to 3:05PM (actually also starting 1 min early). Usually the sy...

Just a note on the side: mythbackend --setverbose doesn't seem to work on the current release. The backend log shows this 2019-01-07 15:30:15.504391 E [1020/1211] ProcessRequest mainserver.cpp:7092 (HandleSetVerbose) - MainServer: Invalid SET_VERBOSE string: 'SET_VERBOSE ' so I actually used: mythba...

No it does not use OpenMAX for decoding during commercial flagging. I do not recommend running a backend on raspberry pi, commercial flagging is likely way past its capabilities. yeah, that's what I suspected as mentioned before. It's just such a nice quiet and low power solution, but in the long r...

Thanks, with your info I got the command line as /usr/bin/mythcommflag -j 106 --noprogress --verbose general,jobqueue --logpath /home/mythtv/ --loglevel debug --quiet so I ran this manually (without the quiet), first with the backend still running then without in both cases it dies with seg fault: ....

Got mythtv-light 29 working just fine on a RasPi 3 B+ with backend and frontend on same Pi or remote FE. (One at a time with local FE idle. Haven't tried both simultaneously yet). System has a single ATSC tuner. It runs mythcommflag after recording is finished and does its job fine if recording is f...