You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Sean Reid (Jira)" <ji...@apache.org> on 2020/02/13 04:55:00 UTC

[jira] [Commented] (GUACAMOLE-465) Guacenc should support more formats and containers

    [ https://issues.apache.org/jira/browse/GUACAMOLE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035915#comment-17035915 ] 

Sean Reid commented on GUACAMOLE-465:
-------------------------------------

In an effort to be completely accurate, should the title of this issue be changed now that we're marking it for 1.2.0? This issue was originally written to enhance guacenc to support new containers and codecs, but guacamole-server PR 159 only adds the dependency on libavformat that will eventually enable more containers and codecs. Since, in my mind, it's probably smart to keep that PR's scope where it is for 1.2.0, does it make sense to re-title this issue so that other issues can be filed to track the additions for codecs and containers in future PRs?

> Guacenc should support more formats and containers
> --------------------------------------------------
>
>                 Key: GUACAMOLE-465
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-465
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: guacenc
>            Reporter: Sean Reid
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> Guacenc should support more formats than just mpeg4 in an m4v file type. It should support true media containers with libavformat rather than just writing the encoded frames into a file. 
> Because Guacamole is a web-based application, it makes sense that at the very least its video encoder should support common web video formats (h.264 + mp4).



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