Forum › Forums › Freeview HD › YouView DTR-T › Youview missing end of programme
- This topic has 44 replies, 9 voices, and was last updated 10 years, 1 month ago by
Anonymous.
-
AuthorPosts
-
October 10, 2015 at 7:55 pm #40765
grahamlthompson
ParticipantNow they have some real competition (Freeview Play). perhaps they may at last listen (or face extinction
).
October 10, 2015 at 8:51 pm #40766Anonymous
InactiveI suppose it’s up to BT.
October 11, 2015 at 8:59 am #40767Anonymous
InactiveIt may still be Youview to start it off. Section 3.6.1 The technical specification from 2011 dictates that the EIT p/f is use for the start and end for over the air scheduled recordings. Unless there is a later version which has not been placed on public release and the later version contains the required scope then Youview would first need to supersede that document.
October 11, 2015 at 9:26 am #40768Anonymous
InactiveBut does it dictate that the EIT p/f be used to signal actual start / end of programmes or just the notional start / end as shown in the published schedule and which run strictly by the clock regardless of early starts and over-runs?
October 11, 2015 at 9:33 am #40769Anonymous
InactiveQuote:It may still be Youview to start it off. Section 3.6.1 The technical specification from 2011 dictates that the EIT p/f is use for the start and end for over the air scheduled recordings. Unless there is a later version which has not been placed on public release and the later version contains the required scope then Youview would first need to supersede that document.They haven’t bothered updating up till now, in spite of the numerous ways in which the existing box does not meet the specification.
The technical specification was published at a time when it was expected, or bruited, that YouView was going to be the new Freeview, with standards and certification etc. That didn’t happen, so the 2011 spec doesn’t fill the same rôle as the D-Book. But it must be of concern to BT if its system box isn’t able to record these channels correctly due to the intersection between the deficiencies of the box and the sloppiness of the broadcaster. Putting pressure on YouView is the way owners of retail YouView boxes (non-BT customers) can influence the consortium (dominated by BT) to lean on UKTV or (much less likely I suspect) authorize an update to add padding to the box.
BT TV customers can complain direct to BT, or to both.
October 11, 2015 at 12:13 pm #40770Anonymous
Inactivegomezz – 2 hours ago »
But does it dictate that the EIT p/f be used to signal actual start / end of programmes or just the notional start / end as shown in the published schedule and which run strictly by the clock regardless of early starts and over-runs?
I see what you mean.
Section 3.6.1 of chapter XI states “shall be controlled by changes in the EIT present/following information”.
October 11, 2015 at 12:30 pm #40771Anonymous
InactiveJamesB – 2 hours ago »
But it must be of concern to BT if its system box isn’t able to record these channels correctly due to the intersection between the deficiencies of the box and the sloppiness of the broadcaster.
The usual complaints are mostly of UKTV channels and occasionally BBC Radio channels. That is not ‘sloppiness’. Its just that the broadcaster hasn’t taken up using the EITp/f to also provide AR.
Looking at the DUK guide to launching a channel it clearly states that AR is optional at launch and after launch.
JamesB – 2 hours ago »
Putting pressure on YouView is the way owners of retail YouView boxes (non-BT customers) can influence the consortium (dominated by BT) to lean on UKTV or (much less likely I suspect) authorize an update to add padding to the box.
I’m not sure that pressure does exist for Youview from its current owner base. There are some active members of the Youview community forum who think that because a broadcaster must provide the data for the EIT p/f that they must also do it in such away that it supports AR.
October 11, 2015 at 12:46 pm #40773Anonymous
InactiveQuote:The usual complaints are mostly of UKTV channels and occasionally BBC Radio channels. That is not ‘sloppiness’ of either UKTV or the BBC. Its just that the broadcaster has not taken up the option of using the EITp/f to also provide AR.Looking at the DUK guide to launching a channel it clearly states that is is optional at launch and after launch.
You’re right – sloppiness for C5, who are YouView shareholders and therefore must have undertaken to provide AR, but if it’s not mandatory for Freeview then UKTV have no obligation to use it. Point accepted.
Quote:I’m not sure that pressure does exist for Youview from its current owner base. There are some active members of the Youview community forum who think that because a broadcaster must provide the data for the EIT p/f that they must also do it in such away that it supports AR.Sorry, I don’t follow. If you mean that YouView tends to ignore complaints from retail users, I agree. I think they’re alert to feedback about problems that matter to BT customers though.
October 11, 2015 at 1:09 pm #40774Anonymous
InactiveAs a trial user of the Youview box my experience is that of all the many issues we reported only a small handful have ever been acted upon especially if you discount the bug fixes.
October 11, 2015 at 1:25 pm #40775Anonymous
Inactivegomezz – 8 minutes ago »
As a trial user of the Youview box my experience is that of all the many issues we reported only a small handful have ever been acted upon especially if you discount the bug fixes.
I agree. It’s only if BT is bothered about something that action is ever taken. Which is pretty much to be expected, IMO, since it’s BT who provide most of the funding. Retail customer satisfaction/dissatisfaction is not of much weight, the way things have been set up.
October 11, 2015 at 1:28 pm #40776Barry
Moderatorgomezz – 16 minutes ago »
As a trial user of the Youview box my experience is that of all the many issues we reported only a small handful have ever been acted upon especially if you discount the bug fixes.
To true, and even before the ‘big’ trial started they were made aware of many of the shortcomings, as I have said many times.
Off topic – Have a read of our FVP 4000T FAQ for answers to question asked elsewhere.
October 11, 2015 at 1:59 pm #40777Anonymous
InactiveJamesB – 27 minutes ago »
gomezz – 8 minutes ago »
Retail customer satisfaction/dissatisfaction is not of much weight, the way things have been set up.
When I bought a BY Youview+ and a Talktalk Youview+ in April it took me ages to work out how to complain about the Humax auto-tuning which was causing recordings to be missed on the BT Youview box. It has now been recognised by Youview as an issue (but probably from other complaints not mine).
October 11, 2015 at 2:24 pm #40778Anonymous
InactiveWhen I had a YouView box I formed a theory that complaints in the BTCare forum (BT customers only) got the most attention, after that came complaints from retail users direct to YouView, and a long way after that came complaints posted in the YouView forum. The latter two only if it was something BT was prepared to consider. The problems stemming from the lack of manual tuning used to come into the “Who cares?” category, so that sounds like progress if they are undertaking to address it. Are they promising manual tuning?
October 11, 2015 at 4:56 pm #40779Anonymous
InactiveNo they were stating that they where now aware that Humax Youview machines and only Humax Youview machines, only take note of the owner’s preferred transmitter for the PSB multiplexes and that this causes issues further down the line. They did not promise anything or say what they were going to do about it.
Unfortunately I can’t now find that announcement to see if they have added any other comments.
Any ideas/tips on how to raise complaints with Youview? I have two bugs to report – one for Humax and one for Huawei. They each have a different Audio Description bug, the worse of the two being Huawei.
October 11, 2015 at 5:20 pm #40780Anonymous
Inactive“Contact us” button at the bottom of the page lets you raise a ticket.
-
AuthorPosts
- You must be logged in to reply to this topic.