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

Splicing tests not working correctly #57

Closed
yanj-github opened this issue Oct 5, 2021 · 4 comments
Closed

Splicing tests not working correctly #57

yanj-github opened this issue Oct 5, 2021 · 4 comments

Comments

@yanj-github
Copy link
Contributor

We cannot run splicing tests on the test runner correctly, can you please confirm the playout parameters have been defined and tested successfully, we are not able to use what is in the current release (branch feature-multi-mpd).

ref: #22 (comment)

@louaybassbouss
Copy link
Collaborator

We cannot run splicing tests on the test runner correctly, can you please confirm the playout parameters have been defined and tested successfully, we are not able to use what is in the current release (branch feature-multi-mpd).

ref: #22 (comment)

@yanj-github -> cta-wave/Test-Content#19 (comment). Can you make sure you are using the latest version in feature-multi-mpd branch.

@yanj-github
Copy link
Contributor Author

yanj-github commented Oct 6, 2021

@louaybassbouss and @FritzHeiden Thank you very much the splicing logic now is fixed and works fine to me on the latest commit: "Commits on Oct 5, 2021 34ebcbb"

Can I also have the content changed please?
Instead t1 and t2 can we have ss1 and t21 (temporory demo solution while we waiting to get right content)
Can you kindly help please? Thanks.

@FritzHeiden
Copy link
Collaborator

Can I also have the content changed please? Instead t1 and t2 can we have ss1 and t21 (temporory demo solution while we waiting to get right content) Can you kindly help please? Thanks.

@yanj-github I changed the content for splicing test accordingly.

@yanj-github
Copy link
Contributor Author

Thank you very much for fixing this @FritzHeiden and @louaybassbouss.
I just checked this and this is working fine now. Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants