![]() ![]() In my personal experience this is the most stable version you can get, at least if you are running a standard desktop type machine with a 64-bit processor. Then if I do "which ffmpeg" from the command prompt, it shows that it's at /usr/local/bin/ffmpeg It seems to be updated every three or four months, and I just use Midnight Commander to open the downloaded archive and then just copy the executable files into the /usr/local/bin directory, since it's already in my path. Just FYI, on Ubuntu Server I always use the static build from, specifically the release: x86_64 build (currently at ). I've created a new IP TV Network and a new Mux in that network.įor the URL parameter i've set: pipe:///usr/bin/ffmpeg -loglevel fatal -fflags +genpts -i rtsp://:554/11 -vcodec copy -acodec copy -metadata service_provider=IPCAMS -metadata service_name=ENTRANCE -f mpegts -tune zerolatency pipe:1Īt tv headend i can see the following error at the console: iptv: libav: Could not open input 'pipe:///usr/bin/ffmpeg -loglevel fatal -fflags +genpts -i rtsp://:554/11 -vcodec copy -acodec copy -metadata service_provider=IPCAMS -metadata service_name=ENTRANCE -f mpegts -tune zerolatency pipe:1': Protocol not foundĪny Idea why tvheadend states "*Protocol not found*" ? The following command at the console works and generates a output "out.ts" /usr/bin/ffmpeg -loglevel fatal -fflags +genpts -i rtsp://:554/11 -vcodec copy -acodec copy -metadata service_provider=IPCAMS -metadata service_name=ENTRANCE -f mpegts -tune zerolatency out.ts ![]() ![]() I've installed ffmpeg now but i cannot get it to work with TVHeadend :(.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |