-
Notifications
You must be signed in to change notification settings - Fork 13
HOME > FAQ
[[TOC]]
Read the Setup Guide again.
If it still do not work, please open a bug report. It could be due to a change in the InfoQ markup or some integration issue like your ffmpeg version.
I don't know.
I have not tested Windows support and I am not interested to do it. The code is designed to be portable, so if you manage to install the native dependencies it should be ok.
It mainly depends of two things:
- Your network bandwidth
- Your CPU and the specified output format
First the video has to be download. The usual size of a video is 100 to 200MB, I let you do the math.
Then the final video has to be created by ffmpeg. The legacy and h264
output formats are quite fast. It usually takes less than one minute on a
modern CPU, and five to ten minutes on an Atom. The h264_overlay output format
is usually ten times slower. It will most likely takes 10 minutes to convert an
one hour presentation on a modern CPU.
You are right. However, presentations created before July 2011 only support rtmp not HTTP. I believe that some of theses presentations are still valuables.
I could make rtmpdump optional too. But I don't want to make the code more
complex than it has to be. rtmpdump is not that hard to install.
I will reconsider this point in few months/years when the content from 2010 will be mostly outdated.