I've installed TVHeadEnd on a RaspberryPi4 64bit OS with a Hauppauge WinTV 950q adapter .

I've consistently been running into this problem.

When I access TVHeadEnd from Palemoon, everything works fine.

When I access TVHeadEnd from Brave, I get this:

I'll click on the "TV" in the EPG to watch something and I'll get this:

And then shortly thereafter TVHeadend crashes:

This is either on Windows or Linux

Any idea of why?

chris

    Are Palemoon and Brave requesting different streaming profiles?

    If you are unable to tell from the applications, you may need to enable debug/trace logging on TVH as check there to see if there is a difference.

      doobs Any idea of why?

      The logs should tell you exactly why, there should be a stack trace in them.

          Flole
          Ok.
          I'm a complete noob.
          Where can the logs be found?
          thanks

            DeltaMikeCharlie
            Dunno.
            Access to both is exactly the same way IP-Address:9891
            Action is the same on both.
            Click on the little screen icon, the viewer opens.
            In palemoon it works, on brave it doesn't and then crashes

                doobs In palemoon it works, on brave it doesn't and then crashes

                Browse into http://<TVH-IP>:9981 go into config/debugging and enable debug/trace for 'all' and supply a file name.

                If you don't see a debugging option, go into config/base and change the view level to 'expert'

                Once TVH crashes. Read through your log file looking for when your clients make contact. See if a streaming profile is mentioned and if it differs between the 2 clients.

                You can also try going into config/stream/profiles and setting 'pass' as your default profile.

                  You should see a stacktrace in the log file even without enabling that option. That error is a fatal error, which is logged regardless of the debug level.

                    doobs Where is the log file?

                    If you enable logging, you specify the location for the file.

                    Perhaps you could also look in syslog for any crash details.

                      Nope.

                      Nothing written in the file defined for debugging. (/home/pi/logs/logs.txt) Nothing at all actually, no file, nada, zip, zippo, bupkiss....

                      When the thing comes back up for air, the entry is blank, on both Brave and Palemoon.

                      I was able to show the log at the bottom of the webtool and grab a screen grab.

                      Palmoon:

                      Brave:

                      Maybe that will help.

                      cheers

                      chris

                        @doobs

                        Palemoon mentions the following profiles: ‘webtv-vp8’ and ‘webtv-vorbis’. This combination suggests the TVH streaming profile ‘webtv-vp8-vorbis-webm’ is being used. THIS WORKS OK.

                        Brave mentions the following profiles: ‘webtv-h264’ and ‘webtv-aac’. This combination suggests the TVH streaming profile ‘webtv-h264-acc-mpegts’ is being used. THIS CRASHES.

                        You could try to configure Brave to use the ‘webtv-vp8-vorbis-webm’ or ‘pass’ TVH steaming profiles.
                        -or-
                        You could try disabling the ‘webtv-h264-acc-mpegts’ TVH streaming profile in the hope that Brave can automagically select something else.
                        -or-
                        You could disable all TVH streaming profiles except ‘pass’ and see if that helps.

                        If you don't see these options, go into Config/General/Base and set your 'Default view level' to 'Expert'.

                        doobs Nothing written in the file defined for debugging. (/home/pi/logs/logs.txt)

                        Does Tvheadend (or the user it's running under) have the necessary permissions to write to that file? I doubt that Tvheadend is running as "pi", and generally writing to another users home directory is not possible without messing up the permissions.