The same for me. I have found that with my OTA recordings, it misses more than it gets right. So I adjusted the forward skip to 60 seconds and the backward to 15. Most commercials over here are 4-5 minutes these days.
Jim A
The same for me. I have found that with my OTA recordings, it misses more than it gets right. So I adjusted the forward skip to 60 seconds and the backward to 15. Most commercials over here are 4-5 minutes these days.
in studying the script I see that only the systemd service for mythtv backend was setup and not any override for waiting on the network to be up so the network tuners like HDHR don't fail.MikeB2013 wrote: ↑Tue Jul 23, 2019 7:46 pmAttached is a helper script (by product of my testing mythtv-light builds) to automate the setting up of mythbackend after mythtv-light (30 or 31pre) has been installed on a Pi 4 or a Pi 3.pgbennett wrote: ↑Sat Jul 06, 2019 12:38 pmmythtv-light does include the backend so it should not be necessary to build from source. Also the wiki guides should give all the info on setting up the database etc. although that info is in the "Build from source" article https://www.mythtv.org/wiki/Build_from_ ... tall_tasks
In brief, see comments in script for more details:
Installs mariadb-server, creates mythconverg database (password is mythtv) and sets daily backup
Installs mythweb
Installs xmltv
setup mythtv user for running mythbackend
setup various directories on the file system for recordings etc. uses /srv/mythtv/
setup logging with rotation
setup systemd mythtv-backend.service file
setup remote access
The script is provided "as is" but any comments are welcome.
Just download the file,unzip, make sure it is executable and run it.
Edit : 20190822 attachment updated to fix issue with daily backup on mythtv-light 30
Mike
When I first turn on "Wait for network" everything seems to work as you'd expect, but if I add fstab mount statements for NFS drives, then next boot I don't have a menu at the top of the screen. It may appear and go away or it may only show a white bar. if I have a terminal shortcut on the desktop I can get in and check stuff, but I've never been about to fix it. So for now I do not wait for network and do a systemctl stop/start mythtv-backend. I had this menu issue even back on Stretch on a RPi3B+ when I'd use NFS mounts in fstab. I have a lot of my scripts and stuff on a NAS so once of my first moves is to get access to that.MikeB2013 wrote: ↑Sun Oct 27, 2019 2:38 pmJim,
I use a SiliconDust HD HomeRun CONNECT QUATRO (Model: HDHR5-4DT, Firmware: 20190621) all I have done is set "Wait for network" using Raspberry Pi Configuration screen (or sudo raspi-config in a terminal session).
My Raspberry Pi's get ip address from my router.
This works for me and I do not see any other problems.
Can you expand on "screws up a lot of other things" ?
Mike
Code: Select all
pi@pi4-20191006:~ $ cat /etc/fstab
proc /proc proc defaults 0 0
PARTUUID=83c29599-01 /boot vfat defaults 0 2
#PARTUUID=83c29599-02 / ext4 defaults,noatime 0 1
# a swapfile is not a swap partition, no line here
# use dphys-swapfile swap[on|off] for that
/dev/disk/by-uuid/c69b1b51-2c53-4ce3-a099-5aa3d077b702 / ext4 defaults,noatime 0 1
192.168.0.22:/mnt/sharedfolder /srv/sharedfolder nfs defaults,timeo=900,retrans=5,_netdev 0 0
Code: Select all
pi@pi4-20191006:~ $ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 220G 99G 110G 48% /
devtmpfs 1.7G 0 1.7G 0% /dev
tmpfs 1.8G 0 1.8G 0% /dev/shm
tmpfs 1.8G 8.9M 1.8G 1% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 1.8G 0 1.8G 0% /sys/fs/cgroup
/dev/mmcblk0p1 253M 53M 200M 21% /boot
192.168.0.22:/mnt/sharedfolder 234G 66G 157G 30% /srv/sharedfolder
tmpfs 367M 0 367M 0% /run/user/1000
@MikeB2913 I can't run the mythtv-setup from the application menu like I can mythfrontend. It fails to launch with an error. When I look into why I see the properties of the launcher uses "@env@/usr/bin/mythtv-setup"MikeB2013 wrote: ↑Tue Jul 23, 2019 7:46 pmAttached is a helper script (by product of my testing mythtv-light builds) to automate the setting up of mythbackend after mythtv-light (30 or 31pre) has been installed on a Pi 4 or a Pi 3.pgbennett wrote: ↑Sat Jul 06, 2019 12:38 pmmythtv-light does include the backend so it should not be necessary to build from source. Also the wiki guides should give all the info on setting up the database etc. although that info is in the "Build from source" article https://www.mythtv.org/wiki/Build_from_ ... tall_tasks
In brief, see comments in script for more details:
Installs mariadb-server, creates mythconverg database (password is mythtv) and sets daily backup
Installs mythweb
Installs xmltv
setup mythtv user for running mythbackend
setup various directories on the file system for recordings etc. uses /srv/mythtv/
setup logging with rotation
setup systemd mythtv-backend.service file
setup remote access
The script is provided "as is" but any comments are welcome.
Just download the file,unzip, make sure it is executable and run it.
Edit : 20190822 attachment updated to fix issue with daily backup on mythtv-light 30
Mike
The reason I use the application menu is I need to launch both the setup and the frontend with the option to disable the CEC stuff and I can't remember that command line so I edit the properties in the application menu for the 2 launch items and then I don't have to remember. I can also pin those launch items to the Desktop or add them to the quick launch box at the bottom of the screen of XFCE4. I have it solved and document for myself so I know how to fix it.MikeB2013 wrote: ↑Fri Dec 20, 2019 1:08 amSorry for delay in responding - I have been traveling.
No idea why it's there, it is original code which I have not changed.
I have done nothing to fix any issues with running mythtv-setup from application menu for Raspbian Buster.
I only run mythtv-setup from a terminal on Raspbian.
After mythtv 31 is released I will have a look a seeing if a normal packaged build of mythtv for Raspbian is easily doable (not my area of expertise so it will take a while to get up to speed).
Mike
Hello MikeB2013 and everyone,MikeB2013 wrote: ↑Sun Oct 27, 2019 2:38 pmJim,
I use a SiliconDust HD HomeRun CONNECT QUATRO (Model: HDHR5-4DT, Firmware: 20190621) all I have done is set "Wait for network" using Raspberry Pi Configuration screen (or sudo raspi-config in a terminal session).
My Raspberry Pi's get ip address from my router.
This works for me and I do not see any other problems.
Can you expand on "screws up a lot of other things" ?
Mike