Tvheadend

but your repository for nightly TVH builds seem to be down

yes should be fixed this week (wrong bank account at the provider -> not paid )

can't register on Libreelec

currently closed due HEAVY amount of chinese crap spam (2k messages in 1h)

C vH wrote:

but your repository for nightly TVH builds seem to be down

yes should be fixed this week (wrong bank account at the provider -> not paid )

ha, no worries, would you mind to put the latest test builds on dropbox or google-drive? The site is still down and I would like to mess around with my rpi this weekend...

https://1drv.ms/f/s!Ap8mNU55Kk6C3Tu8qNMuDfyd1_aj

have fun hopefully everything is working soon again

My configuration:

HTS Tvheadend 4.3-1857
Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-76-generic x86_64)
DVB-C with 4x Xbox One DVB-T/T2/C tuner

VAAPI i915 v1.6.0 (/dev/dri/renderD128)

In short I have the following configuration:
With hardware profile, all DVB-C channels on QAM64 tp work perfectly.
On QAM256 TPs errors occur and after a while the h264 hardware decoder is blocked until the channel is changed.
If I uncheck Hardware acceleration the viewing can be done despite the stream errors.
It is obvious that the problem comes from the USB tuner or more precisely from the drivers, but there could be a change in the TVH to restart the Video stream in libav.

Attach a log:

02:52:07.439 libav: AVCodecContext: reference picture missing during reorder
02:52:07.439 libav: AVCodecContext: Missing reference picture, default is 66123
02:52:07.771 libav: AVCodecContext: mmco: unref short failure
02:52:24.677 TS: DIGI/442MHz/DIGI Sport 3 HD: H264 @ #1711 Continuity counter error (total 2)
02:52:36.939 TS: DIGI/442MHz/DIGI Sport 3 HD: H264 @ #1711 Continuity counter error (total 3)
02:52:37.002 libav: AVCodecContext: Found reference and non-reference fields in the same frame , which
02:52:37.002 libav: AVCodecContext:  is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
02:52:37.002 libav: AVCodecContext: If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. ([email protected])
02:52:37.002 libav: AVCodecContext: decode_slice_header error
02:52:37.002 libav: AVCodecContext: Failed to upload decode parameters: 18 (invalid parameter).
02:52:37.002 libav: AVCodecContext: Failed to end picture decode after error: 18 (invalid parameter).
02:52:37.002 libav: AVCodecContext: hardware accelerator failed to decode picture
09:37:13.088 libav: AVCodecContext: Missing reference picture, default is 95603
09:37:13.230 libav: AVCodecContext: reference picture missing during reorder
09:37:13.230 libav: AVCodecContext: Missing reference picture, default is 95610
09:37:13.347 libav: AVCodecContext: reference picture missing during reorder
09:37:13.347 libav: AVCodecContext: Missing reference picture, default is 95618
09:37:13.347 libav: AVCodecContext: mmco: unref short failure
09:39:04.717 TS: DIGI/442MHz/Channel HD: H264 @ #1711 Continuity counter error (total 9)
09:39:04.813 libav: AVCodecContext: Found reference and non-reference fields in the same frame, which
09:39:04.813 libav: AVCodecContext:  is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
09:39:04.813 libav: AVCodecContext: If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. ([email protected])
09:39:04.813 libav: AVCodecContext: decode_slice_header error
09:39:04.813 libav: AVCodecContext: Failed to upload decode parameters: 18 (invalid parameter).
09:39:04.813 libav: AVCodecContext: Failed to end picture decode after error: 18 (invalid parameter).
09:39:04.813 libav: AVCodecContext: hardware accelerator failed to decode picture

Hi,
I am thinking to get one of these for DVB-C on Rpi2/3 running Dietpi or Nanopi Neo2 weith Dietpi or Armbian.
Will run Tvheadend. Provider DIGI Hungary.

Any info if it is working fine for DVB-C? Low or high freq too? No continuity or lock errors?

Hi Gurabli Gurabli,

Sadly for the Xbox tuner low and high frequencies errors on DVB-C qam256, the least was ~15/20 an hour both on shielded, correctly wired, filtered and amplified setups have been tested. Only DVB-T2 has been fine if reception is clean/strong with external antenne H265&AAC with FTA 1080p50. The results were similar on RPI3 vs x86.

If you want a correct working (dual)tuner for DVB-C use the "Hauppauge WinTV-DualHD 01590" (USB id 2040:0265 Hauppauge) or go HD-homerun quad.

You may even find a triple tuner, with iptv capabilities but not compatible yet with Tvheadend or Satip(tuner sharing) like the MUT@NT HD530C TRIPLE DVB-C which may cover you needs.

