Recordings in progress...

[Fuzzy]

Hi
I bought an Ultimo 4k a week or so ago, to replace a Duo2.

It has a twin FBC tuner with a feed to each input, these feeds come from a universal octo lnb. Both tuner A and B are set to 28.2E, C to H come up as automatic and I can record 8 channels at once.

However, if I record a channel even if only for a few seconds, I cannot then access tuner settings. I get 'recordings are in progress or coming up'. Same if I try to reboot, I get the same warning but I can override this one. There are no timer recordings coming up for several hours, there are none in progress and I have tried tweaking the tuner settings but I always get this if anything has been recorded.

I don't get the message if I try to delete deleted items, unless recordings are actually in progress.

Apologies if this has already been asked but I have searched and I cannot find a solution anywhere. Thanks in advance :)

[twol]

However, if I record a channel even if only for a few seconds, I cannot then access tuner settings. I get 'recordings are in progress or coming up'.
Do you really mean tuner settings (menu/setup/tuner) or are you just trying to access another service/channel?

[Fuzzy]

Thanks for your reply :)

Yeah, menu/setup/tuner config/tuner setup/tuner A gives me the recordings in progress message if I have had a recording. In all other aspects the tuners seem fine.

[Fuzzy]

Not having used an FBC tuner before I'm not sure the settings are correct. These are what I am using.

58148

Tuner B is set up the same as A, C to H come up as automatic. Could the lnb be the problem? It feeds the Ultimo, a Duo2 and a SkyHD box. No problems with any of those but they don't use FBC tuners.

Thanks :)

[ccs]

I've nothing like you setup, but had a slightly similar problem which was fixed by using different timeshift settings (to disable it).

[Fuzzy]

I've nothing like you setup, but had a slightly similar problem which was fixed by using different timeshift settings (to disable it).

Thanks, but I tried disabling timeshift and it made no difference. I have tried a few different tuner settings as well. The only way I can get into any of the tuner settings is a gui restart when there is nothing being recorded and no timed recordings are coming up. As soon as it's recorded something I get 'Recording(s) in progress or coming up' when I try to access any of the tuners' settings. Same message if I try to reboot or go into deep standby. I don't get the message if I try to permanently delete items in the trash can though, which I should do if the box thinks something is being recorded, surely?

I'll try a different pair of feeds from the lnb and unplugging the Duo2 and the SkyHD box, see if that does anything when I have time.

[abu baniaz]

Why would you want to change tuner settings if a recording is taking place?

It is by design that we block changing tuner config if a recording is taking place. The idea is you set your tuners correctly and do not go into it again.

[abu baniaz]

You should really just set the the two physical tuners as: simple, single, 28.2

[Huevos]

Why are you trying to change your tuner setup? This is a set and forget item configured at the time of loading the image.

[abu baniaz]

Not having used an FBC tuner before I'm not sure the settings are correct. These are what I am using.
Tuner B is set up the same as A, C to H come up as automatic.

FBC tuners are the same as other tuners. You configure them to the signal they have access to. Your configuration is correct. Advanced is more prone to errors, but don't worry about it as you have it correct.

The 6 leaf tuners should be left as FBC automatic. They will operate in "loop though" mode.



Could the lnb be the problem? It feeds the Ultimo, a Duo2 and a SkyHD box. No problems with any of those but they don't use FBC tuners.
Thanks :)

Apart from not being able to change the tuner configuration when a recording is taking place, are you having any other issues?

By the way, you can do more than 8 recordings.

[birdman]

I've nothing like you setup, but had a slightly similar problem which was fixed by using different timeshift settings (to disable it).
That's the bit mentioned in this post:

https://www.world-of-satellite.com/showthread.php?48033-Unable-to-go-into-deep-standby-after-a-recording&p=382929&viewfull=1#post382929

You don't need to have timeshift enabled for this to be an issue - just that value (somehow) being set.

[Fuzzy]

Why would you want to change tuner settings if a recording is taking place?

It is by design that we block changing tuner config if a recording is taking place. The idea is you set your tuners correctly and do not go into it again.

Thanks Birdman.

A recording isn't taking place though. The problem occurs if anything has been recorded and is finished and there are none coming up. Even recording something for a few seconds and stopping it stops me accessing the tuner settings.

I first noticed it through the warning when I tried to reboot that recordings were in progress, when there weren't, nor were any coming up. Then I wondered if I could go into the tuner settings and I couldn't.

It's not a massive problem, more of an annoyance but it is bugging me :confused:

[abu baniaz]

What about streaming to another device?

[Fuzzy]

FBC tuners are the same as other tuners. You configure them to the signal they have access to. Your configuration is correct. Advanced is more prone to errors, but don't worry about it as you have it correct.

The 6 leaf tuners should be left as FBC automatic. They will operate in "loop though" mode.



Apart from not being able to change the tuner configuration when a recording is taking place, are you having any other issues?

By the way, you can do more than 8 recordings.

Thanks Abu

All other aspects of the tuners are fine. Crossepg doesn't use tuners C to H for some reason. Reboot/shutdown gives me the same warning but I can over ride it so it's not really a problem, more an annoyance.

Cheers :)

[abu baniaz]

CrossEPG and ABM will not use the leaf tuners.

[ccs]

A recording isn't taking place though. The problem occurs if anything has been recorded and is finished and there are none coming up. Even recording something for a few seconds and stopping it stops me accessing the tuner settings.That's exactly what was happening for me, have you checked the link Birdman posted?

