public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Video editing advice on formats and size of file
Date: Fri, 23 Dec 2011 09:45:22 -0500	[thread overview]
Message-ID: <4EF49402.3000907@gmail.com> (raw)
In-Reply-To: <4EF48DA6.1080203@gmail.com>

Dale wrote:
> Howdy,
>
> I been trying to get this to work right for a goooooood while now. I'm
> confused here. I have some videos that I download that are split up.
> Some have two or three parts and a few 4 or 5. What I can't get is this,
> I can't seem to take say two 250Mb videos and make it come anywhere near
> 500Mbs when spliced together. They usually end up being 1.5Gb and
> sometimes much more. I use Kdenlive to do this with. I have tried every
> setting that I can find. I have used exiftool to try to match the
> encoding and rates and all that with no improvement or very little
> improvement.
>
> Is there some secret spice that I am missing or something? Why can't I
> take two videos and splice them together and it be something close to
> the two file sizes added together? I'm not asking for a perfect fit but
> at least something close. If I can get 2 250Mb videos to splice together
> and be 600Mbs, that would be good enough.

You're probably re-encoding, rather than simply splicing the existing 
streams. The resulting size will necessarily have some quality loss, and 
the resulting file size will depend greatly on the quality of your 
encoder, not just on your settings for codec choice and options.

What you really want to do is repackage the audio and video streams from 
all your files into a single container file.

Back when I was poking "simple" things like this, I used 'avidemux'. 
That was ages ago, and on Ubuntu, but it might work for you. You'd want 
to use 'copy' for your audio and video selection, to avoid any transcoding.

On Ubuntu, I usually had difficulties(read: crashes) with avidemux when 
some tool or library it wanted wasn't installed--it wasn't smart enough 
to remove those options from its menus if those options weren't present. 
I haven't tried it on gentoo; it's plausible someone fixed that either 
upstream or as part of some USE flag awareness in the past couple years.

I expect there are ways to do the exact same thing on the command line 
using ffmpeg, but I'm less familiar with that tool.



  reply	other threads:[~2011-12-23 14:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 14:18 [gentoo-user] Video editing advice on formats and size of file Dale
2011-12-23 14:45 ` Michael Mol [this message]
2011-12-24  1:52   ` Dale
2011-12-24  3:26     ` Dale
2011-12-24  3:50       ` Michael Mol
2011-12-24  8:54         ` Dale
2011-12-24 10:36           ` Dale
2011-12-24 15:41             ` Michael Mol
2011-12-24 17:42               ` pk
2012-05-03 23:30         ` David Haller
2011-12-23 14:49 ` [gentoo-user] " Grant Edwards
2011-12-24  1:55   ` Dale
2012-01-01 18:56     ` Mick
2012-01-04  3:14       ` Claudio Roberto França Pereira
2012-05-03 23:07       ` David Haller
2011-12-23 16:29 ` [gentoo-user] " David Haller
2011-12-24  1:57   ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EF49402.3000907@gmail.com \
    --to=mikemol@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox