Sat May 22, 2021 5:30 pm
Thank you for responding!
Ah echolab Atem, very nice. Probably would be a good move but cost prohibitive:
For folks that might have an Overture2 MD here's a description of what I am seeing
and a few requests:
Its an Overture 2 MD. It has 16 inputs and 16 outputs.
I presume there is some way to assign an output to view program or preview, and I might guess you can route any input to any output too, but I cannot find a facility to do this on the buttons or in the configuration programs. It would be very bad if setting outputs is only supported with the Conductor
panel... I would have thought that setting the program and preview output would have been addressed in the very first setup section. Was shocked that it was not.
I expected that the function would be in the I/O app but the screen only shows the 16 inputs.
Perhaps the app thinks there are no outputs in the unit? There are 4 cards full...
I thought maybe you have to flip to an "output" view but see no way to do that.
Would make sense since the app is called Input/Output and not just Input. On the other hand
the screen I see does define the output FORMAT, but not the output assignments.
Thought maybe the outputs were below the inputs but there is no scroll bar to scroll down further to perhaps expose more UI. I expected that there would be an OUTPUT button on the panel right
by the INPUT setup button under the I/O function of the HOME Menu, but no. I'm stuck.
Again... its looking like the unit doesn't think I have outputs, and hence not presenting the output setup
features.
The manual does not discuss what version of windows was required to run the apps. XP and Vista were out over the timeframe of the MD. The manual points out that microsoft.net framework is required, but not which version. I assume that in 2008 most users employed Windows XP,
I would like it to be internally sync'd as we are not timing anything else and expect to use frame
buffers on every input.
But the manual is confusing because it emphatically says that an SDI SYNC must be applied
for the switcher to work. Really? Or is that only because perhaps the factory default is SDI sync
(just a guess) and that until you get the apps talking to the unit to switch it to internal you are dead
without SDI sync??? (Again manual seems very prelim)
I have applied analog sync and I have seen in the input app that the current sync selection is in
fact analog so I presume the unit should be happy with that and work normally.
In the meantime, I have also applied SDI sync and the lock lights light up but I think
it is being ignored.
I tried to change the input sync selection in the app, but as I said, when I write back the unit
the app crashes. As the only machine I had hand was Windows 7, the apps are set to run in XP SP3 mode which could be the problem there. Or it is a .net issue. But the apps are not complaining for
lack of .net. I will put a real XP system in there next opportunity, and have all the historically relevant
.net versions handy.
I'm working from memory here and may not have this part exactly right,
but the System LEDs have not been what I expected.
Without analog sync applied I have seen D sometimes lit, and A not lit.
With sync applied I have seen ABC lit but not D. B is lit- even when there is no CF card
activity- perhaps it really indicates that it is mounted and ready?
If you would be so kind, I'd love to know:
- If your System LEDs perform as documented- is A ever unlit?
Is D ever unlit when you would expect it to be lit?
- Are you using internal sync but does the unit still require you to apply an SDI sync
just to function? (even though it may not be timed to it)
- Are you using the apps, and if so what exact OS, service pack, and .net are you using?
- How do you set up the definition of each outputs? Do you have outputs in the I/O app?
Do you have an output setup button under the I/O menu button on the panel?
Thanks very much in advance for any clarity you can contribute.
DC
Last edited by
dmemphis on Sat May 22, 2021 6:43 pm, edited 1 time in total.
