Looking for Vegas Pro + Ignite Pro users to help track a bug

TTTT wrote on 6/3/2020, 9:17 AM

Hello,

I’ve been using Vegas Pro + Ignite Pro * plug-ins (previously known as HitFilm plug-ins) for years.

And since a year or two, I have this issue. I have a very long-lasting ticket with FxHome’s support.

I also had this topic: https://www.vegascreativesoftware.info/us/forum/confused-about-hitfilm-plug-ins-and-where-are-some-of-my-plug-in--114662/

(I also participated in this topic: https://www.vegascreativesoftware.info/us/forum/vegas-pro-edit-16-won-t-open--112623/ And had a temporary call for users/testers with this topic: https://www.vegascreativesoftware.info/us/forum/looking-for-owners-of-previous-vegas-pro-suite-or-vegas-pro-ignite--117074/ )

After nearly a year of hopes and delusions, I found a workaround to the problem, hoping that FxHome would fix it in plug-in updates.

I wrote it in details in this topic: https://www.vegascreativesoftware.info/us/forum/looking-for-owners-of-previous-vegas-pro-suite-or-vegas-pro-ignite--117074/

Here is a copy of it:

Ok, I think I have found the source of the problem and a workaround. I must say it looks so surrealistic, well unexpected to me that I'm still a bit stunned.

As mentionned, I install my softwares including OS in English/UK. But also, I live in Belgium.

After many tests on 2015-computer, I can now make the bug appear, disappear and reappear at will on 2019-computer, without requiring Windows reinstalled.

Here were my language and region settings:

Country or region: Belgium

Regional format: "Recommended - English (Belgium)"

Language (selected) : English (United Kingdom)

Language also installed: English (Belgium)

I changed Regional format to English (United Kingdom). Deleted Vegas cache. Restarted Vegas and everything worked fine.

(On another computer, I made this the other way around, adding the French language pack to a US English Win 10, and setting a matching “Regional format” and it crashed too.)

So it looks like if you are not using a system language that is not native to the country setting, the plug-ins will crash.

And after some times, I noticed that I need to keep my system with undesired regional settings in order to keep have Ignite Pro plug-ins working. And this may have impact on other softwares (typically those using regional date/numbers formatting).

I sent this info to FXhome's support, I hope they will be able to fix the problem in the plug-ins or identify if it's a Vegas, or other, problem.

Update: FxHome said they are unable to reproduce the bug.

As I had no news, I contacted FxHome again … there seemed to something going on with their ticketing system and they only replied again like 1 or 2 month later, in January, closing my ticket at the same time.

They said that they could not reproduce the issues.

Since January I’ve been very very busy and couldn’t do much video editing and coulnd’t really focus on writing this post, but I’m still hoping for a real solution to this issue.

That’s I would ask again if some Vegas Pro + Ignite Pro* users could this testing:

Create an empty project so that it is the project that will appear when you open Vegas next (if you open an existing project, this bug will NOT damage it unless you save it, but using a new dummy project feels even safer).
Change your computer regional setting to a non-native language. (something like Belgium and English (UK), or USA with French as language)

Example of a precise settings which should trigger the bug:
(Optional?) Delete/move Vegas Pro cache.
Launch Vegas Pro.
Do you get the bugs as described in https://www.vegascreativesoftware.info/us/forum/confused-about-hitfilm-plug-ins-and-where-are-some-of-my-plug-in--114662/

Can you tell us your setting, OS, softwares versions, any useful info ?

Thank you for your help

(* As this has been confusing to some in the past, when I’m talking about Ignite Pro plug-ins, I’m not talking about the few demo plug-ins that you may receive with some standard of Vegas Pro, I’m talking about the fully licensed collection of Ignite Pro plug-ins which you could receive with some "Suite" edition of Vegas Pro or buy desperately.)

Comments

TTTT wrote on 6/16/2020, 8:08 AM

Hello, no one can help ?

Reyfox wrote on 6/16/2020, 8:20 AM

I live in Poland, but speak English, so my computer is in US English.

Computer specs listed below, and I have no problems with Ignite Pro 4.1 using AMD graphics card. I can't speak on Nvidia.

Dexcon wrote on 6/16/2020, 8:24 AM

You may not have got any responses because the set of circumstances that you have described are so obscure that they don't seem to have any real world relevance.

1. Create an empty project so that it is the project that will appear when you open Vegas next (if you open an existing project, this bug will NOT damage it unless you save it, but using a new dummy project feels even safer).

2. Change your computer regional setting to a non-native language. (something like Belgium and English (UK), or USA with French as language)

3. (Optional?) Delete/move Vegas Pro cache.

It would be great if you could advise why you would want to take this approach in the first place.

TTTT wrote on 6/16/2020, 8:28 AM

I live in Poland, but speak English, so my computer is in US English.

Computer specs listed below, and I have no problems with Ignite Pro 4.1 using AMD graphics card. I can't speak on Nvidia.

Thank you maybe it's specific to Belgium and/or UK English then ... en some other configurations...

I tried with an AMD GPU, got the same problem so it's probably no Nvidia

TTTT wrote on 6/16/2020, 8:34 AM

You may not have got any responses because the set of circumstances that you have described are so obscure that they don't seem to have any real world relevance.

1. Create an empty project so that it is the project that will appear when you open Vegas next (if you open an existing project, this bug will NOT damage it unless you save it, but using a new dummy project feels even safer).

2. Change your computer regional setting to a non-native language. (something like Belgium and English (UK), or USA with French as language)

3. (Optional?) Delete/move Vegas Pro cache.

It would be great if you could advise why you would want to take this approach in the first place.

The answer is somewhere in the year-long thread that is linked.
- I advise creating a new project because if you use and existing project AND go through the bug pop-ups AND then save your project, some track/event effects may disappear.
- Deleting cache is recommended to test that kind of plug-in issues. Actually I think that parts of the problems happens when generating plug-in cache, so if cache is not regenerated, they may go unseen. I suggest some people may prefer to move their cache to a dummy folder rather than delete it.

As I already stated, these are my current best-conclusions of many tests spread over an entire year, some involving complete resets of various computers (including computers/hardware that didn't belong to me), and I cannot go into complete test cycles each time I write a line on the forum.

Dexcon wrote on 6/16/2020, 8:40 AM

@TTTT ... I think that you've missed the point. This seems to be an academic problem rather than a real world problem. Other than a quirky issue, why is this a real world ongoing issue for you? How does this affect your real world editing processes? Why???????

TTTT wrote on 6/16/2020, 8:56 AM

It affects real world because I have to keep my whole computer in a "wrong" system state if I want to edit video, and it seems to be caused by a fault in the editing (plug-ins) software (or even if it's an OS bug, it would solve real issues if traced and corrected).

lan-mLMC wrote on 6/16/2020, 8:57 AM

Ignite Pro 4.1 everything goes well. "Ignite Color Temperature" and "Ignite Cine Style" show normally.

2 suggestions for you to try:

1. When you fresh install Ignite Pro, you should cut "IgniteCore.ofx.bundle" and "IgnitePro.ofx.bundle" from "C:\Program Files\Common Files\OFX\Plugins" to other directory before you launch Vegas.

After you succeed in launching Vegas a time, cut "IgniteCore.ofx.bundle" and "IgnitePro.ofx.bundle" back to "C:\Program Files\Common Files\OFX\Plugins";

2. Or you can directly cut "IgniteCore.ofx.bundle" and "IgnitePro.ofx.bundle" to "C:\Program Files\VEGAS\VEGAS Pro 17.0\OFX Video Plug-Ins".

Try it.

Dexcon wrote on 6/16/2020, 9:05 AM

I have to keep my whole computer in a "wrong" system state

You still haven't explained what the problem is. You have previously said that you have to change languages. Why? What is the "wrong" system state?

For heavens sake, tell us what you are actually doing while editing on the timeline that creates the problem.

Like Reyfox, I have no problem using Ignite Pro 4.1 in VP17 (any build).

TTTT wrote on 6/16/2020, 9:16 AM

@lan-mLMC

I've already tried launching Vegas without Ignite plug-ins and then with Ignite plug-in, problems always came back when re-including Ignite plug-ins (+ regional setting conditions as described in first) post.
About suggestion 2. I think I tried it, can't be sure.
(Won't be able to do concrete testings before Thursday, at best.)

TTTT wrote on 6/16/2020, 9:20 AM

I have to keep my whole computer in a "wrong" system state

You still haven't explained what the problem is. You have previously said that you have to change languages. Why? What is the "wrong" system state?

For heavens sake, tell us what you are actually doing while editing on the timeline that creates the problem.

Like Reyfox, I have no problem using Ignite Pro 4.1 in VP17 (any build).

Resulting problem is that I need to choose between:

- being able to edit video with Ignite plug-ins, but using wrong regional settings on my computer that will mess with with normal usage of other softwares such as Microsft Excel, Windows Calculator, and home-written pieces of code, and anything you might expect would rely, in a visible or non-visible way, on date formats, comma vs point decimals etc.
(These can go from usage comfort issues to calculation errors.)

- having my computer with correct setting but not being able to use any project with Ignite plug-ins.

- Also, one may expect that some users in my situation have just never found the workaround and just can't use Ignite plug-ins anymore... So, this may be an issue turn people silently away from Ignite plug-ins.

TTTT wrote on 6/21/2020, 11:13 AM

2. Or you can directly cut "IgniteCore.ofx.bundle" and "IgnitePro.ofx.bundle" to "C:\Program Files\VEGAS\VEGAS Pro 17.0\OFX Video Plug-Ins".

Just tested this one, leads to the same crashes and bug as usual.

TTTT wrote on 6/21/2020, 11:17 AM

Also here's a screenshot of on of the precise settings that causes bugs and crashes.

TTTT wrote on 6/21/2020, 11:28 AM

1. When you fresh install Ignite Pro, you should cut "IgniteCore.ofx.bundle" and "IgnitePro.ofx.bundle" from "C:\Program Files\Common Files\OFX\Plugins" to other directory before you launch Vegas.

After you succeed in launching Vegas a time, cut "IgniteCore.ofx.bundle" and "IgnitePro.ofx.bundle" back to "C:\Program Files\Common Files\OFX\Plugins";

Tested this (though I did many more precise tests in thepast like trying to trim it down to the precise plug-ins that causes the issues and see at what line the logs "break" and things like that, so I'm 99% sure that I have already done this precise test)
Bugs and crashes are back as soon as I move "IgniteCore.ofx.bundle" and "IgnitePro.ofx.bundle" back to "C:\Program Files\Common Files\OFX\Plugins"

Out of the many past tests, it doesn't seem to have to do with "installation time" but the bugs and crashes come back anytime when running the application with plug-ins and with some precise regional settings.

TTTT wrote on 6/21/2020, 11:37 AM

@lan-mLMC in additions to previous replies, I tried the combination of you two suggestions, not success.

TTTT wrote on 6/21/2020, 11:43 AM

Out of the many past tests, it doesn't seem to have to do with "installation time" but the bugs and crashes come back anytime when running the application with plug-ins and with some precise regional settings.

Also, if I do not uninstall/re-install/move any file , simply switching back from "English (Belgium)" to "English (United Kingdom)" make Vegas work again including Ignite Pro plug-ins.
I think this show that the problems happen at any Vegas launch , not only at installation of first plug-in detection.