[Bf-committers] can we update ffmpeg to have RTSP support?

Dalai Felinto dfelinto at gmail.com
Thu Jul 17 17:15:54 CEST 2014


The Blender (BGE)  - side of rtsp support is committed [6f846da], now
to the ffmpeg backend:

> Seems like a special case - couldn't the BlenderCAVE/remote-camera
users who want RTSP  do their own builds?

That's a possible compromise, but then I would ask to at least have
wiki pages on how to build our OSs libraries. I think Linux and OSX
are clear enough-ish, but Windows is definitively not. I remember a
script to build the libraries for windows in a similar way we have for
Linux. Was this abandoned?

I get that devs are supposed to know those things, but I think to ask
someone to know how to build libraries to all OSs on its own is a bit
too much. (thinking on people that relying on custom libraries to get
the most out of Blender).

That said I still don't see the harm in enabling everything in the
ffmpeg backed that doesn't bloat the library size ...

Cheers,
Dalai
--
blendernetwork.org/dalai-felinto
www.dalaifelinto.com


2014-07-15 23:55 GMT-03:00 Campbell Barton <ideasman42 at gmail.com>:
> On Wed, Jul 16, 2014 at 5:31 AM, Dalai Felinto <dfelinto at gmail.com> wrote:
>> @Fasekas: we are wrapping some of the functionality directly from the
>> FFmpeg library so unless ffmpeg can do it I believe we can't. That's
>> besides the point though, why to reinvent the wheel if we are already
>> using a library that provides streaming.
>>
>> @Sergey
>>> And maintain means communicate with the users in the tracker, making sure this stuff works in upcoming blender releases, invest time on fixing stuff when it becomes broken (and stuff tends to become broken in FFmpeg).
>>
>> As I said in IRC I can commit to the Blender side of this (in this
>> particular subset of FFmpeg features). Meaning replying to tracker
>> entries and orienting clueless users. This will be used by BGE
>> anyways, so it won't affect Blender users in general. That said, even
>> with the backend RTSP support in the ffmpeg the feature is not fully
>> working. But I believe it's an issue in BGE code (more details in the
>> tracker).
>>
>>> But seems we need to update FFmpeg anyway (because of https://developer.blender.org/T41065) so technically tweaking configuration flags is not that much an issue.
>>
>> Anyways we support so many bizarre things (webcam!), I can't see this
>> going over whatever line we drawn. I think in cases like this we
>> should have reasons to not include things, not to include them (when
>> it comes to 'readers [decoders]'). Either way the reason/use case was
>> explained in the original email. I'm just not sure about the h264, if
>> this violates any GPL/patent thing.
>
> On the other hand we end up loosing time to support various
> configurations, its hard to know beforehand if enabling options incurs
> maintenance overhead.
>
> Seems like a special case - couldn't the BlenderCAVE/remote-camera
> users who want RTSP  do their own builds?
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers


More information about the Bf-committers mailing list