Posts by petediscrete

Quote from Reddirt

One additional item may or may not be relevant is that when I booted up Win10 and powered up the two drives I saw a flash message about hard drive collision which I understand to mean the drives were being accessed at the same time and should never happen. This also occurred last update.

Every little detail helps. Hopefully that type of information will be as forthcoming from others. While the logs are so important for developers to determine the cause of an issue, behaviour and habits unfortunately are not recorded in them. While I don’t use NTFS drives with LE I too am curious what is causing this issue for some and not for others.

Quote from Reddirt

As I mentioned in post #7 the storage drives were not powered at time of LE update. They were powered on the next day and failed to mount at that time. I have two separate systems on this unit. Each system occupies a 1TB SSD with LE11.01 the default boot drive Win10 on the other. The Win10 is always connected via sata. The 4TB storage drives are exact copies and connected to the system via USB3 interface. Hope that helps.

It’s certainly a start and hopefully others who are experiencing this issue are a little more expansive beyond the proverbial “I’m having the same problem” as if by magic the developers will be able to address it.

Quote from Reddirt

I repaired the drives in Win10 and now they both are mounted as expected. As this is the second time after updates I can only assume something in the process is the cause. I'm good till the next update (just my guess)

Maybe if you provided a little more background to the circumstances prior to this issue it would help to identify and isolate the problem. Was the drive attached to a Windows system and then transferred to a Linux system. Was it in a hibernated state. Is the Windows system set up for fast start etc.

Users stating their drives no longer mount in Linux LE without any background will not help resolve this issue and you couldn’t expect the developers to do so if they can’t replicate the problem.

Quote from photogsy

Hopefully a straightforward answer to this one - I am manually mapping just the channels I want from the services list in TvHeadend, however there are lots of duplicate services e.g. "Channel 4 HD" has 12 services. Should I map more than one of these to one channel, or is there a way to see in the services list which one I should map?

Thanks for any advice!

They are constantly referred to as “duplicates”. They are in fact regional variations. Decide which region you wish to retain and then disable the remainder in the Services tab. Full details can be seen here under transponder number 10714 H

Astra 2E/2F/2G at 28.2°E - LyngSat

Even with all the feedback from fellow users the only true way to make a judgment call is to install it yourself and decide.

Quote from LybsterKodi

I gave up on moving from my dual RPi3 to an RPi4 4GB last year. I'm about to have another go. I intend to run TVHeadend server & client as well as watch films through Kodi. I've tried Kodi (no TVHeadend) and it seems fine. Is there any reason I shouldn't run TVHeadend client & server on the same Pi?

Absolutely none. What tuner if any are you running with TVH.

Guide data invalid after daylight saving time change

As I mentioned previously, in LE11 support for DVB drivers has fallen away. You never mentioned if you ever installed LE10 but my suggestion to you if it ain’t broke don’t fix it, as in stay with your LE 9 setup unless there’s something you particularly need in LE11.

DVB USB tuners are notoriously troublesome in LE. You stated earlier in the post you were using a HVR4000 and never mentioned a DVB USB tuner. Now you mention a WinTV Nova S2. I’m totally confused.

Anyway you now know where you stand and the decision is entirely yours. Your original issue of duplicate channels is down to regional variations and TVH 4.3 does function correctly in LE11. Good luck with the troubleshooting 👍

Your TV adapters appear not to be correctly configured either. If as you say you have a HVR4000 card if memory serves me you cannot use both DVBS and DVBT tuners together. Read the overview section of this

Hauppauge WinTV-HVR-4000 - LinuxTVWiki

I suggest removing the DVBT adapter in the TVH configuration section which just leaves the DVBS adapter and then you can properly configure it.

I’ve given you a number of pointers to help you finally resolve your issue. Unless you have anything further to add we can take this as resolved.

Quote from SamJ

Yes, you're right. I misread that in a hurry (another call on my time); I was right the first time. Not clear to me what's causing the duplicates.

Again what duplicates are you referring to.

The duplicates you’ve shown here are regional variations. Just look at this Lyngsat entry for 10714H. 5 regional variations. You do understand that. https://www.lyngsat.com/Astra-2E-2F-2G.html

What channels are showing up as duplicates. Are they duplicated on the same mux.

I’m assuming the other cables coming out of your LNB are connected directly to some sort of DVBS set top boxes. Are they standard set top boxes or are they something else.

If you have no motor installed or no diseq switches attached in line between these set top boxes or your LE box you only need to configure TVH for a single universal LNB. Set it for initial scan and turn off idle scan.

Can you screen grab the Configuration>TV Adapters screen so I can see how your TV adapters are set up.