Hi Walter,
Sorry to hear, I thought the Xbox tuner will work fine.

So you say the Hauppauge WinTV-DualHD 01590 is working perfectly with DVB-C, no problems at all? I already looked at this stick, but didn't find anything that confirmed it is working fully as it should.

I have a Mygica/Geniatech T230 in use now, but have problems with certain frequencies, and get continuity errors, glitches.

If you say the wintv-dual is running great, than I will buy one.

One more thing: are both dvb-c tuners working now?
I am getting one and I do hope there will be no continuity errors or similar problems.

Gurabli Gurabli to answer both questions, yes dual tuners are working. You have to use a recent 4.17 kernel or a hauppauge supported ubuntu kernel. On recent debian 10 buster it works ootb with only firmware requirement. See this thread for more info including comprehensive support for custom kernel (not necessary anymore):

https://ubuntuforums.org/showthread.php?t=2336566

Walter av wrote:

Gurabli Gurabli to answer both questions, yes dual tuners are working. You have to use a recent 4.17 kernel or a hauppauge supported ubuntu kernel. On recent debian 10 buster it works ootb with only firmware requirement. See this thread for more info including comprehensive support for custom kernel (not necessary anymore):

https://ubuntuforums.org/showthread.php?t=2336566

Many thanks! Well, the kernel on Rpi and Neo2 are both higher versions than 4.17, so it should not be a problem. You mean every kernel after 4.17 has the support or it has to be 4.17?

The Hauppauge support by Brad Love mostly get upstreamed to the linux media tree, in this case it means that support has landend in 4.17 and higher. Debian 10 works with linux 4.19 and its working ootb. However it can be that in future versions regressions can break things but be sure to check out https://github.com/b-rad-NDi/Ubuntu-media-tree-kernel-builder.

Thank you, Walter.
I will receive my DualHD on Monday, hope it will work as it should. Your help is very much apprecieted.

Btw, do you think minisatip can be a good solution for me? It would be a source for a Tvheadend backend on remote location.

Hi Gurabli Gurabli did you have any success with the Hauppauge dualHD already?

About satip, by default it uses some layer2 network tricks to get recognized by devices in local networks, which means you need to make a remote tunnel to make it function like it was designed. However minisatip and tvheadend are very configurable and you maybe able to make it work in a ip layer3 only routed fashion. Remember that Tvheadend HTSP protocol was designed to work over low quality network links from server to client but satip may need a better local wired connectioning with change in frame/packet size it will probably depend on client and channel/provider/hd/sd etc.

Perhaps foolishly, I started an entirely fresh install of the OS Formerly Known As Raspbian with the Buster kernel on my Pi3 with it's X-Box tuner that was, at that stage, working reasonably. Updated and upgraded everything, then proceeded to install tvheadend and dvb-demod-mn88472-02.fw, the firmware that has served me in the past from this thread. Saw the tuner, told it to look for the Sutton Coldfield muxes, but their scan status stays resolutely at PEND. Which is annoying. Extracting from dmesg I have the following

[    5.318738] dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in cold state, will try to load a firmware
[    5.387491] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
[    5.724628] dib0700: firmware started successfully.
[    6.239883] dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in warm state.
[    6.240645] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    6.250439] dvbdev: DVB: registering new adapter (Microsoft Xbox One Digital TV Tuner)
[    6.536169] mn88472 3-0018: Panasonic MN88472 successfully identified
[    6.588066] tda18250 3-0060: NXP TDA18250BHN/M successfully identified
[    6.590327] usb 1-1.3: DVB: registering adapter 0 frontend 0 (Panasonic MN88472)...
[    6.590653] dvb-usb: Microsoft Xbox One Digital TV Tuner successfully initialized and connected.
[    6.591085] usbcore: registered new interface driver dvb_usb_dib0700
...
[   12.696260] mn88472 3-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw'
[   12.919328] usb 1-1.3: DVB: adapter 0 frontend 0 frequency 0 out of range (42000000..870000000)

Can anyone suggest what the problem may be?

Tom Joyce wrote:

Perhaps foolishly, I started an entirely fresh install of the OS Formerly Known As Raspbian with the Buster kernel on my Pi3 with it's X-Box tuner that was, at that stage, working reasonably. Updated and upgraded everything, then proceeded to install tvheadend and dvb-demod-mn88472-02.fw, the firmware that has served me in the past from this thread. Saw the tuner, told it to look for the Sutton Coldfield muxes, but their scan status stays resolutely at PEND. Which is annoying. Extracting from dmesg I have the following

[...]

Can anyone suggest what the problem may be?

