I wonder what the state of RealPlayer, HelixPlayer in generel, is. As you might now, the HelixPlayer or the RealPlayer in its current version, 1.0.something (or RealPlayer 10.0.x) was released in its first version almost three years (!) ago. As you can see in this list there have been minor updates but none of them is really important, judging from the changelog of the 1.0.8 release.
So for three years now nothing has been released in the player area. If you search the homepage for current development plans and roadmaps, you find for example the progress map for the Player version 2.x. Looks like last time someone did something in this area was 2005. Again, one and half year ago.
However, interesting in this case is that all plans are aiming for the Cayenne engine. To explain what Cayenne is: all HelixPlayers are powered by an underlying engine, called Helix DNA client. For HelixPlayer 1.x the engine was generation 1. The next generation engine, generation 2, is called Cayenne.
The Helix DNA client is also used in other devices – and it is actively developed. Not only was the development of Cayenne finished, the project page does already list the next generation of the Helix DNA client, Atlas. According to the plans it was supposed to be finished at the end of December 2006 – and it was only delayed to that date because they wanted to include Windows Media stuff. Also, the development of the next generation, generation 4, has already begun.
On the other side, the HelixPlayer is still based on generation 1.x (which does not even has ALSA support). The only information I was able to find, hidden somewhere in the developer lists, was that in August 2006 the idea was still to release a player based on Cayenne because it is stable and Atlas “was just finished” at that time. Also there seem to be x86_64 and FreeBSD ports going on, but in the first case there is not even an official announcement about the topic.
So the picture I draw with all these information is that the development is focused on the Helix DNA Client – and that the HelixPlayer development is down to occasional fixes, some ports, and the aim to release a player “sometime” in the future. Sounds like an almost dead future to me
There is nothing bad about that because the Helix Community can focus as they want – if you want to change it, join there team. Nevertheless, if they are not going to release a new (as in 2.x) version of the HelixPlayer in the close future, they should make this clear, and communicate it to the people who hope (and build on this hope) that there will be a new release.
So, if its dead, just say it. Than everyone else can mark the HelixPlayer support as “legacy” and concentrate on the task to integrate something else instead of waiting.
Or, if it is not dead: please release a roadmap or some bits of information about the close future.
But before someone starts acting or ranting now (against me or the helix developers): keep in mind that I took all these listed and linked information from the homepage and the e-mail lists – I drew my conclusions from these information. It is possible that I overlooked something, or missed an important bit – or that the homepage is just outdated because everyone is preparing the next HelixPlayer release (I wish it would be like that)!
Btw., I also tried to shed some light on this topic by contacting a developer of the team by e-mail some days ago (got his e-mail address from the devel-list), but he hasn’t answered yet (too busy maybe).
If he replies I will of course post the information here.
I wrote an e-mail to the devel list. Let’s see if someone has time to answer it.