Reply to thread

Message

<blockquote data-quote="dpmcrae" data-source="post: 823845" data-attributes="member: 113997">Currently I am traveling for Christmas so I have limited internet access and log files. It is not a sync issue with video and audio it is a TV server and TV3 blaster issue sync issue. Each capture card or TV card has a specific device ID number in the windows registry which corresponds to a specic device number in TV Server, e.g. a Colossus card could have a registry ID of 0007 and which might correspond to a TV Server ID of 13. In TV3 Blaster the TV Server device ID would to a specific Firewire blasting parameter that blast to a specific cable box that has a specific device ID in the Windows registry and a executable such as channel 1.exe or channel2.exe. In my case I have 3 Colossus cards each with their own device ID that points to a specific cable box in the blasting parameters. So in TV Server Colossus #13 should correspond to cable box #5 channel1.exe which has the highest priority over all the other cards. After the forced reboot instead of using Colossus card #13 the TV Server uses Colossus card #18 or Colossus card #12 but still blast the channel change to cable box #5.As far as the timeshifting issue it happened at on Dec 19 6:20 AM in the logs. I had to restart MP to correct the channel change timeshift issue. When I return home in a week or so I’ll recreate the issue and include the logs.</blockquote>

[QUOTE="dpmcrae, post: 823845, member: 113997"] Currently I am traveling for Christmas so I have limited internet access and log files. It is not a sync issue with video and audio it is a TV server and TV3 blaster issue sync issue. Each capture card or TV card has a specific device ID number in the windows registry which corresponds to a specic device number in TV Server, e.g. a Colossus card could have a registry ID of 0007 and which might correspond to a TV Server ID of 13. In TV3 Blaster the TV Server device ID would to a specific Firewire blasting parameter that blast to a specific cable box that has a specific device ID in the Windows registry and a executable such as channel 1.exe or channel2.exe. In my case I have 3 Colossus cards each with their own device ID that points to a specific cable box in the blasting parameters. So in TV Server Colossus #13 should correspond to cable box #5 channel1.exe which has the highest priority over all the other cards. After the forced reboot instead of using Colossus card #13 the TV Server uses Colossus card #18 or Colossus card #12 but still blast the channel change to cable box #5. As far as the timeshifting issue it happened at on Dec 19 6:20 AM in the logs. I had to restart MP to correct the channel change timeshift issue. When I return home in a week or so I’ll recreate the issue and include the logs. [/QUOTE]

Verification