[Fuzzy]

That's the bit mentioned in this post:

https://www.world-of-satellite.com/showthread.php?48033-Unable-to-go-into-deep-standby-after-a-recording&p=382929&viewfull=1#post382929

You don't need to have timeshift enabled for this to be an issue - just that value (somehow) being set.

Sorted! I changed "Stop timeshift while recording" to 'no' and the problem has gone! I even have timeshift enabled and it is still working fine. I wrongly assumed that because timeshift was turned off that it couldn't affect anything.

Thanks Birdman and everyone else who has helped because I can honestly say that I would never have found it because I wouldn't have even considered it a possibility. :thumbsup:

[birdman]

Sorted! I changed "Stop timeshift while recording" to 'no' and the problem has gone! I even have timeshift enabled and it is still working fine. I wrongly assumed that because timeshift was turned off that it couldn't affect anything.I couldn't (quickly) understand what the code was doing so stopped trying to fathom it.
However, it has now hit a few people and the workaround isn't obvious, as it seems to relate to something that isn't used.
Looking at the code again I see that the only other use of stopwhilerecording also checks self.pts_record_running, so perhaps the one causing this problem should too.
I'll poke around....

[birdman]

Looking at the code again I see that the only other use of stopwhilerecording also checks self.pts_record_running, so perhaps the one causing this problem should too.
I'll poke around....Seems to work.
If I check both values as a combination then I can set off a recording, stop it and get no "are you sure" prompt when accessing tuner configs and rebooting.
I do still get the prompts if I leave the recording running.
I'll submit a PR.

EDIT:
Well, I will, but not that one, and not quite yet,
The actual issue is the setting of timeshift.isRecording at the end, which shouldn't be set if timeshift isn't actually on....

[birdman]

Hmmm...why did I decide to look at this :-(.

There are 13 places in the code where config.timeshift.isRecording.value is set. I've enabled it, run an instant recordings and run a timer. This only results in two of those assignments being used. That's the initialization (to False) and the setting to True at the end of a recording if config.timeshift.stopwhilerecording is True (the one causing the problem). Not sure how the other code places ever get reached. So once it is set that's seems to be it - it won't become unset.

Might help if I could find out what does unset it, as it's not exactly clear what this variable represents. It is used by RecordTimer, which returns the next timer as being in 300s from now if it is set (which is what causes the prompts at shutdown and tuner config). Now, running a standard timeshift doesn't count as "recording" - possibly this is juts meant to be set if a timeshift buffer is being converted into a recording?
Any ideas welcome...

Perhaps I need to concentrate on the TODO section of the comment related to the offending lines?

[birdman]

An update.

(I think) I've worked out what config.timeshift.isRecording represents. It's whether the current timeshift buffer should be converted into a recording when the programme ends (an option you can set using the record button when timeshift is active). This is needed so that activities which would affect a recording (shutdown, changing tuner configs, etc.*) can warn if you try to use them when this is active - since it does not show as an actual recording timer.

So, I set off a "timeshift recording" whilst having a recording timer set to start and stop before the current programme ended and looked at what was happening (leaving the remote control alone...). This was done with stopwhilerecording set to True.



The timeshift recording buffer started to fill. config.timeshift.isRecording was set to True (by setting of the "timeshift recording": code in Screens/InfoBarGenerics.py at line 3190).
Then the recording started - at this point the timeshift buffer went away (and was not converted to any actual recording - I'm going to ignore that here too).
The recording stopped (and was OK). Timeshift started up again. config.timeshift.isRecording was set to True (by a recording ending: code in Components/Timeshift.py at line 1272, which is the setting causing this issue).
At the end of the programme timeshift stops! config.timeshift.isRecording is set to True again (because we're about to merge recordings - read on...: code in Components/Timeshift.py at line 632
The timeshift buffer is copied(moved) to a recording file.
A 5-min timer recording (a real one - it shows up in the timer list) of the channel that I was "timeshift recording" now appears!
After 5-mins, this stops abd timeshift starts running again.
There are now a few occurrences of config.timeshift.isRecording being set to True in quick succession.
At the end the 5-min recording has been merged with (appended to) the "timeshift recording".
config.timeshift.isRecording is then set to False (cleanup after merging: code in Components/Timeshift.py at line 1043


[* but not, interestingly, changing the channel, which does restart the timeshift buffer and hence remove the recording you think you are making. But I'm going to ignore that here...]


From what I can see config.timeshift.isRecording is never unset when timeshift is paused for a recording.
Consequently it doesn't need to be set when a recording ends.
So I reckon the solution to this problem is to remove line 1272 in Components/Timeshift.py.

[Joe_90]

@birdman - I think you have identified an issue that I have experienced occasionally. Sometimes, I go to bed with a timeshift recording in progress and I put the box in standby, assuming that my auto deep standby timer (30 mins) will put the box to deep sleep after the timeshift recording is finished. Quite often I find the box still running in the morning and the shutdown timer being blocked by "recording in progress" when there is actually none! I think it happens when I have an actual timer recording which may have finished shortly before I put the box in standby which is simultaneous with the timeshift.

[birdman]

I think it happens when I have an actual timer recording which may have finished shortly before I put the box in standby which is simultaneous with the timeshift.So presumably you don't have the option to stop timeshift when recording set?
This issue should only affect those who do.

[Joe_90]

Can't check the setting right at the moment, but will respond later.


EDIT - I have the option to "stop timeshift when recording" set to NO