Beyonwiz Australia

Posted: **Sat Nov 28, 2015 15:16**

I understand the issues with needing new picons for the new channel 9 channels, and maybe this is wrapped up with what I'm seeing, but just wanted to check...

If I use the IceTV app on my phone to record anything on 9hd, the Timers list on my T4 shows them as recording on GEM. Manually editing a timer also says it will be recorded on channel GEM. If I edit the channel, I get the expected list of proper channels, like 9Gem, 9HD etc. to choose from.

Should I be worried?

Posted: **Sat Nov 28, 2015 15:32**

sddawson wrote:I understand the issues with needing new picons for the new channel 9 channels, and maybe this is wrapped up with what I'm seeing, but just wanted to check...
...

The picons on the T series have nothing to do with the problem you've described.

Posted: **Sat Nov 28, 2015 16:56**

Any ideas then? I've just rescanned on two T4's and a T3, and they all do the same thing. Waiting to see if they properly record on 9HD once the cricket's finished!

Posted: **Sat Nov 28, 2015 17:04**

I'm not in a position to test the changes to Nine services. They haven't made it out to distant regional areas like the nation's capital.

Posted: **Sat Nov 28, 2015 17:14**

Haha!

Hoping someone else can chime in to see whether it's a common problem....

Posted: **Sat Nov 28, 2015 18:13**

When you say you 'did a rescan', how did you do it? When I followed the Beyonwiz rescan instructions (which say go to Location Scan), it insisted on keeping the old name for any LCNs it already knew about - 90 stayed as GEM, rather than switching to 9HD Adelaide. Based on some posts in other threads, I then went back and selected Manual Scan, and made sure to tick the Clear Services option. That actually only scanned for SBS channels (because that was the default channel it was set on), but it deleted everything else - so after doing that, I then did a Location Scan, and then it all worked fine. No icons for any 9-related channels, but that's entirely expected until the picons get updated. (Thinking back, I may also have gone into my Favourites and removed all 9-related channels before doing anything else; but I think that was probably overkill.)

Tim

Posted: **Sat Nov 28, 2015 20:55**

I've got a similar problem,

I performed a factory reset of my T3 and performed a scan of the tuners.

I then enabled IceTV on my T3 and forced a reload of the IceTV LCN settings from the icetv website to my T3 and my android IceTV app.

Here is where it gets interesting. Whenever I create a timer on the android app for 9HD and it is updated on the T3, the timer is missing a value for the timer's channel field. This is not an issue for all the other 9 channels, eg 9live, 9gem and 9Go! and 9SD.

Also, the timer is missing from the IceTV EPG, which I believe is due to the timer's channel field not being present in the timer.

Any thoughts?

Andrew

Posted: **Sat Nov 28, 2015 21:53**

tjcurnow wrote:When you say you 'did a rescan', how did you do it?

I just did a Sydney location scan. My channels actually looked fine. Channel 90 said it was 9hd. I just get the problem where a recording on 9hd done from the iOS app is shown as being on GEM (not 9gem) in the Timer list. So then I did a full manual scan and...

fastcars wrote:Here is where it gets interesting. Whenever I create a timer on the android app for 9HD and it is updated on the T3, the timer is missing a value for the timer's channel field. This is not an issue for all the other 9 channels, eg 9live, 9gem and 9Go! and 9SD.

After my manual full scan I now get this problem too. No channel identification at all on the timer!

So - is this a Beyonwiz or IceTV problem?

Posted: **Sat Nov 28, 2015 22:47**

As per my reply on the icetv forum I'm seeing the same issue. Ie. A timer triggered on 9HD from the icetv app or website appears on the T3 as GEM (ie the old channel name). The timer does not appear in the epg but it does actually record the correct show.
A timer created locally on the T3 is correctly assigned to 9HD and appears in the epg, so I suspect there is an issue at the icetv end.

Posted: **Sun Nov 29, 2015 03:43**

Delete the old channels from the wiz and see how you go (so delete GEM, not 9GEM).
I had a bunch of duplicates doing a manual scan on the Nein frequency (Didn't have clear channels check box ticked as I figured that would likely purge all channels which I didn't want).
Possibly purge all Nine related channels and scan it's frequency again. Timers will need to be fixed/resent for the rest of the week until the next Ice update I presume.

