Posts: 785
Threads: 16
Joined: Mar 2020
From log seems it is something related to "got no version info for: sox"
Seems in sox version that you compiled instead of fixing sox itself you probably remove version check for sox in new Hybrid UI and so new sox became not compatible with old Hybrid UI.
Here is log:
Posts: 10.551
Threads: 57
Joined: May 2017
Ah, I see, I added 'sox' to the noVersionInfo list on MacOS.
When building from latest source (like I did) there is no version info string in sox.
So for older builds the sox version from 2015 is needed.
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
Ok. Guess i didn't notice this problem in last package because i use saved defaults preferences from earlier version.
VapourSynth + Plugins + Scripts + Hybrid package update [2020.10.10]
Changes:
- sox downgraded to version 14.4.2 from sourceforge because it appears that newer versions don't compatible with legacy Hybrid UI versions.
- Hybrid UI 2020.09.15 with internal components updates from Hybrid 2020.10.10.
- Updated FAQ
DOWNLOAD package from Google Drive:
https://drive.google.com/drive/folders/1...sp=sharing
Posts: 31
Threads: 10
Joined: May 2017
(10.10.2020, 17:31)shijan Wrote: Ok. Guess i didn't notice this problem in last package because i use saved defaults preferences from earlier version.
VapourSynth + Plugins + Scripts + Hybrid package update [2020.10.10]
Changes:
- sox downgraded to version 14.4.2 from sourceforge because it appears that newer versions don't compatible with legacy Hybrid UI versions.
- Hybrid UI 2020.09.15 with internal components updates from Hybrid 2020.10.10.
- Updated FAQ
DOWNLOAD package from Google Drive: https://drive.google.com/drive/folders/1...sp=sharing
Is it supposed to work on Mojave 10.4.6? Because I got that repeatedly with this version at startup
Posts: 10.551
Threads: 57
Joined: May 2017
11.10.2020, 11:32
(This post was last modified: 11.10.2020, 11:34 by Selur.)
"overWriteOutputFrameRateValue"
Ahh,.. this happens because Vapoursynth isn't present.
-> will fix. (accidentally moved it's definition to the Vapoursynth section ;))
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
How is everyone doing? Kinda quiet lately.
Posts: 10.551
Threads: 57
Joined: May 2017
I've some heath issues atm. but other than that I've fixed quite a bunch of bugs.
And currently I'm waiting of feedback from two users regarding bugs they reported and hunting
another bug, where I don't see what's going wrong.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
I hope you are feeling better.
Hope it is something chicken soup can fix.
Posts: 10.551
Threads: 57
Joined: May 2017
Sadly chicken soup didn't help, won't kill me, but at least this week I'm still on sick leave and visiting the docs three times this week.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Just checking im.... everybody alright?
