I am now switching from KVCDx3 to KDVD Full-D1 (New GOP, CQ_VBR, CQ=25, min=1000, max=4000), do I really need any filters, if so, which one (ones) suits the best (Blockbuster, Nomosmooth, Fluxsmooth)?
|
Quote:
-kwag |
New version 0.3
Here's 0.3 (and the source).
Changes: * Fixed bad bug that was messing up the algorithm. * Because of above, put defaults back to 7, 7. * Made numerous optimizations, should now be significantly faster. Like I said above, I'm very excited about this one, but I need you guys to put it through its paces. I'm especially interested in figuring out the best thresholds for various sources (clean DVD, noisy DVD, captures, anime, etc.) and perhaps adding a "preset" parameter at some point. Have fun :). Edit: Removed links to old version. |
Request for version number...
SansGrip:
Can you add to the code the version number of each .dll file? Too many updates, somtimes i don"t remember which version currently i"m using... :) |
Re: Request for version number...
Quote:
Quote:
|
Update
Just to let you all know that I've not been idle over the past week or so, but have been attempting to reimplement Flux with multimedia extensions. It was hard going for a while, but then something seemed to click and this morning I fixed the last bug in the new iSSE version of Flux-for-YUY2 (I'm going to start the YV12 version this afternoon, and it should go quicker because I won't have to monkey around with pixel order like I do in the YUY2 version).
While the code is not optimized wrt pairing and stalls and all that good stuff, it still runs at twice the speed of the old C++ version on my system :D. I'm predicting the YV12 version will see an even bigger increase because of the lack of aforementioned monkeying around. I'm hoping to finish it and release today, but I'm not promising anything. This is my first real C-to-MMX port and I'm still pretty slow at the moment. |
You guys are great!
Just yesterday I got the hang of FITCD. Blockbuster is working wonders for my video, and I can't wait to add Flux into the mix. I'm using Kwag's KDVD Half D1 template with all default settings. I'll let everyone know how the video turns out with these filters. I'm sure the results will exceed my expectations. :D
|
New version 0.4
I just released 0.4. Sorry about the delay -- darn real life ;).
The biggest change in this version is that I implemented ISSE-optimized algorithms for both the YUY2 and YV12 versions. From my quick benchmarks it seems to run about twice the speed of the C++ version. I also added chroma smoothing. As usual you can get the latest version (and the source) from the web site in my sig. (By the way, I apologise for the downtime: the web server it's on is located in North Carolina, and they had a killer storm which took power down for days. It should be back up now.) Many thanks to Doom9's trbarry, sh0dan, dividee, and everyone else who helped me figure out assembler and MMX by putting up with and patiently answering my stupid questions. Also many thanks to Kwag and all the other testers here on KVCD :). |
Thanks SansGrip,
Glad to see you're back :D -kwag |
Quote:
It was kinda disturbing looking at the Flux source code again -- even after a couple of weeks I had to go through it line by line to figure out how it works 8O. I'm hopefully going to spend some time on the Predictor next, but I'll write more about that in the appropriate thread. |
so would this be a good script?
BiLinear Blockbuster .... the noise partor it FluxSmooth for both DVD and DVD anime? Thanks |
Quote:
Bilinear FluxSmooth Blockbuster or you'll be smoothing the noise you'll apply with Blockbuster. |
Ok, I'll try it. thanks, why do you put the add noise (blockbuster) at the end of the script?. So you guys think FluxSmooth is still better than Convolution3D?
|
Quote:
|
so the added noise at the end is a good thing then? wierd. I was putting the noise before resize because of stuff like solid colour spots in video, like walls, is what the resizer is having problems with and not allocating bitrate properely hence the DCT blocks, so by adding noise at the begining then would make any varience in the 'wall' more prominant which intern gives the resizer a better 'view' of what's happening and alocates bitrate a little better. back to the drawing board :(
|
It seems that FluxSmooth chokes on some video material. I'm trying to encode a DivX5 movie to KVCD at 352x576, but FluxSmooth chokes badly. It's a helluva lot slower than it should be, I'd say the prediction with FluxSmooth takes normally less than 5 minutes and with this video it takes more than 10! I've had this problem before and but I was able to get rid of it by moving FluxSmooth after resize. This time it was already after resizing so that's no good now (I did try moving it before resize without any luck). TemporalSmoother works OK.
|
Quote:
|
Quote:
|
Quote:
|
That's YUY2 input, I use Avisynth 2.07 currently. I'll try the same clip with AVS2.5a tomorrow and see if it's still the same result.
The frame size is 320x368. I don't think this is the issue as I've done numerous clips like this and have had only once or twice the same thing. Here's the script I've tried if it's of any use: LoadPlugin("c:\windows\system\fluxsmooth.dll") LoadPlugin("c:\windows\system\convolution3d.dll") LoadPlugin("c:\windows\system\dctfilter_yuy2.dll") LoadPlugin("c:\windows\system\blockbuster.dll") LoadPlugin("e:\progra~1\gabest\vobsub\textsub.vdf" ) LoadPlugin("c:\windows\system\legalclip.dll") LoadPlugin("c:\windows\system\sampler.dll") AVISource("c:\temp\leffat\evilde~1\ed2.avi",false) Fadeout(250) Crop(2,8,-2,-6) LegalClip() TextSub("c:\temp\leffat\evilde~1\ed2.srt",25) BicubicResize(320,368) FluxSmooth() Blockbuster( method="dither", variance=0.7, seed=1 ) AddBorders(16,104,16,104) DCTFilter(1,1,1,1,1,1,0.5,0) LegalClip() Sampler(length=24) |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.