[MacPorts] #32219: ffmpeg-devel
#32219: ffmpeg-devel --------------------------------------+------------------------------------- Reporter: marcin.operacz@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: ffmeg-devel --------------------------------------+------------------------------------- Enhacement to use librtmp in ffmpeg to address issue with connecting to non default instance applications -- Ticket URL: <https://trac.macports.org/ticket/32219> MacPorts <http://www.macports.org/> Ports system for Mac OS
#32219: ffmpeg-devel: use librtmp --------------------------------------+------------------------------------- Reporter: marcin.operacz@… | Owner: devans@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: haspatch | Port: ffmeg-devel --------------------------------------+------------------------------------- Changes (by ryandesign@…): * keywords: => haspatch * owner: macports-tickets@… => devans@… * cc: devans@… (removed) Comment: Is there a reason this shouldn't be on all the time? (Why a variant?) -- Ticket URL: <https://trac.macports.org/ticket/32219#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#32219: ffmpeg-devel: use librtmp --------------------------------------+------------------------------------- Reporter: marcin.operacz@… | Owner: devans@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: haspatch | Port: ffmeg-devel --------------------------------------+------------------------------------- Comment(by marcin.operacz@…): no reason at all... but... there is a rtmp protocol implementation in ffmpeg sources witch will suffice for most of the peoples.. and using librtmp require additional component... -- Ticket URL: <https://trac.macports.org/ticket/32219#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#32219: ffmpeg-devel: use librtmp --------------------------------------+------------------------------------- Reporter: marcin.operacz@… | Owner: devans@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: haspatch | Port: ffmpeg-devel --------------------------------------+------------------------------------- Changes (by jmr@…): * cc: jeremyhu@… (added) * port: ffmeg-devel => ffmpeg-devel -- Ticket URL: <https://trac.macports.org/ticket/32219#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#32219: ffmpeg-devel: use librtmp -------------------------------+---------------------- Reporter: marcin.operacz@… | Owner: devans@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: | Keywords: haspatch Port: ffmpeg-devel | -------------------------------+---------------------- Comment (by jay@…): Just a nudge on this one. ffmpeg's built-in rtmp code path is incompatible with at least crtmpserver, perhaps others. Using librtmp fixes this issue, and I've not found any ill effects from using it. Could this be merged? -- Ticket URL: <https://trac.macports.org/ticket/32219#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#32219: ffmpeg-devel: use librtmp -------------------------------+---------------------- Reporter: marcin.operacz@… | Owner: devans@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: | Keywords: haspatch Port: ffmpeg-devel | -------------------------------+---------------------- Changes (by devans@…): * status: new => assigned Comment: Thanks for the nudge. This one slipped under my radar. Can you be a little bit more specific about the incompatibility involved. Is this a protocol compatibility issue? Or a bug in ffmpeg's internal implementation? Is it CRtmpServer specific? I see an (incomplete ?)[https://trac.ffmpeg.org/ticket/1700 upstream ticket] and [https://groups.google.com/forum/#!topic/c-rtmp-server/ywQPjvciPgc a thread on Google Groups] that might be relevant. -- Ticket URL: <https://trac.macports.org/ticket/32219#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#32219: ffmpeg-devel: use librtmp -------------------------------+---------------------- Reporter: marcin.operacz@… | Owner: devans@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: | Keywords: haspatch Port: ffmpeg-devel | -------------------------------+---------------------- Comment (by devans@…): More to the point it is still an issue with the current ffmpeg version @2.2.2 and ffmpeg-devel @20140507? -- Ticket URL: <https://trac.macports.org/ticket/32219#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
#32219: ffmpeg-devel: use librtmp -------------------------------+---------------------- Reporter: marcin.operacz@… | Owner: devans@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: fixed | Keywords: haspatch Port: ffmpeg-devel | -------------------------------+---------------------- Changes (by devans@…): * status: assigned => closed * resolution: => fixed Comment: Committed in r119872 as non-default +librtmp variant for ffmpeg/ffmpeg- devel to allow users the choice of which implementation to use. If this is still a current issue with ffmpeg trunk, it should be pursued upstream. -- Ticket URL: <https://trac.macports.org/ticket/32219#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts