The following warnings occurred: | |||||||||||||||
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.3.12-nmm1 (Linux)
|
[GUIDE] VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: [GUIDE] VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS (/thread-1279.html) |
RE: VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS - Selur - 18.07.2021 Quote:That's strange... When i click to libdecross.dylib or to libdpid.dylib - Finder relaunches. As i remember same problem was noticed due conflict somewhere in names.Do the filters work in Hybrid? RE: VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS - shijan - 18.07.2021 Where to look for DPID in Hybrid? Can't se it at all in UI. P.S. I removed libdpid.dylib and there is no more Finder crash when i click to libdecross.dylib So i guess problem goes to l33tmeatwad RE: VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS - Selur - 18.07.2021 DPID is a downscaler so it's under "Filtering->Vapoursynth->Frame->Resize->Resizer" and will only be used when scaling down. (it's only really useful when downscaling a lot, like from 4k to SD, for small scale factors I would recommend not to use it) Cu Selur RE: VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS - shijan - 18.07.2021 I reinstalled Vapoursynth and installed libdpid.dylib (without libdecross.dylib). It is hard to say if DPID works or not for real, but i can't see any error messages in Hybrid when use it. So i guess it is some namespace problem somewhere between these filters. RE: VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS - Selur - 18.07.2021 Quote:but i can't see any error messages in Hybrid when use it.Check the Vaporusynth Script View to be sure it's used. Also when using the Filter View it should be easy to spot whether dpid works or not when down-scaling a lot (here 4k to sd): Quote:So i guess it is some namespace problem somewhere between these filters.What makes you thing that? With sangnom.SangNom and sangnom.SangNomMod the collision is since they both use the same namespace 'sangnom'. Using both filters, works fine in Windows: # Imports I also don't see where 'decross.DeCross(' and 'dpid.Dpid(' would overlap), or I simply don't understand what you understand as 'some namespace problem'. Cu Selur RE: VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS - shijan - 18.07.2021 It only guess. I remember when i installed both sangnom.SangNom and sangnom.SangNomMod i got same Finder crash and relaunch. RE: VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS - Selur - 18.07.2021 Okay, I never had that effect in Finder, but may be l33tmeatwad has some idea why this could happen. Cu Selur RE: VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS - shijan - 18.07.2021 It is some plugins conflict for sure. I also got Hybrid crash at second launch (sometimes) when both plugins are installed. DPID was never installed before, so yet it conflicts somehow with decross due unknown reason. It is macOS only problem partially due Vapoursynth autoload. RE: VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS - Selur - 18.07.2021 Yes, I understand that the previewer and encoding jobs could crash, but that Finder crashes seems strange. Quote:An option to disable auto loading is probably coming soon. With more exciting things as well.source: https://forum.doom9.org/showthread.php?p=1947774#post1947774 So with a bit of luck may be with Vapoursynth R55 (probably not R54) auto loading can be disabled. Cu Selur RE: VapourSynth + QTGMC Deinterlace + Hybrid UI FAQ for macOS - shijan - 18.07.2021 Probably when selecting .dylib in Finder, Vapoursynth attempt to generate quicklook preview for file or reads something from it or somehow else interacts with it. And this provoke conflict if both filters use something similar inside that is already autoloaded in Vapoursynth. And after conflict it is not enough to simply delete .dylib. Vapoursynth reinstall required to delete that cashed data of both conflicted plugins. |