[Venton Unibox HDx] Spinning ViX when no free tuners available

[BoxFreak]

Another "Spinning ViX" issue. I Have 1*S and 2*T2 tuners in Venton HD3. If there starts timer recording from two different T2 bouquets (so that the channel I am watching is not in one of them) and there should happen an forced channel change, it does not happen (channel not changed or no message of forced channel change seen on screen) but results in enigma2 process to eat 100% of cpu and spinning ViX in screen. The recording that starts later fails to record. Only rebooting the box helps.

 

[judge]

Debug log?

 

[BoxFreak]

Sorry, I did not have debug on when faced this issue. There were many programs that I wanted to get on hdd
yesterday, so no free gap to test this.
I'll reproduce it in the evening (with debugs, that I'll post here)...

 

[BoxFreak]

Here is the debug log. Earlier one shows the problem, and later one is from time after I gave at problem time "kill -15 enigmaprocess" and recordings started with no free tuners message on screenView attachment No_free_tuner_logs.zip.

 

[BoxFreak]

Same hang happens still on Apollo 90. Any news on this?

 

[BoxFreak]

Same thing happens still on Hades 8. The same problem seen in Finnish forum by an other user with Vu Duo2 with twin T2/C tuner.

 

[sevk]

Sad feature this is indeed. Could it be hardware problem?

 

[BoxFreak]

This could be related to the fact that there is only one favorites list in use. Someone in Finnish forum tried with multiple favorites allowed and did not get this issue anymore. So if only one favorites list is allowed this problem is seen when forced channel change should happen and message displayed. Can someone else verify that this is the case?

 

[BoxFreak]

Now tested also this problem with Hades 12 and I can confirm that the problem lies with the parameter "only one favorites allowed" (don't remember the exact line in English, as using Finnish translation).
If parameter is set yes, then it does not work (as described in this thread) if parameter is set no, then it works.
Hopefully this can get fixed soon...