Hi all.
It's why I came up with the pgmtoy4m program. The YUV4MPEG output
from mpeg2enc was a local hack (I think Andrew did it eons ago to
an old version of mpeg2dec).
Its actually *really* easy to do. I don't think mpeg2dec has changed all
that much in quite a
On Thu, 18 Dec 2003, Andrew Stevens wrote:
Its actually *really* easy to do. I don't think mpeg2dec has changed all
True, especially if the scaling part is left out. No need for YUVs,
YUVh, and so on.
On the other hand having a forked copy of mpeg2dec to maintain
Hallo
Its actually *really* easy to do. I don't think mpeg2dec has changed all
True, especially if the scaling part is left out. No need for YUVs,
YUVh, and so on.
That has historic reasons, because they were written at a time no scaler
(yuvscaler or Matto's scaler)
Am Dienstag, 16. Dezember 2003 01:53 schrieb Steven M. Schultz:
demuxing tool (I use mpgtx but transcode might have a tool for that
also).
tcextract -i test.mpg -x mpeg2 -d 1 test.m2v
tcextract -i test.mpg -x mp2 -d 1 test.mp2
Al
Does anybody have scripts/tools they use to do this? It is possible,
right?
...
Off the top of my head (finger memory) you'll want the latest
y4mscaler (0.6.1), a recent (preferably cvs) mpeg2dec (decoder) and
...
I'd recommend scaling down from 480x480 to 352x480
On Tue, 16 Dec 2003, Matto Marjanovic wrote:
mpeg2dec -s -o pgmpipe input.mpg | pgmtoy4m -i t -a 15:11 | \
y4mscaler -S option=sinc:8 -O sar=20:11 -O size=352x480 | \
mpegenc -f 8 -E -8 -K tmpgenc -4 2 -2 1 -o output.m2v
Yes, and the new -O preset=CVD will take care of all of
Huh? All that pgmtoy4m does is unpack the data from mpeg2dec -o
pgmpipe and slap a YUV4MPEG2 header on it (and FRAME markers). No
conversion done at all.
Ooops... I misread it as ppmtoy4m. Disregard everything I wrote.
This reminds me, maybe a better name for pgmtoy4m
On Tue, 16 Dec 2003, Matto Marjanovic wrote:
Ooops... I misread it as ppmtoy4m. Disregard everything I wrote.
Ok - consider it disregarded ;)
This reminds me, maybe a better name for pgmtoy4m is pgmpipetoy4m
--- because the current name makes it sound like it takes a PGM
This reminds me, maybe a better name for pgmtoy4m is pgmpipetoy4m
--- because the current name makes it sound like it takes a PGM (portable
gray map, a la NetPBM) as input, which it does not.
Technically it is a gray map - you can take the output of '-o pgm'
and view it
I have several dozen (s)vcd's I've made from digitizing the old VHS
collection. Now I finally have a DVD burner (woohoo!) and I want to
transfer them to DVD. I know I could get better quality by
re-capturing, re-editing and re-compressing, but I'm lazy. I just
want to take the 2 shrek VCD's and
On Mon, Dec 15, 2003 at 04:53:54PM -0800, Steven M. Schultz wrote:
Right - that's because the encoded frame size of a standard SVCD
is 480x480. Legal sizes for DVDs are 720x480, 704x480, 352x480
MPEG-2, and 352x240 MPEG-1
Ok, so much for SVCD's, but my VCD's are 352x250
On Mon, 15 Dec 2003, Barry Roberts wrote:
On Mon, Dec 15, 2003 at 04:53:54PM -0800, Steven M. Schultz wrote:
Right - that's because the encoded frame size of a standard SVCD
is 480x480. Legal sizes for DVDs are 720x480, 704x480, 352x480
MPEG-2, and 352x240 MPEG-1
Ok, so
Hallo
On Mon, Dec 15, 2003 at 04:53:54PM -0800, Steven M. Schultz wrote:
Right - that's because the encoded frame size of a standard SVCD
is 480x480. Legal sizes for DVDs are 720x480, 704x480, 352x480
MPEG-2, and 352x240 MPEG-1
Ok, so much for SVCD's, but my VCD's
13 matches
Mail list logo
