Container format: Dolby Digital (AC3)Ĭomplete name : E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar ID2 English.ac3 "C:\StaxRip_圆4_1.3.1.7_beta\Apps\MKVToolNix\mkvextract.exe" tracks "E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar.mkv" 1:"E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar ID2 English.ac3" -ui-language enĮxtracting track 1 with the CodecID 'A_AC3' to the file 'E:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar temp files\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar ID2 English.ac3'. Writing library : libebml v1.2.3 + libmatroska v1.3.0 Writing application : mkvmerge v5.7.0 ('The Whirlwind') built on 20:08:51 Any comment before proceeding to staxrip guide or you wanna setup DSS2 LAVF CUVID?Īfter "upgrading" to Win 10 I got the following error trying a reencode:ĬPU : Intel(R) Core(TM)2 Duo CPU E8400 3.00GHzĮ:\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar\Day for Night 1973 720p WEB-DL AAC 2.0 H.264-HDStar.mkv Oh.about deinterlacing part.I wonder if you can use LAVF CUVID for the deinterlacing.either this or wait rigaya to come out with his version of HW deinterlacing. -? Why would you use these if you can simply use -tune grain X265 Medium (x265 default preset, no issue here)ĬRF 26.5 (The default recommended factor from x265 documentation is 28)
Wait a minute here.There are few problem with your so called "preset". John can you assist on converting this handbrake preset to staxrip?Īq_mode=1: aq_strength=2.00: qcomp=0.8: psy_rdoq=14.00ĭenoise -> NLMeans -> Preset Ultra light -> Tune Film NVEncC64.exe -codec h265 -level 4.1 -bframes 0 -ref 0 -cqp 20:22:25Įncoded 34409 frames, 314.94 fps, 2049.56 kbps, 350.64 MBĮdit : CPU info = I5 3570K 4.2Ghz OC, just in case if someone wanna compare the Staxrip CPU based bilinear resizer.and GTX970 in case anyone wanna check the gpu resizer?Įdit V2 : Hohoho.I wonder if rigaya can implement other form of resizing algorithm (bicubic? lanzcos? Catmul?), all hail rigaya!!~~Įdit V3 : Stax76~~~~I hope you can implement this functionality as soon as possible, seem like rigaya adds custom CUVID decoder to be used in conjunction with the gpu resizer. 34362 frames: 398.46 fps, 2136.07 kb/s, remain 0:00:00 2:13Įncoded 34410 frames, 398.69 fps, 2133.29 kbps, 364.98 MBįor comparison, staxrip with DSS2 LAVFilter DXVA Copy-Back + its built-in Bilinear resizer with setting below Wow, I am totally amazed by nvencc v2.00β1 resizing speed.
New NVEncC v2.00β1 is out supporting HW decode and HW resize using CUVID. i understand how you want the language detection to work when reading from the file to try and detect what language the audio is in 1.1.8 this wasn't an issue at all as it did respect the settings that the user set i.e english as even if the audio was encoded or the audio was auto loaded by itself it will keep it as english :cool: (both of these issues are still there even in the latest test version )
I've also notice that the default audio language being set for mkv/mp4 isn't being respected for some odd reason if i load a encoded audio file it will change from the default english (which i set) to undetermined which i find very odd as the only way to over come this is setting it to english every single time (not ideal if you only use one audio language) :confused: however. so would it be possible to set the default indexer only for the video comparison to ffms2 so there isn't any issues like this and works like it "should" do ever time no matter what demuxer/indexer you use ? :eek: if you do set your demuxer/indexer to your favor demuxer/indexer it can cause issues when it comes to using the video comparison as it will try and use that demuxer/indexer which you set which can fail quite alot or badly however if its left as default (auto detect?) it will use ffms2 like it should do. It seems i've came across a few bugs firstly.
0 kommentar(er)
