Skip to content

CEA608: PAINT-ON Mode must keep the last shown captions on the screen#5147

Merged
ojw28 merged 1 commit intogoogle:dev-v2from
zsmatyas:dev-v2
Dec 5, 2018
Merged

CEA608: PAINT-ON Mode must keep the last shown captions on the screen#5147
ojw28 merged 1 commit intogoogle:dev-v2from
zsmatyas:dev-v2

Conversation

@zsmatyas
Copy link
Contributor

Problem

PAINT-ON mode is not implemented. From compliance tests:

  • RDC command has no effect except to select paint-on style.
  • Next data are written directly to the display upon receipt.
  • If other captioning is already on the screen, it stays on
  • The four-row limit is still in effect.

Solution

It is a rare use case, we do not support overriding characters in
existing cueBuilders as PAINT-ON would require. But the screen
must not be cleared when the mode switch happens.
We must keep the old captions when switching to PAINT-ON mode

Test

  • Live Over-the-Air content, beginning of commercials often uses
    PAINT-ON mode

[Problem]
PAINT-ON mode is not implemented. From the compliance tests:
* RDC command has no effect except to select paint-on style.
* Next data are written directly to the display upon receipt.
* If other captioning is already on the screen, the four-row
limit is still in effect.

[Solution]
It is a rare use case, we do not support overriding characters in
existing cueBuilders as PAINT-ON would require. But several
compliance tests check if the screen is cleared when the mode
switch happens. We must keep the old captions when switching
to PAINT-ON mode

[Test]
- Live Over-the-Air content, beginning of commercials often uses
PAINT-ON mode
@ojw28
Copy link
Contributor

ojw28 commented Nov 28, 2018

Looks fine to merge

@zsmatyas
Copy link
Contributor Author

zsmatyas commented Dec 3, 2018

Shall I add the next change on top of this in a new pull request? Shall I wait till this one gets merged so the branches have no conflicts?

@ojw28
Copy link
Contributor

ojw28 commented Dec 5, 2018

Does it need to be on top at all? Unless the next change happens to be touching the same lines of code, I'd expect it to be possible to prepare it on dev-v2 and have both changes merge fine. That said, we should get this merged tomorrow, so if you want to avoid experimenting you should probably just wait :).

@ojw28 ojw28 merged commit d1e49f2 into google:dev-v2 Dec 5, 2018
ojw28 added a commit that referenced this pull request Dec 5, 2018
PiperOrigin-RevId: 224114911
@google google locked and limited conversation to collaborators May 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants