What version of FFMPEG should I use on DEBIAN to transcode RTSP to RTMP? -

-

i using command: 

   ffmpeg -i rtsp://login:password@90.70.42.54:554/axis-media/media.amp -f flv  rtmp://localhost:1935/live/yarek

which worked fine on 1 windows,

this command gives errors on linux1 (ffmpeg version 0.8.6-4:0.8.6

writen, rtmp send error 10053 (129 bytes) writen, rtmp send error 10053 (45 bytes) writen, rtmp send error 10038 (42 bytes) av_interleaved_write_frame(): operation not permitted

and gives errors on linux2: (ffmpeg version 0.7.15)

[h264 @ 0x98e2f80] rtp: pt=60: bad cseq c54f expected=b90c [h264 @ 0x98e2f80] rtp: pt=60: bad cseq b90c expected=c551 [h264 @ 0x98e2f80] rtp: pt=60: bad cseq c552 expected=b90f [rtsp @ 0x98de5e0] estimating duration bitrate, may inaccurate  seems stream 0 codec frame rate differs container frame rate: 180000.00 (180000/1) -> 90000.00 (180000/2) input #0, rtsp, 'rtsp://login:password@90.70.42.54:554/axis-media/media.amp':   metadata:     title           : media presentation   duration: n/a, start: -4756.582667, bitrate: n/a     stream #0.0: video: h264 (main), yuvj420p, 1024x768 [par 1:1 dar 4:3], 90k tbr, 90k tbn, 180k tbc

so 100% sure command line good, ffmpeg bad.

my question is: what version of ffmpeg should use on debian transcode rtsp rtmp ?

can recommend me correct version of ffmpeg works ?

regards

the ffmpeg using in windows ffmpeg project via zeranoe's ffmpeg windows builds, , so-called ffmpeg using in debian fork of ffmpeg called libav. confirm if included console outputs each command. see:

i recommend using real ffmpeg since version fork buggy. have 2 main choices:

compiling embiggen nerd cred, using build lazier.


Comments

Post a Comment

Popular posts from this blog

java - JavaFX 2 slider labelFormatter not being used -

-
i have following code not label slider "foo50", etc... 1 expect setlabelformatter call, instead seems have no effect (the slider labelled 50, 100, etc , println's dont run). there missing? not implemented in default 2.2 skin? using oracle java 7 package javafxbugtest; import javafx.application.application; import javafx.scene.*; import javafx.scene.control.*; import javafx.stage.*; import javafx.util.stringconverter; public class javafxbugtest extends application { @override public void start(final stage primarystage) { slider cp = new slider(); cp.setlabelformatter(new stringconverter<double>() { @override public string tostring(double t) { system.out.println("nope?"); return "foo" + t.tostring(); } @override public double fromstring(string string) { system.out.println("he
Read more

Detect support for Shoutcast ICY MP3 without navigator.userAgent in Firefox? -

-
the current version of mozilla firefox 23.0.1, version not support play mp3 shoutcast streams tcp port different 80 (most common 8000 shoutcast 1.9.8). i use flash when mp3 support not available in html5 audio, way detect is: try{ var = document.createelement('audio'); r = !!(a.canplaytype && !!a.canplaytype("audio/mpeg; codecs=mp3").replace(/^no$/,'')) }catch(e){ r = false; } the support mp3 shoutcast streams in firefox added in version 24 . a.canplaytype("audio/mpeg; codecs=mp3") = in chrome , firefox, chrome support, firefox not support, due current code detect not work firefox. the current version of jquery support ie 6 1.10.2, version not has .browser i think "stylized" way testing features , not querying browsers / versions, notwithstanding here see hard not violate "principle". what "stylized" way of detect mp3 icy support without navigator.useragent in firefox? ther
Read more

web - SVG not rendering properly in Firefox -

-
i have problem svg renderring in firefox. whilst works in safari, chrome or in ie, doesn't work in firefox. inspecting element seems layers there, background visible if it's z-index higher z-index of others. rendered in firefox: svg logo in firefox link original source file: svg file thanks help. ps: used sketch 3 export svg. if helps somehow. you're experiencing bug 995813 . i fixed bug time ago change still making way through release process example display correctly firefox 31 onwards released on 22 july 2014. in meantime if move fill="white" <mask> element child <use> element work around firefox bug.
Read more