Yes, the difference between the two frames does seem odd, and there's probably an answer for the green effects. I had no such effects on your sample. I guess we'll have to check the overall results for problems like that. If it's all over the video, something's definitely amiss. If it's just in parts, we should get a sample of those parts to see what's up.
This is why most users process a long video in sections. But you've accomplished a great deal today. Congratulations! If it had been me, I'd be in therapy by now. Right now the wife is grumpy and trying to force me to go to sleep. Gosh, wives just don't understand these things!
+ Reply to Thread
Results 61 to 84 of 84
Our inventions are wont to be pretty toys, which distract our attention from serious things. They are but improved means to an unimproved end. -- Henry David Thoreau
Hehehe yeah computer is my drug, I can't just stop. Coffee, forums and sleep (sometimes) is my personnal therapist. Well thank you very much... You are a great helper Now you can get some rest, and tell your wife I'm sorry for keeping you awake late
Yeah I think I will just process like 30 seconds at the begining and 30 seconds in the mddle and play with that, and when I get the expected result, I'll try to cut video and small part and then merge them (even I dont know how.
I stopped the saving and played the avi output, I have green spot on some scenes. I'm going to make some screenshots and post them here (before/after in PNG format). If you want to, and if you're available, maybe you'll take a look at it tomorrow
Good night sanlyn and I'll keep you posted on my progress.
Just though about it, may it be caused by the RGB32 instead of RGB24?
And I tried to load the movie with :
to compare with modified avi but once exported with lagarith, the image is overlayed with blue green and maganta colors, is there any plugins that are loaded even if they are not included in a script?
Last edited by askiplop; 7th Jan 2013 at 23:14.
A few things I missed, before shutting down tonite:
Lagarith's window is "RGB24 32" -- meaning that Lagarith can compress either RGB24 or RGB32, depending on what it gets. RGB is the default unless you specify otherwise. But be careful: if you work a video and save it as YV12 in VDub, the next time you open Lagarith's dialog you'll see YV12 in there. It remembers the last colorspace you used with it.
But I'm thinking it would be a good idea to use the free MediaInfo utility to read the properties of your mkv and your m2v files, and save the data as text files. I think we can find some clues there.
LoadPlugin("C:\Videos\AviSynth 2.5\plugins\DGDecode.dll")....once exported with lagarith, the image is overlayed with blue green and maganta colors, is there any plugins that are loaded even if they are not included in a script?[/QUOTE]
There might be incompatible/outdated versions of individual dll's, but usually they generate errors. Yes, there are many more support files being called than is obvious at first, but the downloads are all thoroughly tested by the designers (except for silly stuff like FastLineDarken. Guess what? They came up later with FastLineDarkenMod and it had other errors! But that's unusual, and the plugins are being continually improved.
But some dll's come in downloaded packagaes in several versions. For example, if you have RemoveGrainSSE2 in your plugins, the lesser RemoveGrain.dll (non-SSE version) shouldn't be there.
MediaInfo might tell us more later.
I'm just thinking, though: If you created a demuxed m2v, but didn't use Force Film, you're working with telecined video. That would explain a few things. Then there's the matter of the field order shift. Check that tomorrow. I'm already asleep in my chair and having dreams about this stuff.Our inventions are wont to be pretty toys, which distract our attention from serious things. They are but improved means to an unimproved end. -- Henry David Thoreau
Dont worry I just forget to remove the comments , it's a script based on a of sanlyn'sprevious script. He suggested to import the video in RGB, then save it in RGB. Reopen it with a second script, applying the necessary filters in VDub, and then put it back to YV12.
I found which script is causing the green thing on the sides of frames... :
mergechroma(aWarpSharp(depth=20.0, thresh=0.75, blurlevel=2, cm=1))
EDIT - Response to sanlyn:
It's okay, my brain does the same hehe dreaming about the thing I've done all day... today: editing videos.
After some research about the aWarpSharp plugin, I find out someone mentionning green bars on the side of his frames... and the new version of aWarpSarp:
Do youn think we can adapt your aWarpSharp command to run on version 2012 ?
Humm, that's true, I'm not working on a telecined video. I'll take a look at MediaInfo right now. I'll let you know
When I run VDub... the process uses 1.5-2GB and 15% CPU (even if I set higher priority in the program and 6 core in the script), and yes most programs doesnt run any faster on x64... depends how much you're willing to pay for faster software (photoshop x64 is faster than the x86 version, but they have the money to develop such softwares).
DGDecode line removed thx man!
45% off? Wow amazing, I wish we had great deal like that around here!
Good night buddy!
EDIT - adding MediaInfo files for the mkv file and the demuxed video file
Last edited by askiplop; 8th Jan 2013 at 00:21.
awarpsharp2 replaces the old awarpsharp for the green border issue (but the settings are slightly different; read the instructions for more info)
Okay thanks poisondeathray, I'm actually reading right now on AviSynth plugins
For the Forced Film, I've found a way, I don't know how, I don't know why...
I put the extracted video (.mpg file) from the mkv into DGIndex and save it. It works, no error at all, same size (I don't know if it is okay). Attached is the MediaInfo data.
Yeah I king of like the editing function
I didn't find the docs about the awarpsharp plingin to adjust the current settings with the newest version.
Last edited by askiplop; 8th Jan 2013 at 01:03.
Avisynth plugin on the usual download site at http://avisynth.org/mediawiki/External_plugins . aWarpSharp downloaded from that site gets you the 2003 version of the dll, which is what I downloaded and posted. You'd think that after a year, the wiki's post would be updated -- but nnnoooooooooooo. So, like FastLineDarken.avs the corrected version still isn't in "official" posts. Next time I contribute scripts/plugins, I'll just copy the ones I'm using instead of the archived stuff.
You're not using MCTemporalDenoise yet (another monster plugin with a script longer than the Sunday New York Times). The internet wiki documentation has errors. For the most thorough doc see the downloaded script itself, which is correct. It was pdr or jagabo who pointed that out to me a while back, when I screamed in horror that my settings wouldn't work. And recall RemoveGrainT? Its functions were moved to newer dll's but some old code keeps calling it: only the "old" dll will work.
If you download the new "aWarpSharp2" dll you'll see it's still named aWarpSharp.dll, not aWarpSharp2.
Documentation for the new version is a .txt file shipped inside the ZIP download.
And if you think this video is a problem, you should have seen....well, no, that's too discouraging.Our inventions are wont to be pretty toys, which distract our attention from serious things. They are but improved means to an unimproved end. -- Henry David Thoreau
You can use the same statement that's in the script -- but you have to replace the awarpsharp.dll with the new one.
The current line for aaWarpSharp is:
mergechroma(aWarpSharp(depth=20.0, thresh=0.75, blurlevel=2,cm=1))
I don't know what is MCTemporalDenois(), do I need to run it in script 1?
VDub won't open any MPEG 2 file. So I opened it with an AVS script:
MPEG2Source("C:\Videos\vid_onceupon\once_upon_a_forest.d2v") Trim(2000, 2050)
Also, I attached a png file showing 3 sequential frames (half width, not squeezed). odd images are pretty similar to the even image before it. (Don't know if that make sence in english)
Also, you were right about QTGMC, once disabled, it's fast as hell!
Don't worry about MCTemporalDenoise. Not for now, anyway.
Odd/Even differences: this is progressive anyway, so odd/even isn't a problem.
I don't see the problems you mention with the AVI. However, there's the same fine-grain chroma noise as in the Test-002 sample (Did this video originate as tape ? ? ? I thought it was a DVD). There's also some flicker and stutter. I don't know how well DGIndex generates Force Film. In my experience I never used it, I always took the telecined video as-is and used TIVTC to inverse telecine. Someone with a knowledge of DGIndex innards might have something to say.
It's also possible that those disturbances were in the original source. For some reason, the video and any processing I work on it plays better in Windows Media Player than in other players (now that's a twist!). We keep running into oddities with this movie. But, then, why am I not surprised?
I note that any noise reduction filter (I tried several) causes object shimmer that isn't in the AVI. I see temporal denoisers do this often, especially with stuttery video. Having a tough time with those effects on my current project. So...right now I'm just full of guesses about that stutter that turns into shimmer when smoothed. In other words, I don't have a ready answer. Some of the experts around here surely must have experienced this.
I question MediaInfo's data on the original mkv. There's nothing about pulldown in that MediaInfo text, it just says 29.97 fps progressive. That's odd, as DVD source is usually interlaced or telecined. How did it get from pure progressive to telecined? But there's much I don't know about mkv containers.
Okay I'll try not to worry about MCTemporalDenoise
The original original source is tape, it was the sold to DVD (but they just put the video tape on the DVD without much processing). The original source (where I took the movie) is on a DVD.
And you're right, on WMP I don't see any visible problem, but play the file on VLC...
I didn't know Microsoft was capable of doing good programs.. o.O
So, how should I proceed? Normally you don't use DGIndex to reverse the telecine... so maybe I should try your usual way?
I found the TIVTC plugin here, v1.0.5. http://avisynth.org.ru/docs/english/externalfilters/tivtc.htm
Is it possible for you to give me some exemples on how you would use this plugin on my current video please? That would be great!
By curiosity, I ran the original video in VLC and the d2v file in vdub, the image displayed in vlc is larger.
Then I compared the m2v image vs the mkv image side by side in vlc, they are the same.
So, I don't know how VLC knows it and how MediaInfo doesn't know it, but 'm sure the video need a 3:2 pulldown.
(And quick question, whats the command to crop the image? I want to remove the black borders at the top and at the bottom the the video )
Next step: well, step 2: applying VDub filters and make tests
I'm trying to apply a TIVTC filter to my video, but a frame count error always popup, no matter what I try:
--------------------------- VirtualDub Error --------------------------- Avisynth open failure: TFM: d2v frame count does not match filter frame count (127180 vs 101744)! (C:\Videos\vid_onceupon\Script1.avs, line 19) -------------------------
Last edited by askiplop; 8th Jan 2013 at 16:58.
MediaInfo will see it. If you have NTSC DVD that starts out as 23.97fps film, it has to be telecined to playback at 29.97fps. Telecine (hard-coded or soft-coded 3:2 pulldown flags) happens in several ways -- not to get into all that now -- but a tape from a telecined video will be played from a VCR with what amounts to hard-coded telecine (i.e, the telecined frames are actually encoded that way, not just flagged for 3:2 pulldown). So that's why this "progressive" description in the mkv and then the 3:2 pulldown notes in the m2v's are confusing me.
Depending on those considerations, there might be some difference with TIVTC, and there might not.
Specs for the Crop statement are here: http://avisynth.org/mediawiki/Crop
In fact, every Avisynth command and function is covered in the files on your PC. In Windows click "Start", go to your Program listings, find the Avisynth program group, and open that group to see the link for online documentation. The docs are located in your AviSynth installation folder, so there's no need to check the internet for it.
To try out TIVTC, you need to open a telecined d2v project or AVi file. You can run the same script, but note the sequence of the statements (TFM() and TDecimeate() functions are in TIVTC.dll):
[Open a telecined clip with MPEG2Source and a d2v project file, or AviSource for an AVI] ColorYUV(off_y=12,cont_y=15) ColorYUV(off_u=4) daa3() AssumeTFF().TFM(order=1).TDecimate() RemoveSpots() FastLineDarken() AssumeTFF().QTGMC(InputType=1,preset="medium") DeBlock_QED() GradFun2DBmod() TTempSmooth() mergechroma(aWarpSharp(depth=20.0, thresh=0.75, blurlevel=2, cm=1)) AddGrainC(var=1.5,uvar=1.5) ConvertToRGB32(matrix="rec601",interlaced=false) Crop(2,4,-2,-8).AddBorders(2,6,2,6)
DGIndex and Force Film to reverse the telecine when it's a soft telecine, as this one is.
I'm trying to apply a TIVTC filter to my video, but a frame count error always popup, no matter what I try:
Last edited by manono; 8th Jan 2013 at 19:17.
Oppsy, I tried to reverse telecine before setting YUV
I just think this: When I extracted the mpeg file from the MKV file with MKVextractGUI tool, it removed the pull down flag.
If we go back at the begining, you suggest me to take the mkv file and put it in AVI lossless Lagarith format...
Well, it's not magic, but with VDubMod I can open the mpeg file and save it with "fast compression" to avi with lagarith codec.
What do you think? (The pulldown flag will still miss unfortunatly.
I don't really know what that statement means.
I'll wait for the lossless AVI file and I'll try to find a workaround .. maybe?
And what'S your usual way to reverse telecine?
Thanks for the VCR/telecine explanation It makes a lot of sence.
TSMuxer and it didn't. And I don't believe MKVExtractGUI did either. Open that MPG in DGIndex and run the Preview. If Video Type=Film, the pulldown is still there. If Video Type=NTSC, it was removed.
What do you think?
Last edited by manono; 8th Jan 2013 at 19:12.
Thanks manono!!! DGIndex shows "Film" as Video type... cool!
Here's the link to purchase the DVD on Amazon:
I'm sure it's from the VHS because I have the VHS version, and it have the same white spot on the same frames
Sorry for the pulldown thing, I shuffled couple of things and my head and that's the result.
Saving as m2v with Forced Film worked, Script 1 works fine.
Now sanlyn suggest to save the video after script 1.avs as splitted avi with lagarith. (Splitted in case something is going wring after 80% o.O)
But after I need to re-open all AVI individually to apply my filters?
The normal ratio is 1.33:1 according to Amazon... So I not sure anymore... :S
Walm*rt sells a widescreen/fullscreen version of the movie.
Got it! It supposed to by 16:9, in the movie we can see a moon, in 4:3 the moon is more like an egg
Ohoh!! Big Ohoh! (I think)... is it normal that the m2v file as a fps of... 59.940059 ? (Like PAL I believe)
And is it going to change something to what we've done until now?
I tried to run an Avisynth script and got this error:
Avisynth open failure:
Script error: there is no function named "Clense"
(C:\Videos\AviSynth 2.5\plugins\RemoveSpots.avs, line 6)
(C:\Videos\vid_onceupon\Script1.avs, line 30)
I didn't change anything!
I created a new folder with somes images in it and try to open bmp file with avisynth... got this error. I tried the script for my video, same error.. :S :'(
Last edited by askiplop; 8th Jan 2013 at 21:17.
The hard/soft telecine issue....two sets of mediainfo specs kinda threw me off. But there's still a few oddities about motion effects in a few frames. Guess I'll have to wait for more of the video and see how it looks.
Thanks to the O.P. for the DVD info. I'm tempted to look up a copy. Nice artwork.
Last edited by sanlyn; 8th Jan 2013 at 22:13.
Thanks to the O.P. for the DVD info. I'm tempted to look up a copy. Nice artwork.
Avisynth as Lagarith RGB with the Fast Recompress option.
Yes, it's acceptable to run "full processing Mode" and filters like NeatVideo at the same time in one step, but that depends on the CPU usage involved in running everything at once. Your NeatVideo v3 will run at 10 to 15 fps, but if you try that with Avisynth running in front of it, you won't get 1/4 that processing speed. With a slow script or slow RGB filters, running it all at once and then encountering a problem can be hassle, as well as a double whammy slowdown.
If the results of script #1 are saved properly as RGB, all you have to do in VirtualDub is open the file and add the filters, then save as RGB again. But not even Lagarith can recompress from RGB-back to-YV12 as well as dither can, so that"s why I made RGB->YV12 with dither as a separate step in the process.
However, apparently some DVDs of the film have both the 'fullscreen' and 'widescreen' versions on the same DVD (maybe without mentioning the fact in the advertising). Is that true in your case?
Thanks for the tip, manono. My Amazon "Tell me when" email informer must be asleep at the switch.
Yes, the specs had me confused as well. Glad manono stepped in to clarify.
If I remove the function RemoveSpots(), I got an error for the next plugin:
--------------------------- VirtualDub Error --------------------------- Avisynth open failure: Script error: there is no function named "nnedi3" (C:\Videos\AviSynth 2.5\plugins\daa3.avs, line 5) (C:\Videos\vid_onceupon\Script1.avs, line 31) ---------------------------
If you want to use RGB filters, which I think you should do here to get the corrections and the "look" you want, then at some point you have to convert from YV12 (your source m2v is YV12) to RGB. The script shows the accepted way of making that conversion. Because it's the 1st script that makes that RGB change at its end, the script's output should be saved in Avisynth as Lagarith RGB with the Fast Recompress option.
Thanks for helping me with that guys! I think we can rename this subject to: a step by step guide for n0ob.
Found the avisynth problem. For an unknown reason, now I need to call all the plugin's DLLs and avsi scripts in file... yesterday it was working without that...
vidpath="C:\Videos\vid_onceupon\once_upon_a_forest.d2v" ppath="C:\Videos\AviSynth 2.5\" numcpu = 6 Import(ppath+"plugins\QTGMC-3.32.avs") Import(ppath+"plugins\RemoveSpots.avs") Import(ppath+"plugins\daa3.avs") Import(ppath+"plugins\FastLineDarken 1.3.avs") Import(ppath+"plugins\DeBlock_QED.avs") Import(ppath+"plugins\GradFun2DBmod.v1.5.avsi") LoadPlugin(ppath+"plugins\DGDecode.dll") LoadPlugin(ppath+"plugins\MaskTools.dll") LoadPlugin(ppath+"plugins\mt_masktools_25.dll") LoadPlugin(ppath+"plugins\RemoveGrainSSE2.dll") LoadPlugin(ppath+"plugins\mvtools2.dll") LoadPlugin(ppath+"plugins\RemoveDirt.dll") LoadPlugin(ppath+"plugins\RepairSSE2.dll") LoadPlugin(ppath+"plugins\nnedi3.dll") LoadPlugin(ppath+"plugins\deblock.dll") LoadPlugin(ppath+"plugins\DctFilter.dll") LoadPlugin(ppath+"plugins\AddGrainC.dll") LoadPlugin(ppath+"plugins\gradfun2db.dll") LoadPlugin(ppath+"plugins\TTempSmooth.dll") LoadPlugin(ppath+"plugins\aWarpSharp.dll") # ---------------------------------------------- # .d2v project file created with DGIndex using # "Forced Film" switch for # progressive 23.97 fps video (telecine removed). # (Input is YV12 MPEG2) # ---------------------------------------------- MPEG2Source(vidpath,CPU=numcpu) Trim(2000, 10000) ColorYUV(off_y=12,cont_y=15) ColorYUV(off_u=4) RemoveSpots() daa3() FastLineDarken() QTGMC(InputType=1,preset="medium") DeBlock_QED() GradFun2DBmod() TTempSmooth() mergechroma(aWarpSharp(depth=20.0, thresh=0.75, blurlevel=2,cm=1)) AddGrainC(var=1.5,uvar=1.5) # ---- to RGB for VirtualDub work ------ ConvertToRGB32(matrix="rec601",interlaced=false) Crop(2,4,-2,-8).AddBorders(2,6,2,6)
Last edited by askiplop; 9th Jan 2013 at 12:18.
[QUOTE=askiplop;2211902]And in the codec tab in VLC, I found Planar 4:2:0 YUV, I don't know if it may be a useful information.
DVD and BD video are stored as a form of YV12 4:2:0 (that's another vast simplification). It all gets expanded into RGB (sorta) by monitors and TV.
If you have a d2v project, you can open it in Avisynth and cut into pieces for chunk-at-a-time processing by using Trim():
MPEG2Source("path to some .d2v project file") # Or AviSource or some other "Open" Trim(2549,10420) ....process... ....process...
Why you'd get a dll call error by removing a function that doesn't even use that dll beats me. RemoveSpots doesn't use that dll, but daa3 does.
Last edited by sanlyn; 9th Jan 2013 at 20:40.