|
||||||||
With the launch of YouView should Arqiva considerd relaunching SeeSaw |
![]() |
|
|
Thread Tools | Search this Thread |
|
|
#1 |
|
Inactive Member
Join Date: Feb 2013
Posts: 943
|
With the launch of YouView should Arqiva considerd relaunching SeeSaw
With the launch of YouView should Arqiva considerd relaunching the SeeSaw TV service or find partners to re-launch SeeSaw on YouView?
|
|
|
|
|
Please sign in or register to remove this advertisement.
|
|
|
#2 |
|
Forum Member
Join Date: Jul 2001
Posts: 458
|
er.........No
|
|
|
|
|
|
#3 |
|
Inactive Member
Join Date: Dec 2012
Posts: 2,107
|
Why on earth would they want to do that?
|
|
|
|
|
|
#4 |
|
Inactive Member
Join Date: Feb 2013
Posts: 943
|
Why not ? VOD is taking off
|
|
|
|
|
|
#5 |
|
Forum Member
Join Date: Jan 2013
Location: Cambridgeshire
Posts: 120
|
Yeah but SeeSaw never did anything particularly notable and was virtually ignored in the marketplace. Hard to see Arqiva managing to compete any better the second time around.
|
|
|
|
|
#6 |
|
Forum Member
Join Date: Feb 2004
Location: London
Posts: 7,519
|
As a Content provider would you want to go through an aggregator like See-saw to access a platform like you view when you can do it yourself(Easily).
See saw and Kangaroo made a lot of sense when they would be the only/ a leading platform - but now that there are others there ..... is there much point.... (and or is a technology company the right way of doing it ??) |
|
|
|
|
|
#7 |
|
Forum Member
Join Date: May 2008
Location: Reading, UK
Posts: 23,357
|
Isn't what Youview offers a *common client spec* as opposed to a common content client application?
Best of both worlds would have probably been a reference device AND reference playback application; instead of a reference device running multiple playback clients... and "competition" between them.. As opposed to best-of-breed at each layer... Youview done *right* would have been... Reference hardware (Youview box) - defined to... TV App Layer (recently opened under Apache licence by BBC) iPlayer client used as codebase for a Youview playback client, either opened or licensed liberally to allow recompilation to run anywhere - this was the basis for Seesaw. (iPlayer beign best of breed) On the server side - open-licensed iPlayer playout infrastructure... Rather than different clients playing in a common frame. Effectively rebadge the best-of-breed and you have the wide reach enabled through the open layers... become the PAL-I of TV IP playout... |
|
|
|
|
#8 |
|
Inactive Member
Join Date: Dec 2012
Posts: 2,107
|
Quote:
Isn't what Youview offers a *common client spec* as opposed to a common content client application?
Best of both worlds would have probably been a reference device AND reference playback application; instead of a reference device running multiple playback clients... and "competition" between them.. As opposed to best-of-breed at each layer... Youview done *right* would have been... Reference hardware (Youview box) - defined to... TV App Layer (recently opened under Apache licence by BBC) iPlayer client used as codebase for a Youview playback client, either opened or licensed liberally to allow recompilation to run anywhere - this was the basis for Seesaw. (iPlayer beign best of breed) On the server side - open-licensed iPlayer playout infrastructure... Rather than different clients playing in a common frame. Effectively rebadge the best-of-breed and you have the wide reach enabled through the open layers... become the PAL-I of TV IP playout... |
|
|
|
|
|
#9 |
|
Forum Member
Join Date: May 2008
Location: Reading, UK
Posts: 23,357
|
Quote:
It was my understanding the above is the way YouView was meant to be. With the BBC iPlayer Team writing all the coding for each PSB's content selection and thereby improving the vastly inferior ITV Player to boot. Only the PSB's said no, because they 'wanted their own identity'. Pfft, if true. And I'll throw in an allegedly, too.
|
|
|
![]() |
|
All times are GMT. The time now is 07:01.


