Ok. Thanks.

If you can't find an error, pleas let me know, and I will try to describe the steps to reproduce the problem.

I will check if there is an error in the script.

Quote:
The index_local seems to help only temporarily (for the first channel selection) in keeping the connection really local.

If I switch to another channel, I see again my public ip displayed in the stream.

Hey nice tests what you did !
I will do the same on my side and if the newest mongoose 3.7 gives a better result then I will include it in the next release.
Many thanks for your feedback, I appreciate.

Best regards,

Ok. That's good to hear!

Nonetheless I tried something; updating Mongoose webserver to the latest version (3.7), and set time out to 2500msec (no idea if the last one indeed does help).

Result:
- NO delay anymore while logging in (instant!). This was 5-10 seconds!
- Hardly no delay anymore after selecting the provider and able to select channel. This used to take up to 30 seconds!
- Delay from channel selection to showing the stream is now sometimes as fast as 10 seconds! Most of the times however around 20 seconds.

So no more channel change times of 30-60 seconds for my setup.

This all still sounds weird to me, but I'm very happy!
Streaming over WiFi, including HD channels is possible now (not supported by VU+ IOS app), the problems with sound on HBO channels on IOS is history, and even streaming over 3G works very good.

Keep up the good work

Hi,

Correct, so there is no issue regarding your setup.
All seems to be normal.

Best regards,

Thanx for some of the answers.

I did some extra testing on the server itself and timed response (logon), zap & stream speeds.

I get the idea that something polls in 5sec intervals orso:
= Logon takes 5, 10 or 15 seconds to complete
= If I select a channel, I get the following intervals:
-- Select channel -> ETV shows zap to: 5, 10 or 15 seconds
-- From zap to, to streaming: 5 or 10 seconds
-- From streaming to show epg: 5 seconds
-- From streaming to actually playing stream on webif: 10 seconds.

So even locally, it can take 15+10+10 = 35 seconds between channel selection and actually showing the stream!

I forgot something :
You can call the web media player from inside of your network or externally.
Inside with http://ipOfYourPC:localPort/index_local.html
Outside with http://ipOfYourDSL:publicPort/index.html

Best regards,

Hello,

Thanks for you questions
When you are using the web media player feom your iPad, the profiles are automatically selected by the device itself. For an iPad it is considered as a computer if i'm right ...
But this is not the most important.
What is important is to set the video & audio parameters from the settings tab on the web interface (not within the tool on your PC)
The slow response just wonder me : it should take less than 10 seconds to detect a channel change.
Then on iOS devices (like iphone or ipad) the start of a stream can take about 30 seconds because of the video convertion and cash generation), this is normal.
If it takes more time then I would suspect something is weong on the network.
The profiles are just a way to define mutliple set top box into the app, so you can switch from one device to the other.

Best regards,

I'm using Enigma-TV for a few hours now.

My system consists of a VU+ Solo2 (LAN), a server (i5-3570K CPU/8GB ram) running WHS2011 (LAN) and some iPads (WiFi).

Enigma TV is installed on the server of course

Questions / Problems:
- One can define a Profile. What is the use of profiles? I defined two of them (SOLO2 and SOLO2-Mobile), but I can't select them from the iPad.
- I defined the profile iPhone in the SOLO2-Mobile profile, but once connecting from the iPad it shows Computer again, and I can't change that again...
- Streaming seems to be using my EXTERNAL IP, instead of the local network. Why?
- For some reason, logging in and zapping is in most cases E-X-TREMELY slow. It can take 30-60 seconds before any response is seen on the iPad. Looking at the Enigma TV app on the server, I sometimes see a delay between selecting the channel on the iPad and the app showing "Zapping to..." of 30 seconds or more, which seems to explain why zapping is so slow... Timeout or something ???
- I disables firewalls on my server to make sure that that can't be the problem...

The slow UI is currently the most annoying part, so I hope someone has a solution to this...