Alex Gollner
Zone 2, North-west, London
alex4d.wordpress.com
I'm an editor and ideas man.

I use Vimeo primarily for doodles, sometimes for production (private videos) and to show some of my work (some private, some public).

Recent activity

  • Video comment
    2 months ago
    Alex Gollner commented on You Can Be My Friend

    More popping bubbles!

  • add_tags
    3 months ago
    Alex Gollner tagged Final Cut free plugin demo: Text Crawl with:
  • add_tags
    3 months ago
    Alex Gollner tagged King of Snake - New York style - iPhone version with:
  • Forum comment
    4 months ago
    Alex Gollner commented on Preflight upload, preflight encodes: if need be provide warnings

    Cool. Looking forward to new developments!

  • Forum comment
    4 months ago
    Alex Gollner commented on Preflight upload, preflight encodes: if need be provide warnings

    There seem to be many reasons why people are having problems with uploading and encoding. With uploading, people are using older versions of Flash than you recommend. They are using browsers that don't seem to like your uploader. They are using their browser and internet link for other work during the upload. You have two options, make your uploader more robust. As you probably don't have enough money to make that happen, it would be a good idea if your uploader did some environment tests before starting a long process. Then it could warn that the uploader doesn't work very well with this specific combination of plugin and browser. You could even fill the window with a warning if something causes the process to run slowly. When it comes to the encoding phase, I imagine most people are leaving their audio as 48kHz as they don't know how to change it. They might be using IMA 4:1. Others will have non-square pixels. If your encoder is very fussy, again you have a long-term and short term solution; long-term: make your system less fussy and serve your customers based on what they are able to supply to you, or short-term: add a pre-flight phase for your encoder. If people have not followed your exact recipe, provide warnings: "Checking your video" "Your audio stream seems to be 48kHz. The suggested sample rate is 44.1kHz" "Your video stream is encoded using Cinepak. The suggested encoder is H.264" "We will attempt to upload and convert your video, you also have the option to cancel and re-submit with these suggested changes" Imagine how useful it would be if the encoder could have a look at the header once it has uploaded instead of waiting until hundreds of megabytes have been uploaded (or eventually fail to upload). The encode preflight could happen minutes after the upload starts. I imagine the only reason you won't want to provide warnings is that marketing and PR people would rather not alert the majority of your users that people are having problems using your service. On the other hand, you might be able to convince them that honesty is the best policy and that hiding problems through obscurity isn't a good idea in the long run (not that I'm complaining about this extensive help forum and the regular visits, out of office hours, of staff members).

Advertisement

Contacts