Vision SDI - Internal Loop/Input: Difference between revisions

From MXWendler Wiki
Jump to navigation Jump to search
(Created page with "This applies to all different OS versions and MXWendler 6.0 and above '''Problem''' You have a Datapath FX4 SDI, and a Datapath Vision SDI2 capture card and you try to use...")
 
No edit summary
 
Line 3: Line 3:
'''Problem'''
'''Problem'''


You have a Datapath FX4 SDI, and a Datapath Vision SDI2 capture card and you try to use the outputs of the FX4 as input for you Vision SDI2 capture card. In MXWendler when you setup the input to use as a preload, the video flickers, it timesout randomly and the signal is not stable.
You have a Datapath FX4 SDI, and a Datapath Vision SDI2 capture card and you try to use the outputs of the FX4 as input for your Vision SDI2 capture card. In MXWendler as well as Vision Fenster software, you realize the video flickers and has random timeouts.  


'''Solution'''
'''Solution'''


There is a conflict (at the moment) between FX4 SDI and Vision SDI2 capture cards. Unless this problem is not solved by FX4, try avoiding to use this internal loop, and use only external inputs with the Vision SDI2 capture cards.
Do no connect FX4 SDI outputs directly with Vision SDI2 capture card inputs. If you must make this connection necessarily, try to use a Scaler between the two devices.

Latest revision as of 18:11, 21 March 2023

This applies to all different OS versions and MXWendler 6.0 and above

Problem

You have a Datapath FX4 SDI, and a Datapath Vision SDI2 capture card and you try to use the outputs of the FX4 as input for your Vision SDI2 capture card. In MXWendler as well as Vision Fenster software, you realize the video flickers and has random timeouts.

Solution

Do no connect FX4 SDI outputs directly with Vision SDI2 capture card inputs. If you must make this connection necessarily, try to use a Scaler between the two devices.