Archives by date

You are browsing the site archives by date.

Videos on websites

How videos should be sent (idealy)

  1. Videos should be sent in at the exact size/bitrate they want them and if not it should be sent in at a decent size (mpeg, mp4, h.264, wmv) so we can do a good conversion on it.  That means we’ll need to send the dimensions if we’re trying to fill a certain space in the site.
  2. For flash, videos do get a bit blocky at lower bitrates. I orginally did these BLH ones at 600 kbps, but since they want them sharper I ran them at the default of 1500 kbps even though it doubled the file size.
  3. If file size really matters its going to show in the video quality. Good balance might be around 1000 kbps for flash video.
  4. With html5 video we can get some better quality out of using (mp4, h.264)

I wonder if we should also have a set argument for youtube and/or vimeo? I haven’t looked at what these guys entirely offer, but I’m gonna make a few blanket assumptions…

  1. kinda industry standard as far as interface / processing / file types etc.
  2. handles all OS’s / devices in their own way. We just embed, throw in a prettyphoto, etc..
  3. user wants something better – they upload/set it as such. These guys can handle HD etc.
  4. We are no longer hosting giant ass Video files on our servers or the clients shit-ass server
  5. no conversion tools necessary on our part
  6. etc.

I’m guessing this wouldn’t be the solution 100% of the time, but I think we should spend a little time on discovery to maybe figure out what these services can provide – even if it were an upgraded acct, etc.? It would obviously save us time/energy – but I think we can also make an argument for it being better for the client in ways too.

All other inputers do so in comments section.

St Johns Abbey Cemetery

www.stjohnsabbeycemetery.com

C5, Custom admin for dead people, custom admin for news