14-Feb-2018, 08:42
(This post was last modified: 14-Feb-2018, 09:48 by ovo.
Edit Reason: Bit more clarity
)
agentsmith -
Yes the Beta code solved my 'lost' channel and the config remedied a 'loop' that I had when selecting the active slave input ( the slave display would briefly flash as "S1 input" then show "Opt1" then the display would darken and the slave go into standby. -Nothing I have tried can get a squeek out of an active chaining slave input.
What surprises me is that, if a failure to allow slave inputs to be activated for chaining is a software issue, then why does it not appear to affect every user of dual mono?
Yes the Beta code solved my 'lost' channel and the config remedied a 'loop' that I had when selecting the active slave input ( the slave display would briefly flash as "S1 input" then show "Opt1" then the display would darken and the slave go into standby. -Nothing I have tried can get a squeek out of an active chaining slave input.
What surprises me is that, if a failure to allow slave inputs to be activated for chaining is a software issue, then why does it not appear to affect every user of dual mono?
