logo

Live Production Software Forums


Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
Psing  
#1 Posted : Thursday, August 18, 2016 10:49:27 AM(UTC)
Psing

Rank: Member

Groups: Registered
Joined: 11/27/2014(UTC)
Posts: 16
Man
Location: Portugal

Hi Martin!

I'm using vmix 17 last version in windows 10 and each time I try to add a Title/XAML input I get this error: "Timed out creating WPF thread"
The only Title/XAML that dont generate this error are the "Ticker" and the "Text". All other titles are sending this error.

I've tried reinstalling vmix, rolling back to previous versions and nothing.

Always the same error.

Do you know what's happening?

Many thanks.
sinc747  
#2 Posted : Thursday, August 18, 2016 10:55:41 AM(UTC)
sinc747

Rank: Advanced Member

Groups: Registered
Joined: 8/2/2013(UTC)
Posts: 1,072
Man
United States
Location: Fairhope, Alabama USA

Thanks: 553 times
Was thanked: 200 time(s) in 166 post(s)
Just guessing...

check video driver for latest
check window 10 for update
restart pc

always do the simple stuff first

- Tom
Psing  
#3 Posted : Thursday, August 18, 2016 11:02:42 AM(UTC)
Psing

Rank: Member

Groups: Registered
Joined: 11/27/2014(UTC)
Posts: 16
Man
Location: Portugal

Hi there!

I've done it already. Didn't solved.
Always the same error.

Thanks.
Psing  
#4 Posted : Thursday, August 18, 2016 7:59:34 PM(UTC)
Psing

Rank: Member

Groups: Registered
Joined: 11/27/2014(UTC)
Posts: 16
Man
Location: Portugal

Here is the error log:

========================================
17.0.0.107 - AddNewInput - 18/08/2016 00:00:39
========================================
System.Exception: Timed out creating WPF thread
em kx.zd(String a, String a)
em kx..ctor(Guid a, String a, String a)
em vMix.frmInput.b(Object a, EventArgs a)
Psing  
#5 Posted : Thursday, August 18, 2016 9:58:05 PM(UTC)
Psing

Rank: Member

Groups: Registered
Joined: 11/27/2014(UTC)
Posts: 16
Man
Location: Portugal

Hi there!

After many hours web searching for a possible origin for the error I found the solution.
It just solved my problem.
Problem was in fonts corrupted in Windows registry. (I dont know why!!) Maybe caused by some recent Windows update.

Solution:
I've made a backup from all fonts files, deleted the fonts registry with regedit (scary!!) and then installed all fonts again.

It solved my problem.

Thanks.
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.