Posted: **Sun Nov 29, 2015 06:33**

tonymy01 wrote:Delete the old channels from the wiz and see how you go (so delete GEM, not 9GEM).
I had a bunch of duplicates doing a manual scan on the Nein frequency (Didn't have clear channels check box ticked as I figured that would likely purge all channels which I didn't want).
Possibly purge all Nine related channels and scan it's frequency again. Timers will need to be fixed/resent for the rest of the week until the next Ice update I presume.

I don't have a GEM channel and no duplicates, it's just the icetv timers are coming as labelled GEM. Can you confirm that you are getting icetv timers for 9HD assigned correctly to the right channel.

Posted: **Sun Nov 29, 2015 10:41**

simoncasey wrote:I don't have a GEM channel and no duplicates, it's just the icetv timers are coming as labelled GEM. Can you confirm that you are getting icetv timers for 9HD assigned correctly to the right channel.

Ditto for me. EPG and channel list are fine and pristine. Timers and recordings done via icetv show as GEM, until you do a full scan (clearing existing channels), then they appear with no channel at all. Recordings in both circumstances actually work fine, recording the correct 9hd channel, but don't show highlighted in the guide.

Posted: **Sun Nov 29, 2015 17:06**

What I have noticed if I set a timer on IceTV for 9HD is that it gets assigned a service ref of 1:0:1:431:430:1012:EEEE0000:0:0:0:
That is the old GEM service ref, the 9HD service ref on my T3 in Melbourne is 1:0:19:431:430:1012:EEEE0000:0:0:0:

Not sure when that service ref is assigned

Posted: **Sun Nov 29, 2015 17:22**

simoncasey wrote:What I have noticed if I set a timer on IceTV for 9HD is that it gets assigned a service ref of 1:0:1:431:430:1012:EEEE0000:0:0:0:
That is the old GEM service ref, the 9HD service ref on my T3 in Melbourne is 1:0:19:431:430:1012:EEEE0000:0:0:0:

Not sure when that service ref is assigned

I think you've cracked it

The only difference between the two servicerefs is the service type (third) field. The :1: for Gem means MPEG-2 SD encoding, the :19: for 9HD means H.264/AVC HD. The numbers come from the broadcast stream and are set during scanning and are correct.

However, when the IceTV plugin sets a timer it sets this field to :1:, no matter what's actually in the real serviceref for the channel.

If you rescanned in a way that preserved Gem in the service lists, the serviceref generated by the IceTV plugin will match Gem. If you rescanned in a way that removed Gem from the service lists, the IceTV timer won't match any channel in the service list and won't find a name.

Enough of the serviceref must be preserved for the recording to work

If the recordings still get made, I suggest waiting for peteru to return and fix the problem. I could probably work out how to fix it, too, but I'm not in a position to test it (Canberra, like most WIN regions doesn't have the changes yet), and even if I was able to fix it and believed in my fix enough to want to give it to people, I can't, because I can put stuff in the main software repository, and I can't make a distribution

Posted: **Sun Nov 29, 2015 17:58**

prl wrote:
simoncasey wrote:What I have noticed if I set a timer on IceTV for 9HD is that it gets assigned a service ref of 1:0:1:431:430:1012:EEEE0000:0:0:0:
That is the old GEM service ref, the 9HD service ref on my T3 in Melbourne is 1:0:19:431:430:1012:EEEE0000:0:0:0:

Not sure when that service ref is assigned
I think you've cracked it The only difference between the two servicerefs is the service type (third) field. The :1: for Gem means MPEG-2 SD encoding, the :19: for 9HD means H.264/AVC HD. The numbers come from the broadcast stream and are set during scanning and are correct.

However, when the IceTV plugin sets a timer it sets this field to :1:, no matter what's actually in the real serviceref for the channel.

If you rescanned in a way that preserved Gem in the service lists, the serviceref generated by the IceTV plugin will match Gem. If you rescanned in a way that removed Gem from the service lists, the IceTV timer won't match any channel in the service list and won't find a name.

Enough of the serviceref must be preserved for the recording to work