Quote from SamJ

Understood. Prior to removing 4.2 I only enabled and disabled one or other of 4.2 and 4.3 (only one enabled at a time); didn't change any folder or other settings; used the Kodi/LE front end only for managing.

No, unfortunately, I'm still seeing multiple listings for channels with v4.3. And have rediscovered that choosing a 4 port LNB option is required (no result from choosing a universal LNB).

No worries, I wasn't offended by being pointed to the docs. I last read them when I installed LE 9.2. Apologies for not having given fuller information from the start and thanks again for your patient efforts to help resolve the issue.

You mentioned in your OP that you were advised to use bouquets. What information was this advice based on.

Quote from SamJ

So far, as in with previous LE install (years ago; was on 9.2 prior to 11), I just selected 4 port LNB and then verified which of AA, AB, BA and BB was live. That worked. I'd just forgotten about this, also about Diseq (read the docs long ago and haven't needed to since and can ordinarily get by if it's something I've done before, but thanks for the link anyway). Ofc, I needed to select port AB and link to DVB-S Network to get any scanning to work, but that wasn't a problem as 4.3 was scanning ok.

What finally resolved 4.3 not running to completion: removal of 4.2 and associated files.

I had intended to give up on 4.3 and do a clean install of 4.2, but on removal it wasn't immediately obvious how to reinstall it, so I just re-enabled 4.3 and the last stuck scan then finished. Had it not done so I was considering a complete reinstall from scratch.

If I'm not mistaken then simply disabling 4.2 isn't enough if it's already been installed, at least that didn't seem to be the case here.

Many thanks for your help.

You can have as many instances of TVH installed as you like as long as they don’t reside in the same folder and only one is active at any given time.

Incomplete or incorrectly configured instances of TVH can cause weird behaviour with your system. You can now see that TVH 4.3 is functioning correctly as I originally stated.

I included the link for documentation purely as I didn’t know your level of experience with TVH. While the Wizard is useful for a quick setup or beginners manual configuration gives you a far more precise configuration of your system if it’s followed logically and completely. One example of this is not having to scan a list of predefined muxes which is basically out of date anyway.

It might be useful for future reference to supply as much information as possible regarding your hardware setup. It really does help with the troubleshooting process.

I assume you have now resolved your original issue with multiple instances of channels.

Quote from SamJ

The LNB has 3 ports in use; two to TVs and one to the PVR. I had no idea what Diseq meant and just left it alone (thanks). Will uncheck.

Ok so that’s a simple single LNB setup you have. Adjust your settings to reflect that. Once that’s done you should be able to perform a successful scan and you’ll be able to monitor the scan in the Status tab.

I suggest you familiarise yourself with this TVH document. It will help with configuring your TVH install correctly to reflect your setup

Configure Tvheadend - Tvheadend 4.0

Post back here and let us know your progress. This will be for the benefit of others too.

Quote from SamJ

I may be wrong about the LNB settings. It turns out that once selected they go grey looking unassigned. The LNB is a 4 port model but I don't know for sure which port is connected; I just checked them all, AA, AB, BA and BB (the box only has one DVB-S tuner) and let LE figure it out. Two of the other ports go to TVs and one is unused. I'll check what the config for 4.2 was tomorrow and try specifying one port at a time.

If you have only one cable coming out of the 4 port LNB and your dish is not motorised you don’t need the diseq box checked. You’ll then only have one set of settings to configure. You won’t have those four options to consider. TVH will see that. Your Hauppauge card has only one DVBS input. Single satellite/single input.

Knowing as much as possible about your hardware setup helps to resolve the problem quickly.

I’d say the guys at Kodi Forum would be best placed to address this issue.

Quote from SamJ

I'll see what I can do but recall that my reason for trying 4.3 was repetition of channels (4 times each) in the EPG, so not quite a "working" 4.2, though at least the mux scan finished.

Meanwhile, here's the mux scan log file (attached) with the halt with 28 to go.

I may have found why the automatic scan didn't work when a mux was configured: the 4 LNB settings were unassigned; rebooting and reinstating as shown in the next attachment at least allowed scanning to resume as before.

As I said it looked like a configuration issue. Is this a single or a multi lnb setup. I noticed the diseq setting is ticked. That would have helped greatly knowing that.

As I said if 4.2 was working in LE11 there’s no reason why 4.3 wouldn’t if configured correctly. Just ensure you replicate the 4.2 configuration when setting up the 4.3 configuration.

Once the configuration is correct adding a single mux as I already outlined will automatically throw up the remaining 69 active transponders and scan them for you. No need for predefined muxes. You’ll probably see your original problem resolved too.