Last update on Beta and new update on Stable broke LiveTV completely

[Ronstang 294]

Sometime in the last week I had issues with my network and had to reset it because Windows is complete garbage.  Since then my beta server has not been able to connect to the Ceton card in that machine any longer.  My stable emby server would not connect either but I was able to get it to work by changing the IP address to the tuner but no matter what I tried in my beta machine it would not see my tuner card through the proxy.

Emby stable updated to 4.8.0.80 yesterday and when I restarted the machine this morning my Ceton card no longer works in the stable machine either.  My IP addresses have not changed but no matter which one I set in the proxy and emby my tuner no longer works.

Emby has in the course of a week completely made LiveTV useless and I have no clue what to do now since all I have done before to make this work no longer works.  

How can I revert both servers to versions of emby that actually work?  Unfortunately every time emby tries to fix one thing they break something else.  And it is not my Ceton cards or the proxy since they have been rock solid and working perfectly without having to ever change the settings for almost 4 years.

I have no TV at all thanks to emby now.

And No....Windows has not updated anything in over a week.

embyserver-63842458097.txt hardware_detection-63842458123.txt

Edited February 2, 2024 by Ronstang

[ebr 16184]

 

Can we please look at a specific example? Please attach the information requested in how to report a media playback issue. Thanks!

 

[Ronstang 294]

6 minutes ago, ebr said:

Can we please look at a specific example? Please attach the information requested in how to report a media playback issue. Thanks!

What does that mean, my hardware no longer works.  I cannot provide an example.  Nothing works.  I gave you the logs.  If you want different logs please be specific.

[ebr 16184]

Okay, the logs weren't there originally.  Are no ffmpeg logs generated when you try to play?

If not, something like an AV program may have messed with the update to ffmpeg.

[Ronstang 294]

I just tried to tune a channel and those are the four logs that were created 

embyserver (2).txt ffmpeg-transcode-5246bb29-8183-4865-b3ea-0604d6bf4e92_1.txt ffmpeg-transcode-2e147daf-793f-4ea6-a93c-d7c69d39527e_1.txt ffmpeg-transcode-be7c0a84-6a47-4703-b4f1-c26e6f4e0036_1.txt

[Ronstang 294]

I have recordings I really want in a few hours, this is ridiculous that emby broke something that has worked forever and I can't get any help.

[ebr 16184]

3 hours ago, ebr said:

something like an AV program may have messed with the update to ffmpeg.

Did you investigate this?

It seems highly likely that whatever the issue is is environmental.

[Ronstang 294]

1 minute ago, ebr said:

Did you investigate this?

It seems highly likely that whatever the issue is is environmental.

I have no idea what you are talking about.  The only programs I use that also use ffmpeg have then installed locally in their folders so how does that affect emby.  Where does emby access ffmpeg from, what folder?  I haven't changed anything with ffmpeg.

[ebr 16184]

Do you have Anti-virus software installed on the machine?  Can you check its logs?

[Ronstang 294]

1 hour ago, ebr said:

Do you have Anti-virus software installed on the machine?  Can you check its logs?

No, just Windows Defender and that is not the problem.  I just installed  emby server 4.7.14.0 portable on this machine and the tuner works perfectly once again.  So it is not environmental, nor is it me, it has something to do with the latest updates....both beta and stable.  Which makes sense because the beta broke a week or so ago and stable broke today.

[Luke 42079]

Can you provide the server and ffmpeg logs from 4.7.14? thanks.

[Ronstang 294]

These are all the logs this portable server has created since I got it working correctly

hardware_detection-63842475740.txt embyserver-63842476060.txt hardware_detection-63842476082.txt embyserver-63842476211.txt embyserver (3).txt ffmpeg-transcode-5e701079-3735-46fb-a015-a53be3092388_1.txt hardware_detection-63842476221.txt

[Ronstang 294]

Did the logs give you any idea what got messed up in the updates to both the beta and stable releasse?

[Ronstang 294]

I managed to get it working on my beta server 4.8.0.78 but I still cannot get it working on stable 4.8.0.80.  Is there something different between the beta and stable that could affect this issue?  I am not sure if this has something to do with the second server on the same machine running a portable install of 4.7.14.0 which is using the tuner to record as I type.  I will shut it down when there are no recordings going and fiddle with the stable version.

