(though I'm not sure which one is correct - but they should match)


git-svn-id: file:///var/local/repositories/ffmpeg/trunk@610 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

  (how about making all headers in ffmpeg working this way ?)


git-svn-id: file:///var/local/repositories/ffmpeg/trunk@609 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@608 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@607 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@606 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@605 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@604 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@603 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

  requests. The current state is that at startup, WMP will get the
  best stream that it can handle. However, subsequent rate switching
  only puts a message in the log saying what the new stream ought to
  be. Solving this will be tricky. I guess that we would have to wait for
  key frames to appear in the new stream, and then switch over to it.
  Some care would be needed to deal with the PTS of the new stream
  versus the old stream.


git-svn-id: file:///var/local/repositories/ffmpeg/trunk@602 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@601 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@600 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@599 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@598 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@597 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@596 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@595 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@594 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@593 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@592 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@591 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@590 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@589 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@588 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@587 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@586 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@585 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@584 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@583 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@582 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

a higher priority than extensions. This gives FFM a chance of working. Note
that some of the other probe functions are bit optimistic, and can be
confused by binary data (such as 0x00 0x00 0x01 0xzz) for some values of zz.

This set of changes makes ffserver work again, and fixes the cannot open
video grab device message.


git-svn-id: file:///var/local/repositories/ffmpeg/trunk@581 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@580 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@579 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

* Make sure that the read buffer for the ffm file is allocated in the priv_data.


git-svn-id: file:///var/local/repositories/ffmpeg/trunk@578 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

  my pondcam streams for 24 hours! I'll bet he wasn't watching.
* Add code to allocate the priv_data so that the ffm header can be
  parsed again. [Fix crash]


git-svn-id: file:///var/local/repositories/ffmpeg/trunk@577 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

Helps track down bugs.


git-svn-id: file:///var/local/repositories/ffmpeg/trunk@576 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@575 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@574 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

  results then for -fPIC compilation - don't ask me why...


git-svn-id: file:///var/local/repositories/ffmpeg/trunk@573 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@572 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b

git-svn-id: file:///var/local/repositories/ffmpeg/trunk@571 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b