MrBunny
24th February 2003, 02:25
Hey guys, I was just thinking (quite the rarity) about hybrid clips again and was hoping I could get some opinions on the possibility and/or utility of having external filterschains triggered by decomb's decimate metrics. The syntax would probably be similar to Marc's MAM filter. It would allow extra flexibility with hybrid clips since you'd be able to choose exactly what filters to use when something is NTSC, and when it's FILM. This could be invaluable for those that think they have a nicer or better approach for a certain type of hybrid material, or just for experimentation. For example (I'll call the filter DecimateWrapper for now):
DecimateWrapper(cycle, threshold (a la decimate), filter(s) for below threshold, filter(s) for above threshold)
To mimic telecide().decimate(mode=3,cycle=5) behavior:
Telecide()
DecimateWrapper(cycle=5, threshold=0.5, decimate(mode=0,cycle=5), Convertfps(23.976).temporalsoften(3,5,5,mode=2,scenechange=10))
So anything below the threshold of 0.5 would be simply decimated as usual and anything above would be convertfps'd then tempsoftened.
Similarly, for decimate(mode=1,cycle=5) you could use:
DecimateWrapper(cycle=5, threshold=0.5, TomsMoComp(1,15,1), FieldDeinterlace().Decimate(mode=1, threshold=0.5, cycle=5))
In this case, you'd be able to use TomsMoComp instead of FieldDeinterlace for NTSC portions but still retain the nice mode=1 interpolation ability.
I guess some checks would need to be added to make sure the two filter setups come up with the correct fps, and i'm not even sure the initial cycle=x is necessary at all since the external filters would be the ones actually doing the frame manipulation. I don't know how hard it would be to impliment, but it shouldn't be too hard as it's more of a meshing of ideas than anything revolutionary.
Just a thought :)
Mr. B
DecimateWrapper(cycle, threshold (a la decimate), filter(s) for below threshold, filter(s) for above threshold)
To mimic telecide().decimate(mode=3,cycle=5) behavior:
Telecide()
DecimateWrapper(cycle=5, threshold=0.5, decimate(mode=0,cycle=5), Convertfps(23.976).temporalsoften(3,5,5,mode=2,scenechange=10))
So anything below the threshold of 0.5 would be simply decimated as usual and anything above would be convertfps'd then tempsoftened.
Similarly, for decimate(mode=1,cycle=5) you could use:
DecimateWrapper(cycle=5, threshold=0.5, TomsMoComp(1,15,1), FieldDeinterlace().Decimate(mode=1, threshold=0.5, cycle=5))
In this case, you'd be able to use TomsMoComp instead of FieldDeinterlace for NTSC portions but still retain the nice mode=1 interpolation ability.
I guess some checks would need to be added to make sure the two filter setups come up with the correct fps, and i'm not even sure the initial cycle=x is necessary at all since the external filters would be the ones actually doing the frame manipulation. I don't know how hard it would be to impliment, but it shouldn't be too hard as it's more of a meshing of ideas than anything revolutionary.
Just a thought :)
Mr. B