• Torosay HD out of lip sync

    From MB@21:1/5 to All on Sun Jan 30 12:47:56 2022
    A friend contacted me last night to say that Torosay HD was out of lip sync.

    We had the same fault soon after DSO, the problem then seemed to be that
    it did not raise any alarms so of course with modern digital systems, if
    there is no alarm then it is hard to convince people there is a fault.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Carver@21:1/5 to All on Sun Jan 30 14:12:27 2022
    On 30/01/2022 12:47, MB wrote:
    A friend contacted me last night to say that Torosay HD was out of lip
    sync.

    Which channels ?

    During 5.1 Audio progs, or just 2.0 (I've noticed 5.1 can sometimes be
    quite a way out of sync)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to Mark Carver on Sun Jan 30 14:20:04 2022
    On 30/01/2022 14:12, Mark Carver wrote:
    Which channels ?

    All HD as far as I can tell.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Carver@21:1/5 to All on Sun Jan 30 15:30:20 2022
    On 30/01/2022 14:20, MB wrote:
    On 30/01/2022 14:12, Mark Carver wrote:
    Which channels ?

    All HD as far as I can tell.

    Well yes, everything except I think Shopping Quarter is in HD.

    Torosay is in the same coding group as Black Hill and Darvel, so if the
    problem is within the coding of the transport stream, they will be
    affected too

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to Mark Carver on Sun Jan 30 18:59:56 2022
    On 30/01/2022 15:30, Mark Carver wrote:
    Well yes, everything except I think Shopping Quarter is in HD.

    Torosay is in the same coding group as Black Hill and Darvel, so if the problem is within the coding of the transport stream, they will be
    affected too

    Not sure of the terminology with this funny digitty stuff but last time
    it was the modulator / drive / whatever they call it at Torosay.
    Arquiva did a changeover whilst I watched at homeand then they locked it
    onto the good side until someone could get over and change the unit.

    But it did not seem to be picked up by the monitoring, I thought they
    might have improved the monitoring since then.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Woody@21:1/5 to Mark Carver on Sun Jan 30 20:01:53 2022
    On Sun 30/01/2022 19:36, Mark Carver wrote:
    On 30/01/2022 18:59, MB wrote:
    On 30/01/2022 15:30, Mark Carver wrote:
    Well yes, everything except I think Shopping Quarter is in HD.

    Torosay is in the same coding group as Black Hill and Darvel, so if the
    problem is within the coding of the transport stream, they will be
    affected too

    Not sure of the terminology with this funny digitty stuff but last
    time it was the modulator / drive / whatever they call it at Torosay.
    Arquiva did a changeover whilst I watched at homeand then they locked
    it onto the good side until someone could get over and change the unit.

    But it did not seem to be picked up by the monitoring, I thought they
    might have improved the monitoring since then.


    The video and audio packets are married together at the code and mux
    stage (hundreds of miles away in the SE of England)
    There's nothing modulating that mux transport stream at COFDM level at
    the transmitter that  could affect that, and cause the video and audio packets to lose sync.

    It's either going wrong in the receiver (changing channel away, and back often cures (or makes matters worse)) or, as I say way upstream nowhere
    near Torosay.

    The transmitters these days are largely dumb terminals. Swapping the Tx drives over gives the receiver a similar kick to you changing channel etc


    Agreed changing channel away and back - <but to a different mux>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to Mark Carver on Sun Jan 30 20:11:58 2022
    On 30/01/2022 19:36, Mark Carver wrote:
    The video and audio packets are married together at the code and mux
    stage (hundreds of miles away in the SE of England)
    There's nothing modulating that mux transport stream at COFDM level at
    the transmitter that  could affect that, and cause the video and audio packets to lose sync.

    It's either going wrong in the receiver (changing channel away, and back often cures (or makes matters worse)) or, as I say way upstream nowhere
    near Torosay.

    The transmitters these days are largely dumb terminals. Swapping the Tx drives over gives the receiver a similar kick to you changing channel etc

    The previous time the effect was the same as the present fault. Emley
    Moor did a changeove at Torosay and the fault cleared. They locked it
    onto the good side, I am sure they changed back and the fault reappeared.

    But a few days later the fault reappeared and they put it back on he
    good side which cleared the fault. So something was happening at the transmitter site.

    It was the same on all my receivers and those of several other people
    who I checked with.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Carver@21:1/5 to All on Sun Jan 30 19:36:29 2022
    On 30/01/2022 18:59, MB wrote:
    On 30/01/2022 15:30, Mark Carver wrote:
    Well yes, everything except I think Shopping Quarter is in HD.

    Torosay is in the same coding group as Black Hill and Darvel, so if the
    problem is within the coding of the transport stream, they will be
    affected too

    Not sure of the terminology with this funny digitty stuff but last
    time it was the modulator / drive / whatever they call it at Torosay.
    Arquiva did a changeover whilst I watched at homeand then they locked
    it onto the good side until someone could get over and change the unit.

    But it did not seem to be picked up by the monitoring, I thought they
    might have improved the monitoring since then.


    The video and audio packets are married together at the code and mux
    stage (hundreds of miles away in the SE of England)
    There's nothing modulating that mux transport stream at COFDM level at
    the transmitter that  could affect that, and cause the video and audio
    packets to lose sync.

    It's either going wrong in the receiver (changing channel away, and back
    often cures (or makes matters worse)) or, as I say way upstream nowhere
    near Torosay.

    The transmitters these days are largely dumb terminals. Swapping the Tx
    drives over gives the receiver a similar kick to you changing channel etc

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Carver@21:1/5 to All on Mon Jan 31 09:54:07 2022
    On 30/01/2022 20:11, MB wrote:
    On 30/01/2022 19:36, Mark Carver wrote:
    The video and audio packets are married together at the code and mux
    stage (hundreds of miles away in the SE of England)
    There's nothing modulating that mux transport stream at COFDM level at
    the transmitter that  could affect that, and cause the video and audio
    packets to lose sync.

    It's either going wrong in the receiver (changing channel away, and back
    often cures (or makes matters worse)) or, as I say way upstream nowhere
    near Torosay.

    The transmitters these days are largely dumb terminals. Swapping the Tx
    drives over gives the receiver a similar kick to you changing channel
    etc

    The previous time the effect was the same as the present fault. Emley
    Moor did a changeove at Torosay and the fault cleared.  They locked it
    onto the good side, I am sure they changed back and the fault reappeared.

    But a few days later the fault reappeared and they put it back on he
    good side which cleared the fault.  So something was happening at the transmitter site.

    It was the same on all my receivers and those of several other people
    who I checked with.

    I'm sure it is, but as I say, the marrying of audio and video packets is
    not at the COFDM modulation stage, it's at the H.264 coding stage, so I
    can't see how the transmitter and its drives could have any effect ?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Woody@21:1/5 to Mark Carver on Mon Jan 31 10:28:46 2022
    On Mon 31/01/2022 09:54, Mark Carver wrote:
    On 30/01/2022 20:11, MB wrote:
    On 30/01/2022 19:36, Mark Carver wrote:
    The video and audio packets are married together at the code and mux
    stage (hundreds of miles away in the SE of England)
    There's nothing modulating that mux transport stream at COFDM level at
    the transmitter that  could affect that, and cause the video and audio
    packets to lose sync.

    It's either going wrong in the receiver (changing channel away, and back >>> often cures (or makes matters worse)) or, as I say way upstream nowhere
    near Torosay.

    The transmitters these days are largely dumb terminals. Swapping the Tx
    drives over gives the receiver a similar kick to you changing channel
    etc

    The previous time the effect was the same as the present fault. Emley
    Moor did a changeove at Torosay and the fault cleared.  They locked it
    onto the good side, I am sure they changed back and the fault reappeared.

    But a few days later the fault reappeared and they put it back on he
    good side which cleared the fault.  So something was happening at the
    transmitter site.

    It was the same on all my receivers and those of several other people
    who I checked with.

    I'm sure it is, but as I say, the marrying of audio and video packets is
    not at the COFDM modulation stage, it's at the H.264 coding stage, so I
    can't see how the transmitter and its drives could have any effect ?


    IME loss of lip-sync is the fault of the TV receiver - with mux changing
    often clearing as mentioned earlier.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Carver@21:1/5 to Woody on Mon Jan 31 10:32:32 2022
    On 31/01/2022 10:28, Woody wrote:
    On Mon 31/01/2022 09:54, Mark Carver wrote:
    On 30/01/2022 20:11, MB wrote:
    On 30/01/2022 19:36, Mark Carver wrote:
    The video and audio packets are married together at the code and mux
    stage (hundreds of miles away in the SE of England)
    There's nothing modulating that mux transport stream at COFDM level at >>>> the transmitter that  could affect that, and cause the video and audio >>>> packets to lose sync.

    It's either going wrong in the receiver (changing channel away, and
    back
    often cures (or makes matters worse)) or, as I say way upstream
    nowhere
    near Torosay.

    The transmitters these days are largely dumb terminals. Swapping
    the Tx
    drives over gives the receiver a similar kick to you changing
    channel etc

    The previous time the effect was the same as the present fault.
    Emley Moor did a changeove at Torosay and the fault cleared.  They
    locked it onto the good side, I am sure they changed back and the
    fault reappeared.

    But a few days later the fault reappeared and they put it back on he
    good side which cleared the fault.  So something was happening at
    the transmitter site.

    It was the same on all my receivers and those of several other
    people who I checked with.

    I'm sure it is, but as I say, the marrying of audio and video packets
    is not at the COFDM modulation stage, it's at the H.264 coding stage,
    so I can't see how the transmitter and its drives could have any
    effect ?


    IME loss of lip-sync is the fault of the TV receiver - with mux
    changing often clearing as mentioned earlier.


    Yes, it's either the coding end, or the receiver, not the bit in the
    middle (i.e the transmitter).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to All on Tue Feb 1 17:42:45 2022
    About 17:35h there was a click and sound was lost for a few seconds -
    sure it was OK before then but I was not paying a lot of attention. Now lip-sync is several seconds out - it is like watching a badly dubbed continental film or "Jones" in the Police Academy films!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From charles@21:1/5 to MB@nospam.net on Wed Feb 2 16:41:34 2022
    In article <stebie$7rq$1@dont-email.me>,
    MB <MB@nospam.net> wrote:
    Had a reply from the BBC to the report I submitted on their form.

    Usual case of "if in doubt tell the viewer to reset everything" even
    when same fault on several devices.


    Do remember, that, unlike 30+ years ago, you are not contacting engineers.

    --
    from KT24 in Surrey, England
    "I'd rather die of exhaustion than die of boredom" Thomas Carlyle

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to All on Wed Feb 2 16:30:06 2022
    Had a reply from the BBC to the report I submitted on their form.

    Usual case of "if in doubt tell the viewer to reset everything" even
    when same fault on several devices.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to charles on Wed Feb 2 18:01:49 2022
    On 02/02/2022 16:41, charles wrote:
    Do remember, that, unlike 30+ years ago, you are not contacting engineers.


    I wonder sometimes if we even contacting human beings.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From charles@21:1/5 to MB@nospam.net on Wed Feb 2 19:01:49 2022
    In article <stegue$ugl$1@dont-email.me>,
    MB <MB@nospam.net> wrote:
    On 02/02/2022 16:41, charles wrote:
    Do remember, that, unlike 30+ years ago, you are not contacting engineers.


    I wonder sometimes if we even contacting human beings.

    we certainly were

    --
    from KT24 in Surrey, England
    "I'd rather die of exhaustion than die of boredom" Thomas Carlyle

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to All on Fri Feb 4 09:12:38 2022
    Might be coincidence but HD lip sync seems OK now.

    Around the same time my BT YouView box stopped receiving HD but the
    Panasonic TV and Panasonic PVR just had the lip sync problem.

    I am wondering if either a faulty unit has been replaced or at least a changeover has been done and whether the fault condition could have
    affected the YouView box differently from the other two HD receivers
    because YouView HD is working again.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to Mark Carver on Fri Feb 4 10:12:05 2022
    On 04/02/2022 09:37, Mark Carver wrote:
    It's not as simple as that. Were all the HD channels in the mux affected
    BTW ? It's where they are encoded into H.264 where the problem lies (i.e
    no where near Torosay, or even in Scotland), and each channel will have discrete effects. There is nothing within the COFDM modulation process
    or path that can affect lip-sync. That is baked in way upstream at the
    H.264 stage.

    All channels on the MUX were affected the same.

    So why was the previous problem a few years ago only on one side and
    cleared when switched to the other side (and returned when switched back)?

    The previous occasion, I got nowhere reporting to the BBC and it was
    only fixed when I reported to STV and they must have prompted Arquiva to investigate.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Carver@21:1/5 to All on Fri Feb 4 09:37:52 2022
    On 04/02/2022 09:12, MB wrote:
    Might be coincidence but HD lip sync seems OK now.

    Around the same time my BT YouView box stopped receiving HD but the
    Panasonic TV and Panasonic PVR just had the lip sync problem.

    I am wondering if either a faulty unit has been replaced or at least a changeover has been done and whether the fault condition could have
    affected the YouView box differently from the other two HD receivers
    because YouView HD is working again.

    It's not as simple as that. Were all the HD channels in the mux affected
    BTW ? It's where they are encoded into H.264 where the problem lies (i.e
    no where near Torosay, or even in Scotland), and each channel will have discrete effects. There is nothing within the COFDM modulation process
    or path that can affect lip-sync. That is baked in way upstream at the
    H.264 stage.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Carver@21:1/5 to All on Fri Feb 4 10:30:13 2022
    On 04/02/2022 10:12, MB wrote:
    On 04/02/2022 09:37, Mark Carver wrote:
    It's not as simple as that. Were all the HD channels in the mux affected
    BTW ? It's where they are encoded into H.264 where the problem lies (i.e
    no where near Torosay, or even in Scotland), and each channel will have
    discrete effects. There is nothing within the COFDM modulation process
    or path that can affect lip-sync. That is baked in way upstream at the
    H.264 stage.

    All channels on the MUX were affected the same.

    So why was the previous problem a few years ago only on one side and
    cleared when switched to the other side (and returned when switched
    back)?

    Were you on the phone to Emley when they switched the drives over, and watching. If so which channel  ?
    Presumably the carrier dropped for a split second ? How long before they switched it back. Again did you check all the channels.


    The previous occasion, I got nowhere reporting to the BBC and it was
    only fixed when I reported to STV and they must have prompted Arquiva
    to investigate.

    It's unlikely to be a problem in their domain. The BBC are responsible
    for code and mux. However STV are probably still the best route to get
    the issue fixed, having quite a small engineering dept, you're likely to
    manage to get someone with influence to talk to the Beeb etc

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to Mark Carver on Fri Feb 4 11:16:23 2022
    On 04/02/2022 10:30, Mark Carver wrote:
    Were you on the phone to Emley when they switched the drives over, and watching. If so which channel  ?
    Presumably the carrier dropped for a split second ? How long before they switched it back. Again did you check all the channels.

    It is some time ago now but I am sure I watched listened as they
    switched because they had no way of knowing whether the fault was on.

    Sure I would have checked at least a few channels./

    They locked it on one side but a few days later it was either switched
    again or changed over itself and I think I had to ring them up.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to Mark Carver on Mon Feb 7 08:50:11 2022
    On 07/02/2022 08:24, Mark Carver wrote:
    Well, I gather the Tx exciters do have the ability to modify the
    transport steam packets (notably when there is SFN working required) so
    it's apparently not impossible the fault is being triggered at Torosay.

    I thought it was just the klystrons that were steam powered! :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Carver@21:1/5 to All on Mon Feb 7 08:24:52 2022
    On 04/02/2022 11:16, MB wrote:
    On 04/02/2022 10:30, Mark Carver wrote:
    Were you on the phone to Emley when they switched the drives over, and
    watching. If so which channel  ?
    Presumably the carrier dropped for a split second ? How long before they
    switched it back. Again did you check all the channels.

    It is some time ago now but I am sure I watched listened as they
    switched because they had no way of knowing whether the fault was on.

    Sure I would have checked at least a few channels./

    They locked it on one side but a few days later it was either switched
    again or changed over itself and I think I had to ring them up.

    Well, I gather the Tx exciters do have the ability to modify the
    transport steam packets (notably when there is SFN working required) so
    it's apparently not impossible the fault is being triggered at Torosay.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Carver@21:1/5 to All on Mon Feb 7 08:54:11 2022
    On 07/02/2022 08:50, MB wrote:
    On 07/02/2022 08:24, Mark Carver wrote:
    Well, I gather the Tx exciters do have the ability to modify the
    transport steam packets (notably when there is SFN working required) so
    it's apparently not impossible the fault is being triggered at Torosay.

    I thought it was just the klystrons that were steam powered!  :-)

    A friend of mine used to work for the studio/OB truck side of Pye TVT.
    He'd often rib his colleagues in the transmitter side of the company,
    that their products would totally screw up the output of his stuff by
    the time the video signals had emerged out of the klystrons !

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to All on Mon Feb 7 11:57:27 2022
    BBC Reception Advice have confirmed there was a fault at Torosay, now fixed.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tony sayer@21:1/5 to All on Fri Feb 11 11:52:04 2022
    In article <j6c51jFchq7U1@mid.individual.net>, Mark Carver <mark.carver@invalid.invalid> scribeth thus
    On 07/02/2022 08:50, MB wrote:
    On 07/02/2022 08:24, Mark Carver wrote:
    Well, I gather the Tx exciters do have the ability to modify the
    transport steam packets (notably when there is SFN working required) so
    it's apparently not impossible the fault is being triggered at Torosay.

    I thought it was just the klystrons that were steam powered!  :-)

    A friend of mine used to work for the studio/OB truck side of Pye TVT.
    He'd often rib his colleagues in the transmitter side of the company,
    that their products would totally screw up the output of his stuff by
    the time the video signals had emerged out of the klystrons !

    TvT eh?, used to be there back in around 1969!...


    Anyone here remember Bilko Burton, Freddie Shelton and George
    Hickson?...

    --
    Tony Sayer


    Man is least himself when he talks in his own person.

    Give him a keyboard, and he will reveal himself.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to tony sayer on Fri Feb 11 12:11:21 2022
    On 11/02/2022 11:52, tony sayer wrote:
    Anyone here remember Bilko Burton, Freddie Shelton and George
    Hickson?...

    At the end of last year, the Pension Visitor told me about Davd
    Sandbrook having died so I did a quick search and came across the Obits
    on www.bbceng.info. I mentioned this to an ex-colleague, he replied
    that he was surprised at all the familiar names there that he had not
    realised they had died.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From charles@21:1/5 to MB@nospam.net on Fri Feb 11 18:08:34 2022
    In article <su5jp9$t7q$1@dont-email.me>,
    MB <MB@nospam.net> wrote:
    On 11/02/2022 11:52, tony sayer wrote:
    Anyone here remember Bilko Burton, Freddie Shelton and George
    Hickson?...

    At the end of last year, the Pension Visitor told me about Davd
    Sandbrook having died so I did a quick search and came across the Obits
    on www.bbceng.info. I mentioned this to an ex-colleague, he replied
    that he was surprised at all the familiar names there that he had not realised they had died.


    Dave's death was mentioned in the recent Prospero. That link doesn't seem
    to work

    --
    from KT24 in Surrey, England
    "I'd rather die of exhaustion than die of boredom" Thomas Carlyle

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From MB@21:1/5 to charles on Fri Feb 11 20:04:30 2022
    On 11/02/2022 18:08, charles wrote:
    Dave's death was mentioned in the recent Prospero. That link doesn't seem
    to work

    It was just the top level of the website, try

    https://www.bbceng.info/Deaths/deaths.htm

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)