If the recordings still get made, I suggest waiting for peteru to return and fix the problem. I could probably work out how to fix it, too, but I'm not in a position to test it (Canberra, like most WIN regions doesn't have the changes yet), and even if I was able to fix it and believed in my fix enough to want to give it to people, I can't, because I can put stuff in the main software repository, and I can't make a distribution

There must be a remnant of GEM somewhere but I have no reference to GEM in any of my bouquets and I did a full scan to clear existing services. And bouquets only list service refs rather than services.

However, I have these two records in lamedb,

0431:eeee0000:0430:1012:1:0
GEM
p:Nine Network Australia,c:000201,c:020241,c:030081,c:04028a,c:050001

0431:eeee0000:0430:1012:25:0
9HD Melbourne
p:Nine Network Australia,c:000201,c:020241,c:030081,c:04028a,c:050001

I assume this is where it is getting the reference to GEM from and it seems like lamedb is updated rather than created from scratch.

Posted: **Sun Nov 29, 2015 18:00**

The decimal :1: and :25: are in the lamedb entry correspond to the hex :1: and :19: in the servicerefs.

Posted: **Sun Nov 29, 2015 18:15**

prl wrote:The decimal :1: and :25: are in the lamedb entry correspond to the hex :1: and :19: in the servicerefs.

Yes, I guessed that about the HEX. As we know Halloween and Xmas are really the same day as OCT31 = DEC25

The issues seems to be coupled with the point you made about the 1 being sent by default and that GEM has remained in the lamedb file even after a rescan.

If I was to delete that record from lamedb, what would happen? I want to avoid total protonic reversal.

Posted: **Sun Nov 29, 2015 18:29**

simoncasey wrote:Yes, I guessed that about the HEX. As we know Halloween and Xmas are really the same day as OCT31 = DEC25

Halloween = Xmas, Octal 31 = Decimal 25 -- I like it

Posted: **Sun Nov 29, 2015 19:16**

Good work guys, I've think you've cracked the cause of this issue!

Posted: **Mon Nov 30, 2015 10:31**

simoncasey wrote:
prl wrote:The decimal :1: and :25: are in the lamedb entry correspond to the hex :1: and :19: in the servicerefs.
The issues seems to be coupled with the point you made about the 1 being sent by default and that GEM has remained in the lamedb file even after a rescan.

If I was to delete that record from lamedb, what would happen? I want to avoid total protonic reversal.

Did you try this?

Posted: **Mon Nov 30, 2015 10:40**

The recordings still appear to be being made. I'm sure a fix will be available soon after peteru is available again.

Do you really care that the timer is tagged incorrectly? OK, it doesn't appear in the EPG either (though it may show in Gem if your lamedb and bouquets still have Gem in them and you add Gem to your favourites list), but why go messing with system files when changing them won't fix the problem?

If you do really care about the service name being correct in the timer, apparently changing it manually in the timer edit screen works.

I'm not able to test any of this.

Posted: **Mon Nov 30, 2015 10:47**

The fact that it doesn't appear in the epg is mildly annoying. A manual fix works until it can be fixed properly. I can't add GEM back as I won't get an epg for it from icetv so that wouldn't fix it anyway.

I was really only suggesting editing lamedb as a test step anyway.

Posted: **Mon Nov 30, 2015 10:58**

prl wrote:The recordings still appear to be being made.
Do you really care that the timer is tagged incorrectly? ...but why go messing with system files when changing them won't fix the problem?

If you do really care about the service name being correct in the timer, apparently changing it manually in the timer edit screen works.

Myself I don't know if the recordings will still be made
The question about lamedb hadn't been answered, now it has
I'm more worried I might miss one

Posted: **Mon Nov 30, 2015 11:05**

simoncasey wrote:The fact that it doesn't appear in the epg is mildly annoying. A manual fix works until it can be fixed properly. I can't add GEM back as I won't get an epg for it from icetv so that wouldn't fix it anyway. ...

I agree about it being annoying for people not having the recordings appear in the EPG. However, messing with the scan files can't fix the bug.

That last bit isn't addressed to you

One funny thing is that this bug would also affect IceTV on TurfBetting.com and some infomercial channels like 4ME and ishotv (those only on regionals, I think), but IceTV doesn't have any EPG info for any of them, so the bug isn't exposed.

Posted: **Mon Nov 30, 2015 18:19**

And both of their viewers probably aren't on here

