Improving resolution

[carlmart]

OK. Now I could load AvsP and open the script.

Also could open the script in VD but it crashed.

How do you install ffmpeg?

[Blue_MiSfit]

ffmpeg is just a CLI application. You can download a recent binary from http://ffmpeg.arrozcru.org/builds/ and toss it in your c:\windows\system32 folder.

Now open a command prompt (cmd.exe) and type ffmpeg and then enter. You should get a vomit of text which indicates ffmpeg is installed and functioning.

To actually transcode your AVS to a DNxHD MOV, use a command like this:
(from http://www.itbroadcastanddigitalcinema.com/ffmpeg_howto.html#Encoding_VC-3)
(also assuming you want 1080i60 output at 220mbps)

ffmpeg -i input avs -vcodec dnxhd -b 220Mb -flags +ildct -an output.mov

This MOV should import into your Avid with no problems. It may remux to MXF, or it may operate natively.

~MiSfit

[carlmart]

Well, as I speak ffmpeg is running and supposedly converting my first shot.

I had to modify the script because it didn't accept 1440x108: had to go with 1920x1080.

Also don't know how long will it take to upscale the stuff.

If it turns up well maybe it's time to review what filters to use.

[carlmart]

How much should I expect this HD file to be larger than the original?

It's now 6.5 times the original size, and still going up...

[poisondeathray]

How much should I expect this HD file to be larger than the original?

It's now 6.5 times the original size, and still going up...


It will go up by the change factor of the bitrate

e.g.
If you're using 220Mb/s DNxHD and your original was , for example 10Mb/s, It would go up by about 22x

[Blue_MiSfit]

Right. DNxHD will use roughtly 220mbps at the setting we told it to. If your source was DV, then you can probably comfortably get away with using the lower bitrate options.

~MiSfit

[carlmart]

Ok. File ended up 7.6x the original size. Pity the file is so large for me to pick something for you to see. What can I use to select a few seconds with?

The MOV file imported fine to Avid, so that is very good.

What I would like to know is what program can I use to view the resulting HD file. The others I tried (VLC, MPC and QT) do not play it smoothly. Any suggestions?

[carlmart]

At least a small sample of what I got: a captured frame from Avid.

http://www.mediafire.com/file/mmn2yohq0z2/orixas4a.jpg

[carlmart]

And this is a frame from the HDV image it will be intercut with.

http://www.mediafire.com/file/vqynjtviwtw/orixas3.jpg

[Blue_MiSfit]

Avid should play the DNxHD file smoothly.

Post screenshots with something like imgur or photobucket.

You can trim a piece of the MOV using QuckTime, and do a save as. Then, send this to us with mediafire or something like that.

~MiSfit

[carlmart]

Avid should play the DNxHD file smoothly.

It's not so smoothly, and I would like to know why. There are some artifacts, like short time horizontal-bars like moving up that come now and then. They are not on the original avi file, but they also were there when Avid player the original avi file.

So I guess it might be just an Avid artifact, and that's why I asked for a reliable player to play the HD file.


Post screenshots with something like imgur or photobucket.

I did post some screenshots. Don't they show?

You can trim a piece of the MOV using QuckTime, and do a save as. Then, send this to us with mediafire or something like that.

It's not working. I am using QT Pro, but I can't seem to mark edit points to trim a piece of the file. As I am not familiar with QT, certainly it's my fault.

I do think the SD file can ge cleaned even further using the avisynth script. This is the one I used:


converttoyv12(interlaced=true)

#a=last

nnedi(field=0,dh=true).TurnRight().nnedi(field=0,dh=true).TurnLeft()

limitedsharpenfaster()

spline36resize(1280,960)

sharpen(0.5)

spline36resize(1920,1080)

limitedsharpenfaster()

#interleave(last,a.Bob().spline36resize(1440,1080))

return last

separatefields.selectevery(4,0,3).weave

[carlmart]

Things improved a lot when I just now tried deinterlacing it with:

EDI=NNEDI(field=-2)
YADIFmod(mode=1, edeint=edi)

Seems like a move in the right direction.

Now if I had a way to improve DV border enhancement, that is soften it, which IMHO is one of the things that is (thankfully) missing in HD.

Edit: well, I'm answering myself. Deleting sharpen() or using a lower factor seems to soften border enhancement.

[Ghitulescu]

Why do you need deinterlacing?
Apparently you shot both interlaced (DV per se, HDV as Sony Z1 is 1080i - the cinematic is a bad joke).
Even if you're otherwise happy with cinematic 24/25/30, if you want to interface it with DV then you need 1080i. Once you got the final film, then you have to decide if you're deinterlacing it or not, depending on the support.

[carlmart]

Why do you need deinterlacing?
Apparently you shot both interlaced (DV per se, HDV as Sony Z1 is 1080i - the cinematic is a bad joke).

Yes, I shot both interlaced. And yes, the Z1 cinema setup is a VERY bad joke that many people are falling for and regretting it later on.

What I do not like is the result I am getting from my upscaled interlaced images when played on the Avid. A friend of mine, who knows a lot of Avid, tells me it might be a problem of inverted fields when importing, which should be lower first for NTSC. As it is now you can see the interlace when I think you should not. Look at the hand of the lady or her dress on the left side.

As I am now carrying on a fresher upscale, also without the sharpenings, I will be able to compare them.

[Blue_MiSfit]

Try something like this script instead:


#Assuming YUY2 decoded from NTSC DV

EDI=NNEDI(field=-2)
YADIFmod(mode=1, edeint=edi)

spline36resize(1920,1080)
ConvertToYV12()
#Now we have 1080p60 in YV12

limitedsharpenfaster()
ColorMatrix(mode="Rec.601->Rec.709")

AssumeTFF.SeparateFields.SelectRvery(4,0,3).Weave
#And finally 1080i30, TFF, Rec. 709 YV12, which should match HDV


~MiSfit

[carlmart]

Try something like this script instead:


AssumeTFF.SeparateFields.SelectRvery(4,0,3).Weave
#And finally 1080i30, TFF, Rec. 709 YV12, which should match HDV




Why should we go for something 1080i30 instead of 1080i60?

BTW: you trust me too much that I will be smart enought to correct SelectRvery and put SelectEvery instead. I went googling to see if SelectRvery was correct before modifying it. Was that a test to see if I am paying attention?...
:p

[poisondeathray]

Why should we go for something 1080i30 instead of 1080i60?


This might be confusing, but 1080i30 means the same thing as 1080i60 . They both mean 30 FRAMES per second or 60 FIELDS per second. Just different naming conventions - but this is opening a big can o worms...

[carlmart]

OK, I can understand that and won't get into it.

But why does the last script I mentioned look better (cleaner, no interlace artifacts) in AvsP than this last script?

I can show two frame areas to show what I mean. Believe me, this is helping me understand better a lot of things, so please be patient with me.

[poisondeathray]

But why does the last script I mentioned look better (cleaner, no interlace artifacts) in AvsP than this last script?

I can show two frame areas to show what I mean. Believe me, this is helping me understand better a lot of things, so please be patient with me.



Exactly which scripts? which post#

Every source is different. You might find artifacts in different sections in one script , but not in the other using a different deinterlacer

I've found yadifmod+nnedi2 on DV material can leave artifacts more often than nnedi2 alone ; you could try adjusting blue_misfits script and see if that helps

Assuming you have BFF DV, change the first 2 lines to
NNEDI2(field=2)

[carlmart]

Exactly which scripts? which post#

Oh, sorry. Post #161. Then I added the deinterlacer and things got cleaner.

Every source is different. You might find artifacts in different sections in one script , but not in the other using a different deinterlacer

My question is whether I should use a deinterlacer or not. Apparently I shouldn't need one because my stuff is interlaced and will continue to be so. But then it's difficult to see in AvsP what improvements I am getting as I change the filters.

I've found yadifmod+nnedi2 on DV material can leave artifacts more often than nnedi2 alone ; you could try adjusting blue_misfits script and see if that helps

Assuming you have BFF DV, change the first 2 lines to
NNEDI2(field=2)

Things didn't change much with that. In any case this is what I get by applying the first script (http://www.mediafire.com/i/?1nhdoiz1hyt) and then Blue_MiSfit's (http://www.mediafire.com/i/?zntmzmhnyjt).

[carlmart]

Just to show things better, the script corresponding to "hand1" is:


converttoyv12(interlaced=true)
EDI=NNEDI(field=-2)
YADIFmod(mode=1, edeint=edi)
nnedi(field=0,dh=true).TurnRight().nnedi(field=0,dh=true).TurnLeft()
spline36resize(1280,960)
sharpen(0.3)
spline36resize(1920,1080)
return last
separatefields.selectevery(4,0,3).weave

[poisondeathray]

My question is whether I should use a deinterlacer or not. Apparently I shouldn't need one because my stuff is interlaced and will continue to be so


You can't resize interlaced material. Or you can, but it has to be in an interlace aware method. (I think you can resize horizontally without anything special, but that's not very useful by itself).


I can't see any of the screenshots; they have to be approved. You could use a 3rd party site like imageshack, tinypic, imagebam etc...

Anyways just use whatever you think works better. Every source is different

[Blue_MiSfit]

Indeed. You can resize an interlaced image horizontally without any issues. Doing it vertically works as well (so long as you do it with an interlaced aware method, otherwise you will slaughter it messily), but bobbing, resizing, and re-interlacing usually delivers more stable results (less aliasing etc).

Attachments take forever to get approved. I also suggest using a 3rd party image hosting service and just posting links here

~MiSfit

[carlmart]

Sorry, I thought you were seeing the sample screens.

Already uploaded them to Mediafire, and the URLs are above and on page 8.

[carlmart]

If it's not asking too much, I would like a brief explanation on the deinterlacing filters we are using and why.

The main purpose for this upscaling was being able to use my DV camera in order to help my editing.

The first step is resizing it, so I can put them all on the same timeline and later export it as an HD file.

The second step is processing the image in order to blend it, so it can cut smoothly. That will require some processing within Avid, even if some things I might get ready when using the Avisynth filters.

For instance: as the HDV image on some cases had some lens reflections that caused a certain softening, which was not present on the DV images, I tried a Tiffen filter effect called Black Mist and it softened the DV harder contrast very well. But also the borders got softened, so I might try some sharpening on the Avisynth to see how Black Mist processes all that later on.

What do you think?

A harder job will be on the other shots, which were the ones you had seen at the beginning of this topic. The thing that bothers me most is that everything seems to be on the same focus plane, including the background. That is a result of the large depth of field natural in small cameras.

That is something I will have to foresee in the future, shooting farther away and using tele in order to defocus the background.

For now it was suggested to me that I might use a mask that might help me split the image, then blurring the background in order to look "out of focus".

What I wonder if this is something I might be able to do with Avisynth too. The most critical part is adding that mask, which apparently can be done with Photoshop or Adobe After Effects, both programs I have nil experience with.

[Blue_MiSfit]

Hi Carlos,

The big depth of field issue will be very difficult (if possible at all) inside avisynth. This is where a real VFX / compositing platform like After Effects will come in handy. A proper GUI seems like a prerequisite for doing good masks etc..

About deinterlacing, there are always several things to choose from. We could use a dumb Bob, but that usually kills sharpness and is prone to aliasing. TDeint is good, but sometimes falls apart in fast motion, and needs TMM and NNEDI's help to clean things up, which is very slow. YADIF is good, extremely fast, and rarely falls apart completely. YADIFMod + NNEDI is a nice compromise because it lets you use YADIF's high speed and good intelligence with NNEDI's incredible interpolation! This leads to a sharper output, less aliasing etc... If you want to really maximize quality you can use TempGaussMC, which is the absolute latest word in software deinterlacing AFAIK. It's also rather slow, but not horribly so :)

