I went through the guide and have WebMediaPortal as an application running on my "Default Web Site" but still get 404 errors. I've tried restarting IIS and MPExtended services to no avail.yes, if u have IIS already then use MPextended as usual and then use the WebMediaPortal for IIS Edition for access =)
It didn't help here...Oh yeah it also appears to work better if you change to the encoding profiles to "ultrafast" on the mq->HQ profiles in streamingprofiles.xml
I don't have a problem with it. You can try to set the fps=25 option in the transcoder profile, that seems to have helped some people with similar problems.Is anyone able to stream 1080i live tv smoothly to a windows machine (using any Flash profile available)? I can watch any SD and 1080p HD file just fine, and also SD livetv... but 1080i channels stutters badly (the effect would be as low fps I would say)... deinterlacing problems may be? I discard performance problems in either server or client machines. Server doesn't reach 100% at all, and I've tested in 2 different laptops as clients.
Thanks a lot.
No, not possible. I've explained quite some times that there's no suitable codec and container combination supported by HTML5 (search for it if you're interested).IWhat about HTML5 Oxan? Is it even possible with windows inside Webmediaportal?
No, not at the moment. Might be added to 0.6, thanks to @DieBagger.Is there a way to enable seeking when in VLC Direct mode?
Yeah, that's supposed to happen when you use the IIS edition. Do you still need to get the IIS Express edition working or is it ok now?EDIT: OK, it looks like I can access it by going to http://192.168.1.99/WebMediaPortal, rather than http://192.168.1.99:8585. I guess it doesn't really matter if it's accessed via the standard 80 web port?
Seems to be working fine, thanks.Yeah, that's supposed to happen when you use the IIS edition. Do you still need to get the IIS Express edition working or is it ok now?EDIT: OK, it looks like I can access it by going to http://192.168.1.99/WebMediaPortal, rather than http://192.168.1.99:8585. I guess it doesn't really matter if it's accessed via the standard 80 web port?