View Full Version : Upscale 480x270?
helplessandlost
21st January 2010, 23:16
I have an image sequence .avi created that is @ 480x270. I'm putting this into a 1920x1080 project.
What would be good LanczosResize or spline settings to do this?
Thanks!
poisondeathray
21st January 2010, 23:21
It's not going to look very good, because it's 4x, and you can't generate details from nothing , and there is no "best", because every source is different
I would try NNEDI2 , to upscale with less aliasing. If your source is noisy, denoise it first before upscaling, or you will upscale noise, then you might want to apply a sharpener after the upscale. Compare that to LanczosResize(1920,1080) or Spline36Resize(1920,1080) and you will see a lot less jaggies
#source filter AVISource()
#maybe some denoiser
nnedi2_rpow2(qual=3,rfactor=4,cshift="spline36resize")
#Some Sharpener e.g. LSFMod()
helplessandlost
22nd January 2010, 01:24
Thanks, what do you think would be a better size, and borders obviously?
poisondeathray
22nd January 2010, 01:26
Thanks, what do you think would be a better size, and borders obviously?
I don't know what your project entails, but I wouldn't mix that footage with 1920x1080 footage at all. The differences will be dramatic (e.g. if this was a multi cam edit or scene changes).
helplessandlost
22nd January 2010, 01:27
Ah, and reading up on nnedi2_rpow2 see that it's meant for interlaced - should have said this was progressive...
poisondeathray
22nd January 2010, 01:29
Ah, and reading up on nnedi2_rpow2 see that it's meant for interlaced - should have said this was progressive...
That's fine. NNEDI2 has 2 functions, 1 is an intra field deinterlacer, the other is an upscaler. The example above is the upscaling one
Try it out and compare with the LanczosResize script. I 100% assure you will see a big difference in the aliasing and jaggies, but I would never intermix with native footage that is 4x larger
helplessandlost
22nd January 2010, 01:30
I don't know what your project entails, but I wouldn't mix that footage with 1920x1080 footage at all. The differences will be dramatic (e.g. if this was a multi cam edit or scene changes).
This is actually an image sequence out of Vegas that I'm trying to re-import as a time-lapse which will be mixed with normal footage as well. Problem is Vegas seems to only like this size for the image sequencing - the original was 1920x1080...
Assuming of course there is a better way to do this in Vdub or Avisynth and keep the original resolution that I assume would be a better choice if you can point me to that...
Thanks!
poisondeathray
22nd January 2010, 01:33
This is actually an image sequence out of Vegas that I'm trying to re-import as a time-lapse which will be mixed with normal footage as well. Problem is Vegas seems to only like this size for the image sequencing - the original was 1920x1080...
Assuming of course there is a better way to do this in Vdub or Avisynth and keep the original resolution that I assume would be a better choice if you can point me to that...
Thanks!
Please clarify what the original source was. Were they stills from a still camera? What dimensions? How did you end up with the tiny frame size?
thetoof
22nd January 2010, 01:33
What would be more efficient is to upscale the image once with high quality processing (nnedi2, maybe some lsfmod or sssharp, a bit of grainfactory3 and magical powder here and there to make it look nice) and then create the image sequence.
i.e. imagesource for 1 frame.processing, then loop it or something for the desired duration
helplessandlost
22nd January 2010, 01:35
Please clarify what the original source was. Were they stills from a still camera? What dimensions? How did you end up with the tiny frame size?
Might have cross-posted - this is 1920x1080 AVCHD progressive footage - converted to Cineform .avi then using the "Render Images" function in Vegas which doesn't give you a choice on size :( outputed as .png
I set it for every 6 frames and like the way it's coming out, except for the size of course.
poisondeathray
22nd January 2010, 01:37
I see. Don't use "render images". Use a normal source filter on your native video footage e.g. DirectShowSource(), then SelectEvery() and some parameter. This way you get no reduction in resolution, and no need to upscale. You can change the FPS with various functions like AssumeFPS()
You can frameserve .avs scripts into vegas with AVFS , or encode that script to cineform intermediate in vdub (like your other thread) for import into vegas
If for some reason you wanted the individual (full sized) still frames, you could still use that .avs script, and export the .png in vdub by using file=>export=>image sequence
helplessandlost
22nd January 2010, 02:04
so something like this?
AVISource("myclip.avi")
SelectEvery(clip, 6, 0)
ConvertFPS(29.97)
poisondeathray
22nd January 2010, 02:10
Yes something like that, if your "myclip.avi" was a 1920x1080 cineform clip derived from your original AVCHD source.
You might have to adjust the FPS , or play with the selection of frames to whatever your goal was.
You can preview your scripts in MPC
helplessandlost
22nd January 2010, 02:51
Worked perfectly, thanks!
helplessandlost
22nd January 2010, 11:52
Incase your interested, this is a rough edit of what I was trying to do:
http://www.youtube.com/watch?v=wcoGQbl0rtI
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.