[Ronstang 294]

Nope, it only worked for a little while, now it is not working again. My settings in LiveTV won't hold.  Every time I go back to the settings the tuner settings have changed.  I save changes and they won't hold...especially with a reboot.  You definitely broke something with the updates.  

I gave you the logs from the older version.....did you find anything.  Until you fix this I might as well just turn off both my servers as my main use is recording from cable TV and running multiple versions of the server is rather stupid especially with all the benefits of the never version which I want but now can't use because it broke LiveTV.

My wife is not happy as she no longer has TV in the kitchen.

Edited February 3, 2024 by Ronstang

[Ronstang 294]

Look at this....the first photo is the tuner page of LiveTV, notice the tuner address.   Now look at the second photo. This is the tuner address when you click on the tuner to check or change the settings....they ar NOT THE SAME.  And this has been saved multiple times.   This is on the latest beta version.  If I add the port to the end of the address it disappears next time I check the settings.  So I did get the tuner working last night, set up some recordings as a test and went to bed to wake up to no recordings and found my settings had changed all by themselves.

[Ronstang 294]

I just did another test.  The port MUST be at the end of the IP address to the tuner for it to work properly through the proxy.  Multiple times I have tried adding the port to the end of the address like: 192.168.200.2:5004 but even though emby says the settings have been saved if you immediately click back on the tuner settings emby shows the address sans the port.  I finally got it to save the port to the address and verified it several times but then when I tried to tune a station it said "no compatible streams available".  I go back to setting and the port is missing from the address.  Without the port added to the address the tuner will not work through the proxy.  

Last night it worked for a while then it didn't work, then it did.....over and over.  Now I understand what was happening.  When the settings STUCK it worked, when they changed or didn't take then it didn't.  It was working and tuning when I went to bed.  The power blipped sometime in the night due to a storm and the reboot caused the tuner settings to revert and once again the tuner will not work and no matter what I do today I cannot get the settings to stick and make the tuner work.  It seems trying to tune a channel makes the tuner settings revert or change.

So this is definitely an issue with the new update and how it handles saving the tuner settings.

If there is a log that will show you this let me know which one you need.  I've included the last two logs from the beta server as it's the only one since the change that I have ever had the tuner working on if only for a few minutes.

ffmpeg-transcode-4d0f2a7e-bccf-41ef-98d2-c0ac26ab5e48_1.txt embyserver.txt

[Ronstang 294]

OK, this is strange.  My wife is now watching TV on my 4.8.0.80 server but the desktop app will not tune and thus I cannot record anything the way I normally do.  I am currently watching TV on my wife's kitchen TV and it is recording the movie she is watching.  I verified this by looking in the recordings directory.  But I cannot tune to or use the Desktop app to record.  So something is really screwy with the desktop app in the new release....and this is why I thing my tuner is not working.  But it appears that the tuner is only not working from the desktop app and that is how I use it to set recordings for most things.

I am more confused than anything now.  It appears that the tuner settings is automatically setting the IP to the physical IP address of the card but this has never worked in through the proxy before.  Are they elements of NextTV in the new release?  Like direct support for my cards and the proxy is causing the issues on the desktop app?  I am so confused now but there is light at the end of the tunnel if the TV can actually use the tuner it means I'm on the right track to finding the issue.

Anyone have any clue what is going on here?

[Luke 42079]

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

[Ronstang 294]

29 minutes ago, Luke said:

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

Forget it, I attached a bunch of logs yesterday and you never even responded.  My 4.8.0.80 server just shut itself down while I was standing in the kitchen and my wife was watching live TV that I can't use on the actual computer.  It wouldn't restart, refused connection.  I had to reboot.  I'm taking this garbage off my computger.

[Ronstang 294]

Did you find the issue Luke, I ask because this issue appears to be resolved in the latest beta release 4.9.0.3.  I just upgraded to this version on my beta machine from 4.8.0.71 and tuned several channels and all worked.  Then went back a while later and tried again and all channels I tried were able to be tuned in.  I will check again in the morning.

[Luke 42079]

1 hour ago, Ronstang said:

