Hi Matt

We've got a lot of video as texture in on sfmoma.org, on the homepage and 
exhibition pages for example, and at the time we were developing it, a service 
like Brightcove made that possible. I'd like to be able to replace it, however 
it's so baked into our workflows and content syndication that we're staying 
with it.

If we decided today, I think we'd look elsewhere.

Keir

-----Original Message-----
From: mcn-l-boun...@mcn.edu [mailto:mcn-l-boun...@mcn.edu] On Behalf Of Matt 
Morgan
Sent: Friday, July 07, 2017 12:33 PM
To: mcn-l@mcn.edu
Subject: Re: [MCN-L] Managing and storing video content for website

Like SFMOMA, I've used Brightcove before, but I think the reasons to do so are 
getting really skinny ... it's super expensive and only does a bit more than a 
$20/month Vimeo Pro account (as far as I know).

Keir, do you think if you made the decision today, you would go with 
Brightcove? Why?

Thanks!
Matt

On 07/07/2017 12:42 PM, Keir Winesmith wrote:
> Hi Lisa
>
> We use Brightcove as our video CDN, and in-page player for videos on 
> sfmoma.org. It's fine, the CMS is pretty straightforward and it's players are 
> easily templated.
>
> We put made-for-YouTube videos on YouTube.
>
> We store non-public video, b-roll, etc. on our DAMS (NetX).
>
> Hope that helps.
>
> Keir
>
> Keir Winesmith
> Head of Web and Digital Platforms
>
> San Francisco Museum of Modern Art
> Don't miss Edvard Munch: Between the Clock and the Bed, June 24 - Oct
> 9 Tickets available at SFMOMA.org
> 415.357.2871
> kwinesm...@sfmoma.org
> 151 Third Street | San Francisco, CA 94103
>
> This message, together with any and all attachments, is intended only for the 
> use of the recipient(s) named above. It may contain information that is 
> privileged and confidential. If you are not the intended recipient, you may 
> not review, copy or distribute this communication. If you have received this 
> communication in error, please notify the original sender by email and delete 
> the message, along with any attachments.
>
>
> -----Original Message-----
> From: mcn-l-boun...@mcn.edu [mailto:mcn-l-boun...@mcn.edu] On Behalf
> Of Susan Edwards
> Sent: Friday, July 07, 2017 9:30 AM
> To: Museum Computer Network Listserv <mcn-l@mcn.edu>
> Subject: Re: [MCN-L] Managing and storing video content for website
>
> Lisa, I am interested in this as well and will follow responses. If you get 
> off-list responses I'd be interested to know what they say.
>
> If it helps, when I was at the Getty, we used the Akamai hosted streaming 
> service. But it was not the most user-friendly option. At the Hammer we post 
> to Vimeo, YT, and Livestream and embed. This is fine for presentation.
> But not so great as a managed storage solution.
>
> Susan Edwards
> Associate Director, Digital Content
> Hammer Museum
> 10899 Wilshire Blvd
> Los Angeles, CA 90024
> sedwa...@hammer.ucla.edu
> 310-209-7921
>
> On Jul 7, 2017 5:52 AM, "Goble, Lisa" <go...@frick.org> wrote:
>
>> Hello All,
>>
>> I'm interested to know what other institutions use in terms of
>> managing and storing video content on their websites (rather than
>> embedding from a video sharing site like YouTube, Vimeo, etc.)  It
>> seems like we can go with a few different options. Are you using CDNs 
>> (Content Delivery Networks)?
>> Cloud-hosted video solutions? Self-hosted? What works best? We are
>> using Drupal.
>>
>> Many thanks!
>>
>> Lisa Candage Goble
>> Media Producer
>> The Frick Collection
>> 1 East 70th Street
>> New York, NY 10021
>> 212-547-6892
>> go...@frick.org
>> The information transmitted is intended only for the person or entity
>> to which it is addressed and may contain confidential and/or
>> privileged material. Any review, retransmission, dissemination or
>> other use of, or taking of any action in reliance upon, this
>> information by persons or entities other than the intended recipient
>> is prohibited. If you received this in error, please contact the
>> sender and delete the material from any computer.
>> _______________________________________________
>> You are currently subscribed to mcn-l, the listserv of the Museum
>> Computer Network (http://www.mcn.edu)
>>
>> To post to this list, send messages to: mcn-l@mcn.edu
>>
>> To unsubscribe or change mcn-l delivery options visit:
>> http://mcn.edu/mailman/listinfo/mcn-l
>>
>> The MCN-L archives can be found at:
>> http://www.mail-archive.com/mcn-l@mcn.edu/
>>
> _______________________________________________
> You are currently subscribed to mcn-l, the listserv of the Museum
> Computer Network (http://www.mcn.edu)
>
> To post to this list, send messages to: mcn-l@mcn.edu
>
> To unsubscribe or change mcn-l delivery options visit:
> http://mcn.edu/mailman/listinfo/mcn-l
>
> The MCN-L archives can be found at:
> http://www.mail-archive.com/mcn-l@mcn.edu/
>

_______________________________________________
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/
_______________________________________________
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (http://www.mcn.edu)

To post to this list, send messages to: mcn-l@mcn.edu

To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l

The MCN-L archives can be found at:
http://www.mail-archive.com/mcn-l@mcn.edu/

Reply via email to