YATTA for VapourSynth (real name: Wobbly)

[K3]

How do you compile this for Windows? Me and another guy have been trying for the past two days and can't figure it out. One of the new commits fixes wobbly for VS r41+ which seems pretty important.
I have qtbase compiled from source with just ./configure and the the two flags to not compile the tests and examples and am using mingw-w64 to cross compile Wobbly with ./configure --host x86_64-w64-mingw32 --target x86_64-w64-mingw32 and had no luck. VS r43 compiled from source with just ./configure. All on a fresh install of Ubuntu 18.04. Am I missing something? Could you just put a new build up?

[jackoneill]

How do you compile this for Windows? Me and another guy have been trying for the past two days and can't figure it out. One of the new commits fixes wobbly for VS r41+ which seems pretty important.
I have qtbase compiled from source with just ./configure and the the two flags to not compile the tests and examples and am using mingw-w64 to cross compile Wobbly with ./configure --host x86_64-w64-mingw32 --target x86_64-w64-mingw32 and had no luck. VS r43 compiled from source with just ./configure. All on a fresh install of Ubuntu 18.04. Am I missing something? Could you just put a new build up?

Here you go:
http://savedonthe.net/download/2169/wobbly-v5-win32.html
http://savedonthe.net/download/2170/wobbly-v5-win64.html

Remember to report any bugs you see, otherwise they won't be fixed.

Cross-compiling this for Windows is a little complicated. I don't recommend it if you can avoid it.

[l33tmeatwad]

Wobbly/Wibbly for macOS neatly packaged into .app with no need to install Qt:

Download (http://www.mediafire.com/file/9dco13m4zaewewa)

You will still need to compile the plugins, it looks for VapourSynth in the standard location of /usr/local/lib.

[no1d]

Here you go:
http://savedonthe.net/download/2169/wobbly-v5-win32.html
http://savedonthe.net/download/2170/wobbly-v5-win64.html


Hi.
These builds are different from latest commit on github. Can you update repository?
Or am I missing something?

[jackoneill]

Hi.
These builds are different from latest commit on github. Can you update repository?
Or am I missing something?

I don't remember what code those binaries are made from. There are more commits on my computer than what you see at Github, that's for sure. I haven't pushed them because development is kind of stuck in the middle of a tedious task (undo support). I don't use the software myself, I don't get paid to write it, and so working on it is not very appealing anymore.

[jackoneill]

Here is the "official" v5: https://github.com/dubhater/Wobbly/releases/tag/v5

It's probably the same as the binaries I posted a few messages ago, because the latest changes are still from 2018.

There is no 32 bit Windows binary because of a compilation problem.

See what's "new": https://github.com/dubhater/Wobbly/blob/v5/changes.rst

[ChaosKing]

It complains about qt plattform (both wibbly and wobbly)
Win10 x64
https://i.imgur.com/vd11QUz.png

[jackoneill]

It complains about qt plattform (both wibbly and wobbly)
Win10 x64
https://i.imgur.com/vd11QUz.png

I added the missing DLLs and replaced the archive. It should work now.

[l33tmeatwad]

Getting ASSERT failure in QList<T>:: operator[]: "index out of range" when trying to run Wibbly on MacOS after compiling, stems back to WibblyWindow.cpp lines 1695:

job->setCrop(crop_list[0].toInt(), crop_list[1].toInt(), crop_list[2].toInt(), crop_list[3].toInt());

[jackoneill]

Getting ASSERT failure in QList<T>:: operator[]: "index out of range" when trying to run Wibbly on MacOS after compiling, stems back to WibblyWindow.cpp lines 1695:

job->setCrop(crop_list[0].toInt(), crop_list[1].toInt(), crop_list[2].toInt(), crop_list[3].toInt());

It's fixed now.

[groucho86]

On Mac 10.15.6, when I open a ProRes MOV in Wibbly via "Add jobs" I get the following error:
Final script for job number 1 evaluated successfully, but no node found at output index 0.

[Tima]

Here is the "official" v5: https://github.com/dubhater/Wobbly/releases/tag/v5

It's probably the same as the binaries I posted a few messages ago, because the latest changes are still from 2018.


"Old" binary is static and "official" one is not.

That makes issues when unpacking into the same folder as VSEditor 2, as it overwrites some (QT?) libraries with ones that are not compatible with both programs.

For now I've just grabbed old release, but it might be a good idea to switch to static builds back in v6. :)

[jackoneill]

"Old" binary is static and "official" one is not.

That makes issues when unpacking into the same folder as VSEditor 2, as it overwrites some (QT?) libraries with ones that are not compatible with both programs.

For now I've just grabbed old release, but it might be a good idea to switch to static builds back in v6. :)

It's a good idea, but too much effort to compile static Qt.

[Usopputo]

Hi, I have this problem when loading any video I already tried it with a .mkv and with .d2v

https://imgur.com/ZHHHfih

https://imgur.com/MkIPyuY

one is with .d2v and the other is a .mkv and that problem comes up, thanks in advance and have a happy afternoon.

[Earthnuker]

Hi,

i was trying to build a version of wibbly with debug symbols to diagnose a crash (GitHub issue #9) and it compiles fine but during linking it can't find any of the Qt functions.
build command+compilation log: https://gist.github.com/Earthnuker/36b7cff685448fced13c7fa34cfcdbd2

has anyone encountered a similar issue or knows a solution?

help would be appreciated

best regards,

Earthnuker

[sl1pkn07]

maybe you need set QT5PLATFORMSUPPORT_CFLAGS ?

also, qt5 install pkg-config files (maybe you need install pkgconf in msys). you can invoke the includes and libs with


pkg-config --libs foo


or


pkg-config --cflags foo


you also combine options and targets for complex output

EDIT: qt5 packages in msys2 have separated debug symbols in other package
https://packages.msys2.org/base/mingw-w64-qt5

greetings

[Myrsloik]

Here's a test build (https://www.dropbox.com/s/ytxu9e5z9e33njf/wobbly-test1.7z?dl=1) that works with the latest vs. It also has some other small changes. More to come.

Compilation is now also greatly simplified. Simply install the VS2019 Qt 5.15 libraries using the official Qt installer (bugmenot accounts accepted). Grab VS2022 (or 2019 I guess) and install the Qt extension and point it at the libraries you just installed.

Open project and compile. Release builds have all required files in the output dir. I hope this will encourage more contributions form windows users.

[Yomiko]

Would you make tool windows docked or centered on screen when first enabled? The default behavior is quite unfriendly for users with taskbar on top.

[Myrsloik]

Would you make tool windows docked or centered on screen when first enabled? The default behavior is quite unfriendly for users with taskbar on top.

Patches welcome I guess. Especially for minor GUI things since my Qt skills are limited.

My main goals are:

Add yatta telecide metrics and yatta style features like pattern guidance/other useful things that depend on it
Cleanups to script generation (there seems to be a certain consensus on certain changes)
Other minor convenience tweaks