if I have a source of 100 fps, how I have to do to convert to 25 fps?

[marcorocchini]

Hi cats,

I have a gopro mp4 file recorded @ 100 fps

I would like convert it to 25fps (without jerking) via avisynth, and via virtualdub: how I have to do?

thanks

[hello_hello]

I don't think there's much alternative other than deleting frames.

ChangeFPS(25,1)

http://avisynth.org.ru/docs/english/corefilters/fps.htm

[Cornucopia]

Do you want it to S-L-O-W D-O-W-N? (just change the header info, or use AssumeFPS in AVISynth).

or

Do you want it to run the same length of time, but at the slower framerate? (use ChangeFPS, or do some other types of interpolation/blending).
Note that any of your choices for this 2nd option are going to look worse than the original. Just depends on what kind of look you want it to have.

Scott

[johns0]

Try handbrake and set the fps to 25,see if it plays with no issues.

[jagabo]

I have a gopro mp4 file recorded @ 100 fps

I would like convert it to 25fps (without jerking) via avisynth

AssumeFPS(25) # slow motion

or

ChangeFPS(25) # decimate

or

Merge(SelectEven(),SelecteOdd()) # blend 2 frames together
Merge(SelectEven(),SelecteOdd()) # blend 2 frames together

[ndjamena]

dblur = 0.75
c = Merge(src.SelectEvery (4, 0, 1).SelectEven(), src.SelectEvery (4, 0, 1).SelectOdd(), weight = dblur)
d = Merge(src.SelectEvery (4, 3, 2).SelectEven(), src.SelectEvery (4, 3, 2).SelectOdd(), weight = dblur)
interleave(c,d).merge(SelectEven(), SelectOdd())

Merge(SelectEven(), SelectOdd())
AssumeTFF().SeparateFields().SelectEvery(4,0,3).Weave()

[marcorocchini]

this is a original mp4 from gopro hero3+ recorderd at 100 fps but seems to me quality is very very very bad, it have a native aliasing in details

https://www.dropbox.com/s/1jp2mhc8zwd5hnh/GOPR1252.MP4?dl=0

However I have to decimate, not slowmotion.

Using this script:

FFVideoSource("C:\GOPR1252.MP4")
ConvertToYUY2(interlaced=true)

changeFPS(50)
Assumetff().SeparateFields().SelectEvery(4, 0, 3).Weave()

all semms ok but there is a lot of aliasing

[jagabo]

there is a lot of aliasing

That's what happens when you interlace very sharp video. Use a vertical blur to reduce it. Blur(0.0,1.0). Some editors have a "reduce interlace flicker" filter which limits the blur to areas where there are high contrast comb artifacts.

[ajk]

I think that has been re-encoded by Dropbox (or you have some bad settings in the GoPro). It should be able to record 100fps in very nice 720p quality, especially in good daylight like that. I've got the regular Hero3 and it's nothing like that at all.

EDIT: Never mind, it's just the online version that is really low bitrate. Downloaded file looks better, though I'd personally use the "protune" setting so you get more bitrate and less sharpening - you can always tinker with those later.

[marcorocchini]

sorry but I'm a cat and I don't know well english language, hoewver I think or I hope to have a "regular" Hero3+ black edition (what does mean regular? I think, or I hope, my gopro is original: or how I can determinate if my camera is original?) however I can switch on the protune but if I don't mistake the protune become "effective" only using the software developed by the gopro... but I cannot use it because I have to batch automate the mp4 files, and I have to put transcoded files into my timeline (I have a very very special editing software :=) it's so particularry).

Hoewver the question is: when shot video in 1280x720@100fps (bitrate is 30Mbps) image has native aliasing: image is "bad".

When I shot video in 1920x1080@50fps image is good or enough.

Dropbox don't re-encode: it's only a container of files

[jagabo]

Hoewver the question is: when shot video in 1280x720@100fps (bitrate is 30Mbps) image has native aliasing: image is "bad".

When I shot video in 1920x1080@50fps image is good or enough.

So don't shoot video at 720p100.

[marcorocchini]

ok but i loss the 100 fps feature. Seems this camera, in 100 fps, can work only @ 1280x720. However also the broadcast camcorder sony pdwf800 work bad @ resolution out of fullHD: it have the same problem of aliasing in details

[jagabo]

Probably because they over sharpen the video and use a poor scaler.

[ajk]

"regular" Hero3+ black edition (what does mean regular? I think, or I hope, my gopro is original: or how I can determinate if my camera is original?) however I can switch on the protune but if I don't mistake the protune become "effective" only using the software developed by the gopro

I mean I have a Hero3 Black without the plus.

Protune doesn't need any particular software, it's just an option that increases the bitrate and turns off any contrast enhancement and sharpening. It might not solve the aliasing problem entirely but it would probably help.

[Cornucopia]

@marcorocchini, don't blame the cats on not understanding: my cats have always understood my English just fine! Let's leave the cats out of it for once.

You CHOSE that software, you're not married to it. Use what is right for your overall work. If your cams are both at the point where your NLE isn't working well with it, either go back to cams that do, or get a new NLE!

And why are you using "interlace=true" on 720p100 material?!! 720 is A*L*W*A*Y*S progressive.

Scott

[pandy]

720 is A*L*W*A*Y*S progressive.

Scott

Nope - it can be interlaced too.

[Cornucopia]

It may be possible to CREATE interlaced 720, but it is NEVER legit. That's like using the DV codec on 640x480 material.