As far as getting these to intercut smoothly - I hate to suggest it, but you might try lowpassing / blurring the HDV footage a bit. Yuck. I feel like I should go wash my hands now.

~MiSfit

[carlmart]

The big depth of field issue will be very difficult (if possible at all) inside avisynth. This is where a real VFX / compositing platform like After Effects will come in handy. A proper GUI seems like a prerequisite for doing good masks etc..

Learning curve for AE is quite steep. Perhaps with Photoshop can be better, but I am not sure.

About deinterlacing, there are always several things to choose from. We could use a dumb Bob, but that usually kills sharpness and is prone to aliasing. TDeint is good, but sometimes falls apart in fast motion, and needs TMM and NNEDI's help to clean things up, which is very slow. YADIF is good, extremely fast, and rarely falls apart completely. YADIFMod + NNEDI is a nice compromise because it lets you use YADIF's high speed and good intelligence with NNEDI's incredible interpolation! This leads to a sharper output, less aliasing etc...


So that's why that YADIFMod + NNEDI combo looked better on my test (see photos)! It's the winner until now, but I thought I might be doing something wrong.

If you want to really maximize quality you can use TempGaussMC, which is the absolute latest word in software deinterlacing AFAIK. It's also rather slow, but not horribly so :)


It might be interesting trying it.

