Comments on: SharePoint Media Center Additional Play Functionality

By: Gerard Pinzone

Gerard Pinzone — Fri, 21 May 2010 19:13:39 +0000

To EndUserSharePoint:

I haven’t had the need to make any other changes other than what I posted in the comments for browser compatibility. The code to turn off the audio is already in the script in the article. I was just pointing it out to Rebecca. The last section in the article, “Stopping WMP audio after the iframe is closed,” explains how I did it, but it doesn’t specifically call out the code. It’s not really a Sharepoint issue; it’s a Windows Media Player / IE / JavaScript issue.

By: EndUserSharePoint

EndUserSharePoint — Fri, 21 May 2010 19:02:31 +0000

Gerard – Thanks for this. People have been asking for months. Do you have other customizations you’vre written that you’d like people to know about for this solution? Might be worth spending some time writing an article. — Mark

By: Gerard Pinzone

Gerard Pinzone — Fri, 21 May 2010 17:34:33 +0000

Look for the comment of “Override lytebox.js end function to stop video playback when closed” in the script posted. I overrode the “end” function of the Lytebox object to send the media player a “stop” command. I could have made these changes in the original lytebox JavaScript, but I did it this way to keep these customizations from affecting other pages using the lytebox script. The way to stop the playback is to run this when the lyteframe closes:

var videoPlayer = this.doc.getElementById(’lbIframe’).contentWindow.document.getElementById(’MediaPlayer’);
if (videoPlayer) {
videoPlayer.stop();
}

This assumes your windows media player’s object tag contains ID=”MediaPlayer” in it.

By: Rebecca

Rebecca — Fri, 21 May 2010 17:17:43 +0000

Is it possible to let me know what the fix was to get lytebox to stop playing the sound when you close it.

By: Gerard Pinzone

Gerard Pinzone — Tue, 20 Apr 2010 15:08:58 +0000

FileName is a column that contains the URL to the video file. The html file is referenced in the formula: “/sites/yoursite/yourlibrary/yourfile.html”

Just edit the formula to match the location and name of the html file.

By: DailyCreative

DailyCreative — Tue, 20 Apr 2010 14:54:49 +0000

Also, I’ve uploaded the html page to my document library. Is there anything else I need to do with it? I didn’t know if I need to include it on the site page or on a separate web part page some how.

By: DailyCreative

DailyCreative — Tue, 20 Apr 2010 14:31:06 +0000

Thanks. I am going to re-create my list from scratch to be sure. What about “FileName”? Is that a variable or is that meant to be replaced with the “title” of the video — as in the orignal version of the formula? Sorry – I am new to all of this….but learning quickly.

By: Gerard Pinzone

Gerard Pinzone — Tue, 20 Apr 2010 13:42:46 +0000

Make sure your column name match what’s in the formula. If not, then change the formula to match what you have. Do you have width and height columns?

By: DailyCreative

DailyCreative — Mon, 19 Apr 2010 20:58:17 +0000

I am unable to get the concatenate formula to work. I get an “refers to a column that does not exist” error message. Besides the URLs for the path to the HTML, the “play” and “download” images, does anything else need to be change specific to my environment? Does “FileName” need to change too?

By: Gerard Pinzone

Gerard Pinzone — Fri, 26 Feb 2010 14:59:48 +0000

I’d like to add that the method used for media playback through lytebox in this article can be applied to non-SharePoint websites, too. It’s pretty much a drop in solution. The only additional work that would be needed would be to port the CONCATENATE formula to asp, php, etc. or to simply hard-code the html statically on the page.

After the article was submitted, I discovered Opera and WebKit browsers display a vertical scrollbar on the videos. This can be fixed by adding the line:

html { overflow: hidden; }

to the videoplayer.html file’s CSS section. Also, the CONCATENATE formula should use escaped ampersands. I’ve noticed a lot of websites generate the same kind of non-standard, but apparently perfectly functioning, URLs. If your concerned about W3C compliance, or if you’re just a perfectionist like me, do a search and replace on that formula before plugging it into SharePoint.