logo

Live Production Software Forums


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

Notification

Icon
Error

3 Pages<123>
Options
Go to last post Go to first unread
admin  
#21 Posted : Tuesday, September 29, 2020 11:08:42 PM(UTC)
admin

Rank: Administration

Groups: Administrators
Joined: 1/13/2010(UTC)
Posts: 4,789
Man
Location: Gold Coast, Australia

Was thanked: 3411 time(s) in 1303 post(s)
Originally Posted by: ArgusHD Go to Quoted Post
This problem is happening to me repeatedly as well. We keep sending our reports to Vmix, but they don't seem to be able to solve the issue. Like everybody else on this thread, we have had the software crash without explanation multiple times. We do not have any other programs running. We have NDI coming from our Tricaster NC1. We have even simplified the network to where there's only the Tricaster into Vmix, and even with that simplified approach, vmix crashed on a show today.We make sure everything is updated to the latest software. There's really nothing we can do at this point and it's very frustrating.

We are really at our wit's end because there is no rhyme or reason when this will happen. sometimes it's 15 minutes into a show, sometimes never, sometimes at the end.


Sorry to hear you are still having trouble. When an issue like this has occurred in the past it has either been due to an NDI SDK bug or a faulty encoder.
In both cases we can either submit a bug report to have the encoder fixed or to NewTek to have the NDI SDK updated.

However in order to do this, we need to be able to replicate the issue.
I would advise as a test to run vMix and Studio Monitor at the same time with the same source
and see if you can trigger the issue repeatedly. (Perhaps by unplugging/plugging in sources on the NC1 for example)

There has unfortunately been a lot of misinformation online that these issues are somehow specific to vMix, which is not the case as we use the same NDI SDK as all other software, but
we can do our best to report any bugs we find to the appropriate vendor for you if this can be replicated on our systems.
umek  
#22 Posted : Monday, October 5, 2020 9:40:07 PM(UTC)
umek

Rank: Member

Groups: Registered
Joined: 4/8/2015(UTC)
Posts: 29
Location: Zagreb

Thanks: 3 times
Was thanked: 1 time(s) in 1 post(s)
Is it possible to make a bubble around NDI SDK so when it crashes it does not kill the main program (vMix)?
caspy  
#23 Posted : Monday, October 12, 2020 7:26:20 PM(UTC)
caspy

Rank: Member

Groups: Registered
Joined: 6/29/2020(UTC)
Posts: 14
Russian Federation
Location: Moscow

Was thanked: 1 time(s) in 1 post(s)
Hi!

