Help With Video Settings and Placing on Web???

Discussion in 'Professional Video Production' started by Dan Williams, Jul 31, 2005.

  1. Dan Williams

    Dan Williams Guest

    I am new to videos and creating web pages. I just recently got engaged,
    therefore thought it would be cool to put the video that was shot of it on
    the web. I am currently using Roxio 7 and am on Comcast. I have a couple
    of questions that I am hoping someone could help with or point me to a good
    source as my search has not been very successful.

    I have placed the video on the web server. Linking to that location
    results in the video downloading and playing. How do you set up so it will
    stream? What is the pros and cons of streaming a video? Do you have to
    save in special format to make this possible?

    What should you do to accommodate your dial-up users?

    Roxio has a ton of different format settings to save the file in. What is
    recommended for the web? Should you have a couple of different options
    (high-speed and dial-up)? I understand the basic types... such as AVI,
    MPEG-2 and WMV... but there are a number of Windows Media Video 8 in Roxio
    followed by different kbps amount. Is this something special for streaming
    or just means version 8 codec?

    Side question... there are MPEG-2 settings in which frame size is slightly
    bigger, but the frame per seconds is slightly less. Why would you want to
    pick one over the other (320x288 25fps vs 320x240 29.97fps)? Is there
    anywhere that really explains all the Roxio settings in which you can save
    in?
     
    Dan Williams, Jul 31, 2005
    #1
    1. Advertisements

  2. In general you can 'embed' one of the media players (WMP, real,
    quicktime) into a web page and tell it where to find the video. It
    won't then download all the clip, the player will try to start playing
    when it thinks it has enough of the clip to play without buffering.

    Embedding code for media player might look like this :

    <object id="MediaPlayer"
    classid="clsid:6bf52a52-394a-11d3-b153-00c04f79faa6"
    type="video/x-ms-wma" width="352" height="328">
    <param name="autostart" value="true" />
    <param name="stretchtofit" value="true" />
    <param name="url" value="http://path/to/your/video.wmv" />
    <param name="uimode" value="mini" />
    <param name="windowlessvideo" value="true" />
    <object id="MediaPlayer2" type="video/x-ms-wma" width="352"
    height="328" data="http://path/to/your/video.wmv">
    <param name="filename"
    value="http://path/to/your/video.wmv" />
    <param name="showcontrols" value="0" />
    <param name="animationatstart" value="0" />
    <param name="transparentatstart" value="0" />
    <param name="showaudiocontrols" value="1" />
    <param name="showtracker" value="0" />
    <param name="showdisplay" value="0" />
    <param name="showstatusbar" value="1" />
    </object>
    </object>

    That'll work for some AVIs and MPEGs and anything in .WMV .ASF format.
    If you need Quicktime code, post back and I'll add that to the thread.

    Obviously, adjust the width and height of each object to match your
    output video, set the http://path/to/your/video.wmv to your real file
    path - best to include the whole path to the video rather than a
    relative path.
    Buffering. Server bandwidth (if paid for). Unable to 'rewind' or
    'seek' if stored on a web server. Otherwise, I don't know - you need
    to ask a more specific question - what's on your mind ? Storing a
    video on a web server isn't streaming, it's a long-term file download
    via the browser - there's a distinct limitation in what you can do -
    but it's cheaper and in many cases, adequate.
    Not necessarily. Many videos will benefit from being indexed (WM) or
    hinted (QT), but make sure it's quite well compressed or your users
    wil get a lot of buffering makking the clip unwatchable. Always
    provide a download link for people who can't play it reliably.
    Buy them each a broadband connection for xmas ? Otherwise, encode at
    QCIF size : 176x144x6fps (about 20kbps) with 22khz, 16kbps mono audio.
    I'd try 360x240 or so at 15fps and see if it's watchable on a 512kbps
    broadband. If it is, you might be able to go up to full screen. 25fps
    is probably wasted on the web, it's not going to be hollywood quality
    video, is it ;-))

    AVI and MPEG-2 are usually not compressed enough to send over the web.
    AVI is just a container though, so you can use say DivX compression to
    get a lot smaller file size. Not everybody has DivX codecs on their
    machine.

    Don't bother with MPEG2, though MPEG4 might be worth a go if your
    viewers have Quicktime or an MPEG4 decoder in another player. H264 is
    about the best, but it needs Quicktime 7 which has a very small
    install base right now (it also needs a *very* fast machine to encode
    it, but the results are excellent and the file sizes quite a lot
    smaller than an equivalent MPEG4)
    Pick WMV9 codecs wherever possible, not everybody has codecs for
    version 8, and the WMV9 codecs are significantly more efficient
    (though as a result, slower to encode the content)
     
    Neil Smith [MVP Digital Media], Jul 31, 2005
    #2
    1. Advertisements

  3. Dan Williams

    Mark Burns Guest

    The general rule for placing video on the WEB is to make it short,
    short, short, and to the point.

    For this discussion here, I will assume that be streaming video that
    you mean real time playing on one computer from a server computer.

    Streaming video requires cooperating computers at each end to send and
    receive video/audio signals. For example, using a web cam, one
    computer is sending data to the receiving computer, and in turn
    becoming the recieving and sending computers. This is simple for point
    to point.

    For a server situation, the host server must be sending a/v frames from
    itself to the client computer, generally via a web browser. There is
    no standard for this built into all web browsers however, this is done
    with ActiveX or Java run time software on the client and host
    computers. This predisposes the need for understanding the nature of
    your client, ability to install software from the server, etc... Too
    much of a hassle unless one is selling the Naked News or something like
    that. Most use dedicated servers for this.

    Much better for the rest of us to use small mpeg files. In the case of
    a wedding video, I would suggest things like the bridal walk, vows,
    cutting the wedding cake, grooms toast, father daughter dance each on a
    short 1-2 min video. WEB viewers will really like that better, imho.

    Also consider taking the still photos and putting them to music into a
    2-3 minute mpeg video looks great. If you have enough for 4-6 min,
    make two videos. Be careful of copyright here on the music, as you
    will be a broadcaster. The video will be well compressed, as there
    will only be about 2 I-frame's per second. I generally use a four
    second display.

    I use 352X240 @29.97 fps. Keep it small for quick download. For the
    web, it really doesn't matter as long as you keep the aspect ratio
    comparable. The PAL standard is 25 fps, the NTSC is 29.97. The
    reason for these differences has to do with their broadcast history's,
    not that one is better or worse than the other. As far as I know, all
    PC's play both standards well.

    I also use Womble mpeg-vcr to recode my DVD 720x480 videos to the
    352x240 size. One should use mpeg-2 with a 4000 max vbr and 192 mpa
    audio sampling.

    AVI should be used for embedded mpeg files. (Remember that AVI is just
    a container. It can contain mpeg-2). I generally just use mpeg-2
    files referenced that play in whatever the user has referenced to mpeg.
    On my computer it is Windows Media Player. It used to be Real Player.
    Six of one, ...

    Cheers and congratulations...

    ..
     
    Mark Burns, Jul 31, 2005
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.