Hallo
> > Might be a interresting idea to be able to tell yuvfps you own
> > resampling style.
>
> Doesn't it exist in Kino ?
I don't know. I do not have a DV video source. So I don't need to use
kino.
> That could be another option for me, to convert the all lot in DV then use
> the Fx slow dow
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
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
>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
>>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
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
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
> 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...
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
> 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
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 Mon, 24 Jan 2005, Trent Piepho wrote:
> On Tue, 25 Jan 2005, E.Chalaron wrote:
> > 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
I was curious how the Super8 conversion was goi
On Tue, 25 Jan 2005, E.Chalaron wrote:
> 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.
Most efficient would be to create a custom soft-pulldown that goes from 18 to
25 or 50 since
13 matches
Mail list logo
