[Bug] VP15.0.384 not accepting HitfilmPro 8.1.7719 effect

AVsupport wrote on 7/19/2018, 3:05 AM

'Add Hitfilm Effect' via right-click a clip on the timeline, edit the clip in Hitfilm Pro (latest version). Exit or Save clip will prompt to replace the project file with the new version of HF8.1 You then can see & work absolutely fine with the roundtripped HF project file in Vegas, until you save

Once you save your VP project and reload, it first causes a fatal crash, at re-open you will get prompted to replace/find/ignore the Hitfilm files. None of the HF8 files can be imported. All greyed out in the project media list.

I think this only just happened..and it seems it's on the Magix' side..As I can easily re-open any file in HF and keep editing..This is a real big bummer as this is the only good 3D animation / tracking roundtrip plugin I know and currently use..; Also, pls don't confuse this with Ignite plugins [which seem to work fine]

Comments

Marco. wrote on 7/19/2018, 7:03 AM

I can repro an issue with loading VP15 (b. 384) projects which contain HitFilm Pro 2017 files (and just saw HitFilm Pro 9 is released).

AVsupport wrote on 7/19/2018, 4:35 PM

Are these HF2017 files also crashing VP at first load attempt? Are they also not readable / accessible ('unknown file format') once the project is loaded @Marco. ?

AVsupport wrote on 7/19/2018, 4:52 PM

just seen this on the https://fxhome.com/hitfilm-pro/whats-new/

Can someone pls confirm this is the only currently working fix to the broken situation?? This situation rings a bell, last time there was the same artificially imposed version-incompatibility block with VP14..this is so frustrating

AVsupport wrote on 7/19/2018, 5:12 PM

from the FVX forum:

https://fxhome.com/forum/discussion/comment/116004/#Comment_116004

@Emma just speculation here, but Vegas has used "named" internal calls for decades. When Vegas shifted from Sonic Foundry to Sony many Vegas scripts stopped working because the internal call was looking for "Sonic Foundry Vegas" but now needed to be "Sony Vegas." The same issue happened with the change from Sony to Magix.

Immediate guess is that at the Vegas end the integration library is looking for something called "Hitfilm 2017" and getting confused by the current drop in version/year numbers. Especially as, internally, Hitfilm's gone from v6 to v8 in a very short period of time.

This would be consistent with @Palacono's infamous "hack," with earlier versions which really was basically changing the name in a file to point to the correct Hitfilm application name.

AVsupport wrote on 7/20/2018, 6:28 AM

Upgrade to Hitfilm Pro 9, roundtrip works fine, no problems (so far..)

Marco. wrote on 7/20/2018, 7:24 AM

"Are these HF2017 files also crashing VP at first load attempt?"

It freezes Vegas Pro while trying to load.

"Are they also not readable / accessible ('unknown file format') once the project is loaded."

This part works fine. No problem to import/read the .hfp files once the Vegas Pro project is opened.

AVsupport wrote on 7/20/2018, 2:50 PM

FYI, HF8.1 will force you to upgrade the file format from what it got sent from VP15 which in turn makes it incompatible. I believe this has to do with a version check on Magix's behalf..

Marco. wrote on 7/21/2018, 6:12 AM

"HF8.1 will force you to upgrade the file format from what it got sent from VP15"

Same happens with HitFilm Pro 2017 (version 5.0).

But this HitFilm message doesn't make sense to me because the current HitFilm project definitely was not saved in a previous version of HitFilm.

AVsupport wrote on 7/21/2018, 5:28 PM

When I 'add Hitfilm effect' it's Vegas that creates he initial first instance of the HF file..I think this is where it starts gettin fishy?