As far as getting these to intercut smoothly - I hate to suggest it, but you might try lowpassing / blurring the HDV footage a bit. Yuck. I feel like I should go wash my hands now.


You're grounded for emitting dirty thoughts! ;)

I think the sharpen (avisynth) + Tiffen filter (Avid) on the Dv image will get me there.

Question is how to do it fast, like using still images to feed into Avid and see which combo works better. Then I will not have to wait so much for processing.

[Blue_MiSfit]

Any luck?

[carlmart]

Any luck?

You mean about the blurring thing?

Well, yes, I got some instructions from a forum guy apparently quite knowing what I want to do.

The problem is that I am not that familiar with Avid yet to completely understand all the steps involved. Will need the help of another friend of mine, currently on vacation, to decipher and implement the thing.

But it involves a mask and works within Avid itself.

What I would like to know from you is where we can start with TempGaussMC in our script.

[Blue_MiSfit]

Easy!

First, install http://avisynth.org/mediawiki/upload/c/c8/TempGaussMC_beta1mod.avsi and any plugins it requres (if you don't have them already)


Required Plugins

MVTools
RemoveGrain + Repair
MaskTools v2
NNEDI / NNEDI2 (2009) / EEDI2 / Yadif , depending on which EdiMode you want to use


Replace


EDI=NNEDI(field=-2)
YADIFmod(mode=1, edeint=edi)

