Windows / Vegas / Hitfilm / Resolve / Commandline

[sebasti...@gmail.com]

Hello,

First I'd like to say tuttleofx seems very good tool.

Unfortunatly that's about unusable on Windows for video enthousiasts like me.
I'd like to use it in my workflow and/or commandline but can't success to have any significant result... so if any one succeeded in some way and want to share knowledge it would be welcome ^^

First it lacks of good and clear documentation for proper install and solving main encountered issues on windows.

I followed readme.md, installed latest python 2.7, and put tuttle 0.8.1 win dist in "C:\Program Files\Common Files\OFX\Plugins"

most of ofx plugins are detected by my hosts (Sony vegas, hitfilm Pro 3, and Resolve)... but can't get anything of any plugin :

- on Vegas : plugins have none impact on video preview nor render (and eye of effect preview looks golden/brown on all except viewer ... so I think there's some issue somewhere)... even if I put my Vegas projects in 32bit (Video) or 32bits (Full-range) by default, as I read somewhere on community forum, and even if I des/activate GPU/CPU mode... so I guess there's some ofx interface communication fail somehow ^^

- on Hitfilm : generators work, but effects etc. make crashing Hitfilm (If I don't say a mistake Hitfilm uses GPU accelerator and process images with floats 16bits depth internally)

- on Resolve : I have a few plugins showing and if I remember well they make Resolve crashing

I didn't test on Nuke cause free version is too limiting (especially resolution), price's too high, and I have license for Vegas & Hitfilm.

So I've tryed to work by commandline for getting some overview... but first the sam.bat doesn't work if any space in the sam.py path ^^ ... I've tryed many things but couldn't get rid of .bat, win command line combined with python parsing issue ... So I moved to an other directory without space in path... but when all looking ok I realized over a huge set of detected supported video format/ext, only the 2 main one seem unsupported : .mov and .mp4 :/ so when I launch a simple :

sam do r test.mov|mp4 (4k UHD from my Gopro Hero 4 or GH4)
I get an error saying : unsupported extension mov|mp4

Well I'm surprised avreader can't read these containers or maybe I missed something ?
I have installed AnotherGUI that relies on ffmpeg too and seems to handle them properly ^^ ... And I guess a lot of users would like to use these container formats whatever codec used inside ^^

Last question : is it potentialy possible to use DnxHR (AnotherGUI handle it) ? I'd like to keep a 4k UHD pipeline for the workflow I'm trying to build... so DnxHD can't do it and I'd prefer DnxHR over ProRes.

Thanks in advance for any help.

PS : Win 7, 16GB Ram, GeForce GTX970 3GB, Sony Vegas 13 PS, HitFilm Pro 3, Resolve 12 Lite Beta, all uptodate

[Clément Champetier]

Hello,

Hello Sebastien,

And thanks for your feedback: it seems you tried a lot of configurations and tools with tuttle!

To be honest with you, it has been several months that the developer team has not made efforts to work/develop/test on Windows platforms. This is not the priority right now, but the project was done to be multi-platform, so the issue still exists and some work was done for that (for v0.8.1).

 

First I'd like to say tuttleofx seems very good tool.

Unfortunatly that's about unusable on Windows for video enthousiasts like me.
I'd like to use it in my workflow and/or commandline but can't success to have any significant result... so if any one succeeded in some way and want to share knowledge it would be welcome ^^

Let's do this ;)

 

First it lacks of good and clear documentation for proper install and solving main encountered issues on windows.

Sorry about that: documentation is still one of our weakness point. Especially on Windows...

First, tuttle v0.8.1 is the last windows binary available, but it is an old version (a lot of corrections were made since there)... If you are a developer and know something about building a software, this page will help you.

 

I followed readme.md, installed latest python 2.7, and put tuttle 0.8.1 win dist in "C:\Program Files\Common Files\OFX\Plugins"

Why this readme?

 

most of ofx plugins are detected by my hosts (Sony vegas, hitfilm Pro 3, and Resolve)... but can't get anything of any plugin :

- on Vegas : plugins have none impact on video preview nor render (and eye of effect preview looks golden/brown on all except viewer ... so I think there's some issue somewhere)... even if I put my Vegas projects in 32bit (Video) or 32bits (Full-range) by default, as I read somewhere on community forum, and even if I des/activate GPU/CPU mode... so I guess there's some ofx interface communication fail somehow ^^

Some other users had issues on Vegas. Check this thread could be a good way to start.

 

- on Hitfilm : generators work, but effects etc. make crashing Hitfilm (If I don't say a mistake Hitfilm uses GPU accelerator and process images with floats 16bits depth internally)

You did not find any tuttle effect which works on Hitfilm? Did you try with OFX plugins from other third party (Natron, Sapphire...)?

 

- on Resolve : I have a few plugins showing and if I remember well they make Resolve crashing

I didn't test on Nuke cause free version is too limiting (especially resolution), price's too high, and I have license for Vegas & Hitfilm.

Ok. Most of the time, the tuttle plugins are tested with the command line (sam), and with Nuke. But we try to fix issues like yours on the other hosts too.

 

So I've tryed to work by commandline for getting some overview... but first the sam.bat doesn't work if any space in the sam.py path ^^ ... I've tryed many things but couldn't get rid of .bat, win command line combined with python parsing issue ...

I don't understand the problem here. You just need to use the sam.bat (which calls the sam.py).Can you just give us your path where you put tuttle?

 

So I moved to an other directory without space in path... but when all looking ok I realized over a huge set of detected supported video format/ext, only the 2 main one seem unsupported : .mov and .mp4 :/ so when I launch a simple :

sam do r test.mov|mp4 (4k UHD from my Gopro Hero 4 or GH4)
I get an error saying : unsupported extension mov|mp4

Well I'm surprised avreader can't read these containers or maybe I missed something ?

Indeed avreader should support this common format. Can you give use an example (a short movie)?

Maybe the problem is solved within the last version (v0.12.2), and it could be a good reason to deploy a new tuttle version for Windows.

 

I have installed AnotherGUI that relies on ffmpeg too and seems to handle them properly ^^ ... And I guess a lot of users would like to use these container formats whatever codec used inside ^^

I'm curious : what GUI around ffmpeg do you use for this kind of cases?

 

Last question : is it potentialy possible to use DnxHR (AnotherGUI handle it) ? I'd like to keep a 4k UHD pipeline for the workflow I'm trying to build... so DnxHD can't do it and I'd prefer DnxHR over ProRes.

In theory, all ffmpeg can do, avreader can do as well (for unwraping/decoding). And as far as I know, ffmpeg does not support DnxHR yet (see this ticket).

I heard that Davinci Resolve can export DnxHR if you use some Avid codecs packs (check this one). But for now, I don't know any open source library which can export to DnxHR...

 

Thanks in advance for any help.

PS : Win 7, 16GB Ram, GeForce GTX970 3GB, Sony Vegas 13 PS, HitFilm Pro 3, Resolve 12 Lite Beta, all uptodate

Regards,

Clement 

[sebasti...@gmail.com]

> To be honest with you, it has been several months that the developer team has not made efforts to work/develop/test on Windows platforms. This is not the priority right now, but the project was done to be multi-platform, so the issue still exists and some work was done for that (for v0.8.1).
>  

I anderstand and support you. Multi-platform/software is indeed a nice goal but never easy to reach :)

Achieving it can potentially enlarge user set/community if functionnal and a minimum user friendly. I think you'd gain of robust integration, once main interfaces handled you should only get minor issues and could work on MAC/linux without care ;)

That's why I pushed my tests a little and will try to help if I can.
I'm a dev but really not used to python nor win cmdline.

I guess in the current state most (non dev) videasts will pass their way for win plateform even if content is potentially great and interesting to them.

> Sorry about that: documentation is still one of our weakness point. Especially on Windows...
> First, tuttle v0.8.1 is the last windows binary available, but it is an old version (a lot of corrections were made since there)... If you are a developer and know something about building a software, this page will help you.

No problem for doc, you can't do everything at same time ^^
But in case it becomes fully functionnal it would be sad there's no great one to make all hard work shine.

I could give a try for building from sources (even if I don't dev on win too ^^ and would have to gather a proper dev environment). I'll try if I have enough time but that's not sure.

> I followed readme.md, installed latest python 2.7, and put tuttle 0.8.1 win dist in "C:\Program Files\Common Files\OFX\Plugins"
>
>
> Why this readme?

cause that's the only one delivered in win dist :)
I've also read doc on site and users/issue forums.

> Some other users had issues on Vegas. Check this thread could be a good way to start.

yes I've already read this thread before posting, but the conclusion is there's still no fix/workaround with current win dist (or I missed something).

I guess the guy had exactly the same problem than me. He gave a clue about contacting VisionColor that used your source code to build their impl. Did you try to know how they got their plugin working inside Vegas ?
Maybe they did only minor fix to your plugin interface lib or they simply used a later build as you suggest. I can't know right now without testing.

>
> Ok. Most of the time, the tuttle plugins are tested with the command line (sam), and with Nuke. But we try to fix issues like yours on the other hosts too.
>  

I anderstand. Thanks for your help anycase.

> I don't understand the problem here. You just need to use the sam.bat (which calls the sam.py).Can you just give us your path where you put tuttle?

The problem is as soon as there is a space character in the sam.bat directory path (TUTTLE_HOME or TUTTLE_ROOT env or local var, I don't remember) then executing the bat from the windows commandline fails cause win commandline removes the quotes by some magic or python fails to parse it correctly.

ex :
if you put the tuttle dist directoy naively (like I did) in

"C:\Program Files\Common Files\OFX\Plugins"

the sam cmd gets error saying "C:\Program" is not a file.

I've tryed to play with quotes, double quotes, \", \', in the sam.bat file but couldn't find a trick :)

note : no problem as soon there's no space char in tuttle home path.

I put it there cause I wanted ofx plugins detected (that's the default directory for plugins for win hosts) and not split/spread tuttle files across multiple storage disks (and eventually break some tuttle local depends, keep things organized if I want to remove it etc.)

 
>
> Indeed avreader should support this common format. Can you give use an example (a short movie)?
> Maybe the problem is solved within the last version (v0.12.2), and it could be a good reason to deploy a new tuttle version for Windows.
>  

I'll try to give you a few short 4k samples mp4 and mov from my gopro h4 and Panasonic gh4.
Could it be linked to resolution ? Maybe video/channel orders (I think I've seen some issues like that somewhere) ?

> I'm curious : what GUI around ffmpeg do you use for this kind of cases?

I use AnotherGUI, that's only a GUI that lets you fill a list of files and launch an ffmpeg preset on them. It does nothing ffmpeg can't do. That's just for kindof batch for trans/encoding without using commandline.

> In theory, all ffmpeg can do, avreader can do as well (for unwraping/decoding). And as far as I know, ffmpeg does not support DnxHR yet (see this ticket).
> I heard that Davinci Resolve can export DnxHR if you use some Avid codecs packs (check this one). But for now, I don't know any open source library which can export to DnxHR...

Yes that's my bad, I talked too quickly, indeed ffmeg can't export DnxHR right now (but can DnxHD and ProRes).

Resolve can indeed, I had already installed the Avid codecs for QuickTime.
Vegas can use them also as it has a quicktime export module too.

Note Avid write on their site they can share source code on demand with non-commercial softwares that want to build their own encoding module also.

Anycase thank you very much for your help. I'll try to recheck my tests & come back asap to share sample material.

Have a nice day,
Best Regards,

Sebastien