Have made this test:
- two absolutely identically computers,
- two absolutely identically windows (made by cloning),
- 5 NDI sources (4 vMix'es, 1 NDI Scan Converter),
This 5 NDI sources was open in vMix on one machine, and in Studio Monitor's on another.
vMix crashed, StudioMonitors still running.


ps:
replacement of 'Processing.NDI.Lib.dll' to corresponding one from NDI Tools does not change things.


Originally Posted by: admin Go to Quoted Post

I would advise as a test to run vMix and Studio Monitor at the same time with the same source
and see if you can trigger the issue repeatedly. (Perhaps by unplugging/plugging in sources on the NC1 for example)



admin  
#24 Posted : Tuesday, October 13, 2020 2:39:38 AM(UTC)
admin

Rank: Administration

Groups: Administrators
Joined: 1/13/2010(UTC)
Posts: 4,789
Man
Location: Gold Coast, Australia

Was thanked: 3411 time(s) in 1303 post(s)
Remove some of the sources to see which is causing it.
Set Receive mode to Multi TCP in NDI Access Manager under advanced tab.
niemi  
#25 Posted : Thursday, October 22, 2020 11:25:04 PM(UTC)
niemi

Rank: Advanced Member

Groups: Registered
Joined: 2/16/2017(UTC)
Posts: 167
Location: Denmark

Thanks: 27 times
Was thanked: 17 time(s) in 14 post(s)
Not pleased to hear multiple users reports crashing issues with even the most simplest NDI setups. I was under the impression that it was mostly - if not only - BirdDog converters that caused these issues with vMix crashing caused by corrupt frames being sent from the converter to vMix.

Any working theories?

I know that a sandbox feature for NDI inputs will be rolled out in vMix 24, but it would certainly be great to find the root cause(es).
niemi  
#26 Posted : Monday, November 16, 2020 6:10:52 AM(UTC)
niemi

Rank: Advanced Member

Groups: Registered
Joined: 2/16/2017(UTC)
Posts: 167
Location: Denmark

Thanks: 27 times
Was thanked: 17 time(s) in 14 post(s)
Any updates on this?
admin  
#27 Posted : Monday, November 16, 2020 12:37:02 PM(UTC)
admin

Rank: Administration

Groups: Administrators
Joined: 1/13/2010(UTC)
Posts: 4,789
Man
Location: Gold Coast, Australia

Was thanked: 3411 time(s) in 1303 post(s)
In all the cases we have seen, the cause is likely one of the following:

1. Faulty encoder
2. Faulty system (we have seen faulty hardware and faulty drivers cause problems)
3. Out of date NDI software on sources where the bug was already fixed in latest releases. (specifically related to UDP)

For point 1, update the encoder firmware.
For point 3, making sure Receive mode in Access Manager is set to Auto solves this problem.

For point 2 this is harder, as anything on the system could be potentially faulty.

We have numerous systems running on NDI 24/7 with various types of sources and have not seen any issues
besides 1 and 3, which can both be permanently solved. This would appear to confirm that the faulty hardware is likely the cause in all other cases.

We are happy to be proven wrong if someone can point us to an example NDI source that crashes consistently on the latest version, but so far no one has been able to demonstrate that.

Regards,

Martin
vMix
thanks 2 users thanked admin for this useful post.
doggy on 11/16/2020(UTC), eduardocfs on 11/17/2020(UTC)
mazranz  
#28 Posted : Thursday, December 10, 2020 11:06:41 AM(UTC)
mazranz

Rank: Newbie

Groups: Registered
Joined: 12/10/2020(UTC)
Posts: 4
Malaysia
Location: Kuala Lumpur

I'm getting the same problem too.

Yesterday was working fine all day.

Today, can't even run for more than 5 minutes!

Same file, same sources.

HELP!

edit

Creating a new vmix file from scratch seems to fix my issue for now.
Nothing was changed in setting and scenes.

odd.
rjwerth  
#29 Posted : Tuesday, December 15, 2020 1:47:50 AM(UTC)
rjwerth

Rank: Newbie

Groups: Registered
Joined: 6/9/2020(UTC)
Posts: 9
United States
Location: Michigan

Originally Posted by: admin Go to Quoted Post
In all the cases we have seen, the cause is likely one of the following:

We have numerous systems running on NDI 24/7 with various types of sources and have not seen any issues
besides 1 and 3, which can both be permanently solved. This would appear to confirm that the faulty hardware is likely the cause in all other cases.

We are happy to be proven wrong if someone can point us to an example NDI source that crashes consistently on the latest version, but so far no one has been able to demonstrate that.

Regards,

Martin
vMix


Ok, I'm in. What do you want me to do the next time my BD Flex crashes Vmix? Last time it was in that state that Vmix would crash EVERY time it tried to receive from the Flex was just a week ago. I'm fairly certain it has to do with some sort of HDMI error not being properly handled by the Flex (which it should be, of course), but it should also be properly dealt with by the receiver as well.

To be fair, when Vmix crashes, Studio Monitor will as well.

Robert Wertheimer
niemi  
#30 Posted : Friday, December 18, 2020 10:12:46 PM(UTC)
niemi

Rank: Advanced Member

Groups: Registered
Joined: 2/16/2017(UTC)
Posts: 167
Location: Denmark

Thanks: 27 times
Was thanked: 17 time(s) in 14 post(s)
Quote:
What do you want me to do the next time my BD Flex crashes Vmix?

Update the BirdDog firmware. Does the BirdDog still crash vMix? If so contact reach out to support.
rjwerth  
#31 Posted : Sunday, December 20, 2020 10:21:00 AM(UTC)
rjwerth

Rank: Newbie

Groups: Registered
Joined: 6/9/2020(UTC)
Posts: 9
United States
Location: Michigan

I've had the latest firmware for the flex since day one.

Neither side seems to want to come up with a proper solution to this issue as I've been mentioning it to BD and vmix for several months now.

Had my typical phone call from my church again tonight complaining about the issue.

Robert
DWAM  
#32 Posted : Sunday, December 20, 2020 6:26:45 PM(UTC)
DWAM

Rank: Advanced Member

Groups: Registered
Joined: 3/20/2014(UTC)
Posts: 2,721
Man
France
Location: Bordeaux, France

Thanks: 243 times
Was thanked: 776 time(s) in 586 post(s)
Quote:
Neither side seems to want to come up with a proper solution

This is not a "2 sides only" situation.
As it's been explained, it can be YOUR hardware's fault. Did you try with another computer?
caspy  
#33 Posted : Sunday, December 20, 2020 7:21:01 PM(UTC)
caspy

Rank: Member

Groups: Registered
Joined: 6/29/2020(UTC)
Posts: 14
Russian Federation
Location: Moscow

Was thanked: 1 time(s) in 1 post(s)
Originally Posted by: DWAM Go to Quoted Post
Did you try with another computer?


I have tried a lot of various coumputers. A lot of network cards and switches. A lot of drivers and other versions. A lot of sources.
I was not able to mention any stable dependency.
Sometimes it seems(!!) to depend on source, sometime network. but any time i try to check single thing - not reproduced.

Seems like depend on Mars weather ;)
it can crash a 10 times a day, but next day rock solid (even without any change).
admin  
#34 Posted : Monday, December 21, 2020 1:15:52 PM(UTC)
admin

Rank: Administration

Groups: Administrators
Joined: 1/13/2010(UTC)
Posts: 4,789
Man
Location: Gold Coast, Australia

Was thanked: 3411 time(s) in 1303 post(s)
Originally Posted by: rjwerth Go to Quoted Post

