Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - prl

Pages: [1] 2 3 ... 209
1
Beyonwiz / Re: Broken/ Pixelated Images
« on: April 15, 2019, 10:50:45 AM »
Do you get the signal from the transmitter on Mt Wellington or on of the secondary transmitters, which are lower powered if memory serves me correctly.

The main Mt Wellington transmitters are 50kW. The Risdon transmitters are 1.2kW. Taroona, 450W & Acton Rd, 40W.

2
Beyonwiz / Re: Broken/ Pixelated Images
« on: April 15, 2019, 10:44:26 AM »
If you can't find any external issues that might be causing the poor reception on the T4, it may be a problem with the T4 itself.

On some production runs of the T4, the heat sink cement on a set of 4 regulators that feed the tuners is also susceptible to breaking down, and the breakdown products can damage the circuit board around the regulators. This can lead to a variety of different problems (when it happened to my T4, the T4 was completely unbootable).

If that's the problem, you should get it repaired ASAP, because the damage to the circuit board is progressive, and can end up being non-repairable. The photo links in this post are a good example of the problem The black stuff on the circuit board around the heat sinks should be white. On my T4, the cement was more a milk coffee brown, but had still done enough damage to make the PVR unbootable.

If you are willing to open your T4's case, you can check for discolouration of the cement. The two heat sinks are near the tuners, which are in the row of small aluminium boxes directly behind the antenna connections on the back panel. You can see the bottom ends of the tuner "cans" in the first and third photos in the Whirlpool post I inked to.

If you do open the T4's case, unplug it from the mains and leave it for 15 min before opening the case. The power supply has capacitors charged to over 350V when it is running. Leaving it after disconnecting the mains allows time for those capacitors to discharge.

If the cement is discoloured, you should get the T4 repaired anyway, even if the your reception problems aren't caused by the action of the thermal cement. That issue is progressive and is very likely to cause issues later. You can either contact Beyonwiz support ((02) 9603 1822 or https://dtcsupport.zendesk.com/hc/en-gb/requests/new) or Mark Vasile (http://www.decisivecomputersolutions.com.au/contact.html) about the problems. Mark posts as Warkus on the Beyonwiz forum.

I can recommend Mark: he's done excellent repairs for me on both an old Beyonwiz DP-S1 and on the T4 I mentioned above. You can see feedback from others on the Beyonwiz forum in Warkus is a Legend!! (aka Mark).

As Ian-LS suggests, you may get more help on this problem, which almost certainly isn't an IceTV issue, on the Beyonwiz forum.

The differences between the exact channel names used by the broadcasters and those used in IceTV are normal. I think that IceTV regions cover areas where broadcasters use different names for the channels in different locations, but they all have the same IceTV EPG information, so the location part of the name isn't used in IceTV.

3
IceTV EPG Content / Re: 70HD Perth is now simulcasting 7mate
« on: April 06, 2019, 07:03:41 PM »
Watch out for any 7/7HD recordings set to "HD only"!

4
Beyonwiz / Re: Doubled up recording
« on: March 18, 2019, 01:56:32 PM »
My changes have been merged into the Beyonwiz source code repository, but I'm not sure when they will be available in a release (beta or official).

5
IceTV EPG Content / Re: Monty Python not a repeat? Really?
« on: March 17, 2019, 01:43:10 PM »
Thanks, Alison.

6
Beyonwiz / Re: Doubled up recording
« on: March 17, 2019, 12:59:52 PM »
I've submitted a fix to eliminate the unnecessary delete/recreate operations that happen when IceTV sends a timer update, but the timer details have not changed.

Daniel, the version number for the updated Beyonwiz IceTV plugin is 20190308. If IceTV sends the Beyonwiz a "record" timer but the timer id already exists and the message from the IceTV server doesn't change the Beyonwiz timer, the Beyonwiz response for the "record" timer is
iceTimer["state"] = "pending"
iceTimer["message"] = "Timer already up to date Show Name"

If the timer is in fact already running, its state will be updated to "running" shortly after this response.

7
IceTV EPG Content / Monty Python not a repeat? Really?
« on: March 15, 2019, 09:51:13 PM »
I happened to notice that this evening's Monty Python (Viceland) was marked as first run. It first ran 50 years ago this year.

It's a repeat, even if the SBS guide says that it isn't.

8
Beyonwiz / Re: T Series - Scheduling Conflicts Bug with IceTV
« on: March 09, 2019, 03:14:05 PM »
The "missing in action" tuner problem can have some quite odd results, especially when a recording scenario using all the tuners is created and then, when the recordings start, one of the tuners is missing or isn't recognised properly.

9
Beyonwiz / Re: T Series - Scheduling Conflicts Bug with IceTV
« on: March 09, 2019, 03:11:08 PM »
Yep. I just couldn't remember for sure and didn't feel like trawling through the discussion to make sure.

10
Beyonwiz / Re: Doubled up recording
« on: March 08, 2019, 04:12:06 PM »
Hi, Judy.