Did you assign the tuner to the network in tvheadend? Otherwise you might try right click and force scan

Tom Joyce wrote:

Perhaps foolishly, I started an entirely fresh install of the OS Formerly Known As Raspbian with the Buster kernel on my Pi3 with it's X-Box tuner that was, at that stage, working reasonably. Updated and upgraded everything, then proceeded to install tvheadend and dvb-demod-mn88472-02.fw, the firmware that has served me in the past from this thread. Saw the tuner, told it to look for the Sutton Coldfield muxes, but their scan status stays resolutely at PEND. Which is annoying. Extracting from dmesg I have the following

Can anyone suggest what the problem may be?

Problem is that scan tables are old

try W-SCAN to find correct frequency's

w_scan -f t -x

This Xbox Tuner with MN88472 didn't work for me for DVB-T2 either:
drivers, firmware got loaded:

usb 1-4.1: new high-speed USB device number 19 using xhci_hcd
usb 1-4.1: New USB device found, idVendor=045e, idProduct=02d5, bcdDevice= 1.10
usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-4.1: Product: Xbox USB Tuner
usb 1-4.1: Manufacturer: Microsoft Corp.
usb 1-4.1: SerialNumber: 001097280915
dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
dib0700: firmware started successfully.
dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvbdev: DVB: registering new adapter (Microsoft Xbox One Digital TV Tuner)
usb 1-4.1: media controller created
dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
mn88472 13-0018: Panasonic MN88472 successfully identified
tda18250 13-0060: NXP TDA18250BHN/M successfully identified
usb 1-4.1: DVB: registering adapter 0 frontend 0 (Panasonic MN88472)...
dvbdev: dvb_create_media_entity: media entity 'Panasonic MN88472' registered.
dvb-usb: Microsoft Xbox One Digital TV Tuner successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_dib0700
mn88472 13-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw'

when doing

w_scan -f t -c DE

./w_scan2 -c DE -f t2 
w_scan2 version 1.0.10 (compiled for DVB API 5.11)
using settings for GERMANY
DVB aerial
DVB-T Europe
scan type TERRESTRIAL, delivery system SYS_DVBT2, channellist 4
output format vdr-2.0
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
    /dev/dvb/adapter0/frontend0 -> TERRESTRIAL "Panasonic MN88472": very good :-))

Using TERRESTRIAL frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.11
frontend 'Panasonic MN88472' supports
DVB-T2
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO
FEC_AUTO
BANDWIDTH_AUTO not supported, trying 6/7/8 MHz.
FREQ (42.00MHz ... 870.00MHz)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
Scanning DVB-T2...
Scanning 7MHz frequencies...
177500: plp0 (time: 00:00.196) 
184500: plp0 (time: 00:02.236) 
191500: plp0 (time: 00:04.240) 
198500: plp0 (time: 00:06.284) 
205500: plp0 (time: 00:08.320) 
212500: plp0 (time: 00:10.332) 
219500: plp0 (time: 00:12.332) 
226500: plp0 (time: 00:14.376) 
Scanning 8MHz frequencies...
474000: plp0 (time: 00:16.408) 
482000: plp0 (time: 00:20.816) 
490000: plp0 (time: 00:22.848) 
498000: plp0 (time: 00:24.864) 
506000: plp0 (time: 00:26.864) 
514000: plp0 (time: 00:28.900) 
522000: plp0 (time: 00:30.920) 
530000: plp0 (time: 00:35.440) 
538000: plp0 (time: 00:37.472) 
546000: plp0 (time: 00:39.492) 
554000: plp0 (time: 00:41.508) 
562000: plp0 (time: 00:43.516) 
570000: plp0 (time: 00:45.564) 
578000: plp0 (time: 00:50.052) 
586000: plp0 (time: 00:52.100) 
594000: plp0 (time: 00:54.108) 
602000: plp0 (time: 00:56.120) 
610000: plp0 (time: 00:58.144) 
618000: plp0 (time: 01:00.164) 
626000: plp0 (time: 01:02.168) 
634000: plp0 (time: 01:04.192) 
642000: plp0 (time: 01:08.852) 
650000: plp0 (time: 01:10.884) 
658000: plp0 (time: 01:12.924) 
666000: plp0 (time: 01:17.468) 
674000: plp0 (time: 01:19.485) 
682000: plp0 (time: 01:21.505) 
690000: plp0 (time: 01:26.001) 
698000: plp0 (time: 01:28.021) 
706000: plp0 (time: 01:30.037) 
714000: plp0 (time: 01:32.065) 
722000: plp0 (time: 01:34.085) 
730000: plp0 (time: 01:36.093) 
738000: plp0 (time: 01:38.097) 
746000: plp0 (time: 01:40.129) 
754000: plp0 (time: 01:42.149) 
762000: plp0 (time: 01:44.161) 
770000: plp0 (time: 01:46.177) 
778000: plp0 (time: 01:48.193) 
786000: plp0 (time: 01:50.209) 
794000: plp0 (time: 01:52.217) 
802000: plp0 (time: 01:54.241) 
810000: plp0 (time: 01:56.261) 
818000: plp0 (time: 02:01.069) 
826000: plp0 (time: 02:06.769) 
834000: plp0 (time: 02:08.797) 
842000: plp0 (time: 02:10.801) 
850000: plp0 (time: 02:15.389) 
858000: plp0 (time: 02:17.393) 

