[Formuler F1] Error -6 When Recording Makes Box Unresponsive

[cactikid]

Sicilian has posted a bug alert now for this image as a bug has been found

http://www.world-of-satellite.com/s...ting-from-Release-5-1-012&p=465417#post465417

 

[Sicilian]

Sicilian has posted a bug alert now for this image as a bug has been found

The bug is nothing to do with whatever is being discussed here. It's a small bug concerning online update.

 

[cactikid]

but as he has an issue i do see newer image giving him the option?:thumbsup:

 

[PJDiddy]

Happened again last night, off out today but had a few mins to tinker this morn. Changed sat tuner to single rather than equal to and turned on show message when starting recording before trying to recreate problem. Successfully did so, watching BBC 1 London with timers set for Channel 5 HD and BBC 1 HD using just sat tuners. Box hung with no message to say recording was due to start. Was able to use Dreaboxedit to restart box so does this mean just the GUI was frozen?

I changed the skin to test it wasn't that and again successfully froze box with no message using same channels. Did the same a third time but watched a Freeview channel, again no message but box did not freeze this time (expected as not all tuners needed were in use). Tried recording a Freeview channel using the C tuner DVB-T2 whilst watching another Freeview channel, received a message that a recording was about to start and that service had been changed to the recording channel. I guess this is what should happen when using both sat tuners but it seems to be ignoring the settings when both in use.

Did it one last time, watching a sat channel and recording another and got a message to say a recording was starting. Could it be a bug?

 

[ccs]

Which skin(s) have you been using?

I can confirm that service changes to the recording channel works fine on a T2 only setup.

 

[PJDiddy]

Which skin(s) have you been using?

Now away from box so can't remember exactly name but I normally use the Confluence skin and this morning I tried a test timer on the YouVix skin, both fail to show any recording message and both hang box as above using the sat tuners. Can't remember which skin I used when testing the DVB-T2 tuner but it worked fine as it should.

 

[birdman]

Ditch the usb and point the EPG to your HDD.

OK if you're downloading EPG once a day (or so) but not if you are getting it from the transponders (EIT), as having it on the hdd then stops your disk sleeping.

 

[ccs]

OK if you're downloading EPG once a day (or so) but not if you are getting it from the transponders (EIT), as having it on the hdd then stops your disk sleeping.

I thought transponder epg was only written to "disc" at shutdown, and at regular intervals you can define.

My hdd certainly sleeps.

 

[PJDiddy]

I thought transponder epg was only written to "disc" at shutdown, and at regular intervals you can define.

My hdd certainly sleeps.

Check when the file was last modified and see if it corresponds to a shutdown time?

 

[birdman]

I thought transponder epg was only written to "disc" at shutdown, and at regular intervals you can define.

Ah yes - you are right.
So it makes no significant difference at all whether it be on hdd or usb, as it's only ever read/written once.

 

[PJDiddy]

An overdue update to the original issue. I eventually got tired of trying to fix it, reflashed the box and started over. Since then for almost 4 weeks it worked fine in regard to this (although I have had some short/empty blank recordings), a quick message flashed up to say recording started and if needed it zapped to the recording service. However, despite not changing a single setting lately it started doing it again, or rather not zapping the channel when it should leading to a hung box once again when it needs to use both tuners and I'm watching one. I checked and the setting are as I left them, recording take priority etc. Why does one recording not just fail instead of hanging the box? Have upgraded to 5.1.013 but it has been working under this (til now).

 

[birdman]

Having said that, why does the box effectivly hang until the plug is pulled just because all the tuners are busy when it does encounter this conflict?

Answering an old-ish query here.
It shouldn't.
However, more than that, for a recording to start a timer needs to be added, and a timer can only be added if it won't cause conflict (run out of tuners) at the timen (and for the duration) of the actual recording. So, in theory, their can't be a conflict when a timer starts unless your hardware has been recently reconfigured (e.g. disabled a tuner) - there can only be a conflict when a timer is added, and then it is created as a disabled one.

So what is happening here is strange.

 

[Valiant]

So, in theory, their can't be a conflict when a timer starts unless your hardware has been recently reconfigured (e.g. disabled a tuner) - there can only be a conflict when a timer is added, and then it is created as a disabled one.

There can be a conflict - I have experienced a couple some time ago where I have added an auto-timer through the EPG blue button and it clashes with two extant auto-timers. However the clash goes unreported by the timer sanity check and when the time comes there are not enough tuners available and there is a crash. I later found that the clash, though unreported, resulted in the suspension of further creation of timers from auto-timers, so I was able to safely rescue the situation before any conflicting timers were executed. This was in OpenVix 4. I don't know if the current OpenVix exhibits the same behaviour and I am not up-to-date anyway. However, as I have not gathered enough evidence to determine if a fault exists, I think I should look at it again.

 

[birdman]

This was in OpenVix 4.

And was fixed (I remember it well...). But it shouldn't happen (hence the "in theory"). And when it did happen it didn't result in a system lock-up.