Seems to be a wrong understanding about what is going on with s3D. The active shutter displays work with 120Hz - but that does not mean that the footage has to have 120 fps. The s3D PAL camcorder record with either 1080 50i or 1080 24p. 1080 50i is an issue (but so is 1080 60i of NTSC units), since 3D Blu-ray requires 1080 24p or 720 50p. The conversion to 120hz takes place by the active shutter unit.

So there is no need to interpolate frames to 120 fps.

Seems to be a wrong understanding of my post :)

I want to convert my 50p footage to 60p, not 120, its just the 3D refresh rate, which works great with 60fps video, but not with 50fps. S3D PAL camcorders? What if i use my own dual cam setup with 2x 50p cameras? :)

Who talked about 3D Bluray and 24Hz? I hate it for family videos, etc.

There is even no need to go to 60p. A lot of people use the stereoscopic player if they hate BDs. Even if there are players that run 3D-BD images without an issue.

Sorry, looks like you still don't understand my problem. A real 60p video looks much better in 120Hz 3D system, than 50p video (which i have) That's why i like to convert my 50 to 60p, without changing duration of course. Twixtor do the job, but at 60x realtime render speed :(

Oh, i know and use Stereoscopic player since 10 years :)

Despite Twixtor being the "holy grail" of framerate resampling, 60p will never "look better" than its 50p source. Framerate smooting comes at the expense of frame sharpness, pick one.

Sorry to burst the bubble, but doggonit, I told you why four posts up ;?)

You may also try avisynth filters or function such as interframe or mvtools.

Musicvid: you didn't burst my bubble, when i wrote it looks much better, i only refer to motion judder, not the actual sharpness, of course.. 

Thanks GJeffrey, i will try some avisynth script with frameserver!

Here's a basic script for AviSynth converting a frameserverved D:\fs.avi file to 59.94p:

AviSource("d:\fs.avi")
ConvertToYV12()
super = MSuper()
backward_vec = MAnalyse(super, overlap=2, isb = true, search=3)
forward_vec = MAnalyse(super, overlap=2, isb = false, search=3)
MFlowFps(super,backward_vec, forward_vec, num=60000, den=1001, blend=false, thSCD1=304, thSCD2=100, ml=500)
AssumeFPS(59.94)

Here's my full script with comments and options ready ripping through footage at high speed in multi-threaded AviSynth+ on a machine with 32GB RAM. It does the same as the above script but much faster:

SetMemoryMax(3072) #3072 fastest for AVS or AVS+ x86. 4096 fastest for AVS+ x64.
#SetMTMode(3, 12) #12 fastest for AVS. Remove for AviSynth+

SetFilterMTMode("DEFAULT_MT_MODE", 2) #Only for AviSynth+

SetFilterMTMode("AviSource", 3) #Only for AviSynth+

#Frameserve in RGB24 format (or RGB32 if AviSynth will not accept RGB24)
AviSource("d:\fs.avi")
ConvertToYV12(matrix="Rec601") #Rec601 is correct for encoding MagicYUV etc. in Vdub

#SetMTMode(2) #Disable for AviSynth+

super = MSuper()
backward_vec = MAnalyse(super, overlap=2, isb = true, search=3)
forward_vec = MAnalyse(super, overlap=2, isb = false, search=3)

#"num" equals result of 30 fps, times 2, multiplied by slo-mo factor 
#So, 60000 equals normal speed; 120000 equals 50% normal speed, etc.
#For PAL, num=50, den=1 equals normal speed, so go from there
#MFlowFps(super,backward_vec, forward_vec, num=24000, den=1001, blend=false, thSCD1=352, thSCD2=110) #23.976 out
#MFlowFps(super,backward_vec, forward_vec, num=48000, den=1001, blend=false, thSCD1=352, thSCD2=110) #23.976 out
#MFlowFps(super,backward_vec, forward_vec, num=30000, den=1001, blend=false, thSCD1=352, thSCD2=110) #29.97 out
MFlowFps(super,backward_vec, forward_vec, num=60000, den=1001, blend=false, thSCD1=304, thSCD2=100,ml=500) #59.94 out
#MFlowFps(super,backward_vec, forward_vec, num=60000, den=1001, ml=100, blend=false) #59.94 out

#AssumeFPS(23.976)
#AssumeFPS(25)
#AssumeFPS(29.97)
AssumeFPS(59.94)

Prefetch(16) #12 fastest for AVS+ x86. 16 fastest for AVS+ x64. Only for AviSynth+

If you want to try AviSynth+, use the standard installer for it then overwrite with Pinterf's dll from https://github.com/pinterf?tab=repositories Also grab his versions of mvtools and other dependencies you might need. You have to use 32-bit AviSynth+, not 64-bit, if you are frameserving.

GJeffrey and I have been using VirtualDub Filtermod to render, and running its VirtualDub.exe file through Large Address Aware.

Just ask if you want us to fill in the blanks to get this going.

Very nice, thank you!

I tried some avisynth script (mvtools2) with great result, but cpu usage is around 15%, and videos are converted in 30x realtime.

Now i have to finish the multithreaded version :)

The other day I had a variant of the 2nd script converting 59.94>23.976 in AviSynth+ x86 at 29fps. I think that's source frames, so it's half realtime. System specs in my profile.

