Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £99! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £149! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

[TM-NANO-SE] issue with recording 2 channels simultaneously

What do you mean by "switch the receiver off"? Are you putting it into deep standby first?
 
You are confusing things by the settings restore. You should not set things up and then undo it by applying a previous settings.

Please also answer how you are turning the box off.
 
No, I simply switch the power off on the back of the receiver, this has never caused a problem in the past 4 years that I have been using Vix, on 2 separate receivers.
I can re-install Image v 5.3.030 and power down in the same way without any problem too.
 
after turning the box on again your recordings resume .That is the problem.Both tuners are in use
 
To test I set 2 timers to record BBC1 and ITV with the same start times. The recordings perform perfectly!
If I then turn the receiver power off wait a few seconds then switch back on, I then repeat the same procedure, however this time when I am setting the second timer I get an error message stating that there is a record conflict with the first timer that I had just set.

If you shut the box down cleanly (ie deep standby) while timers are still running, they will start up again when you switch the box back on (assuming they are still within the time-frame for the recording). Even powering off at the mains will do the same, but is never advised until the box is shut down properly.
 
No, I simply switch the power off on the back of the receiver, this has never caused a problem in the past 4 years that I have been using Vix, on 2 separate receivers.
I can re-install Image v 5.3.030 and power down in the same way without any problem too.
You are not meant to do it that way. Timers etc are kept in RAM saved when receiver shuts down properly.

Can you try flashing 5.3 039, use Image Manager instead of USB as it is easier.
After it restart, restore your settings, let it restarat. Install CrossEPG and restart if it isn't installed as part of restore process. Check ABM and run it if needed (shouldnt need to), Check CrossEPG and run it if needed. Restart using remote to make sure everything is saved.

Repeat your recording test.
 
After flashing the image via usb, I set AutoBouquetMaker for Sky and to my area, then populated the bouquets. I then installed CrossEPG plugin using Sky as its source.
at this point I performed a settings backup.
to test I set 2 timers to record BBC1 and ITV with the same start times. The recordings perform perfectly!
If I then turn the receiver power off wait a few seconds then switch back on, I then repeat the same procedure, however this time when I am setting the second timer I get an error message stating that there is a record conflict with the first timer that I had just set.
However If I restore the saved settings file I am now able to set 2 simultaneous timers again.

An easier way to test is after the initial install select BBC1 press the record button to start a manual record. Then select ITV and again press the record button, it will then happily perform the second recording.
If however I now switch the receiver off, then perform the same procedure, the second recording (ITV) will be refused. Then if once again if I perform a settings restore it will quite happily record the 2 channels.
So the bug appears when the power is switched off then back on.

I tried to keep the install to the basic minimum to rule out any changes to settings.

Many thanks for your continued help, itstelboy

Before turning off the box off did you delete the two timers you previously enabled? A timer that is set up can continue after an off / on sequence if the program being recorded is still being transmitted.

When switching off (shutting down the box) did you get the warning that you couldn't put the box into deep standby because there was a recording in progress (or pending recording about to start)
 
I was just performing the restore to see if it made a difference. I could just as easily do another flash install of the image, then power down and back up again. As I have said I've always been able to do this on every image for the past 4 years right up to v 5.3.030. Also there are the odd occasions when my RCD will get triggered which loses power instantly and would cause the same problem.
 
I am not saying that this is my preferred way of operating the receiver, as it is left on permanently and goes into standby at night with a power timer. it's just that I had a power outage that cased this problem to occur, so I set about trying to get to the bottom of what had caused the problem.
 
Last edited:
The problem is present after power is lost to the receiver whether timers are set or not. even if I perform a new flash install, then power down and try to do manual records on 2 different channels the second recording will always throw up an error and refuse to record. So something is triggered by a power loss that has never happened in the past, even recent past with v 5.3 030.
 
I am not saying that this is my preferred way of operating the receiver, as it is left on permanently and goes into standby at night with a power timer. it's just that I had a power outage that cased this problem to occur, so I set about trying to get to the bottom of what had caused the problem.

A short power outage can cause crashed software. If you switch the box off at the mains without first going into deep standby you should ideally wait 60 to 120 seconds before restoring the mains. This time is to allow internal power supplies to fully discharge. If not fully discharged parts of the electronics may be still operational or semi operational while other parts may be inoperative. In this state a clean cold boot may not be possible.

Perhaps in the past you have removed the mains for more than 120 seconds and/or different boxes have different power supply discharge times?
 
Last edited:
No, I simply switch the power off on the back of the receiver, this has never caused a problem in the past 4 years that I have been using Vix, on 2 separate receivers.
I can re-install Image v 5.3.030 and power down in the same way without any problem too.
You wouldn't do that to your computer.
What makes you think it would be okay to do it to your receiver box.
It is just a computer that's dedicated to receiving, recording and playing back TV.
 
Just to clarify, 5.3 030 has no problem. and 5.3 031 has it?

