Sur d’autres sites (9179)

• The Future of the VP8 Bitstream

  17 juin 2010, par noreply@blogger.com (John Luther) — vp8

  Recently we’ve seen software products such as VLC, FFmpeg, Logitech Vid, Flumotion and Tixeo adopting and using WebM and VP8 (the video codec in WebM) in exciting new ways.

  In addition to software developers, many hardware vendors have committed to shipping VP8-accelerated products based on our current bitstream in 2011 . Devices that use hardware acceleration for video are a very small percentage of overall web traffic today, but they are a rapidly growing segment of the market and our project must be mindful of these vendors’ needs. Given the longer lead times for changes in chipsets, hardware companies implementing the codec today need to be confident that it will be stable and supported as VP8 content proliferates.

  Like every codec, WebM is not immune to change ; the difference in our project is that the improvements are publicly visible, and compatibility and implementation issues can be worked through in an open forum.

  So, to maintain codec stability while also allowing for quality and performance improvements in VP8, we have added an experimental branch to the VP8 source tree. The WebM community can use this unstable branch to propose changes to VP8 that will produce the best video codec possible, but without the constraints of a frozen bitstream. At some point in the future, when the experimental branch proves significantly better than the stable branch, we will create a new version of the codec.

  Teams dedicated to improving WebM are actively investigating and evaluating new techniques, and are committed to do so for the long term. We encourage the WebM community to keep contributing as well. To learn more about the experimental branch and get involved, see our repository layout page.

  Jim Bankoski is Codec Engineering Manager at Google.

  

• The Future of the VP8 Bitstream

  18 juin 2010, par noreply@blogger.com (John Luther) — vp8

  Recently we’ve seen software products such as VLC, FFmpeg, Logitech Vid, Flumotion and Tixeo adopting and using WebM and VP8 (the video codec in WebM) in exciting new ways.

  In addition to software developers, many hardware vendors have committed to shipping VP8-accelerated products based on our current bitstream in 2011 . Devices that use hardware acceleration for video are a very small percentage of overall web traffic today, but they are a rapidly growing segment of the market and our project must be mindful of these vendors’ needs. Given the longer lead times for changes in chipsets, hardware companies implementing the codec today need to be confident that it will be stable and supported as VP8 content proliferates.

  Like every codec, WebM is not immune to change ; the difference in our project is that the improvements are publicly visible, and compatibility and implementation issues can be worked through in an open forum.

  So, to maintain codec stability while also allowing for quality and performance improvements in VP8, we have added an experimental branch to the VP8 source tree. The WebM community can use this unstable branch to propose changes to VP8 that will produce the best video codec possible, but without the constraints of a frozen bitstream. At some point in the future, when the experimental branch proves significantly better than the stable branch, we will create a new version of the codec.

  Teams dedicated to improving WebM are actively investigating and evaluating new techniques, and are committed to do so for the long term. We encourage the WebM community to keep contributing as well. To learn more about the experimental branch and get involved, see our repository layout page.

  Jim Bankoski is Codec Engineering Manager at Google.

  

• FFMPEG - infinite file video stream to RTMP server

  5 août 2022, par samoht9277

  I'm trying to create an infinite video stream that I can push to a local RTMP server.

  


  I believe it's worth mentioning that I'm not very good with ffmpeg, I started using it some weeks ago.

  


  Here is a similat question, but it doesn't fully answer what I need.

  


  What I tried

  


  At my first attempt, I made a bash script that spawned a new ffmpeg instance for each video I was trying to stream. I noticed that that the few seconds that takes to spawn the new instance interrupts the stream.

  


  After I noticed this problem, I decided to google some kind of queue system, and I found that ffmpeg has a concat function, that reads a file with a custom syntax and queues it.

  


  So I made a script that lists the files in the directory where I store all my videos, modifies the output with sed, shuffles it (so the episodes are random), and then it redirects the output to a playlist.txt

  


  find /mnt/episode/ -print | sed '/**.mp4/!d' | sed "s/^/file '/; s/$/'/" | shuf > playlist.txt


  


  playlist.txt

  


  example :

  


  ...
file '/mnt/episode/9/1.mp4'
file '/mnt/episode/8/4.mp4'
file '/mnt/episode/5/11.mp4'
file '/mnt/episode/7/15.mp4'
...


  


  This creates 2 problems :

  


  

  1. For some reason, while using the playlist/queue method, when it finishes a video... it takes like 30 seconds to switch to the next video.

  


  


  ffmpeg -f concat -safe 0 -i playlist.txt -f v4l2 /dev/video0


  


  (simplified command, using /dev/video0 device for testing purposes)

  


  ffmpeg does output something after the first video, but i'm not quite sure what it means.

  


  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x55c8abc1b900] st: 1 edit list: 1 Missing key frame while searching for timestamp: 0
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x55c8abc1b900] st: 1 edit list 1 Cannot find an index entry before timestamp: 0.


  


  

  2. Once the playlist finishes, the stream is over. I could run the script that generates the playlist again, but that would mean that the stream cuts, which I don't want.

  


  


  ---

  


  What I want

  


  I need a way to pick a random file, stream it normally via RTMP and once it finished, automatically pick another one without interrupting the streaming, and keep doing this until I decide to turn it off.

  


  This is the directory format :

  


  episodes
│
├── 1
│   ├── 1.mp4
│   ├── 2.mp4
│   ├── 3.mp4
│   ...
├── 2
│   ├── 1.mp4
│   ├── 2.mp4
│   ├── 3.mp4
│   ...
├── 3
│   ├── 1.mp4
│   ├── 2.mp4
│   ├── 3.mp4
│   ...
├── 4
│   ├── 1.mp4
│   ├── 2.mp4
│   ├── 3.mp4
│   ...
├── 5
│   ├── 1.mp4
│   ├── 2.mp4
│   ├── 3.mp4
│   ...
├── 6
│   ├── 1.mp4
│   ├── 2.mp4
│   ├── 3.mp4
│   ...
├── 7
│   ├── 1.mp4
│   ├── 2.mp4
│   ├── 3.mp4
│   ...
├── 8
│   ├── 1.mp4
│   ├── 2.mp4
│   ├── 3.mp4
│   ...
└── 9
    ├── 1.mp4
    ├── 2.mp4
    ├── 3.mp4
    ...


  


  Gladly appreciate some help here. I tried to make the problem as clear as possible.

  


  Thanks <3

  &#xA;