Neither side seems to want to come up with a proper solution to this issue


As you mentioned it also happens in Studio Monitor, it can't be a vMix issue, so that tells you who needs to fix the problem!
That said, we have still been proactive and implemented an isolation mode for NDI sources in vMix 24.
You can download the beta here:

https://forums.vmix.com/...4-Early-Preview-Released

Then when adding the NDI input tick the FEIM checkbox in that window.

This won't solve the input stopping when the encoder sends bad data, but it will stop vMix from crashing so you can at least
remove the input and add it again without stopping the stream.
seomaii  
#35 Posted : Saturday, December 26, 2020 7:41:09 PM(UTC)
seomaii

Rank: Member

Groups: Registered
Joined: 1/30/2018(UTC)
Posts: 21
Location: Dublin

Thanks: 5 times
Was thanked: 1 time(s) in 1 post(s)
Hi All,

I've only saw the new posts here and not receiving notifs in my email when another member post/replied.

So, my issue was fix after a few weeks of struggle. Apparently, it had to do something with Windows update because when I updated my Win10 to the next available update, it fixed my issue but was still cautious when I was using it as I didn't know whether it will crash or not.

My only fix is not to jump to the next Windows update unless it's stable and consistent.

Hope this helps..
Halfbit  
#36 Posted : Wednesday, January 13, 2021 2:01:35 AM(UTC)
Halfbit

Rank: Newbie

Groups: Registered
Joined: 1/12/2021(UTC)
Posts: 3
United States
Location: New York

I just started experiencing these crashes myself. Windows event viewer is pointing towards the same ntdll.dll file, as well as a few others.

Can you share which version of Windows 10 you currently have installed where vMix is now running stable?
rjwerth  
#37 Posted : Friday, January 15, 2021 5:18:52 AM(UTC)
rjwerth

Rank: Newbie

Groups: Registered
Joined: 6/9/2020(UTC)
Posts: 9
United States
Location: Michigan

Originally Posted by: admin Go to Quoted Post
Originally Posted by: rjwerth Go to Quoted Post

Neither side seems to want to come up with a proper solution to this issue


As you mentioned it also happens in Studio Monitor, it can't be a vMix issue, so that tells you who needs to fix the problem!
That said, we have still been proactive and implemented an isolation mode for NDI sources in vMix 24.
You can download the beta here:

https://forums.vmix.com/...4-Early-Preview-Released

Then when adding the NDI input tick the FEIM checkbox in that window.

This won't solve the input stopping when the encoder sends bad data, but it will stop vMix from crashing so you can at least
remove the input and add it again without stopping the stream.


Guys, I agree that the problem isn't only a Vmix problem. The BD encoder should NEVER kick out a bad frame and yes, I'm talking to them about that. But problems like this should be anticipated and dealt with. Glad to see there is now input isolation. I'll have to try it out if I can't get this dealt with on the encoder side.
seomaii  
#38 Posted : Saturday, January 23, 2021 7:09:20 PM(UTC)
seomaii

Rank: Member

Groups: Registered
Joined: 1/30/2018(UTC)
Posts: 21
Location: Dublin

Thanks: 5 times
Was thanked: 1 time(s) in 1 post(s)
I am currently running Win10 20H2 version 19042.746

vMix is stable... I hadn't had a crash since the last time. I OC'd my PC to give it a boost just to help but I don't think it's to do with my PC but Win10 itself. I did a full reset before and only installed vMix and NDI but it was still crashing. So, I had to use another PC which had a previous version of Win10.
mecentur  
#39 Posted : Wednesday, February 24, 2021 2:40:41 PM(UTC)
mecentur

Rank: Newbie

Groups: Registered
Joined: 2/24/2021(UTC)
Posts: 1
United States
Location: ORLANDO

Hello guys,

I have a problem. I need you guys help, if it is possible.

I am trying to send via NDI the output from Propresenter 7 to vMix. The feed went but when I have tried to change the presentation slides, vMix kept crashing and restarting. I have tried to update vMix. The same reaction.
Any ideas?

Thanks in advance.
calonpintar  
#40 Posted : Friday, March 12, 2021 4:10:59 AM(UTC)
calonpintar

Rank: Newbie

Groups: Registered
Joined: 11/8/2020(UTC)
Posts: 1
Indonesia
Location: Jakarta

hello,

so I did setup with 12 laptops + 1 resolume arena + 1 millumin + 1 vmix.
- all laptop just outputting NDI via vMix desktop capture
- arena is receiving NDI from laptops and send to millumin
- millumin only receiving arena & laptops
- vmix only receiving laptops

arena, millumin, vmix all crashed randomly about 1 minute after

NDI setup are configured using NDI discovery server to prevent network flooding, NDI version 4.5

did same setup, but using NDI scan converter (now screen capture) instead of vMix desktop capture, everything is stable

vMix version 23.0.0.60, all windows on 20H2, 24 port gigabit network, bandwidth topped no more than 800mbps

now I'm suspecting vMix desktop capture, at least on this version, or someone can share different experience?

Users browsing this topic
3 Pages<123>
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.