If so, these are the commits, there are two commits related to timers. However, we need a definite way to reproduce the bug. I prefer stating the necessary facts and omitting what is not applabale to the specific question.

openvix: developer 5.3.031.001a5f892db3eTue, 19 May 2020 17:38:25 +0000
estring: add formatNumber functione4a6cb522fSat, 25 Apr 2020 15:10:00 +0300
[Timezones.py] Update to match changed geolocation (#168)65e04e5835Tue, 19 May 2020 10:31:02 +1000
[Geolocation.py] Allow config control of geolocation (#167)24a93fe29cTue, 19 May 2020 10:29:52 +1000
[OnlineUpdateCheck.py] Shutdown and close socket (#166)3a8db1abf6Tue, 19 May 2020 10:27:44 +1000
[rcinput.cpp] Add decimal display of key code (#164)c9e7403b46Tue, 19 May 2020 10:25:36 +1000
Frontend: Finetune some approximately dB calculations8a0ec465c0Mon, 18 May 2020 17:28:04 +0200
frontend: add debug message on setVoltage39ca27a7f2Mon, 11 May 2020 19:31:31 +0300
multitype: fix satellite frequency checka70e76c729Sat, 25 Apr 2020 16:08:51 +0300
frontend: format numbers in getCapabilities7df5e534c7Sat, 25 Apr 2020 15:52:58 +0300
Detect split programs when setting timers (#543)f8f127a82fTue, 19 May 2020 00:22:28 +0100
e2avahi: strdup the service_name and service_type95c4c41590Sat, 16 May 2020 18:14:14 +0300
e2avahi: add some extra eDebug701ac617c1Fri, 15 May 2020 22:22:53 +0300
openvix: release 5.3.030d7c33417f0Sun, 17 May 2020 04:23:55 +0000
openvix: developer 5.3.030.001aeb5a4aa4cSat, 16 May 2020 18:36:10 +0000
[SystemInfo.py] String False" no longer exists in branding module."59577431a2Sat, 16 May 2020 20:12:19 +0200
Fix timer rendering bugs in the Grid EPG (#541)b95bd3ee8fSat, 16 May 2020 16:40:59 +0100
Check resume_point exists for any answer, not just a True one. (#540)Sat, 16 May 2020 16:39:57 +0100

[TD="width: 447"]openvix: release 5.3.031[/TD]
[TD="width: 117"]427975a41d[/TD]
[TD="width: 288"]Wed, 20 May 2020 09:18:55 +0000[/TD]

[TD="class: xl63"]65e737e8bc[/TD]
 
I was only repeating the conditions that caused the problem - that is standard practice in fault finding. it's not my way of using the receiver from day to day.
It was a power outage that first alerted me to the problem, as steam from a soup maker caused my RCD to trip.
----------------------------

I have just taken the installation down to the bare bones as it were, flashed with v 5.3.039, run AutoBouquetMaker to populate channels.
Then manually recorded 2 channels BBC1 & ITV - both record fine. Powered down and back up and can now only manually record the 1 channel (BBC1).

I repeated the process flashing v 5.3.030 - I can manually record both BBC1 & ITV simultaneously.
Powered down and back up and can still manually record both BBC1 & ITV simultaneously.

So that's as simple as i can take it, I haven't changed a single setting, not even set any timers as I haven't set up any epg service.
 
I have just taken the installation down to the bare bones as it were, flashed with v 5.3.039, run AutoBouquetMaker to populate channels.
Then manually recorded 2 channels BBC1 & ITV - both record fine. Powered down and back up and can now only manually record the 1 channel (BBC1).
By powered down, you mean cut the power? i.e not shut down it properly, simulate a power cut.

We need a specific and reproducable method of recreating the fault.


Please answer this question so we can pinpoint the change and look to fixing it.

Just to clarify, 5.3 030 has no problem. and 5.3 031 has it?

There is a pull request pending to make the timer polling wait till after 3 minutes instead of running as soon as it boots as part of other code.
 
Last edited:
Very sorry I've not gone through all the versions after 5.3.030 as they came in quick succession so I jumped from 30 to 39. It may be a worthwhile exercise to go through them incrementally until I find the point at which things change. - When I've got a few hours free.
 
This could be totally irrelevent (so maybe best to ignore)...

A while ago "Behaviour when a movie reaches the end" was an issue, and probably still is.

I confirmed its random nature https://www.world-of-satellite.com/...nd-of-playback&p=500294&viewfull=1#post500294

The setting is in menu/setup/recordings, playback & timeshift.

Also in there is "Recordings always have priority". Is there a slight chance this is getting interpreted as "no" under some circumstances??
 
@itstelboy - When you do get the time, it might be worth switching on debug logs and posting the results when the recording fails.
 
I personally want confirmation on how to trigger this issue. We can then start testing at which point the issue cropped into image.
 

OpenViX Feeds Status

Back
Top