Messages

Yes, updating to 11.6.2 does not require a service scan let alone a full setup wizard.

I do not recall seeing the black screen artifact. I have seen greenscreen on my Toppys which is caused by problems with the HDMI handshake between the Toppy and the TV. But that tends to stay rather than coming and going and you can see the output but it is green.

If you are lucky then the move to 11.1.2 may resolve the problem.

[just as I am about to click on "post"]

Third time lucky? Keep on loosing connection to IceTV forum - just as I am about to click on "post".

No idea about diagnostic; well beyond my expertise.

Could be a BIOS issue, a firmware issue, or just bad luck.

During beta testing, if I recall correctly, using HDMI2 solved the problem. But the unit I was using had slightly different hardware - DIV output as well as 2 HDMI ports.

I assume you have tied different HDMI cables? They can fail or just not get on with the HDMI port on the TV or the IceBox.

Another possibility is that (for some reason) the IceBox is decoding the signal using software rather than hardware assistance that is built into the CPU. My recollection is that hardware assistance maxes out at 1080p, one reason reason not to set output at 4K. Recent CPUs may have more advanced hardware assistance.

Try plugging in the HDMI cable to the other port on the IceBox; during beta testing hardware assistance was only working on one of the two ports.

On my IceBox I have it set to 1920x1080p - this reflects HD broadcast are not interlaced when using h.264. I think MEPEG2 may be interlaced. MY old Toppys do not support 1080p, max out at 1080i - some ancient Beyonwiz use the same SOC. So, try 1920x1080p.

My recollection that recent builds of the IceTV add-on upload timers set on the IceBox itself, either through the EPG or a timer rule, to the IceTV server. Looking at the change list, this was introduced in IceTV add-on version 0.1.68; the current build is 1.0.2. You can delete timers created using the IceBox EPG via the IceTV App. My recollection is that they cannot be deleted on the IceBox, as they are immediately download from the IceTV server. Timers created by IceBox timer rule can be problematic - but I doubt that they are a popular feature with users.

Screen resolution should be set to 1920x1080 @ 50 Hz. Other settings can produce suboptimal results. 1920x1080 is the resolution used by HD transmission that use h.264. Most HD transmission use h.264; some regional areas have MPEG2 HD.

That is unusual. In the early days there was an Timer update bug that could result in occasional doubling up of timers.

All I can suggest is that you create a support ticket.

Also check to see if you are running the latest build which is, if I recall correctly 11.6.2.

You could try a soft reset but I am not hopeful that it will make any difference.

Are in area where you can receive 9Life from multip0le transmitters? With recent builds it is possible that both are active - however in my experience it does not result in duplicate timers. Indeed it should not do so.

Hopefully the new build will mitigate the problem you are having. I know that @Daniel Hall has been working on a solution to the EPG/timer update problem.

We do not have a list of the changes, and @Daniel Hall is currently out of action with the flu.

I cannot test for the problem as I am currently running a beta build.

Dan has a dreadful dose of the flu so may be off-line for a day or so, and I'd rather leave the technical comments to him as the software author.

Hope Daniel gets well soon.

Yes, a new build was distributed a few hours ago. I understand that @Daniel Hall will be making an announcement about the changes made in that build.

I suspect that the processing time is dependent on the transmission codec (for example h.264 HD is more resource intensive than MPEG2 HD), the resolution, and bit-rate.

HD channels use h.264 codec (although in some regional areas some HD uses MEPG2). Most SD channels use MPEG 2 - notable exceptions include 7Flix (Melbourne and probably elsewhere) and racing.com. The bitrate used on a particular (logical) channel is not fixed and can change from on program to the next.

[http://{IPAdress of IceBox}:9981/]

The post and pre padding has to be set in TVHeadend www server. You access via your web browser of choice:
http://{IPAdress of IceBox}:9981/

You the select Configuration > Recording, and change the pre and post padding in the dialogue box, then save using the save "button" in the menu - on far left.

The two setting you tried on the IceBox pick up the amounts of pre and post padding from the TVHeadend setting at this time when the installation wizard runs. They are not changed to reflect subsequent changes mad by the TVHeadend web server.

The ten hour late for timer rules timers setting suggest that it max have something to do with the time used by the IceBox. Could it be that the IceBox uses UTC +0 but those local timers being set UTC+ 10? I will see if I can replicate the problem on one of my BYOB.

Are you using Timer Rule or timer rule (guide based)

Update: Just set a timer rule for recording 18:00 to 18:30 and it comes through as starting at 04:00 tomorrow. Looks like UTC offset related problem. This is not for a guide based timer, Guide based timers work correctly.

I have seen instances where all the channels (LCN's) have been found but are not picked up in the matching process. Not sure if it is happening with the current build and quite some time since I first installed it. On all three units the LCNs are reported correctly (not sure if that was initially the case).

[not]

It would be helpful if the USB Keyboards also had a trackball or mouse. On a BYOB I have a Logitech USB Keyboard + Mouse. I have also used another Logitech Keyboard with trackpad - in each case the connection to the BYOB was "wireless". Wireless is OK, but non-wireless is definitely not wife-friendly!