with


TempGaussMC(EDIMode="NNEDI2")


Both examples will bob the video. I think you'll find TempGaussMC's results more visually pleasing, in most cases.

~MiSfit

[carlmart]

All filters seem to be loaded alright, but I keep getting this message:

"There is no function named TempGaussMC".

[Blue_MiSfit]

Whoops!


TempGaussMC_beta1mod(EDIMode="NNEDI2")


:)

[carlmart]

Now I get:

"There is no function named TempGaussMC_beta1mod".

The error must be somewhere else.

Just to clean up the slate, the script I am loading is:


AVISource("e:\file.avi")
converttoyv12(interlaced=true)
TempGaussMC_beta1mod(EDIMode="NNEDI2")
nnedi(field=0,dh=true).TurnRight().nnedi(field=0,dh=true).TurnLeft()
spline36resize(1280,960)
sharpen(0.3)
spline36resize(1920,1080)
return last
separatefields.selectevery(4,0,3).weave

[Blue_MiSfit]

Hmmm.. you did copy the avsi script to you avisynth plugins folder, correct?

[carlmart]

Hmmm.. you did copy the avsi script to you avisynth plugins folder, correct?

You're right to ask that. Unfortunately I did.

Even checked all the filters to see if versions were the latest. They are all updated.

Can't understand why it works with all others and not when adding TempGaussMC_beta1mod.

Edit: OK. As I was booting from my HDD1, instead of the HDD2, I tried the script in #183. This time it did load alright. So I wonder what is wrong on my HDD2 plugin folder.

[carlmart]

Just to add one more interesting info for those reading this project.

There are only some places where I will be using SD to HD blowup, as some of them are not providing good looking results. My fault, because the SD camera was unattended on some occasions where I was shooting alone, and images are too dark. In fact next time I do that, I will leave the camera in auto and also shoot from further away, so the background gets out of focus.

The interesting thing was that I had to go back to an old technique, which is enlarging the shots you are using to get closer angles or close-ups. I was resisting that idea because that tends to show up a bit when using larger screens. Only that this time I will try it adding a mask to separate figure from background, and then focus-out the background. I have already tried it and it looks great.

What I am thinking of using is a Tiffen black mist effect to diffuse the close-up a bit, which is quite usual when going closer with a lens, and hid the enlarging problems.

[carlmart]

OK. Second upscaling, with a different shot.

Have a look at a comparative frame from Avid, with original DV on the right and upscaled HD on the left.

http://www.mediafire.com/i/?ztizzdqu0zj

Quite interesting indeed. The only enhancement I used was sharpen (0,3), and it brought out some subtle detail.


AVISource("e:\file.avi")
converttoyv12(interlaced=true)
TempGaussMC_beta1mod(EDIMode="NNEDI2")
nnedi(field=0,dh=true).TurnRight().nnedi(field=0,dh=true).TurnLeft()
spline36resize(1280,960)
sharpen(0.3)
spline36resize(1920,1080)
return last
separatefields.selectevery(4,0,3).weave


