Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #2525 - map one ISD to one Cue, not one Cue per content element #2549

Merged
merged 1 commit into from Apr 24, 2018

Conversation

davemevans
Copy link
Contributor

Ensures only ISDs with actual content are mapped to Cues, whilst only creating a single Cue per ISD. See #2525 for discussion.

I have tested with a number of the samples in the menu and also with some more complex (multiple active cues etc) content we have internally.

Please test and provide feedback ASAP so this has a chance to make it into 2.6.8.

@epiclabsDASH epiclabsDASH added this to the 2.6.8 milestone Apr 24, 2018
@epiclabsDASH
Copy link
Contributor

I have been testing it exhaustively and everything was fine. @physicsforpoets, any feedback to share? As @bbcrddave said it would be nice having feedback as soon as possible so we can include the change into 2.6.8.

@physicsforpoets
Copy link

@epiclabsDASH @bbcrddave this was the exact change I made in the debug player locally to attempt to fix the issue, looks good to me

@epiclabsDASH epiclabsDASH merged commit 13e49b5 into Dash-Industry-Forum:development Apr 24, 2018
@davemevans davemevans deleted the 2525 branch April 24, 2018 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants