Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Capturing and Editing Video > Avisynth Usage

Reply
 
Thread Tools Search this Thread Display Modes
Old 28th July 2014, 21:58   #801  |  Link
manono
Moderator
 
Join Date: Oct 2001
Location: Hawaii
Posts: 7,260
Quote:
Originally Posted by johnmeyer View Post
Shouldn't the question be: "is film referred to later in the script?
No.
Quote:
If you temporarily change the script so that the final statement is:

return(source)

does it play correctly?
My point exactly. Once the 'QTSource(Film...' is replaced by 'Source', you have to refer to that film in any future lines by 'Source'. Or maybe we're saying the same thing in different words.

I don't use the script and don't know how it opens a video. My only point was that if he uses 'Source=', in the future he has to continue to use it unless it's replaced by something else. To begin to diagnose the problem I'd stick 'return(source)' right after the first 'Source=' line, open the script in VDub to see if the video gets opened, and then go on from there.
manono is offline   Reply With Quote
Old 28th July 2014, 22:03   #802  |  Link
johnmeyer
Registered User
 
Join Date: Feb 2002
Location: California
Posts: 2,194
Quote:
Originally Posted by manono View Post
To begin to diagnose the problem I'd stick 'return(source)' right after the first 'Source=' line, open the script in VDub to see if the video gets opened, and then go on from there.
Yes, I think we are definitely saying the same thing, in different words. I agree 100% with your recommendation that I quoted.
johnmeyer is offline   Reply With Quote
Old 29th July 2014, 00:28   #803  |  Link
papcom
Registered User
 
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
Quote:
Originally Posted by johnmeyer View Post
If any of your plugins are NOT in the original plugin directory, then you must load them explicitly. Since your earlier posts described a problem with plugins not loading, then perhaps this is the issue.
I am using the script and installation of videofred and he is using a proprietary plugin Folder and source Folder which are not within the avisynth Installation.

Anyway in videofred's scripts there is no explicit plugin path indicated for his plugins in use ...and this works normally.

Quote:
LoadPlugin("plugins/Deflicker.dll")
Loadplugin("plugins/Depan.dll")
LoadPlugin("plugins/Depa.......
What I do not understand is the fact that normally the plugins of avisynth are in the avisynth plugin folder (as QTSource.dll, DirectShowSource.dll etc) but the plugins for videofred scripts are in his special folder outside of the avisyth Installation?

Why can't the filter plugins and sources for videofred's script not be within the avisynth directory as all other plugins?

Re QT ... I have QT on my WIN7 PC and I use QTSource sucessfully to open MOV's in avisynth (except for videofred's script)
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore

Last edited by papcom; 29th July 2014 at 00:31.
papcom is offline   Reply With Quote
Old 29th July 2014, 05:35   #804  |  Link
raffriff42
Retried Guesser
 
raffriff42's Avatar
 
Join Date: Jun 2012
Posts: 1,377
Quote:
Originally Posted by papcom View Post
Why can't the filter plugins and sources for videofred's script not be within the avisynth directory as all other plugins?
Because DLL Hell. VideoFred does not want to support all versions, past and future, of the plugins he uses. A wise decision.

I wonder if your problem occurs at this line in the script:
Code:
film= "C:\Users\You\Documents\Yourfile.avi"  # source clip, you must specify the full path here
raffriff42 is offline   Reply With Quote
Old 29th July 2014, 13:08   #805  |  Link
papcom
Registered User
 
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
Quote:
Originally Posted by raffriff42 View Post
Because DLL Hell. VideoFred does not want to support all versions, past and future, of the plugins he uses. A wise decision.

I wonder if your problem occurs at this line in the script:
Code:
film= "C:\Users\You\Documents\Yourfile.avi"  # source clip, you must specify the full path here
That's this section I actually use:
Quote:
#film= "E:\myvideo.avi" # source clip, you must specify the full path here
# YUY2 (default)
film= QTInput("E:\S8_kaltersee_.mov", color=2)
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore
papcom is offline   Reply With Quote
Old 29th July 2014, 16:44   #806  |  Link
johnmeyer
Registered User
 
