Opened 13 years ago
Closed 11 years ago
#32219 closed enhancement (fixed)
ffmpeg-devel: use librtmp
| Reported by: | marcin.operacz@… | Owned by: | dbevans (David B. Evans) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | haspatch | Cc: | jeremyhu (Jeremy Huddleston Sequoia) |
| Port: | ffmpeg-devel |
Description
Enhacement to use librtmp in ffmpeg to address issue with connecting to non default instance applications
Attachments (1)
Change History (8)
Changed 13 years ago by marcin.operacz@…
| Attachment: | Portfile.diff added |
|---|
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | devans@… removed |
|---|---|
| Keywords: | haspatch added |
| Owner: | changed from macports-tickets@… to devans@… |
| Summary: | ffmpeg-devel → ffmpeg-devel: use librtmp |
Is there a reason this shouldn't be on all the time? (Why a variant?)
comment:2 Changed 13 years ago 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...
comment:3 Changed 12 years ago by jmroot (Joshua Root)
| Cc: | jeremyhu@… added |
|---|---|
| Port: | ffmpeg-devel added; ffmeg-devel removed |
comment:4 Changed 11 years ago by jdolan (Jay Dolan)
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?
comment:5 Changed 11 years ago by dbevans (David B. Evans)
| Status: | new → assigned |
|---|
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 ?)upstream ticket and a thread on Google Groups that might be relevant.
comment:6 Changed 11 years ago by dbevans (David B. Evans)
More to the point is it still an issue with the current ffmpeg version @2.2.2 and ffmpeg-devel @20140507?
comment:7 Changed 11 years ago by dbevans (David B. Evans)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
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.
diff for Portfile