servpro Posted October 5, 2014 Share Posted October 5, 2014 Not sure if anyone has this problem, but when I switch inputs using the Monoprice HDMI Matrix it blacks out my TV (drops signal) for a few seconds before reconnecting (normal from what I read here). The problem is it does this no matter what the input is. So if I am on TV and switch to TV manually it disconnects and reconnects to the same input. Anyway around this, maybe check the input first and if not the same switch input? Also, if I switch inputs on TV 1, TV 2 goes out to. Devices: Monoprice HDX-402E - PID 5312 Driver: https://drive.google.com/file/d/0Bza8R7pwok9VaVR4cnVLX0puMlE/view Driver Name: avswitch_MonoPrice_4x4HDMI Rev 3.0 _2.c4i (Using the 4x4 driver but should work the same as the 4x4 is almost identical to the 4x2 minus the two outputs) Running 1.8 Not sure if the driver I am using is outdated and there is a better one. Any advice or input would be much appreciated. Link to comment Share on other sites More sharing options...
lippavisual Posted October 6, 2014 Share Posted October 6, 2014 Normal HDMI behavior on low cost switches Link to comment Share on other sites More sharing options...
servpro Posted October 6, 2014 Author Share Posted October 6, 2014 Normal HDMI behavior on low cost switches Thanks for the reply, can the driver be programmed to check input first to avoid unnecessary signal drops? Link to comment Share on other sites More sharing options...
Matt Lowe Posted October 6, 2014 Share Posted October 6, 2014 with some time and programming this most likely could be done. nothing easy that i can think of off the top my head Link to comment Share on other sites More sharing options...
Cyknight Posted October 6, 2014 Share Posted October 6, 2014 If it can be done, it would be in the driver, not via system programming - to do so is no simple task. Link to comment Share on other sites More sharing options...
RyanE Posted October 6, 2014 Share Posted October 6, 2014 The drivers I've seen are IR "Driver Wizard" drivers, which are going to send the 'switch inputs' code every time, they don't (and can't) have logic in them to remember what input they're on, and not send the 'switch inputs' code again. The Monoprice switch also doesn't always switch, even when it gets the code, so it would likely be unwise to not send it again. RyanE Link to comment Share on other sites More sharing options...
Ramorous Posted October 7, 2014 Share Posted October 7, 2014 The drivers I've seen are IR "Driver Wizard" drivers, which are going to send the 'switch inputs' code every time, they don't (and can't) have logic in them to remember what input they're on, and not send the 'switch inputs' code again.The Monoprice switch also doesn't always switch, even when it gets the code, so it would likely be unwise to not send it again.RyanEIf you have Composer HE you can use variables to track inputs and such so you can resend the commands with a reset, etc...Sent from my Galaxy S5 using Tapatalk Link to comment Share on other sites More sharing options...
Cyknight Posted October 8, 2014 Share Posted October 8, 2014 This won't help a dime to prevent sending repeat codes - driver coding supercedes variable programming. The point being that as you CANNOT prevent the driver from resending the code (dymanically), there is no programming way to prevent it. Link to comment Share on other sites More sharing options...
RyanE Posted October 8, 2014 Share Posted October 8, 2014 In theory, you could create a DriverWorks driver that tracks current inputs, and doesn't resend the IR code in that instance, but it's likely more work than it's worth for the Monoprice switches. RyanE Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.