This AviSynth switcher batch file is useful for trying different versions (link may be down right now so this might get you there), but you'll still have to shuffle the syntax of the .avs script around a bit for AviSynth+, as described here.

Sorry, looks like you still don't understand my problem. A real 60p video looks much better in 120Hz 3D system, than 50p video (which i have) That's why i like to convert my 50 to 60p, without changing duration of course. Twixtor do the job, but at 60x realtime render speed :(

Oh, i know and use Stereoscopic player since 10 years :)

Then the best approach could be to purchase to 60p cameras and pair them. I for my part have never seen an issue here, especially if one uses a 144Hz beamer. And I would never think about to use tools like Twixtor to correct such an issue - even if I think that it is not an issue at all.

No way, i record and project passive 3D with my 50Hz cameras, just like to show some videos with active system too. That's why i need to find a way to convert 50 to 60p. In Europe i could have a problem with NTSC cameras too with indoor lamp frequency.

Nobody talked 144Hz here. That's for 24p material, but i use 50p smooth motion..

Relax,

Interframe will be faster (as it's using GPU) but the overall quality will be lower than Nick's script. It might not be noticeable though.

If you want to try Interframe here is a script to change fps from 50 to 60fps (1st part is copy and paste from Nick's script above).
 

SetMemoryMax(3072) #3072 fastest for AVS or AVS+ x86. 4096 fastest for AVS+ x64. 
SetMTMode(3, 12) #12 fastest for AVS. Remove for AviSynth+ 
ConvertToYV12(matrix="Rec601") #Rec601 is correct for encoding MagicYUV etc. in Vdub
InterFrame(NewNum=60000, NewDen=1001, Cores=12, GPU=true)

This script is working with Avisynth 2.6MT only. Changes "Cores" depending on your CPU cores nb.

Should you need an AVS+ one, just follow Nick's link above.

FYI, speed test result with Interfarme (30 to 60fps with 2704x1520 footage)

Frameserving can't be used with x64 program unfortunately.

Man, a lot of new info here: avs mt, avs+, vdub filtermod, interframe, etc..

Ok, i played a few hours with the scripts..
First, i tried Nick's first script with my installed AVS.

It's not multithreaded, so i get around 10x realtime conversion speed (with overlap=0 setting)

Then i installed AVS MT, and tried Nick's 2nd script (remove # where needed). It was finally multithreaded, render speed was around 3x realtime on my i7 :)

But the problem with these scripts sometime it creates weird shapes from straight lines. See below

Then i tried interframe. Very quick, but not so sharp as above (can i improve somehow? i tried gpu true and false), but the big thing it doesn't product weird shapes from staight lines.

What shapes am i talking about? See:

https://s9.postimg.org/sbdk6f3qn/lines.jpg

Here is a 3 sec test file, it would be good to see, what can you do from it:

https://drive.google.com/open?id=0BzldgVVPxli7VTNWMmZzN1ZpaWs

I didn't tried AVS+, because i think it only made things faster but not better. 3x realtime is very acceptable for me.

thanks a lot!

With Interframe, you can play with the tuning parameter (film (default), smooth or weak).

But the problem with these scripts sometime it creates weird shapes from straight lines.

Yes, that happens sometimes, and it's easy to see how those 2 masts can get confused with each other when the camera is panning fast. Try adjusting the MFlowFps options. MFlowFps has its own section of this page, describing what the options do.

I can't remember the history of how I ended up with the figures in the script above. I tried a render with each of these 2 lines and arguably the shorter line (with more defaults) is a little better.

MFlowFps(super,backward_vec, forward_vec, num=60000, den=1001, blend=false, thSCD1=304, thSCD2=100,ml=500)
MFlowFps(super,backward_vec, forward_vec, num=60000, den=1001, ml=100, blend=false)

Are these scripts actually faster than Twixtor?

Twixtor speed is 60x, while MSuper with MT is 3x. So a MASSIVE 20x increase!! (and i didnt tried avs+)

Can you upload a comparison pair of encoded samples at those figures?

yes, i will

No way, i record and project passive 3D with my 50Hz cameras, just like to show some videos with active system too. That's why i need to find a way to convert 50 to 60p. In Europe i could have a problem with NTSC cameras too with indoor lamp frequency.

Nobody talked 144Hz here. That's for 24p material, but i use 50p smooth motion..

I am aware of all these issues like the disharmony between 50Hz light sources and 60p - but you are going in a complete wrong direction to my opinion. According to you approach nobody in the PAL countries sould be able to deliver s3D in an acceptable quality for active systems - and that is simply not true. I have never heard that professionals use such an workflow for s3D.

There would have been the much easier way to convert from 50p to 25p and then to 24p - but that requires to know how what is important during shooting (especially 1/50s) and then how to convert the footage to 24p if required. That can be done without any time consuming interpolations between the frames and maintains also the original quality.

But much luck with your trials.

Thanks but

1) No 25p,  i need the 50p (or 60p) smoothness. I'm sure people love my 3D films and projections (who hates 3D in cinemas) because of smoooth motion -> less headache.

2) 25 to 24p means slowdown. Which i don't want either.

So i shoot in 50p, but want to show a short demo with my active system sometimes, for which i need this 60p conversion. And this is faaar better with Avisynth than Vegas :)