Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
25th July 2021, 23:42 | #4401 | Link |
Registered User
Join Date: Feb 2002
Posts: 758
|
I just spend time to reconfigure from zero, please say you only added Neo FFT3D. I already added it myself.
Update: ok I see more has been changed in the package. I'm going to re-download and overwrite it without re-configuring again, that would be ok I guess? Last edited by Atlantis; 25th July 2021 at 23:54. |
26th July 2021, 00:04 | #4403 | Link | |
App Digger
Join Date: Sep 2018
Posts: 411
|
Quote:
See this post on the Issue Tracker. It didn't work right before when we could extract timestamps from only VFR MKV files. |
|
26th July 2021, 01:27 | #4404 | Link |
App Digger
Join Date: Sep 2018
Posts: 411
|
FYI, there's a lot of change in the filter profiles/menus in v2.7.0.
For those of you who just overwrite the files (although not recommended officially): do not forget to 1) backup your own custom filter profiles 2) restore the default profiles 3) and then add your custom filter profiles again to see the new changes. Same for VapourSynth. And don't forget to update your old settings by taking similar steps as above for each and every menu, profile, template, setting, etc. And in case you're using installed frameservers (AVS or VS), try switching b/w portable and installed (installed -> portable -> installed, restarting StaxRip each step) to purge any remaining garbage in the settings file. |
26th July 2021, 21:51 | #4406 | Link |
App Digger
Join Date: Sep 2018
Posts: 411
|
Notice for SMDegrain script file update
@everyone,
You need to replace SMDegrain.avsi with the following updated file in order to avoid SMDegrain errors in v2.7.0. SMDegrain.avsi (version: 3.1.2.115s) Location: <StaxRip-Folder>\Apps\Plugins\AVS\SMDegrain\SMDegrain.avsi There was some internal function name changes along the way and this will definitely cause script errors if you keep using the shipped script file SMDegrain.avsi. So please make sure to update the file. |
28th July 2021, 16:59 | #4410 | Link |
Registered User
Join Date: May 2016
Posts: 88
|
I had this problem because I use an old Xeon CPU so had to install an older version of JPSDR
Apps - Manage - Search - JPSDR - Auto Update - let it download and choose the correct version for your system I had to choose Release_XP_SSE2 and it fixed this issue. |
28th July 2021, 19:32 | #4411 | Link |
Registered User
Join Date: Jul 2019
Posts: 4
|
Question about current handling of 'color subsampling' in older DV DVDs.
Hi everyone,
I am currently digitizing my old DVs and DVDs: deinterlacing, etc. and I'm wondering if Staxrip handles color subsampling differently now. Images: (from DV yuv411 / DVD yuv420) - Original DV 4-1-1 capture. - Staxrip encode from 2019: bit darker/contrast. - Staxrip 2.7.0 (and other recent versions): Notice the change in red tone.. Seems like there's a yellowish tint overall in the newer Staxrip encode... I'm hoping maybe someone can test this with older DVs out there to confirm, so I can get a better idea about this. Thanks a lot for any input!! **My script: (MOV ProRes SD or HQ) - Automatic Source: tcFile = "%temp_file%_timestamps.txt" # timestamps file path Exist(tcFile) ? FFVideoSource("%source_file%", cachefile="%source_temp_file%.ffindex", timecodes=tcFile) : FFVideoSource("%source_file%", cachefile="%source_temp_file%.ffindex") ConvertToYUV420() - Crop(8, 6, -16, -10) - QTGMC(preset="Very Slow", InputType=0, sourceMatch=3, lossless=2, sharpness=0.5, tr2=3, ediThreads=8) Prefetch(7) - KNLMeansCL(D=1, A=1, h=2, device_type="auto") - nnedi3_rpow2(rfactor=2, cshift="LanczosResize", fwidth=960, fheight=720) Last edited by SupermanTV; 28th July 2021 at 22:45. Reason: Added details |
29th July 2021, 10:46 | #4412 | Link |
Registered User
Join Date: Feb 2002
Posts: 758
|
Did some tests. So I'm not liking this timestamps thing. I encoded a video. When I jump to a frame number for example, then when I go to the same number on the source, it is not the same frames. It's 2 different frames assigned to the same frame number. This is troubling for me so I'm not going to use them.
|
29th July 2021, 15:46 | #4413 | Link | |
Registered User
Join Date: Oct 2007
Posts: 43
|
Quote:
Source: 23.976 fps Output: 23.8095 fps |
|
29th July 2021, 18:24 | #4414 | Link |
App Digger
Join Date: Sep 2018
Posts: 411
|
Timestamps extraction for MKV files is not hard-wired in the new version. It's an option for the templates/projects.
If it doesn't help, you can turn it off. Do you have any issue with turning it off in your startup or favorite templates? |
29th July 2021, 19:41 | #4416 | Link |
App Digger
Join Date: Sep 2018
Posts: 411
|
I don't think I need to persuade you to use it.
If you think it's not working as expected but you can't help but use it, report a bug with concrete evidence. Like I pointed out, the new timestamps extraction feature is obviously helpful for some users with some videos. As always, there is no universal cure-all in video encoding. If the new feature doesn't work right, then maybe it's not fit for the specific video, or a bug. If you are sure it's a bug, submit a bug report with a valid log or any supporting material. But in this case, it's obviously different: you can always opt out of this new feature in Options. I truly don't understand why you keep complaining about things that you can choose not to use in the first place. Last edited by JKyle; 29th July 2021 at 19:47. |
29th July 2021, 20:26 | #4417 | Link |
App Digger
Join Date: Sep 2018
Posts: 411
|
In case you enabled timestamps extraction, chose MKV as the output format, and there is a change in frame numbers/frame rate/duration, the Assistant is supposed to issue a warning/suggestion as follows in v2.7.0:
If you are sure the Assistant does not warn about those changes, then plz report a bug with a valid example. |
29th July 2021, 22:04 | #4418 | Link | |
Registered User
Join Date: Feb 2002
Posts: 758
|
Quote:
In case you don't know, this is a forum, not your personal home. A forum is a place for people to discuss. So when I notice new stuff I write here to discuss with people. I'm not sending letters to your home. In case you are not interested in a subject matter, it is very easy, you just ignore it. So please stop complaining about posts you don't like. You ignore them. It is very easy. I do it all the time. Last edited by Atlantis; 29th July 2021 at 22:07. |
|
29th July 2021, 22:28 | #4419 | Link | |||
App Digger
Join Date: Sep 2018
Posts: 411
|
Quote:
Quote:
Quote:
And putting several posts about the same topic (timestamps) over and over without providing any supporting material is not a complaint? They sound just like complaints to me. Many developers and contributors including @stax76, @44vince44, and me have repeatedly asked that users please be a little bit more cooperative by posting issue reports and feature requests on the GitHub repo with logs, error messages, and samples. And you squarely declined it and insisted on posting here claiming that you are just giving advice and suggestions. Well, OK. Even though I feel uncomfortable with the way you present your arguments, I will. Last edited by JKyle; 30th July 2021 at 00:25. |
|||
31st July 2021, 19:58 | #4420 | Link |
Registered User
Join Date: Feb 2019
Posts: 47
|
Is it just me but I just went to auto update NVEnc and MKVToolnix to latest versions on 2.7.0 and it failed. In previous versions always worked. Working again in 2.8.0
Last edited by chipxtreme; 2nd August 2021 at 23:28. |
Thread Tools | Search this Thread |
Display Modes | |
|
|