Beta 5 seems to run just as well as Beta 4 here.

Lief H.

Quick feedback on Beta 4

No problem in getting it up and running here.

Still the same sync problem on Android, but following your earlier post I have checked combinations of Flash/HTTP and internal player/MX-player.
It seems the sync delay is related to the internal player used in my Android-client (Ver 2.0). When using MX-player instead, the audio is not delayed, and the sync is acceptable (maybe even perfect).
No difference between Flash- and HTTP-streams.

Web client and Enigma-TV Media Player works well here.

Leif H.

I have been testing beta 3 a bit tonight. My interest lie mostly in remote playing in Android and Windows, so I have not looked much into other functions.

The Windows Media Player now works nicely for me, both on Win 7 and n a new tablet with Win 8.1 which I set up today. Tested version is Enigma-TV_Media_Player_V2.0.0.0_Beta1_20140830
Same with Android, works well in a 4.4.2 device or an older 4.2 device.
The only thing I notice is a slight delay in audio vs video. Maybe 1/3 of a second in Android, hard to measure. In Windows, it is very close to 100% sync, but still I have the impression of a very tiny difference between video and audio.

I have not seen any problems with channel changing from any source, it works very well.

I have not tried the recording functions, since they are out of scope for me.

Leif H.

First impressions with V. 2.0.0.4 Beta 2:

No problems in setting up in Windows. Repeating the setup no problem for me.

Works very well from Android now. I ahve done around 40-50 channel changes with zap delay set to 0,2, and they all worked perfectly.

I notice a slight delay in audio vs video to Android, breaking the audio sync.

EPG does not show up in Android before at least one channel has been played, then doing a refresh of EPG. No problem for me, though. I just now noticed that a long press on a channel in the channel list will bring up the long EPG-text in a box. Nice touch!

I will have to leave my boxes for now, but I will try to do some more testing tomorrow.

This looks like a job well done, Sebastien!

Leif H.

I have done some testing of your new version, EnigmaTV server 2.0.0.4 Beta 1, EnigmaTV Android app version 2.0, and EnigmaTV Player for Windows.

I first installed the new server version on the Win32-machine where I already hade the earlier release-version (2.0.0.3) running. As I just copied the files from the zip to c:\EnigmaTV, it did not "install" as such, and therefore not taking the setup from my earlier installation. At first run, it downloaded vlc and (probably) the ZazouMiniWebServer, and the server program started OK.
It connected to my Dreambox (DM800 SEV2 with WebIF ver 1.7.5) without problems. I could operate the functions in the serverwindow without problems. When starting webserver (Internet control mode), I received C++ error R6034. By OK-ing this, a new R6034 popped up, all in all 4 times. However, the webserver then started, and I could reach it from my Android clients. If I remeber correctly, there wre no problems with changing channels from the Android.
At this time I left the testing, and when coming back to continue a few hours later, my Dreambox crashed when I tried to change channel. The Dreambox then did a soft reboot (restarting only Enigma, not the full Linux), the EnigmaTV tried again to change channel, new crash, and so on until I cancelled change on the Android. Following a full restart of all devices, same scenario. Trying to change port number, same result.

I then installed the EnigmaTV server on a Windows 2012 server, and there I did not get the R6034-error. Webserver started OK. Same problem with Dreambox crashing when changing channel from Android. No problem when changing channels "locally" in EnigmaTV's interface.

Since both the machines tried so far, were implemented in VMWare, I dug up a physical HP-box with clean new Win7/32-installation. Webserver started without error here, but still the same problem with changing channels.

The channel changing problem is not consistent. On all the three machines mentioned, I could do one or a number of changes successfully before a crash would happen. After the first crash, it seems it would always crash until program restarted (not quite sure here, if it was only server, only client, only Dreambox, or all three.) I can not tie the problem to any specific channel, it happens with different channels.

I have taken a look at the output in the debug window when debug is set to on, and as far as I can see, the URL's given there are exactly the same when it is initiated from locally, or when it is initiated from Android. However, when a change from Android leads to a crash in Dreambox, there is a delay between the debug output of the URL and the next lines containing VLC options.

The user/pwd and service reference in the URL in debugwidow are correct, as far as I can see.

I have not been able to get the Windows Player client to work with any of the setups I have tried. I does not connect at all, hanging with the "Settings"-box never closing.
However, using a connection in webbrowser directly seems to work fine, changing channels makes no problem there.

One particular thing I notice, is that there are lots of lines in the log (weblog?) available from the menubutton, all with this text (data/time varies, of course):
07.09.2014 19:49:07 : 07.09.2014 19:49:07 : Data at the root level is invalid. Line 1, position 1.
I can not see that there are any correlation between these and the times of crashing.

I hope this information can prove helpful for you. I have saved the information from debug window and weblog in files here, but I cannot see that they contain anything to shed a light on the problem. Let me know if you would like to receive them by mail.

I could set up a packet analyzer to capture the packets between the EnigamTV-server and the Dreambox, but as you understand, this takes a bit of work to set up. In worst case, if you are unable to recreate these crashes, I might consider setting up a remote access to the devices for you. Let me know if you cannot see any reason why this crash only happens when changing channels from Android, and then we can discuss how I can best help you.

Kind regards from Norway,
Leif Henriksen