From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Video editing advice on formats and size of file
Date: Sat, 24 Dec 2011 02:54:40 -0600 [thread overview]
Message-ID: <4EF59350.3070601@gmail.com> (raw)
In-Reply-To: <CA+czFiDi0ArsLnE0as1LTd-KdrpwSf_GGSsz_KQG2=ij7kp0sg@mail.gmail.com>
Michael Mol wrote:
> This is a slightly simplified explanation, owing to my probably not
> remembering details quite correctly.
>
> Media files consist of at least three parts: The container format, the
> audio stream and the video stream. You're familiar with container
> formats as ".flv", ".mkv", ".avi", ".mpg", ".mp4", etc.
>
> The audio and video streams consist of frames (for video) or samples
> (for audio) where each one consists of information particular to a
> particular video image or audio sample. The audio and video frames
> typically don't include information as to when they occurred; a frame
> won't tell you that it's specific to 33.2 seconds into a sequence, for
> example.
>
> Normally, the file and/or streams will describe how many frames per
> second the video stream should move along at, and how many samples per
> second the audio stream should move along.
>
> When the samples and frames stop matching up as the media file plays,
> you get desync. This is normal to within a certain tolerance; when
> you're moving along 48k audio samples per second, and only 30 video
> frames per second, nobody cares if an audio sample is ten or so off
> from its ideal position.
>
> Unfortunately, I can only tell you what's going on. I can't tell you
> how to fix it; it's not something I dealt with much.
>
> I'd suggest you give the other tools a try, too. The other tools
> brought up will do essentially the same thing as avidemux; they're
> just ripping the audio and video streams out of the source container
> files and placing them into a new container file. Your old approach
> was very, very slow because your tools were generating completely new
> audio and video streams. It's the difference between "dd if=src
> of=dst" and "dd if=src|lzma --decompress --stdout|lzma --stdout|dd
> of=dst" ... except lzma doesn't loose any data in the process, while
> your transcoding was. Once you get the sync issues worked out, you
> might even notice improvements in audio and image quality. :)
>
I been doing some testing on this. I went to about the end of a 3 hour
video. By the time it gets near the end of the video, the sound is
almost 1.4 seconds off. I tested this by telling smplayer to adjust the
audio delay. It is a bit annoying to see something on screen then hear
it a second or so later. It's like seeing a explosion at a distance.
You see it then have to wait for the sound wave to hit you. When I am
midways of the video, it is about .6 to .7 seconds off. So, it gets
farther off as it goes. It's most likely one step off that just gets
worse as it goes.
I tried a couple other commands but I get errors about the file type. I
think a couple movies are in flv1 which is old. I may have to convert
them then stitch them together, which may not do the sound any good then
either. lol
Well, I got something to play with.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"
next prev parent reply other threads:[~2011-12-24 8:56 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
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 [this message]
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=4EF59350.3070601@gmail.com \
--to=rdalek1967@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