Posts: 10.553
Threads: 57
Joined: May 2017
29.03.2021, 14:07
(This post was last modified: 29.03.2021, 14:08 by Selur.)
Regarding the ' value in deinterlacer', does it work if you reset the FilteringModel?
Quote:FilteringModel doSet->found no field: vsCustomCodeSelectValue'
-> I can reproduce it, looking it it now.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 785
Threads: 16
Joined: Mar 2020
"Couldn't set property(2): value in deinterlacer - FilteringModel to QTGMC (Vapoursynth), found: Yadif - fast" seems appears only on fresh start when there is no Hybrid app support folder. and when "Auto save defaults" is not enabled
By the way, update x264. it is 11-Feb-2021 version here
https://artifacts.videolan.org/x264/release-macos/
Also currently inside app contents there is a MKVToolNix.app and same time extracted files mkvextract, mkvinfo and mkvmerge. Can this produce conflicts?
Posts: 10.553
Threads: 57
Joined: May 2017
29.03.2021, 14:25
(This post was last modified: 29.03.2021, 14:29 by Selur.)
Quote:Can this produce conflicts?
Nope, the one listed under Config->Tools will be used.
Quote:FilteringModel doSet->found no field: vsCustomCodeSelectValue'
didn't appear again after a restart. :/
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 785
Threads: 16
Joined: Mar 2020
Maybe back to less buggy qt5
Posts: 10.553
Threads: 57
Joined: May 2017
That has nothing to do with Qt6 those are errors, Hybrid silently fixed in the background, I just disabled the fixing and told Hybrid to popup the errors.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 10.553
Threads: 57
Joined: May 2017
Quote:"Couldn't set property(2): value in deinterlacer - FilteringModel to QTGMC (Vapoursynth), found: Yadif - fast"
..
Couldn't set property(2): value in bitDepth - ProResModel to 8-bit, found: 10-bit
...
Couldn't set property(2): value in vp9ColorSpace - VPXModel to unkown, found: unknown
...
FilteringModel doSet->found no field: vsCustomCodeSelectValue'
should be fixed now -> updated dev version in google drive
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 785
Threads: 16
Joined: Mar 2020
When i uncheck "Auto" checkbox in Deinterlacer, i got error message:
"Couldn't set property(2): value in deinterlacer - FilteringModel to none, found: Yadif - fast"
Posts: 10.553
Threads: 57
Joined: May 2017
will fix
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 10.553
Threads: 57
Joined: May 2017
Should be fixed now too.
(updated dev)
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Posts: 785
Threads: 16
Joined: Mar 2020
Seems some problems with ProRes. Rendered ProRes file length don't match to original ProRers file length (all filters and deinterlace where turned off).
Also i got Error on ProRes file import.
Couldn't set property(2): value in videoAngle - MainTabModel to 0, found: 1
If it helps, here are ProRes file examples rendered from Davinci Resolve
https://www.dropbox.com/sh/bak63hnr7mnpg...aaxFa?dl=0