Join Date: Feb 2002
Location: California
Posts: 2,194
The way the script is written, the variable "film" simply points the file that contains your film/video. Then, later in the script, this variable is fed to the AVISource function that then reads the video from that file.

What you have done -- and this definitely will cause problems -- is to change the "film" variable into something different: it now actually contains the video rather than simply containing the file name of the video. When this different type of variable then later gets fed to the AVISource function, it doesn't know what to do with it.

The correct way to modify the script in order to have it work with a QuickTime video is to leave the "film = ..." line alone (keep it the way Fred wrote it) and instead modify the AVISource line in the way that I already described in my previous post.

I didn't realize that you had modified other parts of the script, and that's why my earlier advice didn't work for you.
johnmeyer is offline   Reply With Quote
Old 29th July 2014, 17:04   #807  |  Link
papcom
Registered User
 
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
thanks to all of You for the help - it made click and now it's running with my ProRes MOV's.

the following lines in my script solved the QT Mov Import:

Quote:
film= "E:\S8_kaltersee_.mov" # source clip, you must specify the full path here
and

Quote:
source= QTInput(film).assumefps(play_speed).trim(trim_begin,0).converttoYV12()
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore
papcom is offline   Reply With Quote
Old 30th July 2014, 00:43   #808  |  Link
papcom
Registered User
 
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
Aspect Problem of Output Video

I notice that I have a slight aspect problem with my videofiles processing with videofred's script: The video is slightly squeezed, (/a circle is a slight Ellipse in heigh)

My Input video is 720x576(rect.pixelformat) and has about 10pixel black on left and right side (this blanking comes from the capture camera).

I guess that if I could crop this 10px left/right the aspect could be corrected. But I did not yet find out where to adjust this parameter.

When I alter the values in the script at "size crop and borders Parameter" I always have issues with the Stabilisation. (large green/black artefacts on the side)

Has anybody a hint for me, where exactely I could correct this aspect problem?
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore

Last edited by papcom; 30th July 2014 at 00:46.
papcom is offline   Reply With Quote
Old 30th July 2014, 02:07   #809  |  Link
johnmeyer
Registered User
 
Join Date: Feb 2002
Location: California
Posts: 2,194
OK, I'm glad you got the first problem fixed.

Most (although not all) of the cropping and re-sizing parameters must be done in MOD4 (divisible by four). Therefore you will probably have problems cropping 10 pixels from each side. Try instead doing 8 or 12 pixels.
johnmeyer is offline   Reply With Quote
Old 30th July 2014, 02:18   #810  |  Link
johnmeyer
Registered User
 
Join Date: Feb 2002
Location: California
Posts: 2,194
Also, the "size crop and borders parameters" actually contains three sets of variables. Which ones are you altering? The Cleft, Ctop, etc. are designed to remove the black borders introduced by the Depan stabilization. They are NOT what you want to use if you are attempting to remove black borders that are in the original video. I actually re-wrote Fred's script, and have posted my changes elsewhere in this thread. I documented in those other posts all the things that I changed (I changed a LOT of things), but one thing I added was an additional set of crop variable to handle film transfers that already contained black borders. I use a NTSC DV camera (720x480) for my captures, and it captures more or less a 4:3 aspect ratio. However, while Super 8 film is this same aspect ratio, regular 8mm film is closer to 1:1 and therefore has black vertical bars on each side. You can't simply crop these out and expand the resulting footage because you will then end up with very fat people (i.e., everything is stretched horizontally). If you don't do anything, these black pillars end up wandering around because of the motion stabilization. What I instead had to do was temporarily crop the video, then motion stabilize, and then add back the black borders.
johnmeyer is offline   Reply With Quote
Old 31st July 2014, 18:11   #811  |  Link
papcom
Registered User
 
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
@johnmeyer - I found Your script and I am trying to work with it but still have some slight loading difficulties:

