Branch: refs/heads/master
Home: https://github.com/mltframework/mlt
Commit: 2e8969380c3bd190791cea6bf045e30d068ea480
https://github.com/mltframework/mlt/commit/2e8969380c3bd190791cea6bf045e30d068ea480
Author: Brian Matherly
Date: 2014-01-22 (Wed, 22 Jan 2014)
Changed paths:
> Well, in that case, the Base64 encoding is the only
> thing that comes to mind. I'm sure it would improve
> performance, and reduce the file size too. After all,
> we don't need a human readable results, do we?
I think the base64 and hash ideas are both worth exploring. First, I'm going to
l
On Wed, Jan 22, 2014 at 11:59 AM, Brian Matherly wrote:
>> Well, in that case, the Base64 encoding is the only
>> thing that comes to mind. I'm sure it would improve
>> performance, and reduce the file size too. After all,
>> we don't need a human readable results, do we?
>
> I think the base64 an
RRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/carl/
On Wed, Jan 22, 2014 at 2:05 PM, Carl Karsten wrote:
> /home/carl/bin/melt foo.flv -consumer avformat:foo.mp4
...
> [libx264 @ 0x7fffdc0c7b00] MB rate (360) > level limit (2073600)
melt is not compatible with that video file. It thinks the framerate
is 1000 fps, which results in this x264 err
ok - thanks.
On Wed, Jan 22, 2014 at 5:33 PM, Dan Dennedy wrote:
> On Wed, Jan 22, 2014 at 2:05 PM, Carl Karsten
> wrote:
> > /home/carl/bin/melt foo.flv -consumer avformat:foo.mp4
> ...
> > [libx264 @ 0x7fffdc0c7b00] MB rate (360) > level limit (2073600)
>
> melt is not compatible with th