Posted: **Mon Nov 30, 2015 18:52**

tezza007 wrote:
prl wrote:The recordings still appear to be being made.
Do you really care that the timer is tagged incorrectly?

If you do really care about the service name being correct in the timer, apparently changing it manually in the timer edit screen works.
Myself I don't know if the recordings will still be made
I'm more worried I might miss one

I had been changing it manually, but I just did a test and without a channel showing on the timer in Timer overview, it still recorded 9HD so I can live with that for now. I don't use the T4's EPG so that doesn't effect me either

Posted: **Tue Dec 15, 2015 21:27**

A fix for this has been merged into the firmware repository.

Posted: **Tue Dec 15, 2015 21:37**

prl wrote:A fix for this has been merged into the firmware repository.

Thanks Peter for the update.

Posted: **Wed Dec 16, 2015 17:17**

prl wrote:A fix for this has been merged into the firmware repository.

Brilliant!

Posted: **Thu Dec 31, 2015 08:35**

Not sure if I'm the only one, but I'm still getting this problem ie if I set a recording on 9HD on icetv, it still appears as GEM on my T3. It records correctly but doesn't appear in the epg unless I change the channel on the timer.

Posted: **Thu Dec 31, 2015 08:38**

simoncasey wrote:Not sure if I'm the only one, but I'm still getting this problem ie if I set a recording on 9HD on icetv, it still appears as GEM on my T3. It records correctly but doesn't appear in the epg unless I change the channel on the timer.

You aren't. Try this.

Posted: **Thu Dec 31, 2015 09:16**

I've tried all of those, I assumed I was the only one as everybody else seemed to say it was eventually working ok.

One thing I have noticed, I still have a reference to the old GEM in lamedb.

Posted: **Thu Dec 31, 2015 09:40**

Do you also still have old GEM servicerefs in your bouquets files in /etc/enigma2?

Posted: **Thu Dec 31, 2015 09:47**

prl wrote:Do you also still have old GEM servicerefs in your bouquets files in /etc/enigma2?

No, nothing referencing GEm or 431:430 apart from 9HD

Posted: **Thu Dec 31, 2015 09:48**

Out of interest, how is lamedb populated? I tried editing that to remove the reference to GEM to see if that helped but it gets recreated on GUI restart.

Posted: **Thu Dec 31, 2015 09:58**

simoncasey wrote:
prl wrote:Do you also still have old GEM servicerefs in your bouquets files in /etc/enigma2?
No, nothing referencing GEm or 431:430 apart from 9HD

You have to look carefully. The old GEM and the new 9HD servicerefs don't differ in their proper defining triple of ONID/TSID/SID. They differ only in the servicetype field, the third field in the serviceref. GEM is :1: and 9HD is :19:. This flags the change of the service defined by the triple from MPEG2 to MPEG4.

Posted: **Thu Dec 31, 2015 10:05**

prl wrote:
simoncasey wrote:
prl wrote:Do you also still have old GEM servicerefs in your bouquets files in /etc/enigma2?
No, nothing referencing GEm or 431:430 apart from 9HD
You have to look carefully. The old GEM and the new 9HD servicerefs don't differ in their proper defining triple of ONID/TSID/SID. They differ only in the servicetype field, the third field in the serviceref. GEM is :1: and 9HD is :19:. This flags the change of the service defined by the triple from MPEG2 to MPEG4.

Yep, there is nothing referencing the old GEM in my bouquets. The only reference to 431 is

Code: Select all

#SERVICE 1:0:19:431:430:1012:EEEE0000:0:0:0:

which is in last scanned, terrestrial and favourites.

Posted: **Thu Dec 31, 2015 10:07**

The only reference I seem to have to GEM is in lamedb

Code: Select all

0431:eeee0000:0430:1012:1:0
GEM
p:Nine Network Australia,c:000201,c:020241,c:030081,c:04028a,c:050001

Posted: **Thu Dec 31, 2015 10:11**

simoncasey wrote:Out of interest, how is lamedb populated? I tried editing that to remove the reference to GEM to see if that helped but it gets recreated on GUI restart.

lamedb is populated during a service scan. However, it is written out each time enigma2 shuts down, whether it has been modified or not.

If you want to modify it by hand, I suggest:

init 4
... edit lcndb in your favourite editor ...
init 3

