Full Field Blended Sources

CCChang · Post by **CCChang** » Sun Oct 28, 2007 7:24 am

Of all things...Darn...

I've read the guide and it suggests three solutions to solve it, all complicated in their own way. What are my other options should I not use those methods (apart from just buy the NTSC version of the DVD)?

Please help. I just got that urge to make AMV's again and now this is annoying me to death.

Many thanks in advance.

Bauzi · Post by **Bauzi** » Mon Oct 29, 2007 11:01 am

I work with full blended material and personaly I don´t think that it sucks too much (beside making masks and other effects). I tried some functions, but they never really worked -.-'

I suggest you to buy the NTSC versions if you have the easy chance to do it. Restoring these full blended material is a pain in the ass and often goes to the unimpossible.

I just got that urge to make AMV's again and now this is annoying me to death.

If you need an example of amvs with full blended source you can check out my two amvs than you´ll see if you´re pleased or not with these footage in action:

(more simpel editing)

(with heavy use of effects)

You can also just try some stuff and than decide if you want to work on with the source. If you don´t like the methods than don´t

I really hope that this post will help you to decide.

Sereenie · Post by **Sereenie** » Tue Oct 30, 2007 11:45 am

MRestore has given me good results for both European and North American releases.

(I know the guide says it only works for PAL, but it's not true.)

S.

Bauzi · Post by **Bauzi** » Tue Oct 30, 2007 4:32 pm

Wow. MRestore really helped my source at some parts.

But there is a new problem with it:

Alright so I tried MRestore:
Here is my code.

Code: Select all

#Bob()
#Mrestore(quality = 2) #Braucht Bob zuerst
#TDeint()

The original amount of frames is 56974, but when I activate Bob() and MRestore() I have just 54640 =/ That would crush the sync of the project.

MRestore(quality 0) #lowest quality
still slows down the speed of my script. That´s not really good.

How can I work around the loose of script velocity without bait&switch methode? Has anybody an idea how to come back to the original framerate?

BasharOfTheAges · Post by **BasharOfTheAges** » Tue Oct 30, 2007 4:38 pm

uh... filtering that alters the frame rate needs to be done before you edit.

Bauzi · Post by **Bauzi** » Tue Oct 30, 2007 4:49 pm

Nevermind I found the solution in the filter itself (this is pretty though stuff):

parameter: numr/denm
You don´t need to set the decimation parameters for the norm conversions restoring Pal_to_NTSC (50->23.976 or 25->11.988)
and NTSC_to_Pal (59.94->25 or 29.97->12.5), but for some seldom other blend conversion restoring
(for example 29.97 back to 23.976 or 50 to 25 - DEFT).
Mrestore use the numerator and denominator instead of a output framerate parameter, because it´s more accurate.
If you know the output framerate you can use these three conditions to calculate the best values for numr and denm:
1) numr and denm are integers
2) input framerate * numr = output framerate * denm = integer
3) (output framerate * x) / (input framerate * x) = numr / denm = smallest possible proper fraction
=> a good starting point for NTSC and Pal sources is the factor 2002.
- Example:
numr = output framerate * 2002 = 25 * 2002 = 50050
denm = input framerate * 2002 = 59.94 * 2002 = 60000 / 1001 * 2002 = 120000
numr / denm = 50050 / 120000 = 1001 / 2400
=> numr = 1001, denm = 2400

To sum it up. To keep PAL stuff at 25fps the parameters "numnr = 1" and "denmr = 2 ". The default settings were for Pal -> NTSC framerate.

Really really tricky =/

My function so far:
Mrestore(quality = 2, mlimit = 0.2, ani = true, numr = 1, denm = 2)
Slow as hell! But nice.

Sereenie · Post by **Sereenie** » Tue Oct 30, 2007 4:56 pm

See my previous post about Mrestore. It might have something to do with that. Those numbers are for NTSC sources though, so you'd have to read up in the documentation to find the right numbers for PAL (which, understandably enough, I don't know by heart!).

Though I'm wondering if that simply isn't just a normal result for this process. It wouldn't surprise me that removing the blending also involved removing a couple of frames. If so is the case, then of course it wouldn't be a problem as long as the footage is cleaned up before starting a project. In your situation... I'm not too sure what can be done besides readjusting the synch. 30 frames isn't much, but it's still a pain in the butt...

S.

Sereenie · Post by **Sereenie** » Tue Oct 30, 2007 4:58 pm

Oops! You replied while I was searching the forum to reply properly!

I'm just glad you found your solution.

S.

Bauzi · Post by **Bauzi** » Tue Oct 30, 2007 5:07 pm

I thought that the PAL settings are default. I got the MRestore stuff from a german (I think so) programmer who posted the stuff in a sticky thread. It was in the german doom9 section/forum and I often read that full blended stuff comes with stuff scalled to PAL. That it appear in NTSC too was something new to me

Uh... Seams that I did my amv homework for today and move now to the funny part, editing =D

CCChang · Post by **CCChang** » Fri Nov 02, 2007 8:08 pm

Bauzi wrote:Wow. MRestore really helped my source at some parts.

But there is a new problem with it:

Alright so I tried MRestore:
Here is my code.
Code: Select all
#Bob()
#Mrestore(quality = 2) #Braucht Bob zuerst
#TDeint()
The original amount of frames is 56974, but when I activate Bob() and MRestore() I have just 54640 =/ That would crush the sync of the project.

MRestore(quality 0) #lowest quality
still slows down the speed of my script. That´s not really good.

How can I work around the loose of script velocity without bait&switch methode? Has anybody an idea how to come back to the original framerate?

I'll try this first when I have time.

Anything else I should try while I'm at it?

Thanks in advance.