You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2020/06/24 19:37:00 UTC

[jira] [Reopened] (GUACAMOLE-465) Guacenc should support libavformat

     [ https://issues.apache.org/jira/browse/GUACAMOLE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Jumper reopened GUACAMOLE-465:
-----------------------------------
      Assignee: Mike Jumper  (was: Sean Reid)

Coverity is reporting an issue with the printf-style arguments of one of the log messages, the way that the created file is deleted on failure (checking {{access()}} before an unchecked call to {{remove()}}), and a possible resource leak.

I'll recheck and fix if valid.

> Guacenc should support libavformat
> ----------------------------------
>
>                 Key: GUACAMOLE-465
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-465
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: guacenc
>            Reporter: Sean Reid
>            Assignee: Mike Jumper
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> Currently, guacenc writes raw mpeg4 frames into a file and gives it a file extension of m4v. While this works for that specific codec and container combination, adding more advanced codecs will require better container support. 
> FFMpeg provides a library, libavformat, that provides true container support. libavformat should be added as a dependency to guacenc and the current file writing code should be refactored to leverage libavformat. These changes will facilitate future work on adding new codec support to guacenc.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)