ERROR: Sorry - i couldn't get any working frequency/transponder
 Nothing to scan!!

I am nealy sitting next to the tower transmitting DVB-T2 on e.g. 522MHz.
I was trying RaspberryPi 4b with 32bit-kernel, userland kernel ~4.19
I tried Ubuntu 20.10 64bit kernel 5.4.0-33
I tried RaspberryPi 4b with 32bit-kernel, userland kernel ~4.19 with the Raspberry TV HAT where i found all muxes and channels.

While doing
w_scan or w_scan2 i can see, that

dvb-fe-tool --femon

The DVB Tuner is known to have problems at some regions. The same happens if you put the tuner at the Xbox so it is likely a firmware/hw problem of the stick.
At other regions the stick works great.

Hello,

I am trying to use this tuner on a raspberry pi 3 using the latest raspbian.

May 15 13:50:47 raspberrypi kernel: [  597.314322] usb 1-1.5: new high-speed USB device number 6 using dwc_otg
May 15 13:50:47 raspberrypi kernel: [  597.445023] usb 1-1.5: New USB device found, idVendor=045e, idProduct=02d5, bcdDevice= 1.10
May 15 13:50:47 raspberrypi kernel: [  597.445047] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 15 13:50:47 raspberrypi kernel: [  597.445064] usb 1-1.5: Product: Xbox USB Tuner
May 15 13:50:47 raspberrypi kernel: [  597.445079] usb 1-1.5: Manufacturer: Microsoft Corp.
May 15 13:50:47 raspberrypi kernel: [  597.445094] usb 1-1.5: SerialNumber: 006327240115
May 15 13:50:47 raspberrypi kernel: [  597.446053] dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in cold state, will try to load a firmware
May 15 13:50:47 raspberrypi kernel: [  597.446287] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
May 15 13:50:47 raspberrypi kernel: [  597.525739] dib0700: firmware started successfully.
May 15 13:50:48 raspberrypi kernel: [  598.044609] dvb-usb: found a 'Microsoft Xbox One Digital TV Tuner' in warm state.
May 15 13:50:48 raspberrypi kernel: [  598.044763] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
May 15 13:50:48 raspberrypi kernel: [  598.045420] dvbdev: DVB: registering new adapter (Microsoft Xbox One Digital TV Tuner)
May 15 13:50:48 raspberrypi kernel: [  598.045439] usb 1-1.5: media controller created
May 15 13:50:48 raspberrypi kernel: [  598.046959] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
May 15 13:50:48 raspberrypi kernel: [  598.310645] mn88472 11-0018: Panasonic MN88472 successfully identified
May 15 13:50:48 raspberrypi kernel: [  598.326754] tda18250 11-0060: NXP TDA18250BHN/M successfully identified
May 15 13:50:48 raspberrypi kernel: [  598.328826] usb 1-1.5: DVB: registering adapter 0 frontend 0 (Panasonic MN88472)...
May 15 13:50:48 raspberrypi kernel: [  598.328863] dvbdev: dvb_create_media_entity: media entity 'Panasonic MN88472' registered.
May 15 13:50:48 raspberrypi kernel: [  598.330878] dvb-usb: Microsoft Xbox One Digital TV Tuner successfully initialized and connected.
May 15 13:50:48 raspberrypi mtp-probe: checking bus 1, device 6: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5" 
May 15 13:50:48 raspberrypi mtp-probe: bus: 1, device: 6 was not an MTP device
May 15 13:50:48 raspberrypi mtp-probe: checking bus 1, device 6: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5" 
May 15 13:50:48 raspberrypi mtp-probe: bus: 1, device: 6 was not an MTP device
May 15 13:50:48 raspberrypi kernel: [  598.449227] mn88472 11-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw'
May 15 13:50:48 raspberrypi kernel: [  598.616291] usb 1-1.5: DVB: adapter 0 frontend 0 frequency 0 out of range (42000000..870000000)

