HDMI encoder windows client

Get Help
1

Hi all, i’m testing ad hdmi video encoder and it works fine on android client but not windows.

The encoder make an output like http://ipaddress:port/main for http stream, another similar for hls stream and an rtsp output.

Format is H.264 TS.

On windows i can’t make it works… if i open one of those output in windows media player are played correcly.

I’ve also installed k-lite codec but no luck in windows player.

Why if i can play the url in windows media player, xibo can’t?

I’m using a region with the Hls module.

Thanks!

2

Could be good to enable auditing on the player and look at the Logs / player status window when it tries to play the HLS widget.

3

HTTP stream is not HLS. Android will be able to play that via the LocalVideo media type, but it won’t work on Windows. Windows can only show HLS streams.

4

Hi, my encoder setup show this:

hls
hls952×388 52.6 KB

So i should have an hls video, i’m wrong?

5

Here is my log, but i cant see nothing about the hls module…

Blockquote
2018-05-18 15:26:52RegisterAgentThreadPopulateFromXmlXML configuration for [UseCefWebBrowser] which this player doesn't understand.

2018-05-18 15:26:52RegisterAgentThreadPopulateFromXmlXML configuration for [ScreenShotRequested] which this player doesn't understand.

2018-05-18 15:26:52UI ThreadRegion - StartMediaStarting media

2018-05-18 15:26:52RegisterAgentThreadPopulateFromXmlUnable to write [Item].

2018-05-18 15:26:52RegisterAgentThreadPopulateFromXmlUnable to write [Commands].

2018-05-18 15:26:53UI ThreadRegion - SetNextMediaNodeNew media detected webpage

2018-05-18 15:26:53UI ThreadRegion - CreateNextMediaNodeCreating new media: webpage, 249

2018-05-18 15:26:53UI ThreadRegion - StartMediaStarting media

2018-05-18 15:26:53UI ThreadRegion - SetNextMediaNodeNew media detected ticker

2018-05-18 15:26:53UI ThreadRegion - CreateNextMediaNodeCreating new media: ticker, 250

2018-05-18 15:26:53UI ThreadRegion - StartMediaStarting media

2018-05-18 15:26:53RequiredFilesAgentThreadRequiredFiles - ReportInventoryReporting Inventory

2018-05-18 15:26:53UI ThreadRegion - SetNextMediaNodeNew media detected clock

2018-05-18 15:26:53UI ThreadRegion - CreateNextMediaNodeCreating new media: clock, 251

2018-05-18 15:26:53UI ThreadRegion - StartMediaStarting media

2018-05-18 15:26:53UI ThreadRegion - SetNextMediaNodeNew media detected image

2018-05-18 15:26:53UI ThreadRegion - CreateNextMediaNodeCreating new media: image, 252

2018-05-18 15:26:53UI ThreadRegion - StartMediaStarting media

2018-05-18 15:26:53ScheduleManagerThreadScheduleManager - RunSchedule Timer Ticked

2018-05-18 15:26:53ScheduleManagerThreadScheduleManager - IsNewScheduleAvailableLayouts in Current Schedule: [21] From 01/01/0001 00:00:00 to 01/01/0001 00:00:00 with priority 0. 2 dependents.

2018-05-18 15:26:53ScheduleManagerThreadScheduleManager - IsNewScheduleAvailableLayouts in New Schedule: [21] From 01/01/0001 00:00:00 to 01/01/0001 00:00:00 with priority 0. 2 dependents.

2018-05-18 15:26:56UI ThreadMedia - SignalElapsedEventMedia Complete

2018-05-18 15:26:56UI ThreadRegion - DurationElapsedEventMedia Elapsed: 53.jpg

2018-05-18 15:26:56UI ThreadRegion - SetNextMediaNodeMedia Expired:(852,192,482,0,image,) . Reached the end of the sequence. Starting from the beginning.

2018-05-18 15:26:56UI ThreadMainForm - DurationElapsedEventRegion Elapsed

2018-05-18 15:26:56UI ThreadRegion - SetNextMediaNodeNew media detected image

2018-05-18 15:26:57UI ThreadMedia - SignalElapsedEventMedia Complete

2018-05-18 15:26:57UI ThreadRegion - DurationElapsedEventMedia Elapsed:

2018-05-18 15:26:57UI ThreadRegion - SetNextMediaNodeMedia Expired:(96,41,679,4,clock,) . Reached the end of the sequence. Starting from the beginning.

2018-05-18 15:26:57UI ThreadMainForm - DurationElapsedEventRegion Elapsed