It's sensible to do the same any time you want to edit anything in /etc/enigma2 behind the system's back.

Posted: **Thu Dec 31, 2015 10:40**

prl wrote:
simoncasey wrote:Out of interest, how is lamedb populated? I tried editing that to remove the reference to GEM to see if that helped but it gets recreated on GUI restart.
lamedb is populated during a service scan. However, it is written out each time enigma2 shuts down, whether it has been modified or not.

If you want to modify it by hand, I suggest:

init 4
... edit lcndb in your favourite editor ...
init 3

It's sensible to do the same any time you want to edit anything in /etc/enigma2 behind the system's back.

Thanks, I often forget to do that.

Manually editing lamedb has fixed the issue and all of my 9HD IceTV timers now arrive on the correct channel.

Posted: **Thu Dec 31, 2015 10:42**

Good to hear. I'm not sure why a rescan didn't fix this, but the exact logic of what happens in a rescan has long eluded me.

Posted: **Thu Dec 31, 2015 10:54**

prl wrote:Good to hear. I'm not sure why a rescan didn't fix this, but the exact logic of what happens in a rescan has long eluded me.

It's beyon me

Posted: **Thu Dec 31, 2015 12:20**

Hi,

Part of the confusion could be a result of Beyonwiz not performing a standard Enigma2 scan. Beyonwiz have integrated a usually optional plugin "lcnscanner"/"inilcnscanner" into the scan process that does the work of associating the transmitted LCNs into the non default "Terrestrial TV LCN" bouquet.

Regards,
Ian.

Posted: **Thu Dec 31, 2015 12:58**

I'm not sure that's relevant, especially not to the contents of lcndb.

Posted: **Thu Dec 31, 2015 17:17**

Hi Prl,

The comment was more directed to Simoncasey to help him follow the code chain of the scanning process.\

Regards,
Ian.

Posted: **Thu Dec 31, 2015 19:05**

IanSav wrote:Hi Prl,

The comment was more directed to Simoncasey to help him follow the code chain of the scanning process.\

Regards,
Ian.

I don't think it was relevant to my issue. I think it was the clear before scan flag that was set to no when I did the scan that brought in the new channels but kept GEM in lamedb.

I think there is still a bug in the icetv plugin as even with GEM still in my list, it should have been able to differentiate between 9hd gem.

Posted: **Thu Dec 31, 2015 22:49**

simoncasey wrote:
I think there is still a bug in the icetv plugin as even with GEM still in my list, it should have been able to differentiate between 9hd gem.

I agree too. It may be awkward to fix given that 9HD is not universal.

Still have to manually edit GEM to 9HD despite the latest firmware. Since I can be a bit OCD it irritates when something is not quite right.

Posted: **Fri Jan 01, 2016 07:05**

simoncasey wrote:... I think there is still a bug in the icetv plugin as even with GEM still in my list, it should have been able to differentiate between 9hd gem.

I don't think there's a good general way to do that with the information that the IceTV plugin has.

Posted: **Fri Jan 01, 2016 08:39**

Paul_oz53 wrote:... Still have to manually edit GEM to 9HD despite the latest firmware. Since I can be a bit OCD it irritates when something is not quite right.

This problem is caused because the definition of a channel that IceTV sends when setting a timer doesn't have enough information in it to correctly distinguish whether it's a timer for 9HD or for the old GEM.

Some sorts of re-scans that successfully find 9HD don't clear out the definitions for the old GEM out of the scan files, and so it's not possible to determine whether the search for a Beyonwiz serviceref that matches the timer channel data has returned the correct serviceref.

Early on in the discussion of this problem, some people noted that some specific sorts of re-scans in the original firmware changed the incorrect "GEM" in new timers to blank. It's possible that the same kind of scan will get rid of the GEM entries in new timers and replace it with 9HD.

I think that the scans that did this were ones done in MENU>Setup>Tuners>Manual scan, with "Clear before scan" set to yes, but I can't recall the exact settings necessary, and I'm not able to test this behaviour, because WIN Canberra is not yet broadcasting 9HD.

Beyonwiz Australia

Recordings on 9HD via IceTV show as GEM on Timers list

Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list

Re: Recordings on 9HD via IceTV show as GEM on Timers list