I am pretty sure that there was once an edit function for existing tasks that allowed them to be directly edited without depending on first having access to any episode of a show at all.
This would be a nice feature to bring back. I have tasks that have been in place for several seasons. I delete ...

The same way you make a new task, the "Record More" option will also edit an existing task for that selected show. You can do it from any episode from that show, including a recording, from the guide, or from the "Discover" tab.

But if one does not have a recording, there is nothing in the ...

One used to be able to edit a rule based on the rule... not having to rely on an episode be available to click on. As it is now in the app, from what i coukd tell, if one deleted all episodes and none are coming up in the next two weeks, there doesn't seem a way to edit the rule as there is no ...

Yes I want to be able to edit an existing task that was set to "all episodes" and I wanted current season episodes only. I did not want to record episodes from previous years, which it was doing.

Does that make sense? @Signcarver?

I figured it out, but yes there must be an upcoming episode ...

As usual thanks for the reply.
I decided to delate a task that had all episodes set and recreate it. I did figure out how to setup a new taks for season 2 and was able to set the options correctly. Of course this process is all different than it was last year when I did this. But I got it sorted.
I ...

I seem to have lost the ability to edit tasks. I also can't seem to find how to tell the system that I want all episodes to just the current season from the current selection which is "all Episodes".
Existing tasks (for shows from last season) have setting for those options, but I can't tell how to ...

Thanks Ned and Sorry for the delay! Which device ID do you need? Should I turn on send data on everything?

The system is working OK now. I think I would need to stop the record engine on the Synology to try to duplicate the problem.

here are the IDs for the Tuners
104EA976
107086F1
1080AB39 ...

Thanks Nick.
But that is not what happened. The reason that I set up 3 record engines was just for the situation that occurred. (losing a single device). All I got was a black screen when selecting a channel. I force closed the client. But that did not help. As I mentioned all of the tuners and two ...

The channel list comes from the tuners... if a record engine is detected, it will use a record engine for live. That engine needs to be able to stream and have access to the channel selected (double check you didn't disable recording on an engine). For cablecard drm, it must be marked properly or ...

Here is my setup. I have three tuners. A duo, a Quatro and a 4K. I have three record engines 2 run on Nvidia Shields and one on a Synology NAS. I set them up that way for failover.
I have all of the tuners and record engines running the latest versions of software and firmware.

Last night I could ...

I just wanted to report that I found that 20250603 App/20250818a (UI) seems to have fixed the black screen 30 to 40 second delay opening Live TV issues... On two different Windows clients. Unfortunately the problem is still there on my Galaxy Phone and Shield android clients 20250708 app with the ...

Black. And 20250818a fixed my issue with the 30 to 40 second delay opening live TV after the splash screen. At least with the Windows client.

Wellsame version on my Galaxy A54 still has the delay... Will need to try other Android devices.
Thanks for that.

I thank you for the comprehensive reply.
OTH I don't think that I can justify blowing my whole system up that has been working fine for years until SD made recent changes. Especially when I suspect that it might not fix anything.
I have verified that the updates are there on all of my devices. I ...

I have gotten no reply or acknowledgement on this continuing problem.

I would like to know if SD is aware that the most recent up date has not fixed the 15 to 30 second black screen delay when opening Live TV.

Another thread reporting the same problem was marked as Solved. I just want to make sure ...

I know this is a known issue and I posted the below in an existing topic. Then I noticed it had been labeled as "Solved" No idea if anyone will look at it So I will try a new topic.
Hopefully this does not violate any rules.

The issue has not been fixed for me with the current release. I am getting ...