Forum Replies Created

Page 88 of 215
  • Daniel Low

    May 6, 2009 at 7:30 am in reply to: Confused over streaming compression settings

    [Chris Blair] ” while true streaming feeds the video in real-time to end users (often called Video on Demand or VOD”

    Not quite, VOD has nothing to do with this, VoD is simply a type of service and can use either type of delivery method.

    [Chris Blair] “When they’re both done correctly, end users usually don’t see a difference between the two, as they both play the video as if it’s in real-time. “

    Progressive downloads will generally always be higher quality. Full HD can be delivered easily by progressive download, that’s nearly impossible for most people via RTSP.

    [Chris Blair] “Progressive download will start playing after only a few seconds of video has downloaded and continues to play as long as the download stays ahead of playback.”

    Not quite, the time it takes for the clip to start to play is based on a combination of the viewers connection speed, the size of the file, and the length of the clip .

    __________________________________________________________________
    Two years from now, spam will be solved. – Bill Gates, World Economic Forum 2004

  • Daniel Low

    May 6, 2009 at 6:55 am in reply to: Confused over streaming compression settings

    There are a few major differences between Progressive Download and Streaming.

    Progressive Downloads can be delivered from a normal webserver via HTTP
    Streaming requires a dedicated streaming server and uses RSTP (Real Time Streaming Protocol)

    Progressive Download saves a file to the viewers hard drive, as such it’s very difficult to stop that file being copied.
    Streaming delivery saves nothing to the hard drive.

    With progressive download, you as the content creator, or owner controls the quality of the picture, users on all types on connection speeds see the same quality picture. Those on slow connections have to wait longer before they can start playing the video.

    With streaming, the quality of the picture is determined by the viewers connection speed, those on slower connections sometimes see little more than digital soup, or if they do get a picture it seems more like a sequence of pixilated stills.

    Progressive download is not suitable for long clips. say over 15 minutes
    Streaming is suitable for long clips, even full length movies.

    Most Flash delivery is progressive download.

    VoD, or Video on Demand can be either.

    Compressing for each is roughly the same only that when compressing for Streaming you have to pay strict attention to realworld bitrates. If for example you are targeting users on a 500kb/s connection, you wouldn’t want the total datarate (audio & video) of your video to go over 425kb/s. With progressive download that could be as high as 1500kb/s.

    When compressing for progressive download you can use CBR or VBR rate control, with streaming you can only use CBR.

    There’s much more, but those are the basics.

    Hope that helps.

    __________________________________________________________________
    Two years from now, spam will be solved. – Bill Gates, World Economic Forum 2004

  • Daniel Low

    May 5, 2009 at 10:32 pm in reply to: Compressor Tips

    Digi Beta is lower field first. compressor should be able to detect the field dominance/order of your Quicktime clips

    __________________________________________________________________
    Two years from now, spam will be solved. – Bill Gates, World Economic Forum 2004

  • Daniel Low

    May 5, 2009 at 4:03 pm in reply to: Compressor Tips

    Check this this thread, especially the last post:

    https://forums.creativecow.net/thread/98/871887

    Check what version of the driver software you have.

    It’s always best not to switch field order unless the output format is the opposite order from your source format. What source format are you capturing from?

    __________________________________________________________________
    Two years from now, spam will be solved. – Bill Gates, World Economic Forum 2004

  • Daniel Low

    May 5, 2009 at 2:19 pm in reply to: Confused over streaming compression settings

    If you deliver the download files as Flash (F4V) then you’ll find a load of useful information here:

    https://www.adobe.com/devnet/flashcom/articles/dyn_buffering.html

    or

    https://www.betriebsraum.de/blog/2007/02/27/flash-video-tip-1-calculating-an-optimal-buffer-size/

    __________________________________________________________________
    Two years from now, spam will be solved. – Bill Gates, World Economic Forum 2004

  • Daniel Low

    May 5, 2009 at 7:46 am in reply to: h264 versus MPEG1 (really)

    Sorry if might come across as arrogant, rest assured I speak to everybody with this tone.

    Chris, thanks for following me around, picking up the pieces and feeding off my scraps. 😉

    __________________________________________________________________
    Two years from now, spam will be solved. – Bill Gates, World Economic Forum 2004

  • Daniel Low

    May 5, 2009 at 7:40 am in reply to: Confused over streaming compression settings

    [Chris Blair] “then he’ll have to live with the fact that likely half his audience will have buffering issues during playback. “

    Depending on what format you are delivering, there are ways of calculating the viewers connection speed and tailoring the buffer settings to match there are loads of resources that will explain how to do this, most for Flash, which should be fine for David/Dan

    __________________________________________________________________
    Two years from now, spam will be solved. – Bill Gates, World Economic Forum 2004

  • Daniel Low

    May 4, 2009 at 10:42 pm in reply to: h264 versus MPEG1 (really)

    [Mike janowski] “(It seems that I’ve seen this when playing back mpeg movies in QT Pro…I notice that there’s a “playback frame rate” item which doesn’t often hit the full 24 or 30 fps which I think it should…)”

    [Mike janowski] “It is. Playback anywhere is not the problem. Accurately finding looping points is. “

    Your first post was obviously unclear. You first talked about not hitting frame rates, now ‘looping points’ are the issue. (BTW – Don’t use QT Pro to accurately report frame rates).

    Maybe I should question your GOPs, or how often you like to set an I frame?

    [Mike janowski] “it too has problems interfacing with our software engine”

    Shouldn’t that be that your ‘software engine’ has problems interfacing with the output it generates? After all, MPEG-1 is an ISO dating back to 1988, you need to work to it, not it to you.

    [Mike janowski] ” an short declarative like “He’s wrong” really doesn’t provide me with the detail I need to solve this problem.”

    What else can I say!? he says “that any mp4-base codec isn’t working because it doesn’t use a fixed frame rate, and thus it gets bogged down when trying to locate start and end point of loops”.

    He’s wrong. Maybe he should figure out how often you set I frames.

    [Mike janowski] “I appreciate that you’re busy and don’t know me from Adam Ant, but if you’re gonna waste your time answering, make it worth both our whiles.”

    I’ll answer you in the most succinct way I know, usually. I don’t waste my time here answering questions, I do it out of the goodness of my heart. If you don’t like it, well, I’ll happily give you a refund.

    Thanks.

    __________________________________________________________________
    Two years from now, spam will be solved. – Bill Gates, World Economic Forum 2004

  • Daniel Low

    May 4, 2009 at 9:25 pm in reply to: Confused over streaming compression settings

    David? Dan? I’m confused.

    More confusion:

    There’s streaming and there’s progressive download. Many confuse the two.

    YouTube is progressive download, sometimes called ‘HTTP streaming’

    Flash (in 95% of cases) is progressive download.

    Therefore, regardless of connection speed, all people see the same video at the same quality only that those on slower connections need to wait longer for the clip to buffer/download before it will play.

    If the clip is stuttering, wait until it has downloaded more and then play it back. If it still stutters then your computer is simply not capable of playing it back properly.

    @Chris:
    “As an example…we have workstation class computers at our facility, most with at least dual processors and several gigs of RAM…along with a T1 line. Yet if only one person is on the internet, we have a hard time playing YouTube HD files without buffering, pausing and stuttering…regardless of the power of the workstation. ”

    T1 is only 1500kbps, as Craig pointed out, YouTube HD is approx 2000kbps

    “At home I have a pretty standard cable connection and a 4 year old laptop with 512MB RAM…yet I can play YouTube HD video without issue. ”

    Your cable connection is likely to be faster than the T1, even with contention.

    For a proper HD experience, regardless of connection speed (but requiring a semi powerful computer at least) this is the ultimate:

    HD/a>

    Like with youtube, these are progressive download so you can view them even on a 56k connection. You’ll just have to wait.

    __________________________________________________________________
    Two years from now, spam will be solved. – Bill Gates, World Economic Forum 2004

  • Daniel Low

    May 4, 2009 at 9:00 pm in reply to: h264 versus MPEG1 (really)

    [Mike janowski] “which MPEG1 won’t do regardless of bit rate”

    This will do MPEG-1 HD

    https://www.digigami.com/megapeg/

    [Mike janowski] “But my programmer says that any mp4-base codec isn’t working because it doesn’t use a fixed frame rate”

    He’s wrong

    [Mike janowski] “I notice that there’s a “playback frame rate” item which doesn’t often hit the full 24 or 30 fps which I think it should…) “

    Perhaps your computer is not capable of playing back the HD content you have created.

    __________________________________________________________________
    Two years from now, spam will be solved. – Bill Gates, World Economic Forum 2004

Page 88 of 215

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy