Has anything been done with this, would be very useful about now.
I found that for a video tag in HTML5 you can't use
v.currentTime = 0;
to seek. I'm going to experiment with removing and re-adding a video tag into the DOM to see if this allows for restarting a video. If this was to work you could add it in hidden, wait x seconds and then show it. A dirty workaround but I've found I've had to do a lot of those up to yet.
So, did anybody come up with a solution to set currentTime=xx or even to set star position at all?
e.g. Almost any client has support for video.mp4#t=12 hash on the url, but not brightsign?
We plan to implement seek command in 4.8 firmware branch. Sorry, I don't currently have the date of its availability.
Has this been fixed yet? The latest firmware version I see for XD2 series is 6.2.94, but as far as I can tell, seek still doesn't work. I'm trying to position a HTML5 <video> by setting its currentTime to a value. When I do so, it seems to jump to a "random" position. I.e., nowhere near where I tell it to go. For example, if I tell it to go to 0.5, it typically ends up somewhere around 11-14 seconds.
Is it possible this behavior is affected by how the video is encoded?
Does anyone know if this has been improved/fixed in the newer generation of players?
-JM
We didn't use it with an html5 videotag so far, but roVideoPlayer does have a seek method and when we used it for tests it perfectly worked. http://docs.brightsign.biz/display/DOC/roVideoPlayer#roVideoPlayer-Seek(positionAsInteger)AsBoolean only mentions that you have to either use an MP4 oder MOV container for the video, which we always do, so I cannot be more specific on its limitations.
We're limited to using the HTML5 <video> tag due to other reasons. But since it works for roVideoPlayer, I would think it's just an oversight/bug that it still doesn't work for <video>. It would be interesting to learn whether this is something they want to fix, or if it is already fixed in the new generation of players.
Yes, MOV and MP4 are essentually the same container formats. And encoding is for HD almost always H.264 these days (or H.265 for 4K). I was thinking more around encoding parameters such as CBR/VBR, GOP structure, "Fast Start" (as it is called iin MOV containers) or similar, which may affect the ability to seek in videos. But since seeking works in roVideoPlayer, it seems the basic support for this is already in the box. It's just a matter of making it accessible also from the HTML5 side of things. I don't see it listed anywhere as a "known limitation" for the HTML5 support either, so I find it odd that it doesn't work out of the box already.
-JM
Can't find what you're looking for?
Contact support