2018-05-18 15:26:57UI ThreadRegion - SetNextMediaNodeNew media detected clock

2018-05-18 15:26:59UI ThreadMedia - SignalElapsedEventMedia Complete

2018-05-18 15:26:59UI ThreadRegion - DurationElapsedEventMedia Elapsed: http%3A%2F%2F10.1.4.37%2Fcaller%2Fcaller4.php

2018-05-18 15:26:59UI ThreadRegion - SetNextMediaNodeMedia Expired:(422,676,0,857,webpage,) . Reached the end of the sequence. Starting from the beginning.

2018-05-18 15:26:59UI ThreadMainForm - DurationElapsedEventRegion Elapsed

2018-05-18 15:26:59UI ThreadRegion - SetNextMediaNodeNew media detected webpage

2018-05-18 15:27:03ScheduleManagerThreadScheduleManager - RunSchedule Timer Ticked

2018-05-18 15:27:03ScheduleManagerThreadScheduleManager - IsNewScheduleAvailableLayouts in Current Schedule: [21] From 01/01/0001 00:00:00 to 01/01/0001 00:00:00 with priority 0. 2 dependents.

2018-05-18 15:27:03ScheduleManagerThreadScheduleManager - IsNewScheduleAvailableLayouts in New Schedule: [21] From 01/01/0001 00:00:00 to 01/01/0001 00:00:00 with priority 0. 2 dependents.

2018-05-18 15:27:13ScheduleManagerThreadScheduleManager - RunSchedule Timer Ticked

2018-05-18 15:27:13ScheduleManagerThreadScheduleManager - IsNewScheduleAvailableLayouts in Current Schedule: [21] From 01/01/0001 00:00:00 to 01/01/0001 00:00:00 with priority 0. 2 dependents.

2018-05-18 15:27:13ScheduleManagerThreadScheduleManager - IsNewScheduleAvailableLayouts in New Schedule: [21] From 01/01/0001 00:00:00 to 01/01/0001 00:00:00 with priority 0. 2 dependents.

2018-05-18 15:27:17XmrSubscriberXmrSubscriber - RunConnected (tcp://10.1.0.22:9505), last activity: 18/05/2018 15:27:17

2018-05-18 15:27:24ScheduleManagerThreadScheduleManager - RunSchedule Timer Ticked

2018-05-18 15:27:24ScheduleManagerThreadScheduleManager - IsNewScheduleAvailableLayouts in Current Schedule: [21] From 01/01/0001 00:00:00 to 01/01/0001 00:00:00 with priority 0. 2 dependents.

2018-05-18 15:27:24ScheduleManagerThreadScheduleManager - IsNewScheduleAvailableLayouts in New Schedule: [21] From 01/01/0001 00:00:00 to 01/01/0001 00:00:00 with priority 0. 2 dependents.

2018-05-18 15:27:31ScheduleManagerThreadScheduleManager - RunThread Stopped

2018-05-18 15:27:31RegisterAgentThreadRegisterAgent - RunThread Stopped

2018-05-18 15:27:31RequiredFilesAgentThreadRequiredFilesAgent - RunThread Stopped

2018-05-18 15:27:31LibraryAgentLibraryAgent - RunThread Stopped

2018-05-18 15:27:31LogAgentLogAgent - RunThread Stopped

2018-05-18 15:27:31XmrSubscriberXmrSubscriber - RunSocket Disconnected, waiting to reconnect.

2018-05-18 15:27:31XmrSubscriberXmrSubscriber - RunSubscriber Stopped

6

Sure, so in that case you’d use the Windows Player on Windows 8.1 or newer, and the HLS module, and enter the url

http://ip.address:8100/main

Note however if you’re using 1.8.9, the HLS widget is broken, and you’ll need to apply the following patch to your CMS:

7

I’m under 1.8.7, i need to apply the patch?

8

No it shouldn’t affect 1.8.7

If you want to test the stream, you can do so on the Player device by opening the browser and going to https://video-dev.github.io/hls.js/demo/

There are presets that will show the HLS functionality works, and then you can also enter your local feed URL to test your local stream too.

9

Also tested with it but no video and no errors, the strange thing is why WMP can play that url but not in xibo?

10

WMP isn’t used to play streams as it isn’t possible for us to do that.

We use HLS.js.

If it can’t play the stream, then Xibo won’t be able to. At a guess, your streaming device doesn’t correctly send CORS (https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) headers to allow the system to work.

You could see if it’s possible to enable that on the device.

11

Thanks, we’re in touch with the encoder reseller to investigate about CORS, i’ll tell you in case of good news.