Did you find the issue Luke, I ask because this issue appears to be resolved in the latest beta release 4.9.0.3.  I just upgraded to this version on my beta machine from 4.8.0.71 and tuned several channels and all worked.  Then went back a while later and tried again and all channels I tried were able to be tuned in.  I will check again in the morning.

For your specific issue of random connectivity problems to the tuner, no, not really. There were fixes for other things, so perhaps those helped.

I also am working on reducing the frequency in which the server has to communicate with the tuner so hopefully that will help as well.

[Ronstang 294]

But remember, before it wasn't random connectivity I was having issues with regardless of what the log was telling you....maybe that's a different issue and related to the proxy.

I could tune in a station once on the web app and then even the same channel would not tune, but using the same server from a TV using the app on that particular TV was fine.  My wife has been watching TV in the kitchen every day since this first started happening but on the same server the web app allowed exactly one tune before it broke until a restart.

It is still working on the beta machine, I just went there and tuned in a different channel than an hour ago and it worked fine so I think you found the issue with the web app being flaky.  When will this fix make it to the stable server?

[Carlo 4561]

On 2/3/2024 at 1:27 PM, Ronstang said:

Sorry for being late to respond. I hope it continues to work as it seems that is the case.

I am curious however about the Ceton showing up with two very different IPs in different subnets.  I also see this in the log:

2024-02-03 12:12:19.862 Info LiveTV: Tuner url has changed from http://192.168.50.224:5004 to http://192.168.200.3

From a new browser window could you run both set of URLs and let us know if one is working and the other not working?

http://192.168.200.3/discover.json
http://192.168.200.3:5004/lineup.json

http://192.168.50.224/discover.json
http://192.168.50.224/lineup.json

PS: It's been a long time since we set this up and got it working.  I do remember having to proxy the tuner which created a new IP address in a different subnet (I think), but I can't remember the exact details. I documented this in a text file in the "Carlo" directory if you still have this.  The configuration could also be pulled from the config file for the proxy (if needed).  Hopefully, it continues to work and there is nothing needed to be done, but if you could run those commands and let me know what each does it will be helpful if we need to investigate further.

Thanks,
Carlo

we had to play around proxying the card which created new IPs

[Ronstang 294]

5 hours ago, Carlo said:

I am curious however about the Ceton showing up with two very different IPs in different subnets.  I also see this in the log:

2024-02-03 12:12:19.862 Info LiveTV: Tuner url has changed from http://192.168.50.224:5004 to http://192.168.200.3

That was me.  I found out Saturday the 27th of January that after updating neither of my machines were tuning anything although at the time I did not know it was only from the web app.  Once I realized I spent all afternoon trying to make it work.  I changed the IP address of the Ceton card in this machine to 200.3 because both Ceton cards were set to 200.2.  When I did that and then pointed emby at the card directly instead of the IP address of the machine itself it started working again, at least on this machine.  It worked for almost a week and then would not work that way again.

It was then I found out through playing around that with the tuner url set to the same as the machine's IP address with the port added, which is the way it has been for 3.5 years the web app would tune ONCE and then refuse to tune, but from the TV the tuner worked fine.  Strangely, any recording chosen in the web app did not record but if I chose the recording from the TV then it would record.

It was then I switched both my machines back to the last beta and last stable release that worked for me just so my LiveTV works but on the stable machine I run 4.7.14.0 with no libraries except recording depositories for making recordings and then I keep the stable running so my users still have access to all my libraries as Paul suggested, with both machines on different ports.  It is still working this 2 weeks later.  

I run portable installs of the temp setups so I can quickly check new updates and restore a backup quickly if they don't.  Last night I updated the beta server to the latest and that is when I found out the web app is now working, and it is still working this morning tuning to any channel I choose so I assume the issue is resolved at least in the beta channel.

It still does not work on stable 4.8.1.0 as I expected.

I cannot connect to the tuner running the url above set to the IP address of the card, but could using the machine IP after I added the port that CetonProxy is expecting, but both will pull up the lineup.

I'm glad your feeling better Carlo, I was concerned.  Please don't mess with this if you are not ready.  I have it working in a roundabout way at the moment.

Edited February 14, 2024 by Ronstang