vMix Forums
»
General
»
General Discussion
»
loss of signal causing issues
Rank: Advanced Member
Groups: Registered
Joined: 12/3/2013(UTC)
Posts: 117
Location: Arizona
Thanks: 8 times
Was thanked: 6 time(s) in 6 post(s)
|
We've been using vmix systems for 4 years now and have never run into this problem.
While on a production last weekend we had major issues with signal loss from our teradek bolt. When this would happen vmix would try to close the source window but if signal came back it would try to re add the source as if nothing were wrong. The source would begin to flash. This caused our entire machine to become unresponsive on more than a few occasions. Has anyone else run into this problem? it also happened with a wired sdi signal as well.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 12/3/2013(UTC)
Posts: 117
Location: Arizona
Thanks: 8 times
Was thanked: 6 time(s) in 6 post(s)
|
I'll retest on Monday in my office and try to duplicate the problem and post video.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 12/3/2013(UTC)
Posts: 117
Location: Arizona
Thanks: 8 times
Was thanked: 6 time(s) in 6 post(s)
|
Well here is a video of part of the problem. I need to hook up all of the cameras to really try to recreate the issue as it happened in production but this is what happened right before the program became unresponsive. In the past I don't recall the input window disappearing and reappearing as such.
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 1/13/2010(UTC) Posts: 5,211  Location: Gold Coast, Australia Was thanked: 4301 time(s) in 1523 post(s)
|
Hi,
What is happening is the Decklink card is constantly flipping between two different video formats.
vMix needs to reset the input each time the format changes, causing it to constantly flicker.
I have seen sources do this that have a bad mini-sdi adapter cable, so try swapping out the cable
to see if that solves the problem.
You should also be able to see the signal changes from the Blackmagic control panel to see
if the formats it is detecting indicate a problem at the source.
Regards,
Martin
vMix
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 1/13/2010(UTC) Posts: 5,211 Location: Gold Coast, Australia Was thanked: 4301 time(s) in 1523 post(s)
|
The format changes should also be listed in the log files in Documents\vMixStorage\Logs
with the heading AVInput.FormatChanged
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 12/3/2013(UTC)
Posts: 117
Location: Arizona
Thanks: 8 times
Was thanked: 6 time(s) in 6 post(s)
|
Sounds plausible! However, this happened on multiple inputs (cables).
Any idea why that would crash the program?
In the logs it looks like the input was switching from progressive to interlaced. Not sure why that would be.
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 1/13/2010(UTC) Posts: 5,211 Location: Gold Coast, Australia Was thanked: 4301 time(s) in 1523 post(s)
|
For crash details, check the Windows Event Log, it could be that the decklink driver is crashing with rapid signal changes.
Do you have the exact formats it is detecting between?
A bad SDI cable can cause the signal to be detected incorrectly, or the Bolt might be sending a bad signal as well (try a Bolt firmware update if possible as well).
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 12/3/2013(UTC)
Posts: 117
Location: Arizona
Thanks: 8 times
Was thanked: 6 time(s) in 6 post(s)
|
17.0.0.112 - AVInput.FormatChanged - 11/27/2016 4:33:57 PM
========================================
{Width=1920, Height=1080},29.97,Progressive
========================================
17.0.0.112 - AVInput.FormatChanged - 11/27/2016 5:00:57 PM
========================================
{Width=1920, Height=1080},29.97,Progressive
========================================
17.0.0.112 - AVOutput.Sync - 11/27/2016 5:39:07 PM
========================================
-100064
========================================
17.0.0.112 - AVInput.FormatChanged - 11/27/2016 5:40:35 PM
========================================
{Width=1920, Height=1080},29.97,Progressive
========================================
17.0.0.112 - AVInput.FormatChanged - 11/27/2016 5:40:38 PM
========================================
{Width=1920, Height=1080},29.97,Interlaced
========================================
17.0.0.112 - AVInput.FormatChanged - 11/27/2016 7:01:06 PM
========================================
{Width=1920, Height=1080},29.97,Progressive
========================================
17.0.0.112 - AVInput.FormatChanged - 11/27/2016 7:14:06 PM
========================================
{Width=1920, Height=1080},29.97,Interlaced
There may have been a bad connection somewhere in the line But the fact that it happened on the Teradek and a hardwired line leads me to believe the cause of the trouble is elsewhere.
Here is the event viewer info-
-.NET Runtime version 2.0.50727.8009 - This application is using the HMAC-SHA-384 or HMAC-SHA-512 keyed hash algorithm. The implementation of these algorithms were updated in service pack 1 of .NET Framework 2.0 and by default do not produce results consistent with the unserviced versions of the classes. For more information about the changes to the algorithms and how to disable this warning message please see the release notes for service pack 1.
-Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0
Problem signature:
P1: vMix64.exe
P2: 17.0.0.112
P3: 57ff3f7a
P4: 448f
P5: 67246336
P6:
P7:
P8:
P9:
P10:
Attached files:
D:\\capture - 27 November 2016 - 07-50-05 PM - 00001.mp4
C:\Users\George\AppData\Local\Temp\WER9674.tmp.version.xml
C:\Users\George\AppData\Local\Temp\WER9675.tmp.xml
C:\Users\George\AppData\Local\Temp\WER9965.tmp.WERInternalMetadata.xml
C:\Users\George\AppData\Local\Microsoft\Windows\WER\ReportQueue\Critical_vMix64.exe_98e5ed377574a85656beb5a8549c57777759bf3d_b98167f1_cab_19279962\minidump.mdmp
WERGenerationLog.txt
These files may be available here:
C:\Users\George\AppData\Local\Microsoft\Windows\WER\ReportQueue\Critical_vMix64.exe_98e5ed377574a85656beb5a8549c57777759bf3d_b98167f1_cab_19279962
Analysis symbol:
Rechecking for solution: 0
Report Id: da7f9fc8-b50d-11e6-830d-54271efcb096
Report Status: 4
Hashed bucket:
-The program vMix64.exe version 17.0.0.112 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 1804
Start Time: 01d248b08c5c18f7
Termination Time: 4294967295
Application Path: C:\Program Files (x86)\vMix\vMix64.exe
Report Id: da7f9fc8-b50d-11e6-830d-54271efcb096
Faulting package full name:
Faulting package-relative application ID:
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 1/13/2010(UTC) Posts: 5,211 Location: Gold Coast, Australia Was thanked: 4301 time(s) in 1523 post(s)
|
If it happened on a hardwired line, then the mini SDI cable sounds like the best thing to check.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 12/3/2013(UTC)
Posts: 117
Location: Arizona
Thanks: 8 times
Was thanked: 6 time(s) in 6 post(s)
|
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 5/24/2015(UTC)
Posts: 370
Location: Netherlands
Thanks: 16 times
Was thanked: 81 time(s) in 72 post(s)
|
I would for sure go for a patch panel. The mini din's are quite fragile. Imagine when someone trips over a cable, it will snap the connector right off.
Besides that, I think bad connections are coming from using it without a patch panel. When you buy these cables new, connections are rock solid. So better connect them once without stressing the connectors.
|
|
|
|
|
|
vMix Forums
»
General
»
General Discussion
»
loss of signal causing issues
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.
Important Information:
The vMix Forums uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close
