1 |
On Tue, Aug 17, 2010 at 9:08 AM, Kevin O'Gorman <kogorman@×××××.com> wrote: |
2 |
> On Mon, Aug 16, 2010 at 1:21 PM, Paul Hartman |
3 |
> <paul.hartman+gentoo@×××××.com> wrote: |
4 |
>> |
5 |
>> On Sun, Aug 15, 2010 at 10:02 PM, Kevin O'Gorman <kogorman@×××××.com> |
6 |
>> wrote: |
7 |
>> > My underling thing, if anyone can make other suggestions, is that my |
8 |
>> > camera |
9 |
>> > broke, and I had to get |
10 |
>> > one in a hurry, and didn't really know what to look for. I wound up |
11 |
>> > with a |
12 |
>> > fairly good Sanyo 1080p camera |
13 |
>> > and video recorder that's super light, and not too expensive. The |
14 |
>> > problem |
15 |
>> > is that its videos are MP4s, |
16 |
>> > which are definitely not ready to put on a web site, and I know nothing |
17 |
>> > about transcoding. My previous |
18 |
>> > camera took acceptable .avi videos, which had worked with most folks |
19 |
>> > browsers. The MP4s are huge |
20 |
>> > and in a weakly supported format. |
21 |
>> |
22 |
>> You might want to check out kdenlive which is a full-featured video |
23 |
>> editor (using mlt as backend) but includes a simple transcoding |
24 |
>> function and several presets for many different formats (with the |
25 |
>> added bonus that you'll be able to edit your raw video should you so |
26 |
>> desire). |
27 |
> |
28 |
> Thanks, I emerged kdenlive. I can not open my MP4 files, but I can add them |
29 |
> as clips. Okay. |
30 |
> |
31 |
> The clips do not play in any reasonable form. I get moments of sound, and a |
32 |
> few pixels |
33 |
> changing on screen; nothing coherent. I'd been told that H264 needs a lot |
34 |
> of CPU and I |
35 |
> guess an old 4-core 32-bit XEON (effectively 800 MHz each) on 2 GB ECC DDR1 |
36 |
> is not enough. Okay. |
37 |
|
38 |
I don't think you'll be able to play back HD video in real-time on |
39 |
that hardware. Even on, for example, Core 2 at 3GHz playing HD video |
40 |
used something like 90% CPU (without a hardware mpeg4 decoder). |
41 |
|
42 |
> The killer though, is that I cannot figure out how to export that clip in |
43 |
> some other form. |
44 |
> And of course, I'm clueless about what form would be optimum. Asking for |
45 |
> help takes |
46 |
> me to a forum that has a thread on the topic, but no useful answer. |
47 |
|
48 |
You need to add it as a clip, then drag that clip to the timeline in |
49 |
the lower half of the window. It may take it a while to process once |
50 |
you've dropped it here (I believe it thumbnails/indexes the video). |
51 |
It's sort of like a multi-track audio editor, you can overlay effects, |
52 |
drag the ends of the video clips to change the start/end point, etc. |
53 |
The more effects you add the slower the encoding will be. For example |
54 |
I used it on a 5-minute video from my wedding to fade-in and fade-out, |
55 |
print a title at the beginning, and normalize the audio. I encoded it |
56 |
to a 720p mp4 which I could then upload to YouTube and let YouTube |
57 |
re-encode it to lower resolutions for people who can't do HD. |
58 |
|
59 |
Once you've got your clip on the timeline, to save as another format |
60 |
click the "Render" button. In the Render window, you can choose the |
61 |
output format. It will give you many options such as MPEG-2, XviD, |
62 |
Flash, RealVideo, Theora etc. You can also adjust the output video |
63 |
dimensions and bitrate. Hopefully you can find something that will |
64 |
work for your audience. If you have other video files that worked well |
65 |
for you in the past, you might check out what their specs are and try |
66 |
to mimic it. |
67 |
|
68 |
It will probably take ages to process, depending on how long your |
69 |
video is. I have a Core i7 920, overclocked, and encoding a 1440x1080 |
70 |
interlaced video to another format still takes more time than the |
71 |
length of the video clip (usually 1.5 to 2 times with no effects |
72 |
added). Since you're dealing with even higher-resolution video and |
73 |
slower hardware I imagine you're probably looking at overnight, or |
74 |
days, depending on how much video you're dealing with. |
75 |
|
76 |
One "trick" to speed things up is to first transcode your video to an |
77 |
uncompressed format, and then do all of your editing operations on |
78 |
that uncompressed file. This requires massive amounts of disk space |
79 |
and fast disks, though (I think a 5 minute clip was about 70 |
80 |
gigabytes). |
81 |
|
82 |
> Is there a kdelive tutorial anywhere? One basic walkthrough and I'd |
83 |
> probably be able |
84 |
> to figure out the rest of what I want. |
85 |
|
86 |
There are some video tutorials here: |
87 |
http://www.kdenlive.org/tutorial |
88 |
|
89 |
And the user manual has a quick-start section, I believe: |
90 |
http://www.kdenlive.org/user-manual |
91 |
|
92 |
If you don't really need or want HD video, you might also consider |
93 |
going "old school" and getting a video capture card (which encodes to |
94 |
something more CPU-friendly like mpeg2). Then you could play the video |
95 |
on the camcorder and record it onto the computer and let the capture |
96 |
card do the heavy lifting. |
97 |
|
98 |
If kdenlive is a dead end, other alternatives might be: |
99 |
Install handbrake binaries into your user directory, forgetting about |
100 |
portage entirely for the moment. |
101 |
Use ffmpeg if you can figure out the commandline options (I never can) |
102 |
Other video-converter packages include tovid, though support of HD |
103 |
video might not be there. |
104 |
|
105 |
Good luck! |