In Your script You use the following plugins which differ from videofred's script resp. are absent there:

autolevels.dll
mt_masktools.dll
RemoveDirtSSE2.dll
RemoveGrainSSE2.dl


Actually I try to find these plugins (DLL and sources) on the net.

1. I can only find autolevels_06... Do I have to rename it to "autolevels.dll ?!
2. unfortunately I cannot acquire RemoveGrainSSE2.dll - (site down)... Is there an alternative?

I assume to put the plugins in the same plugin folder as videofred's plugins?
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore

Last edited by papcom; 31st July 2014 at 18:41.
papcom is offline   Reply With Quote
Old 31st July 2014, 20:40   #812  |  Link
johnmeyer
Registered User
 
Join Date: Feb 2002
Location: California
Posts: 2,194
Here's a link to my version of Fred's script. I have included the plugins you requested. These are the versions used by my script. I did not include MVTools2, because you should easily be able to get that elsewhere, and I don't think anything my script is doing is dependent on minor version changes in that DLL.

johnmeyer version of Fred's script, with needed DLLs

Please note that my script significantly departs from what Fred has been doing, and does not contain many of the enhancements he made in his last interation, most notably some of the changes he has made to autolevels and color correction. I choose to do those things instead inside of my editing program (Sony Vegas).

Just to reiterate what I've said in earlier posts, the main reason I chose to revise his work is that I found that his version adds too much sharpening for the kinds of films I have to deal with, most of which are very old and full of dirt. Too much sharpening does not work well with those films. I also spent a LOT of time changing things to improve performance, and if you can utilize the multi-thread features of my script, you should be able to get at least a 2-3x performance improvement.

Finally, even though I significantly decreased the amount of sharpening, I still often reduce it even further from the default settings that the version of the script I'm posting uses. You should most definitely look at each set of variables in the script and decide if you want to change any of them. Also, the "result=" line is set to "4" which means it uses no autolevels or autowhite functions, and does not provide a "before & after" side-by-side comparison. Change "4" to "S4" if you want that feature. If you want to have deflicker capability, just search on that word, and you'll find two almost identical lines, one after the other, one of which is commented out that contains the deflicker function. Just comment out the line that doesn't have that function, and use the other line instead.
johnmeyer is offline   Reply With Quote
Old 1st August 2014, 11:14   #813  |  Link
papcom
Registered User
 
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
thank You very much John Meyer for your help. I will go through all of this now.

The first Thing I noticed is the NTSC Format You use. Therefore I will will have to adapt the script to 720x576 and 25 fps.

