[
https://issues.apache.org/jira/browse/GUACAMOLE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16297303#comment-16297303
]
Sean Reid commented on GUACAMOLE-465:
-
I think there's something to that, Mike, but I don't think it would be a bad
idea for the time being to open up guacenc to some other options. The idea I'd
been working on was to keep it to a list of tested codecs so that it's
difficult for the user to get themselves into trouble and then document it
well. I'd earmarked the existing mpeg4 support, h.264, VP8, and h.265 support.
I agree that part of guacenc's strength is its simplicity, but I do think we
can find a balance between opening it too much and keeping it where it is. I'd
also planned to leave the defaults the way they are currently so as to
minimally impact people who just want it to work and not think about codecs.
For a long-term project, it might be possible to create an FFmpeg Device using
the libavdevice API so that guacamole protocol data can be read natively by
FFmpeg, but if the idea is to create something that "just works" and also
provide a lot of power, FFmpeg fits the power bill, but can be very complex for
an average user to figure out. If we went that route eventually, I think we
might have to maintain guacenc at the same time just so that people have an
option.
> 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
>Affects Versions: 0.9.13-incubating
>Reporter: Sean Reid
>Priority: Minor
>
> 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
(v6.4.14#64029)