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
richardgatarski  
#1 Posted : Friday, March 29, 2019 5:17:13 AM(UTC)
richardgatarski

Rank: Advanced Member

Groups: Registered
Joined: 2/18/2014(UTC)
Posts: 1,369
Location: Stockholm

Thanks: 110 times
Was thanked: 213 time(s) in 177 post(s)
Note, these are preliminary findings posted as a cautious warning to other laptop users who put their capture cards in Thunderbolt expansion boxes.
I advice you to check things if you have the same or similar setups.

Yesterday we ran into problems as the camera inputs froze soon after going live. My crew rebooted and started again, but the inputs froze after about 30 minutes. vMix kept streaming so we got audio and could repair the production afterwards.

After spending a day looking for a cause I am convinced it is related to recent Window updates affecting Thunderbolt. Perhaps only related to Asus GL502VM-FY211T. So far a sister machine with 6:th gen i7 seems to work fine (can't remember the model number). I have 6 similar PCs, but only checked with 4 so far.

These laptops have the "Thunderbolt controller - 15BF" listed in the device manager. Control panel Programs and features include "Thunderbolt software 16.2.52.250". We use both Firmtek TB2 expansion boxes with Apple's TB2-TB3 adapter and a Sonnet TB3.

Up until I noticed the problem Windows automatically recognized the Thunderbolt device and made the capture card devices available when the Thunderbolt cable was connected to the PC. Now the laptops with issues has to be connected, dis-, and then re-connected before the Thunderbolt device was recognized. But preliminary tests still result in freezing and/or problems to close vMix/Windows.

My current fix, that after some brief tests seems to work, is to:
NOTE perhaps not to recommend, but I need to get things working...
- disconnect the Thunderbolt cable
- uninstall the Thunderbolt software
- reboot
- install TBT_WIN10_64_17.4.77.400
- reboot

In my case with TB3 only I still have to Scan for hardware changes in the device manager. And with the TB3-TB2 adapter I have to twice dis- and reconnect the cable from the adapter.

Hopefully few other users are affected, and future Window updates will fix things up.

If you have any questions, comments, or similar experiences I am here.
Kelvin  
#2 Posted : Friday, March 29, 2019 6:07:27 AM(UTC)
Kelvin

Rank: Advanced Member

Groups: Registered
Joined: 2/9/2013(UTC)
Posts: 226
Location: Katy, Texas

Was thanked: 35 time(s) in 35 post(s)
Recently, I have been experiencing similar bizarre behavior from my Thunderbolt laptops. I will try to post details of the TB driver and software versions I am using later tonight.
IrvinCee  
#3 Posted : Saturday, March 30, 2019 2:32:08 AM(UTC)
IrvinCee

Rank: Newbie

Groups: Registered
Joined: 4/1/2017(UTC)
Posts: 9
Location: Leuven-Belgium

Thanks: 2 times
Not vMix related but I'm running the Windows 10 preview (Work OS) and had several Thunberbolt issues lately with My HP Elitebook 850 G5.
Not recognising my USB devices connected to my Thunderbolt Docking. A full shutdown and removing power from the docking helps.

Besides that I have in my Music OS (same laptop) issues with same model Thunderbolt Docking but at home.
Sometimes my audio (ASIO USB interface connected to Thunderbolt docking) freezes for 2 seconds and then continues like nothing happened.

Think I have this for about 2 weeks now.
So I do agree something is going on with Thunderbolt an Win 10 (Pro in my case)
hellokitty  
#4 Posted : Monday, April 1, 2019 4:44:02 AM(UTC)
hellokitty

Rank: Advanced Member

Groups: Registered
Joined: 8/29/2015(UTC)
Posts: 97
Location: Seattle Wa

Thanks: 14 times
Was thanked: 12 time(s) in 12 post(s)
i have been useing a http://www.sonnettech.co...t/echoexpressseltb3.html for over a year, with a Kona 4 but im useing this in a desktop with a gigabyte card. Maybe try the startech adapter? im useing software 17.2.71.250 nvm firmware 21.00 i have no problems. you can try various versions of the intel software, it dont hurt. see if there is a bios update also for your laptop, switch to windows pro also, they sometimes cut things out of Home, because home dont need thunderbolt for most people. well hope this helps.
dedlinemedia  
#5 Posted : Monday, April 1, 2019 11:28:48 PM(UTC)
dedlinemedia

Rank: Newbie

Groups: Registered
Joined: 11/1/2018(UTC)
Posts: 8
United States
Location: NY

Thanks: 1 times
Richard, thanks for starting this topic. I just purchased a Magewell Pro capture Quad SDI to use in an Akitio Node Lite and having a similar issue. Both Vmix and Capture Express are not seeing or detecting any of the SDI inputs.
I'm using an Asus ROG GL502VMK and am on Win 10 Home Version 10.0.17134 Build 17134.

Interesting thing... last week, I was trying a BMD Decklink Duo 2 and it was working fine in the same enclosure. I just returned it because it was having trouble recognizing a couple of my Marshall cameras at 1080p60.

Now I also notice I see the 4 Quad SDI ports in device manager, but no aikito listed anywhere. Though I believe I saw it listed last week. Perhaps I'll try reinstalling the akitio driver before the t3 software you describe.

Regards,
Henry

EDIT: Hey just found a clue. Win10 added some kind of Thunderbolt protection now, could this be it?
https://docs.microsoft.c...otection-for-thunderbolt
richardgatarski  
#6 Posted : Tuesday, April 2, 2019 2:22:03 AM(UTC)
richardgatarski

Rank: Advanced Member

Groups: Registered
Joined: 2/18/2014(UTC)
Posts: 1,369
Location: Stockholm

Thanks: 110 times
Was thanked: 213 time(s) in 177 post(s)
I can't recall that I've seen a driver for "Akitio" listed. Only shows up if/when the Thunderbolt software recognizes a new TB device and asks if it should be connected. If you check "Always" at that time, it will not ask for it again - you will not see it.

I too found the DMA Kernel thing when I last week searched for ideas. But I don't think it is directly related. First, it's been there since 1803 (version, not year LoL). Second, none of my PCs with the TB issue has DMA Kernel protection On.

I might add one thing to my previous report. For my setups with TB3 only (ie no TB3-TB2 adapter) the device is recognized at bootup if the cable is inserted before booting. (Inserting it after bootup requires un- and re-plugging as I wrote earlier).
dedlinemedia  
#7 Posted : Tuesday, April 2, 2019 2:50:20 AM(UTC)
dedlinemedia

Rank: Newbie

Groups: Registered
Joined: 11/1/2018(UTC)
Posts: 8
United States
Location: NY

Thanks: 1 times
I did read somewhere that there is a BIOS setting that enables or disables T3 ports, sorry can't recall where.
I did fix my own problem. My mistake, in my rush I dl'ed the magewell drivers for Win7,8 as it was top of the list. I uninstalled those, and installed the Win10 versions and my drivers were recognized and authorized just fine. Card working great now.
Good luck. I'll be monitoring my thread in case I see your issue crop up.

Regards,
Henry
Users browsing this topic
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.