FGCom-mumble: Difference between revisions

Jump to navigation Jump to search
m
 
Line 173: Line 173:
** also, the audio data needs to be fetched from the mic, and then handed over to libmumbles audio encoding and sending routine. This probably can somewhat be partly copied from the legacy fgcom implementation.
** also, the audio data needs to be fetched from the mic, and then handed over to libmumbles audio encoding and sending routine. This probably can somewhat be partly copied from the legacy fgcom implementation.
* Questions regarding fgfs currently are:
* Questions regarding fgfs currently are:
** how to exactly the integration on fgfs side works. That needs peeks on fgcoms code as well as some discussion at the mailing list.
** {{tick}} (''Answer:'' use [[Howto:Create_new_subsystems|Subsystem]]) how to exactly the integration on fgfs side works. That needs peeks on fgcoms code as well as some discussion at the mailing list.
** how to integrate the libmubmle code into the fgfs build chain (its cmake).
** how to integrate the libmubmle code into the fgfs build chain (its cmake).
*** {{tick}} legally: libmubmle has a [https://github.com/mumble-voip/libmumble/blob/master/LICENSE BSD 3-clause] licence, is that compatible?
*** {{tick}} legally: libmubmle has a [https://github.com/mumble-voip/libmumble/blob/master/LICENSE BSD 3-clause] licence, is that compatible?
601

edits

Navigation menu