But the tuner shows up with a red dot next to it on the web interface, what could I be missing to make it work?

Thanks !

Should be an option to enable it in the Web UI and select a network. Assuming you've created a suitable DVB-T or DVB-C network

Thank you for your reply, I was mislead by the MTP message, indeed I was able to enable it once I created the network for it.

Hello, I'm an owner of an ASUS tinkerboard running Armbian with Linux Kernel 4.4.213.
I'd like to use my USB XBOX tuner with the tinker. I successfully compiled the backport media_build.
However, when kernel module load the system crash. I debugged the source and the problem is:
when the driver is probed, the interface returned a null usb device despite idVendor and idProduct are correctly returned.
Any advice?

Are there known problems with using multiple of these tuners at the same time?

I have finally got around to creating enclosures for my xbox one tuners, I have 6 tuners where each tuner is set to a single mux (there are 6 of interest here in UK for me), as each tuner is set to a mux I can stream/record any number of combination of channels that I like, I am using tvheadend with emby.

I have the tuners connected to a couple of hubs.

This has been a long term project that I've finally managed to get back to now that I have a 3D printer, I've 3D printed enclosures for the tuners and also the hub+poswer supply, this gives me a rather neat looking system.

I have had this setup working on various hardware configurations, from a raspberry pi 4, to an mini x86 pc to the current hardware which is an x86 virtual machine on a powerful server, one of my USB host controllers has been passed straight through to the VM so it is using that port directly.

The issue I have had since the start is that after an u unknown amount of time, the driver crashes, I see kernel error messages and the tuners themselves have to be unplugged and plugged back in to get them to re-enumerate. I initially thought this was an issue with the Pi 4, so I switched to using a x86 mini pc, but the problem transferred with it. Last week, I switched to the VM and low and behold the same issue is occurring.

The crash doesn't appear to happen when I just have one xbox one tuner connected, it's when I start adding other tuners in that the crashes start.

The crash normally is in the dib0700 driver, but I have been it in other parts of the system, like the frontend driver mn(something).

Has anybody else experienced this? Is there a solution? Am I the only person with this problem? Is it a problem specific for this particular tuner? Are there any tuners that are known to work with multiple connected?

If it means swapping out the tuners for something else, then that's not a problem, I can make whatever modifications I need to accommodate other tuners in my enclosures, but at the moment it's so flakey that I really don't know where the problem is.

Thanks

Sounds like someone's running an IPTV streaming server....

That aside, without being able to suggest any alternative tuners, do you have the ability to detect when a tuner drops out? Either by some sort of simple script on a loop? Then you should be able to trigger a software disconnection/reset of a USB port

No, I have children that schedule a lot of recordings (everything from soap operas to crap like <locations> top model” and I can’t deal with “why didn’t this record” or “why can I record this, but not this at the same time”, I already spend enough time answering “this <device> isn’t working” with “have you tried switching it off and back on again”!

As there are only 6 muxes of interest (I think there is an additional mux here in London, but it only carries a few crappy London “public access stations”) I decided the easiest way to avoid this all of the hassle is to just have 6 tuners and schedule each tuner to be tuned to each of the muxes, in theory this allows instant playback of a channel although due to ffmpeg probing and caching by Emby, it’s currently not a quick channel hop.

But I’ve never managed to get it working reliably with multiple Xbox one tuners, and I’ve eliminated the hardware because my trials have been across across multiple different hardware platforms. (Linux and tvheadend are the only constants).

I did check when I wrote the post you replied to and it hasn’t crashed since I restarted it a couple of days ago, although I currently only have 3 tuners actually connected to the server (the server itself hosts Emby but is mainly used to run development VM’s + teamcity, so it has plenty of cores and RAM) as I have been refining the enclosures and needed one of the tuner housings so that I could do physical fitment tests for the enclosure that holds a DC-DC converter and the 2 USB hubs)

Yes, I could detect it fairly easily, but yesterday when I was summoned to fix the tv not working, I discovered all 3 tuners had panicked in the kernel and I tried restarting the VM and toggling the usb controller pass through and I VM was still unable to see the tuners, I had to physically unplug them to get them seen again.

I’ve got a bunch of crimp terminals and rg316 cable to make up the “neat” cables from the distribution amp to the tuners, once I’ve made those cables up later today, I’ll be able to run more substantial tests and see exactly what happens and how often this problem occurs, it may have been my fault that I couldn’t get them to reenumerate, so that may be easily remedied.

However, a tuner crash mid recording (or stream) is going to end up with “why didn’t this record dad”, so although I may be able to resolve the main problem of them dying, it’s not an ideal solution.

I just want an easy life!