Where do the plugins belong? Do You have the same Folder structure as videofreds Installation? (I have my diffictulies in makingh the script work because it cannot load the dll's as long as the script is not in the same folder as the plugins.)

Also I do have a script error : there is no function named mtsetmode ...
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore

Last edited by papcom; 1st August 2014 at 11:58.
papcom is offline   Reply With Quote
Old 1st August 2014, 19:32   #814  |  Link
johnmeyer
Registered User
 
Join Date: Feb 2002
Location: California
Posts: 2,194
Quote:
Originally Posted by papcom View Post
The first Thing I noticed is the NTSC Format You use. Therefore I will will have to adapt the script to 720x576 and 25 fps.
Just change the numbers in the variables section. That's all you have to do.

Quote:
Originally Posted by papcom View Post
Where do the plugins belong?
My recommendation is to put them wherever you want to put them, and then change the "load" statements to include the entire path, for example:

Loadplugin("C:\Program Files\AviSynth 2.5\plugins\MVTools\mvtools2.dll")

I said this in an earlier post, but let me reiterate: it is good programming practice to explicitly load your plugins by specifying the exact location. There is no downside to doing this, other than having to include these statements in the script. It completely avoids the all-too-common occurrence of having the wrong version of a DLL loaded and then experiencing mystery problems that no one in the forum can help you fix.

Quote:
Originally Posted by papcom View Post
Also I do have a script error : there is no function named mtsetmode ...
First of all, the error is probably SetMTMode, not mtsetmode. Second, if you want to take advantage of the multi-threading capabilities of my version of Fred's script, you must use the multi-threaded version of AVISynth. If you don't change the AVISynth version, you will get this error.

If you don't want to change the AVISynth version and don't want to use multi-threading, you can simply comment out the SetMTMode lines (there are four of them) and you won't get this error message. However, quite frankly, if you are not going to use the multi-threading capabilities of my script, then I recommend that you stick with Fred's script and just add the appropriate crop and resize statements to take care of your black bars. The main reason to use my script is that it is several times faster than his, but only if you use multi-threading.
johnmeyer is offline   Reply With Quote
Old 3rd August 2014, 18:18   #815  |  Link
papcom
Registered User
 
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
Your script (@JHM) is running fine here. I have switched to the MT- capable avisynth 2.6. Unfortunately the script makes my Vdub 1.9.11 crash relatively often. It shows a An out-of-bounds memory access (access violation) occurred in module 'ntdll'...

I muted all four SetMTMode, and tried again with the Standard non MT Anisynth, but also here I have relatively often the crashing and always after quitting the program.

Other issues:
how can I achieve that I do not have any FPS Adaptation? Can I just set 25 FPS instead of 18 for the playspeed. I would like that my films stay 25 FPS without any Change.

I do not quite understand the denumerator. Why there is 60'000:1001=59.94? What does this mean? My films are progressive 25fps, and I want them to stay 100% like that. How should I set the denumerator line?

Do You have any FlipHorizontal filter in this script? I feed a Clip, and after Your script it is flipped 180degrees (horizontally).
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore

Last edited by papcom; 3rd August 2014 at 19:40.
papcom is offline   Reply With Quote
Old 3rd August 2014, 21:26   #816  |  Link
johnmeyer
Registered User
 
Join Date: Feb 2002
Location: California
Posts: 2,194
Quote:
Originally Posted by papcom View Post
Your script (@JHM) is running fine here. I have switched to the MT- capable avisynth 2.6. Unfortunately the script makes my Vdub 1.9.11 crash relatively often. It shows a An out-of-bounds memory access (access violation) occurred in module 'ntdll'...
Yes, it is not 100% stable, probably because of the old RemoveDirt plugin which was written long before MT was invented. It is actually amazing that it works at all.

I have developed some workarounds that work quite well, and should let you get around any stability issues. First, when I am looking at a film and want to make sure I have all the settings just right (you should customize the settings for each film), I comment out the SetMTMode lines. This removes the multi-threading and should give you a totally stable system, albeit much slower. Multi-threading is the source of the instability.

When I am ready to actually create the video, I close VD, add the SetMTMode lines back to the script, open my film, and immediately save the AVI file. Most of the instability seems to happen only when seeking forwards or backward (i.e., jumping by many frames at a time, rather than reading each frame in sequence).

Since the whole point of my version of the script is to improve performance, you really should add back the SetMTMode statements before you create the video. If you don't, you should just stick with Fred's version.

The SetMemoryMax function will make a difference in stability. Try slightly larger or smaller numbers (e.g., 1024 or 512).

Finally, change the number of threads. I have an 8-core computer, but I never set threads higher than 6 for this script. If I have a problem with stability, I'll decrease this to some number between 3 & 5.

Again, the stability isn't an issue with the specific features of this script but instead is due to using several older plugins that aren't very "happy" playing in the multi-threaded environment.

Quote:
Originally Posted by papcom View Post
Other issues:
how can I achieve that I do not have any FPS Adaptation? Can I just set 25 FPS instead of 18 for the playspeed. I would like that my films stay 25 FPS without any Change.
Yes, just set the fps to the playback speed you want. That variable is fed to the "AssumeFPS()" function and does nothing more than change the playback speed: no frames are added or deleted in order to achieve the different playback speed.

Quote:
Originally Posted by papcom View Post
I do not quite understand the denumerator. Why there is 60'000:1001=59.94? What does this mean? My films are progressive 25fps, and I want them to stay 100% like that. How should I set the denumerator line?
NTSC video, prior to the early 1950s, was 30 fps. Then, in 1953, the NTSC group added color to the B&W TV standard, but in doing so, had to change the frame rate slightly. You have probably seen the number "29.97" as the frame rate for NTSC TV. The real NTSC frame rate is the result of the way in which the color signal was added, and that function involved the fraction: (1000/1001) * 30 = 29.97002997003 ...

As you can see, even though it is an irrational number, 29.97 is pretty close. However, when you want to be totally accurate, you should compute the number as shown above.

This same calculation is involved when creating the framerate for film shown on an NTSC TV, which is 23.976 rather than 24.

The reason for creating a rate that is double the desired rate (59.94) is that the code was written for interlaced video, and when doing that, you create video at double the rate, and then use a SelectEvery() function to assemble the final video by using the upper field from one frame and the lower field from the next frame. This gives you a temporal difference between fields, while maintaining the correct spatial difference between fields.

So, if you want to take a film transfer and play it on an interlaced TV set by manufacturing intermediate fields, you want to first convert to double the frame rate (50 fps for your PAL video), and then do a SeparateFields() followed by SelectEvery() followed by Weave().

For progressive video, you don't need to double the frame rate.

As for the playback rate, for your PAL video, just set the numerator to 25 and the denominator to 1 because (you lucky dog), your frame rates are nice, simple integers.

Finally, FWIW, I almost never use the frame interpolation function for film. The temporal gaps in 16 fps or 18 fps amateur film are so large that the interpolation almost always screws up and gives you horrible morphing artifacts on some scenes (such as people's legs when walking across the field of view). I much prefer the traditional approach of adding pulldown frames, and that is what I always recommend people use. I've spent a HUGE number of hours over the past decade working with various motion estimation software, including commercial programs like Twixtor, trying to find settings that minimize or eliminate these artifacts, but the technology doesn't yet exist that can give you clean estimated frames in all circumstances. When it works, it is magic, but when it doesn't it looks awful.
johnmeyer is offline   Reply With Quote
Old 4th August 2014, 18:41   #817  |  Link
papcom
Registered User
 
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
Thank You @JHM, Your extensive explanations are very helpful.
  1. I understand, that there is no Interpolation function enabled in Your script anymore, and the video plays out with a 16 or an 18 or a 24 fps Header, without adding frames for pulldown. - Also there is no blending anymore in the scrtipt ---> Is this correct?
  2. I love not too much to sharpen the image, but I like to Degrain the film more. Where would You recommend me to do that in order to receive less filmgrain? I tryed to set the "denoising strength" to 1200, but this doesen't Change a lot?
  3. I do not yet understand why and how You adapted the Denoising Section. The Part with the MVDegrain is muted out?!?
  4. where do I change the color of the characters in the compare-view (S1-S4)?
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore

Last edited by papcom; 4th August 2014 at 19:09.
papcom is offline   Reply With Quote
Old 5th August 2014, 02:33   #818  |  Link
johnmeyer
Registered User
 
Join Date: Feb 2002
Location: California
Posts: 2,194
Quote:
Originally Posted by papcom View Post
I understand, that there is no Interpolation function enabled in Your script anymore, and the video plays out with a 16 or an 18 or a 24 fps Header, without adding frames for pulldown. - Also there is no blending anymore in the scrtipt ---> Is this correct?
Yes. I do no frame blending, frame interpolation, or even any pulldown. This is purely a personal workflow decision on my part, but I almost always still want to do more with the restored version of the film, like adding titles, more color grading, etc. and therefore since I am going to put it back into my editing program (Sony Vegas) it is just as easy to let Vegas do the pulldown. Vegas can do both pulldown and frame blending, and do it exactly as well as AVISynth.

I did include, but have commented out, three different ways to do motion interpolation, if you want to add frames using that technology. The first uses the MVTools2 function, MFlowFPS. These lines are almost straight from the MVTools2 documentation, although I did increase the block size. I find that large block sizes generally produce fewer morphing artifacts when used on low-fps film rates (YMMV).

I then included two separate ways to do the same thing using SmoothFPS2 plugin. The first example uses it directly, and the second uses it via the InterFrame script. The advantage of SmoothFPS2 is primarily speed. In my tests, I general have gotten better visual quality using MFlowFPS.

Quote:
Originally Posted by papcom View Post
I love not too much to sharpen the image, but I like to Degrain the film more. Where would You recommend me to do that in order to receive less filmgrain? I tryed to set the "denoising strength" to 1200, but this doesen't Change a lot?
I included three different sets of denoising settings, with two of those blocks commented out. The version of the script I sent to you had these settings enabled:
Code:
denoising_strength= 600   
block_size=   8                  
block_size_v= 8
block_over=   4
The block size and overlap can make a difference. You could try the block_size=16 group of settings, or go the other direction by using block_size=4. The only block_sizes you can use are 4, 8, & 16 (maybe 32, but that wouldn't do much). The overlap parameter must divide evenly into block_size (I think).

There is one other thing that you can try, which I describe in answer to your next question.
Quote:
Originally Posted by papcom View Post
I do not yet understand why and how You adapted the Denoising Section. The Part with the MVDegrain is muted out?!?
It may at first look like I did that, but look again and you'll find that I did not. First of all, there is a big block of commented-out code that I should have removed. It is left over from the first iteration of the script I posted, before I started using MRecalculate. I kept it around to remind me of the earlier way I did things, but I should have removed it before I sent it to you. So, you can remove these lines:
Code:
#super = stabcrop.MSuper(pel=2)
#bvec1 =  MAnalyse(super, isb = true,  delta = 1, blksize=block_size, overlap=block_over,dct=0)
#fvec1 =  MAnalyse(super, isb = false, delta = 1, blksize=block_size, overlap=block_over,dct=0)
#bvec2 =  MAnalyse(super, isb = true,  delta = 2, blksize=block_size, overlap=block_over,dct=0)
#fvec2 =  MAnalyse(super, isb = false, delta = 2, blksize=block_size, overlap=block_over,dct=0)
#bvec3 = MAnalyse(super, isb = true,  delta = 3, blksize=block_size, overlap=block_over,dct=0)
#fvec3 = MAnalyse(super, isb = false, delta = 3, blksize=block_size, overlap=block_over,dct=0)
After you remove these lines, this comment will make more sense:
Code:
#Use the second line below, and un-comment two lines above if you want to average more frames. Doesn't seem necessary for most work IMHO.
Actually, that line is still confusing, because once I added MRecalculate, there are actually now four lines that you would have to un-comment. The whole point is that MDegrain can actually use three sets of motion estimation vectors (MDegrain3) rather than two (MDegrain2), and may be able to do a better job (which is what you want). I never saw any real advantage, so after I did some initial tests I never enabled this. As the script is written now (look carefully this time) MDegrain is being called on this line:
Code:
denoised=stabcrop.MDegrain2(super, bvec1,fvec1,bvec2,fvec2,thSAD=denoising_strength).levels(0,gamma,255,0,255).tweak(sat=saturation)\
     .unsharpmask(PRE_sharp_ness,PRE_radi_us,0)
If you want to enable the three-level degraining, then change the denoising section to this:
Code:
#DENOISING
#................................................
input_to_removedirt=stab.crop(CLeft,CTop,-CRight,-CBottom)
stabcrop=RemoveDirtMC(input_to_removedirt,dirt_strength,false)

  prefiltered = RemoveGrain(stabcrop,2)
  superfilt =   MSuper(prefiltered, hpad=32, vpad=32,pel=2)
  super=        MSuper(stabcrop, hpad=32, vpad=32,pel=2)

  halfblksize= (block_size>4)   ? block_size/2 : 4
  halfoverlap= (block_over>2)   ? block_over/2 : 2

  bvec1 =  MAnalyse(superfilt, isb = true,  delta = 1, blksize=block_size, overlap=block_over,dct=0)
  bvec1 =  MRecalculate(super, bvec1, blksize=halfblksize, overlap=halfoverlap,thSAD=100) 

  fvec1 =  MAnalyse(super, isb = false, delta = 1, blksize=block_size, overlap=block_over,dct=0)
  fvec1 =  MRecalculate(super, fvec1, blksize=halfblksize, overlap=halfoverlap,thSAD=100)

  bvec2 =  MAnalyse(super, isb = true,  delta = 2, blksize=block_size, overlap=block_over,dct=0)
  bvec2 =  MRecalculate(super, bvec2, blksize=halfblksize, overlap=halfoverlap,thSAD=100)

  fvec2 =  MAnalyse(super, isb = false, delta = 2, blksize=block_size, overlap=block_over,dct=0)
  fvec2 =  MRecalculate(super, fvec2, blksize=halfblksize, overlap=halfoverlap,thSAD=100)

  bvec3 =  MAnalyse(super, isb = true,  delta = 2, blksize=block_size, overlap=block_over,dct=0)
  bvec3 =  MRecalculate(super, bvec3, blksize=halfblksize, overlap=halfoverlap,thSAD=100)

  fvec3 =  MAnalyse(super, isb = false, delta = 2, blksize=block_size, overlap=block_over,dct=0)
  fvec3 =  MRecalculate(super, fvec3, blksize=halfblksize, overlap=halfoverlap,thSAD=100)

  denoised=stabcrop.MDegrain3(super, bvec1,fvec1,bvec2,fvec2,bvec3,fvec3,thSAD=denoising_strength) \
           .tweak(sat=saturation).unsharpmask(PRE_sharp_ness,PRE_radi_us,0)
I just did a little quick testing and got slightly better results on one test clip by using the three level degraining with the block size set to 16. However, when I raised the denoising_strength from 600 to 1600, various things started disappearing from view.

You'll just have to play around with this. There is no perfect solution to degraining.
Quote:
Originally Posted by papcom View Post
where do I change the color of the characters in the compare-view (S1-S4)?
I actually have no idea without looking it up. I'm 99% certain you do it by setting the text_color and halo_color values in the Subtitle calls in the "COMPARISONS: ORIGINAL VS RESULTS" section of the script.
johnmeyer is offline   Reply With Quote
Old 5th August 2014, 21:12   #819  |  Link
papcom
Registered User
 
Join Date: Feb 2002
Location: Southwest Germany
Posts: 169
thank You again @JHM for all the detail-help. I appreciate it very much.

I like the way to export the film without any frame blending, frame interpolation, or pulldown. This is how I work. I use Premiere CS6 or Apple FCP7 or FCPX.

I saw that You are working with sony vegas. That's one of the Tools i am very interested in. I recently read a test about it, which highly recommended this soft.

Actually I am trying with different parameters and different source material. The results are encouraging. I am testing 768x576 progressive source material, which looks nice after processing. Soon I will start to check images with my other transfer system, which is a modified Bauer525 for frame by frame capturing via a machine vision camera with 1024x768pixels.

btw - I found the way to modify the characters in the comparison view via text_color etc. ..thanks for your hint.
__________________
Lenovo Intel i7Quad/WIN8 - Virtual Dub 1.10.4/Avisinth 2.6MT- MacMini I7 QuadCore

Last edited by papcom; 6th August 2014 at 09:47.
papcom is offline   Reply With Quote
Old 12th August 2014, 00:14   #820  |  Link
Ultimist
Registered User
 
Join Date: Dec 2011
Posts: 18
Can someone tell me which version of Avisynth these scripts are compatible with? I've tried the 2.5 and 2.6 MT versions... and Avisynth+, but I keep getting multiple errors and crashes no matter what I try.

Any help would be appreciated. Thanks!
Ultimist is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 17:39.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.