The HDV camera framed a wide shot of the group, so I can't compare the upscaled HD to it. But obviously there are some resolution differences against the DV, which doesn't seem to behave as well as it does on a well lit shot. The stage here was lit with available fluorescent light.

My way out for this sequence will be to convert it to black & white and use a 2.1 mask, as if it was cinemascope. The B & W will help me correct just the contrast, which will make HDV and upscaled HD shots blend better. I already tried it on the timeline and it looks great. The final test will be next week, when I will screen it on my 42" plasma.

Now a question on the ffmpeg conversion. As I think I mentioned, I installed WinXP SP3 in two different HDDs on my computer. The idea for that is to have a cleaner install where the Avid was supposed to work. But this dual setup has helped me on other questions, like when attacked by virus, avisynth problems and now ffmpeg.

Ffmpeg works fine on one HDD, but it does not on the other. I dropped the same ffmpeg .exe and .play files in the System32 directory on both HDDs, so I don't know what is missing on the one that refuses to load ffmpeg.

The next weird thing is the mov file. After I converted the DV file to HD on the working HDD, I went to the "Avid-clean" HDD to import the mov file. The resulting imported file came out with a completely white screen! That has never happened to me.

So I went back to HDD where I had made the ffmpeg conversion, loaded Avid there and imported the same mov file. Clean as a whistle!

Why is that? The only thing I had done was move the HD mov file from one HD to another. Can that be the reason? Why?

I am not too familiar with mov files, but they seem to be containers. Do they have paths inside that may make them lose their tracks on what is where? My guess is they do, so I wonder how to change that.

[2Bdecided]

Sounds like a codec issue.

[carlmart]

Sounds like a codec issue.

Probably. What do you suggest I should do?

[poisondeathray]

white screen suggests you're missing the codec.

so you should install it

(e.g if you are using dnxhd, install dnxhd)

[carlmart]

OK. Now I am not getting a white screen when I import from Avid. Even if that DNxHD codec should have been installed when I installed this Avid version, which was last week.

What I am still not getting to work is the ffmpeg converter on this HDD. What might be missing?

BTW, please go have a look at the comparison between the SD and upscaled HD here:

http://www.mediafire.com/i/?ztizzdqu0zj

HD on the left, SD on the right.

[2Bdecided]

BTW, please go have a look at the comparison between the SD and upscaled HD here:

http://www.mediafire.com/i/?ztizzdqu0zj

HD on the left, SD on the right.I already did. My comments are the same as, ooo, about a year ago! Those halos make it look more like upscaled SD. Try to get rid of the halos.

Though in the small resolution you uploaded, it's hard to know what it'll look like on a 1080p display!

btw, I'm very proud that you're taking as long to finish this project as I do some of mine. I start, and then something else comes along, and...!

(Still got to finish my wedding video - it's our eleventh anniversary this year!)

Cheers,
David.

[carlmart]

I already did. My comments are the same as, ooo, about a year ago! Those halos make it look more like upscaled SD. Try to get rid of the halos.

I think I tried it back then and I didn't quite like the results or it took to long to render them. But it would be nice to try them again. What would you suggest to use for that?

OTOS I am processing the upscaled SD images further. The one that I uploaded now will be turned to B & W, and I applied a Tiffen Soft/F video effect, so the halos are not so evident now.

I think that what you call halos I call borders, and I am quite aware of them. The filters soften them a lot.

Though in the small resolution you uploaded, it's hard to know what it'll look like on a 1080p display!

Sorry, I will try to capture two full frame shots, upscaled and processed, for you to see the results.

btw, I'm very proud that you're taking as long to finish this project as I do some of mine. I start, and then something else comes along, and...!

I am in the final stages now. Next week I will show the first cut to the musician, and on March 24th should be the public show.

(Still got to finish my wedding video - it's our eleventh anniversary this year!)

Congrats!

[carlmart]

OK. Here are the shots in three versions:

1) Original DV file:

http://www.mediafire.com/file/joiumdzonzd/radio_DV.jpg

2) Upscaled DV file:

http://www.mediafire.com/file/juzmydwtmj0/radio_upscaled.jpg

3) Processed upscaled file:

http://www.mediafire.com/file/gyj2nzo2kjm/radio_B&W + mask.jpg

[2Bdecided]

