Hallo
> > > Most efficient would be to create a custom soft-pulldown that goes from
> > > 18 to
> > > 25 or 50 since you are using pal. Something like 2:3:3:3:2:3:3:3:3 will
> > > convert 18 to 25. It would be a lot easier if you used NTSC framerates.
> >
> > Well not being a programer neither
On Tuesday 25 January 2005 17:25, Bernhard Praschinger wrote:
> > Captures produced by lavrec always end up in B/W. OTOH, I can take xawtv
> > and see my camcorders life feed in color!
> >
> > Specs:
> > lavrec -v2 -fa -iP -a0 -d2 record.avi
>
> Which input do you have selected in XAWTV ?
S-Vide
> Might be a interresting idea to be able to tell yuvfps you own
> resampling style.
Doesn't it exist in Kino ?
That could be another option for me, to convert the all lot in DV then use
the Fx slow down to get a proper speed. Results prove a bit choppy but not
sure that I have a choice right n
On Sat, 22 Jan 2005 09:36:05 -0800 (PST)
"Steven M. Schultz" <[EMAIL PROTECTED]> wrote:
> The latest version of libquicktime is 0.9.4 and it is necessary to
> use the cvs version of mjpegtools if you want quicktime support. You
> could try configuring mjpegtools using "--without
On Tue, 25 Jan 2005, Sebastian Singer wrote:
> took your advice and cvs'ed the files. But running autoconf259 produces
> errors and the configure script produced doesn't run either (no wonder I
> think).
>
> These are the errors:
> # autoconf259
> configure.ac:18: error: possibly undefined mac
Gday
I was wondering what could be the most efficient method to slow down a movie.
I have here some Super 8mm material that I reshoot frame by frame in ppm
files.
The original are playing at a nominal rate of 18 fps.
Once encoded in mpeg2, grany is almost running through the TV screen.
I thou
Hallo
> Are there any particulars involved wrt color / BW?
> Captures produced by lavrec always end up in B/W. OTOH, I can take xawtv and
> see my camcorders life feed in color!
>
> Specs:
> lavrec -v2 -fa -iP -a0 -d2 record.avi
Which input do you have selected in XAWTV ?
If it is Composite -i p
>> This minor update does two.five things:
>>
>>o Implement Keys' 4th-order cubic kernel --- as 'cubicK4' ---
>> as suggested by Nicholas Boos.
>>
>>o Make 'cubicK4' the default kernel.
>
> Oh, so the default is cubicK4 rather than sinc:6 (which I believe
> was m
> I was curious how the Super8 conversion was going - good to hear it's
> progressed to the stage of encoding the data.
almost there..
> The duplicated frames will compress very well but I agree that the
> motion will not be as smooth.
Well, can not have everything...
On Tue, 25 Jan 2005, E.Chalaron wrote:
HI!
I see this item was delayed in the queue for quite some time. I
saw a reply long before the actual start of the thread arrived.
Strange.
>INFO: [mpeg2enc] Aspect ratio code: 1 = 1:1 pixels
Oops - but I thin
On Tue, 25 Jan 2005, E.CHALARON wrote:
> On Tue, 2005-01-25 at 15:40, Trent Piepho wrote:
>
> > Most efficient would be to create a custom soft-pulldown that goes from 18
> > to
> > 25 or 50 since you are using pal. Something like 2:3:3:3:2:3:3:3:3 will
> > convert 18 to 25. It would be a lot e
>>INFO: [mpeg2enc] Aspect ratio code: 1 = 1:1 pixels
>
> Oops - but I think I know what caused that problem...
...
> It's probably necessary to specify the output SAR (-O sar=) before
> you give the size (-O size). That's so that y4mscaler knows
> what output sample
>here is the line I am using
>
>cat *.ppm | ppmtoy4m -F 18000:1000 -L | y4mscaler -I sar=1:1 -O size=720x576
>-O chromass=420_MPEG2 -O sar=PAL | yuvdenoise -b 20,20,680,536 -r 16 -t 2 -c
>80 -F -L 160 | mpeg2enc -r 16 -I 0 -B 96 -g 6 -G 15 -a 1 -H -4 2 -2 1 -F 2 -f
>8 -M 2 -p -o test_pull
On Tue, 25 Jan 2005, Matto Marjanovic wrote:
> (Actually, the problem was the "-a 1" given to mpeg2enc, which
> overrode the SAR tag output by y4mscaler.)
Oops - I didn't spot that one.
> The other thing that you probably should add is a "-O infer=exact".
...
> >Note how
Thanks all for your advice. Will do something about parameters :-) like
RTFM and behaving myself...
Anyway I have another small thing here.
A 400 ft reel of Super 8 comes to 28800 individual frames, which is obviously
too much to handle for bash/cat
I know that
find . -name \*.tga | xar
On Wed, 26 Jan 2005, E.Chalaron wrote:
> Thanks all for your advice. Will do something about parameters :-) like
> Anyway I have another small thing here.
> A 400 ft reel of Super 8 comes to 28800 individual frames, which is obviously
> too much to handle for bash/cat
I
On Tue, 25 Jan 2005, Matto Marjanovic wrote:
> The "-I sar=1:1" to y4mscaler is unnecessary --- the correct SAR will
> be read from the stream which ppmtoy4m creates. (And if that SAR
True - it is un-necessary. But when I use "-I sar=1:1" it is not
to _override_ but to _remind
17 matches
Mail list logo
