It has always worked on my Pi3B+, maybe not in UK, but in NL the whole mux is about 27Mbps (482Mhz, is FTA). Rest is encrypted/commercial.You can't do that. SPI is limited to ~50Mbit/s which doesn't allow the whole mux to be read.The ffmpeg in the transcoder service fetches the whole mux and selects the desired channel from that stream via -map options. If I use the channel URL from TVheadend, no issue.
You need to just capture the channels you need. (tvheadend works for me, and I can record/view a few channels from the MUX but not all of them).
This has never worked on any Pi.
Full mux + 2 radio channels + 1TV channel is 27+0.1+0.1+5 is <50Mbps. Enough bandwidth at least.
I understand that one cannot assume the whole mux fits for SPI, otherwise just 1 time fetch it and do channel demuxing on higher layer.
But it means that with Pi4, for me, I cannot use own/other full mux operations while TVheadend also still does its thing. I have to see what I value most. Maybe go back to old DVBT tools, just make sure the whole mux is on a UDP/IP channel and use some other recording/scheduling program.
Statistics: Posted by redvli — Wed Nov 06, 2024 5:48 pm
