Posts: 26,215
Joined: Oct 2003
Reputation:
187
There is no mistake. Features get in when they're ready. PVR is not ready and until the API is stabilised will be staying where it is.
It's always better to have things NOT on the roadmap so that we ensure things are achievable.
A lot of the stuff on there is still likely to not be done. I have no idea who keeps adding stuff to it :p
Cheers,
Jonathan
Posts: 113
Joined: Jun 2010
Reputation:
15
louis
Senior Member
Posts: 113
Ok Jonathan, thanks for clarification...
Cheers Louis
Posts: 10
Joined: Apr 2012
Reputation:
0
bmn001
Junior Member
Posts: 10
So...PVR moved out of Frodo. I understand how these things go, and am not complaining. Thanks for taking the time to do it right.
But I have to say this: "NOOOOOOOOOOOO!"
Posts: 298
Joined: Jul 2010
Reputation:
0
KRA77
Senior Member
Posts: 298
Seen this so many times now, it's no surprise. Before 10.5 (wich ended as 10.12?) there was talk that pvr would come in next release.
Still though, we got a fairly ok working pvr branch, even though it's not official.
Posts: 16
Joined: Apr 2010
Reputation:
0
MakkaD
Junior Member
Posts: 16
The idea i had since the beginning is that nobody have the minimum clue on what is needed to "stabilise the API".
Actually it looks like there is no effort by the developer on PVR or the interest to spend time on it.
What are the differences since 2 years ago?
What work has been done since then to "stabilise the APIs"?
Which are the showstopper missing features that do not let the PVR branch get into official build?
I have not seen any wiky or documentation or analisys on all these aspect so no surprise the API are not stable and PVR is not yet "ready" for prime time.
The only way to introduce the PVR functionality is to go through these steps:
- PLANNING/FEATURE REQUIREMENTS: Feature definitions to make clear which features are "needed" and what "can wait" future version.
- DEFINITION: Define and stabilise the API that will be available to access the features
- DEVELOP: Start to produce the code needed to fulfill the requirements (creating an OFFCIAL branch?).
- INTEGRATE: Start to introduce the changes in official (trunk) code starting from the core changes and ending with the API. Introducing these features will make the code UNSTABLE which will stabilise with time and bug fixing
- BUG FIXING: To stabilise the code
These steps are to be reiterated at each new feature to introduce.
All these step have to be OFFICIALLY supported, the first two do not even need to change a line of code but without that the stabilisation of a feature is just impossible.
Now the branch is just something more than a proof of concept, there is no planning at all, or at least i have not found any, so nobody have an idea on what is needed and how to do it.
All the work is done by individuals, each one with his own vision, obviously, on what is needed and what can wait.
An example of that is the VNSI/XVDR debate which ended with the XVDR addon not to be supported or included in semi-official XBMC PVR builds loosing the functionalityes it have.
It is not a fault of Pipelka becouse he just "did what he wanted to", and it is not a fault of Dushmaniac (or XBMC developers in general) becouse he could not support it, either way we do not have an official advanced VDR addon (VNSI is all but advanced) and probably will never have it.
Dushmaniac is doing a lot of work but it looks like he is "alone" and not supported by the rest of the developers comunity.
I know that developers are not pyed in any way to work on a particular feature or piece of code so each developer work on "what he likes to", but it is nontheless true that PVR is THE MISSING FEATURE of XBMC.
So, anyone who loves XBNC as I do, should be happy to work on that and probably WILL, looking at the number of people and work present in this section of the forum.
What is missing is clear idea of what to do and how to do it in order to have PVR functionalityes in XBMC.
After my "rant", i really enjoy the slick interface of XBMC, its features and the way content are presented BUT, i am thinking of moving away from all these goodies in order to have some feature i really need:
- Live TV
- Timeshift
- Advanced Recording Timer
- Good EPG support
Ok, the interface will be not so beatifull, the content will not be so rich of linked data etc., but it will do what my htpc is meant to do: be an easy and complete interface to my content (live or stored).
Makka
Posts: 3,025
Joined: Sep 2011
Reputation:
255
DDDamian
Team-XBMC Developer
Posts: 3,025
Grouchiest thread I've seen in a while......sheessh
System: XBMC HTPC with HDMI WASAPI & AudioEngine - Denon AVR-3808CI - Denon DVD-5900 Universal Player - Denon DCM-27 CD-Changer
- Sony BDP-S580 Blu-Ray - X-Box 360 - Android tablet wireless remote - 7.1 Streem/Axiom/Velodyne Surround System
If I have been able to help feel free to add to my reputation +/- below - thanks!
Posts: 24
Joined: May 2012
Reputation:
0
These changes in the road map really don't worry me too much.
I have been running MePo for a number of years on our main living room HTPC and am in the process of moving over to XBMC PVR (NYXBoard Hybrid remote is in the post!!!)
I've been using the PVR builds on my own machine for ages and already there are a couple of features that MePo doesn't support (yet):
- 'Coloured' EPG guide (probably going to be in MePo 1.3)
- Filter by channel name
- Really fast channel changes (seems quicker than MePo)
- Group Management built into the GUI
Yes, the advanced record features are missing but I generally only record films so this isn't a problem.
Also, time-shifting will be great but being able to pause the buffer is enough to make a phonecall or grab a drink, so it's not a problem.
Also, just because it isn't going to be merged for the next release doesn't mean the development will stop.
I've been using the MePo Sky EPG SVN build for the whole time I've used MePo and this hasn't been a problem at all.
Posts: 4,132
Joined: May 2004
Reputation:
4
sho
Team-XBMC Member
Posts: 4,132
The roadmap is in no way a promise of features, it's written by people like me that couldn't code their way out of a paperbag.
Also things change, live with it. (And btw this is a free world, use whatever software you feel is right for you).