It's depressing how bad SD looks by default when you put it on a large screen - I think some NLEs try to do the worst job possible! Thank goodness for AVIsynth!

Yes, halos = borders, and yes, removing them usually makes the picture look softer. Don't think it's slow though.

My suggestions are back in the thread. Don't know if there are any better halo solutions out there now.


SD upscale > B&W as a "feature" is a good idea I think.

Cheers,
David.

[carlmart]

Hi David,

It's depressing how bad SD looks by default when you put it on a large screen - I think some NLEs try to do the worst job possible! Thank goodness for AVIsynth!

Yes, I am quite grateful on what Avisynth does for free. I think many of those programs, like Magic Bullet, implement many things used on Avisynth, charging a bundle.


Yes, halos = borders, and yes, removing them usually makes the picture look softer. Don't think it's slow though.

Let's try it then. First of all, if you can, explain a little to me on what variables do what on BlindDeHalo3. Forget about that last scene I uploaded, as I think the B&W trick worked like a charm.

Please suggest what I can do on the other image, with the black singer, also uploaded there.


Carlos

[carlmart]

Hi David,

It's depressing how bad SD looks by default when you put it on a large screen - I think some NLEs try to do the worst job possible! Thank goodness for AVIsynth!

Yes, I am quite grateful on what Avisynth does for free. I think many of those programs, like Magic Bullet, implement many things used on Avisynth, charging a bundle.


Yes, halos = borders, and yes, removing them usually makes the picture look softer. Don't think it's slow though.

Let's try it then. First of all, if you can, explain a little to me on what variables do what on BlindDeHalo3. Forget about that last scene I uploaded, as I think the B&W trick worked like a charm.

Please do suggest what I might do on the other image, with the black singer, also uploaded there.


Carlos

[carlmart]

Another stage. Today I could view the edited stuff in full quality on my 42" plasma. Remarkably good, superb, we might say without sounding too self-praising.

The editing is not complete, but now I can show it tomorrow with the minimum quality I wanted which is very good.

Today I could also concentrate on an artifact that shows on the upscaled DV stuff, which is difficult to explain. Imagine a circle which splits horizontally in two, and you see them displaced for a split second, sometimes in two places at the same time.

At first I thought it might be something related to Avid and its video player, which is QT, or even the video board. But when I used a Geforce 9600GT, things were crystal clear, so it's not hardware related.

My guess is it might be related to the deinterlacing plug-ins, as the artifact always happens in movements: subject, pan or camera movement. It's a split second, so it doesn't show when you view it frame by frame.

Any suggestions on:

1) The name of this artifact.

2) Tips to avoid them.

[2Bdecided]

I can't remember the name, but it happens when the framerate of the video clip isn't locked to the frame rate of the display device - or even the frame-change of the video clip isn't synchronised to the frame-change of the display device, and the displayed frame changes mid-frame - hence the top half is the previous frame, the bottom half is the next frame.

Can happen in the PC due to the player, or even in the display (if it's doing horrible frame rate conversion).


That's why you don't see it when stepping through frame-by-frame: it's not there in the footage itself.

Cheers,
David.

P.S. Sorry, I know no more about BlindDeHalo3 than you - this thread was the first time I played around with it.

[carlmart]

After two succesful conversions three weeks ago using ffmpeg, now I'm getting an error message like this:

http://www.mediafire.com/i/?mzahzzjiymy

The script I'm using is exactly the same, only changing the avi file.


import("C:\video\AviSynth 2.58\plugins\BlindDeHalo3.avs")
AVISource("h:\capturas\amorim.09-06-25_12-56.00.avi")
trim(1991,3000)
converttoyv12(interlaced=true)
TempGaussMC_beta1mod(EDIMode="NNEDI2")
nnedi(field=0,dh=true).TurnRight().nnedi(field=0,dh=true).TurnLeft()
spline36resize(1280,960)
BlindDeHalo3(rx=3.2,ry=1.5)
sharpen(0.3)
spline36resize(1920,1080)
return last
separatefields.selectevery(4,0,3).weave


The text I'm loading into ffmpeg is also the same, only changing input and output names.


ffmpeg -i tema_começo.avs -vcodec dnxhd -b 145Mb -flags +ildct -an tema_começo.mov

I've already gone back to the ffdshow version I had back then. The only other thing I did since then is installing and updating Megui.

What do you suggest might be happening and what can I do?

There are a few short shots more I need to upscale, and I don't know what other way I may go.