[FFmpeg-trac] #2463(undetermined:new): ffspeak

[FFmpeg]

#2463: ffspeak
-------------------------------------+-------------------------------------
             Reporter:  burek        |                    Owner:
                 Type:  enhancement  |                   Status:  new
             Priority:  wish         |                Component:
              Version:  unspecified  |  undetermined
             Keywords:               |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by saste):

 Replying to [comment:3 burek]:
 > I guess what you suggested might be put into a todo for some future
 versions, but for a start,  it would be enough to enable just audio/video,
 without auth, chat support, etc. just a basic audio/video conference. I
 believe the client part is already implemented in ff* libraries/tools, and
 the server part could just do simple queuing/buffering and rebroadcasting
 to all but the source of the audio and that's it. As simple as possible
 and working, to keep it in the spirit of ffmpeg.

 How is this different from what ffserver does (not a rethoric question)?

 And I agree, proper conferencing is way beyond the scope of ffmpeg, there
 already exist standards and dedicated tools for that (SIP to name just
 one, which is indeed *the* standard in enterprises and in VOIP), *or*
 should be implemented on top of other libraries/standards/protocols.

 > Of course, later on there could be added some additional features, like
 you mentioned, but I think right now, it would probably be the best to
 just wrap all that is already existing in ffmpeg code base and make use of
 it in this way, to provide a new feature to the users. After that, we can
 see if the feature will be as popular as expected and if it is, we can
 start planning some kind of an api or a todo for future versions of the
 feature.
 >

 > Also, I like the name fftalk (it sounds more convenient), but I don't
 know how to change the topic of the ticket.

 I don't like to name things we don't even know what they are (a program,
 an API, a framework?).

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2463#comment:4>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker