discuss: Putting Together Information For a HOWTO


Previous by date: 4 Jan 2004 22:03:48 -0000 Re: Review: Vim as XML Editor HOWTO, Tobias Reif
Next by date: 4 Jan 2004 22:03:48 -0000 Re: man pages, Michael Still
Previous in thread: 4 Jan 2004 22:03:48 -0000 Re: Putting Together Information For a HOWTO, Charles Curley
Next in thread: 4 Jan 2004 22:03:48 -0000 Re: Putting Together Information For a HOWTO, Charles Curley

Subject: RE: Putting Together Information For a HOWTO
From: "Devin Watson" ####@####.####
Date: 4 Jan 2004 22:03:48 -0000
Message-Id: <MABBLNEAJNOGLIECMPMNIENLCEAA.dmwatson@comcast.net>

	Charles -

	Here is my outline for the project. If you have any inputs you would like
to contribute, please let me know. I can also send you what I have written
already. The '*' in the outline denotes areas I've already written to, and
'**' are ones I have written to but need to complete.

	-Devin Watson

-----Original Message-----
From: Charles Curley ####@####.####
Sent: Saturday, January 03, 2004 7:34 PM
To: Devin Watson
Cc: ####@####.####
Subject: Re: Putting Together Information For a HOWTO


On Thu, Jan 01, 2004 at 05:51:39PM -0500, Devin Watson wrote:
> Charles Curley wrote:
>
> > A dependency tree might be a good idea. However, they mutate over time
> > as packages change dependencies. Also, a dependncy checker like yum or
> > apt will help where packages are available in .rpm or .deb packages.
>
> I have something that resembles a dependency tree right now, but it
> is divided amongst each tool set to make it a little more manageable. The
> RPM
> packages for the most part have been available through freshrpms.net, and
I
> mention that wherever possible.
>
> I will install yum and apt and try them out. I do want this to be as
> comprehensive
> a guide as possible to doing this, as there is nothing out there right now
> that documents
> the process in detail. It's also one of my own pet peeves.
>
> Basically each tool has its own section devoted to what it is, how it
works,
> and how to install it. I could make a master dependency tree for
everything,
> since
> many of the tools use the same libraries. I tried to order the
documentation
> so that,
> as you go along, you need to install less and less in advance of the tool
> itself, because
> the tool prior to that had some relationship at the library level.

Sounds good to me. If there is a lot of overlap in dependencies, then
a master tree sounds the way to go. If there is little or no overlap,
then I'd say, use a separate tree for each program.

>
> Part of this also includes a small history of the post-production process
> and how
> it has come to an almost 100% digital medium for filming, editing, and
> output.

Excellent. I'm sure that there are a lot of idiosyncracies in the
terminology and usage because a lot of the software computerizes what
used to be a mechanical or manual process. You (and probably I) would
be able to handle them where a postproduction newbie will have
problems with them.

> I'm also
> compiling a few sections on getting around with some of the tools, and
some
> sample uses,
> since many of the incoming formats are quite alien to a "work" print, so
to
> speak.

Good.

>
> There are some parts I won't write a complete section on, such as
compiling
> the kernel,
> as there are already HOWTOs out there on the subject. Mainly I just
discuss
> how to optimize
> the kernel for video and sound development (i.e, just the kernel options
for
> make menuconfig).

Excellent.

Do you have an outline yet, and is it on the net where we can see it?
Thanks.

--

Charles Curley                  /"\    ASCII Ribbon Campaign
Looking for fine software       \ /    Respect for open standards
and/or writing?                  X     No HTML/RTF in email
http://www.charlescurley.com    / \    No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

Linux Post-Production HOWTO Outline

1 - Introduction

2 - Getting Started

3 - All About DVDs
	3.1 - Physical Structure of a DVD*
	3.2 - Logical Structure of a DVD
	3.3 - The DVD-Video Standard
	3.4 - Hybrid DVD-ROMs

4 - The Post-Production Process
	4.1 - Traditional Post-Production*
	4.2 - Digital Post-Production*

5 - Hardware
	5.1 - Minimum Requirements*
	5.2 - Processor*
	5.3 - RAM*
	5.4 - Hard Drive(s)*
	5.5 - Video Capture Devices*
	5.6 - DVD Burner*
	5.7 - Sound Card*

6 - Software Installation
	6.1 - Linux Distributions*
	6.2 - Xine*
	6.3 - Mjpegtools*
	6.4 - CinePaint (formerly Film Gimp)*
	6.5 - Audacity*
	6.6 - Cinelerra*
	6.7 - dvdauthor*
	6.8 - dvdrtools*
	6.9 - mplayer**
	6.10 - Master Dependency Tree**

7 - System Tuning
	7.1 - Compiling an Optimized Kernel**
	7.2 - Hard Drive Optimization**

8 - Editing and (Re)Mastering
	8.1 - Intermediate File Formats
	8.2 - Stripping Audio from Video
	8.3 - Cleaning Video
	8.4 - Cleaning Audio
	8.5 - Multiplexing and Subtitles

9 - Putting Together the Finished Product
	9.1 - Creating menus with dvdauthor
	9.2 - Creating the DVD ISO with dvdrtools
	9.3 - Burning to DVD
	9.4 - Other Possible Output Formats

10 - Links

Previous by date: 4 Jan 2004 22:03:48 -0000 Re: Review: Vim as XML Editor HOWTO, Tobias Reif
Next by date: 4 Jan 2004 22:03:48 -0000 Re: man pages, Michael Still
Previous in thread: 4 Jan 2004 22:03:48 -0000 Re: Putting Together Information For a HOWTO, Charles Curley
Next in thread: 4 Jan 2004 22:03:48 -0000 Re: Putting Together Information For a HOWTO, Charles Curley


  ©The Linux Documentation Project, 2014. Listserver maintained by dr Serge Victor on ibiblio.org servers. See current spam statz.