From: chuck gelm <chuck@gelm.net>
To: haltec@kvinet.com
Cc: linux-newbie@vger.kernel.org
Subject: Re: tovid - videotrans ? (was Re: Convert .avi to .vob/Linux only??)
Date: Tue, 28 Feb 2006 18:08:20 -0500 [thread overview]
Message-ID: <4404D7E4.70301@gelm.net> (raw)
In-Reply-To: <20060228195752.GA1048@lnx2.kvinet.com>
Hal MacArgle wrote:
> <snip>
>
>
> Thanks Chuck for saving me a lot of leg work.. I suspect, not
>really knowing, that dvdauthor would be a big stumbler because it's a
>very powerful program and we only need a, probably, small part of
>it..
>
> Correct me if I'm wrong but I am beginning to see why it's
>not __easy__... The .avi file/s/ are viewable by themselves but the
>kicker is to get them on a DVD blank in iso9660 format, for one, plus
>
>
I can create an iso9660 DVD without much difficulty.
I used 'growisofs'.
This cannot be viewed on my DVD player, however. :-(
I revisited 'videotrans ./configure' after aquiring the items
required by 'tovid'. Videotrans then 'configure'd, 'make'd, and 'make
install'd.
:-)
It creates folders AUDIO_TS and VIDEO_TS.
However, the 'man' page leaves me lost at the last step:
'a_command_to_burn_a_dvd_from dvd_directory'. :-|
So, what is the command?
---
My 2 GHz Athlon takes over 40 minutes per 350 MB .avi,
so compare this file size and time to your own. :-|
Please show your commands that resulted in a viewable DVD.
Especially your 'a_command_to_burn_a_dvd_from dvd_directory'.
Regards, Chuck
p.s. Perhaps we should take this off list or to a videotrans/tovid list.?!
>into the various video_ts--.vob files plus .ifo and .bup files. etc..
>For kicks I tried a Win98 scheme and it tought me something, mainly
>that you need much more storage than suspected because it writes
>everything to a temp file; not simply file direct to DVD... Bottom
>line with my Duron 1.3M with 512M memory, in a Win98SE partition it
>took almost 3 hours to do the deed, most of the time "converting"
>"rather than "burning," with a DVD+RW 2.4X blank.. I bought some 8X
>blanks to see if that speeds things up a mite; suspect not that
>much... (Plextor PX-708A unit)
>
> I'm guessing that the various routines with Linux; each
>operation is broken down into bits and pieces.. Actually that's what
>we do with CD burning anyway, eh?? Please edit any mistakes above.
><grin> And, oh yes, the burned DVD views fine on an old standalone
>DVD player, that we use for viewing commercial movies..
>
> Update: I just found, buried in my shack, a 3 page txt copy of
>an article by Chris Stoddard; "DVD Authoring." I haven't a clue where
>I fetched it from.. It goes into some good details, some of which may
>not be needed for newer drives.. Worth a look see, maybe?
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2006-02-28 23:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 15:24 Convert .avi to .vob/Linux only?? Hal MacArgle
2006-02-24 19:01 ` Ray Olszewski
2006-02-24 19:13 ` Conway S. Smith
2006-02-24 19:30 ` Stephen Samuel
2006-02-28 2:12 ` tovid - videotrans ? (was Re: Convert .avi to .vob/Linux only??) chuck gelm
2006-02-28 19:57 ` Hal MacArgle
2006-02-28 21:47 ` Ray Olszewski
2006-03-01 21:38 ` Hal MacArgle
2006-02-28 23:08 ` chuck gelm [this message]
2006-02-24 21:30 ` Convert .avi to .vob/Linux only?? Artūras Moskvinas
2006-03-01 22:08 ` Videotrans ... " chuck gelm
2006-03-03 14:47 ` Hal MacArgle
2006-03-16 19:58 ` Hal MacArgle
2006-03-16 20:48 ` chuck
2006-03-16 23:09 ` Ray Olszewski
2006-03-17 18:48 ` Hal MacArgle
[not found] ` <441C6007.50000@comarre.com>
2006-03-22 14:14 ` Hal MacArgle
2006-03-17 13:54 ` Hal MacArgle
-- strict thread matches above, loose matches on Subject: below --
2006-02-28 23:17 tovid - videotrans ? (was Re: Convert .avi to .vob/Linux only??) chuck gelm
2006-03-01 9:59 ` Stephen Samuel
2006-03-01 10:00 ` Stephen Samuel
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=4404D7E4.70301@gelm.net \
--to=chuck@gelm.net \
--cc=haltec@kvinet.com \
--cc=linux-newbie@vger.kernel.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