I just installed a test version of my IceTV fixes on our in-use Beyonwiz T4. I'll submit the changes in a few days if the tests go OK.

11
Beyonwiz / Re: Doubled up recording
« on: March 07, 2019, 07:16:06 PM »
Since you're getting FTTC delivery of NBN, you'll probably get reasonably reliable networking.

12
Beyonwiz / Re: Doubled up recording
« on: March 07, 2019, 05:40:33 PM »
Hi, Judy.

There are two (probably related) bugs here. One is that there's a bug that whenever IceTV sends all of your current timers (e.g. after a "Resend all timers"), the Beyonwiz does delete/recreate operations with the IceTV server on all timers in the list sent from the server, even ones that are unchanged by the new lot of "set timer" messages. As well as being triggered by "Resend all timers", this can also be triggered if an IceTV update fetch fails (e.g. because of a network problem). This bug is only apparent from looking at the debug logs either on the Beyonwiz or on the IceTV server. You'd normally not see any effect on the Beyonwiz user interface, other than it running a bit slower than it should.

The second bug is that it appears that sometimes when a delete/recreate operation is done for a timer, one or other part of the pair can fail. If the delete fails, you get two recording timers, one with the IceTV "star", and the other (the older one) without it. If the "recreate" fails, then the old timer loses its IceTV "star" and the new timer isn't created. I think you've seen both of those cases. This bug may also be being triggered by a network failure.

The possibility of the cause being a network dropout is why I asked about whether you were using WiFi to connect your T2.

I've been able to replicate the first bug. However, I tried forcing the first bug on a realistic timer load (47 timers - the timer load that was then current on our in-use T4) doing the unnecessary delete/recreate of all those timers 100 times over (yes, it was a bit tedious :)) without seeing any instance of the second bug. It may be that the second bug can only be triggered by a network problem.

My current state on this is that I've fixed the bug that causes unnecessary delete/recreates for IceTV timers on the Beyonwiz on my test version of the Beyonwiz IceTV plugin. That was relatively simple. On the way I also found two other minor and unrelated bugs and fixed them. I could not find any cause for the second bug other than the possibility of a networking error, either by stress-testing (as above), or by examining the code.

However, because the fix of the first bug will remove unnecessary delete/recreates I hope that the likelihood of the second error happening will be much reduced. I'm sorry that I can't promise more.

The current state is that I intended to test my modifications on our in-use T4 today, but other things have intervened. I will try to get that going on tomorrow. I'll also make the new version available to Daniel to try if he wants to.

Once I've run that for a few days without problems, I'll submit the fix to the code repository. From there it will need to wait until peteru accepts the changes and builds a firmware release containing them. He's very busy with other stuff at the moment, but I'll ask him if he could make time. In the short term, you may need to run public beta firmware for a while to take advantage of the changes. It will depend on how long it takes between having the changes in public beta to when they are released as official firmware.

Daniel - please get in touch if you'd like a patch kit with the changes.

13
Beyonwiz / Re: T Series - Scheduling Conflicts Bug with IceTV
« on: March 07, 2019, 05:11:13 PM »
Thanks Peter - PRL - much appreciated. I held off on specifics until I could determine if it was just me or a widespread issue

Looks like it was just me and Daniel from IceTV helped out with this advice - the complete power down appears to have done the trick. I checked the tuners before the reboot and all 3 were showing up as working. One of those wonderful quirky things that a reboot fixed

Thanks for getting back on it. The T2 has a strange bug (possibly in the USB tuner drivers) that sometimes causes the USB tuner to be misidentified - it shows up in the devices list, but as a Satellite or Cable tuner, not a FTA (DVB-T or DVB-T2) tuner. Although it's listed in the devices list, it can't be used for recordings in that state, so the T2 acts as though it only has two tuners when recording and also when checking whether a new recording will conflict with existing ones.

In MENU>Information>Devices, the Beyonwiz-supplied "Mini DVB" USB tuner should identify itself as Tuner C and "DVB-T TV-Stick (DVB-T)". If Tuner C is there, but the description has DVB-S (satellite) or DVB-C (cable), then the misidentification problem has happened.

As Daniel suggested, rebooting should fix the problem (check after rebooting).

There's a detailed and at times quite technical discussion on the Beyonwiz forum in Bug - Terrestrial USB tuner identified as non-terrestrial if you want all the gory details.

14
Beyonwiz / Re: T Series - Scheduling Conflicts Bug with IceTV
« on: March 06, 2019, 12:00:08 PM »
If I'm to offer any help, I'll need more than "IceTV reporting lots of scheduling conflicts".

In similar reports, there have sometimes been issues with a tuner failing without the user noticing - that reduces the ability to make multiple recordings across different broadcasters, and sometimes the user neglecting to take padding into account when determining the number of overlaps.

15
Beyonwiz / Re: Doubled up recording
« on: February 25, 2019, 10:48:43 PM »
I don't think there's anything about the bug that would restrict it to one Beyonwiz model. The number of IceTV recordings you have for a device may influence how often the problem happens.

Pages: [1] 2 3 ... 209