Scott

[marcorocchini]

because my broadcats television wants all in standard xdcam 1920x1080 interlaced 25fps. So settings of the NLE have to be correct, and files in timeline have to be previously correct transcoded

I wonder: can I write a avisynth script that convert all framerate for all source into a specific framerate, doing the correct conversion?

[marcorocchini]

[QUOTE=ajk;2347375]

Protune doesn't need any particular software,

if I don't mistake to have a sort of "4:2:2" files from gopro, it's necessary a gopro cineform studio or something of that because otherwise files from gopro are only 4:1:1

[ajk]

@marcorocchini

Well I don't know if the plus version is totally different from the previous one, but mine records everything as perfectly normal 4:2:0, AVC encoded MP4 files, with protune or without.

[_Al_]

I wonder: can I write a avisynth script that convert all framerate for all source into a specific framerate, doing the correct conversion?

sure, all it needs is more script writing,
you focused on fixing avisynth script using avisynth scripting, but for more possible scenarios I guess it is better to use batch scripting, something like,

echo loading clip as you like             > avisynth_script.avs
if %fps%==25 if %field_order%==tff call :double_fps_deinterlace 
if %fps%==25 if %field_order%==bff call :double_fps_deinterlace 
echo # now you have all video 50p >> avisynth_script.avs
if %width%  NEQ 720 call :resize  
echo ....reinterlace    as you like       >> avisynth_script.avs 

:double_fps_deinterlace
echo assume%field_order%()          >> avisynth_script.avs
echo ... you deinterlace as you like  >> avisynth_script.avs
goto :eof

:resize
echo Spline36Resize(720,576)        >> avisynth_script.avs
goto :eof

you know, you can write avisynth script all over your batch file, it does not have to be continuously written, you can interleave it with batch script ...

[Cornucopia]

If you are getting 4:1:1 from your gopro, you are doing something very wrong. ALL gopro cams shoot AVC in MP4 @ 4:2:0.

Scott

[marcorocchini]

I hope the line ConvertToYUY2(interlace=true) of avisynth take well all 4:1:1 or 4:2:0 videos (or not?), hoewver my target is have 4:2:2 converted files

[pandy]

It may be possible to CREATE interlaced 720, but it is NEVER legit. That's like using the DV codec on 640x480 material.

Scott

Nope is perfectly legit as perfectly legit is to have 1440x810i60 - why the heck it can be not legit? - unless You referring to some particular recommendation or requirements then it is perfectly legit and allowed and can be useful to stay within codec limit by selecting this kind of format.

[Cornucopia]

Sure, you keep telling yourself that...

Scott

[jagabo]

legit != industry standard

[pandy]

legit != industry standard

lol - http://www.yify-torrent.org/search/720p/ 1280*688, 1280*694, 1280*528 - i love industry standards in home video... especially if combined with frame rates - yep - definitely not allowed and police will hunt your home...

Guys, don't get me wrong but nowadays there is no standards even in broadcast - bunch of retards with final cut doing materials for emission which are sent with reverse dominance field and directly affecting customers... i would say having 720 in interlace seem to be not biggest problem of industry standards...
And it is perfectly valid and legal from codec perspective and naming it not allowed or illegal sound like almost hate speech...

[hello_hello]

QTGMC has settings for adding motion blur. I haven't downloaded the sample video but it might be an alternative to frame blending. I haven't played around with it enough to know if it'd be any better or worse in this case.

Normally, when using QTGMC to de-interlace to half frame rate, you'd add motion blur in a manner like this (copied from the help file)

QTGMC( Preset="Slower", FPSDivisor=2, ShutterBlur=1, ShutterAngleSrc=30, ShutterAngleOut=180 )

Or for progressive video:

QTGMC( InputType=1, Preset="Slower", ShutterBlur=1, ShutterAngleSrc=30, ShutterAngleOut=180 )

[hello_hello]

legit != industry standard

lol - http://www.yify-torrent.org/search/720p/ 1280*688, 1280*694, 1280*528 - i love industry standards in home video... especially if combined with frame rates - yep - definitely not allowed and police will hunt your home...

I don't think jagabo was passing judgement, just offering a definition of "legit" in this context.

What about...... well...... virtually every video I play??

Xvid encode video in AVIs with resolutions such as 720x400.
Almost all of my DVD encodes at 1024x576.
Unless I crop the borders to make them less legitimate in the process.
iTunes video with a 960x720 resolution and a 16:9 aspect ratio (for older AppleTV devices with a 24fps limit at 1280x720).
Which x264 encoder settings are legit? Must the Bluray compatibility options are used?
SRT subtitles, AAC audio....
Variable bitrate audio......

"Legit" video is the type I'm least likely to play.

[Cornucopia]

People can play all kinds of goofy variants in their own entertainment silos. But just try passing those along to others (who may not have the same setup as you) and see how far you get without problems (not counting the legal kind here, just technical). - That kind of thing happening on p2p sites is one of the main causes for the many VH threads aimed at fixing problems.

SRT & AAC are quite legit (I guess it depends on how they're used, though). x264 is, as you know, an encoder that can be pushed to do legit-type encodes or non-legit encodes.
Apple? hahaha. They love being an "industry leader" but rarely "play well with others", so they have historically had all kinds of non-standard stuff.

Torrents? I'm pretty sure that since nearly none of it is legally legit, very little of it is technically legit. That's an argument?

Maybe you should throw out mod2 as well?

Scott