No Timecode output from Protools I/O

[Bill Denton]

Originally Posted by CDIBarnes

We figured this out. Remember, we are generating TC, not receiving. So Command J does not apply.
>
>In short, our installation, which requires long sync cables, are the
>issue. Apparently, the new cards do not send as beefy of a signal as
>the old systems. It is not an issue of software or old vs. new sync io's.
>Here's how we got to the bottom of this...
>
>This morning, Scott discovered that, for reasons no one can recall, the
>studio D sync cable ran through an ethernet-based extender while
>studios F and C did not. Yesterday, F and C didn't generate timecode,
>although they 'saw' the sync i/o, whereas studio D didn't even see the sync i/o.
>This morning, Scott cycled power on this extender, and voila' - Studio
>D sees the sync i/o, generates timecode, etc just fine. (our session
>was saved. Thanks Scott!)
>
>Next, we used this boosted cable set up from the studio D rig on the
>studio F hardware, and it all works perfectly as well. So we now need
>to buy two new extenders.
>
>The item to add to the knowledge base is something like: Long sync i/o
>cable runs which used to work on earlier systems may not work on the
>new ASX card systems without running though a signal booster.

Maybe that dude who comes on pimping the 800 mile long MIDI cables has a solution...