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

Test Content for Splicing Tests #19

Closed
louaybassbouss opened this issue Oct 5, 2021 · 32 comments
Closed

Test Content for Splicing Tests #19

louaybassbouss opened this issue Oct 5, 2021 · 32 comments
Assignees

Comments

@louaybassbouss
Copy link

Test Content for following tests is missing:

  • 8.8 Playback over WAVE Baseline Splice Constraints
  • 8.13 Restricted Splicing of Encrypted Content
  • 8.14 Sequential Playback of Encrypted and Non-Encrypted Baseline Content
  • 9.4 Splicing of WAVE Program with Baseline Constraints
@jpiesing
Copy link
Contributor

jpiesing commented Oct 5, 2021

Test Content for following tests is missing:

* 8.8 Playback over WAVE Baseline Splice Constraints

* 8.13 Restricted Splicing of Encrypted Content

* 8.14 Sequential Playback of Encrypted and Non-Encrypted Baseline Content

* 9.4 Splicing of WAVE Program with Baseline Constraints

Which mezzanine content does this correspond to?

@FritzHeiden
Copy link

I moved the already generated tests for "8.8 Playback over WAVE Baseline Splice Constraints" and "8.14 Sequential Playback of Encrypted and Non-Encrypted Baseline Content" into the splicing-demo directory to avoid confusion. These tests exist for the purpose of demonstrating the functionality of the playout parameter in a splicing test scenario. The used content is not intended for these tests

@rbouqueau
Copy link
Collaborator

I'd like to make a status here, so that we have it written somewhere.

The current Test-Content-Generation implementation takes an A/V content and processes it in one step (single call to encode_dash.py from run-all.py - these are the two only scripts involved here). This steps includes the encoding, the packaging and the annotations. The archiving and the encryption are done "over-the-top" with direct calls from run-all.py.

Processing in one step causes two kinds of issues: 1) the content is bundled in folders (see cta-wave/dpctf-tests#59) and 2) the composition of content (#19, #4, audio profiles only, ...) is also more complex than expected. The good news is that gpac allows to split them ; my task will be to split the code appropriately to implement this.

Once this is done, generating the splicing content is just a matter of assembling the annotations. We don't need to generate some new CMAF content again. This part of the process needs to be done manually at the moment ; let's see how and how much it can be automatized.

@rbouqueau
Copy link
Collaborator

Ping @louaybassbouss :)

@jpiesing
Copy link
Contributor

jpiesing commented Feb 1, 2022

@louaybassbouss Ping ...

@louaybassbouss
Copy link
Author

@FritzHeiden FYI new splicing test content is now available.

@louaybassbouss
Copy link
Author

@rbouqueau the content is avi

Some first splice content:

Any feedback welcome. Only the first stream (in clear) is playable. The manifests are very similar (some periods are in clear while others are encrypted). If it looks ok then I will update it to the Akamai server.

@rbouqueau can you provide each content in multiple MPDs (2 MPDs one for main and one for spliced) instead of multi-periods ? see issue cta-wave/dpctf-tests#22 .

We check the content manually the clear content is playing properly. Regarding cenc content, we were able to play it even if we don't pass the cenc Key ID and key value. Can you check it please.

@rbouqueau
Copy link
Collaborator

@louaybassbouss Thanks for the feedback.

Can you provide each content in multiple MPDs (2 MPDs one for main and one for spliced) instead of multi-periods ? see issue cta-wave/dpctf-tests#22 .

Here are all the links. I'd be happy if we could clarify this (separate manifests vs multi-period manifest):

Regarding cenc content, we were able to play it even if we don't pass the cenc Key ID and key value. Can you check it please.

See links above. I checked and the content is encrypted. The content still use the same keys, could that be why you can play it back?

@louaybassbouss
Copy link
Author

@louaybassbouss Thanks for the feedback.

Can you provide each content in multiple MPDs (2 MPDs one for main and one for spliced) instead of multi-periods ? see issue cta-wave/dpctf-tests#22 .

Here are all the links. I'd be happy if we could clarify this (separate manifests vs multi-period manifest):

The final decision was in cta-wave/dpctf-tests#22 to use multiple MPDs. There is no multi-period at all.

Thanks we will check and let you know

Regarding cenc content, we were able to play it even if we don't pass the cenc Key ID and key value. Can you check it please.

See links above. I checked and the content is encrypted. The content still use the same keys, could that be why you can play it back?

Thanks for the hint this can be the reason

@rbouqueau
Copy link
Collaborator

@louaybassbouss Note that the URLs (server) will evolve once this is validated on your side.

@louaybassbouss
Copy link
Author

@rbouqueau the streams are working fine. Can you make them available via database.json? @jpiesing regarding content durations 10s for main content and 5s for Ad content are fine from your side? From Test implementation perspective the duration doesn't matter.

@rbouqueau
Copy link
Collaborator

Agreement during the call to create a new "CFHD-splicing" database + front-end tab.

@louaybassbouss
Copy link
Author

@rbouqueau when do you think can you make the new splicing content available in database.json?

@rbouqueau
Copy link
Collaborator

Added by 5ec1ca4. Let me know if this is ok for you.

@louaybassbouss
Copy link
Author

Thanks @rbouqueau . There is still a mismatch of the ID structure for few elements most are related ss1 streams (Example https://github.com/cta-wave/Test-Content/blob/master/database.json#L472) can you make all IDs Zip/MPD URLs following the same structure?

@rbouqueau
Copy link
Collaborator

Thanks for reporting. That's a bug in the script. The ss1 is handled separately. I should have a look this evening.

rbouqueau added a commit that referenced this issue Feb 17, 2022
@rbouqueau
Copy link
Collaborator

That's fixed, thanks again. The script is safe, it was an error when merging the database.

@louaybassbouss
Copy link
Author

@FritzHeiden can we close this issue?

@FritzHeiden
Copy link

@FritzHeiden can we close this issue?

Yes. For now we are using the provided splice_main and splice_ad content

@jpiesing
Copy link
Contributor

jpiesing commented Oct 3, 2022

@FritzHeiden @rbouqueau I would like to update the Google spreadsheet to include splice_main and splice_ad and ensure all our test streams are included. @Romain Do you have the information on their properties? Do we need to add any more rows to the table to capture important details?

@rbouqueau
Copy link
Collaborator

I arbitrarily copied the properties from T1.

@jpiesing
Copy link
Contributor

jpiesing commented Oct 3, 2022

I arbitrarily copied the properties from T1.

Just now or when you made those streams?
Do splice_main and splice_ad_content need to be regenerated with the most recent changes?

@rbouqueau
Copy link
Collaborator

Just now or when you made those streams?

When I made the streams. I had asked during a Tuesday call what to do and the answer was "whatever is conformant".

Do splice_main and splice_ad_content need to be regenerated with the most recent changes?

I don't think so.

@gitwjr
Copy link

gitwjr commented Mar 28, 2023

@FritzHeiden @rbouqueau need to discuss next steps/status to resolve this issue.

@rbouqueau
Copy link
Collaborator

NB: while digging I found randomly that the origin of this request is here: cta-wave/dpctf-tests#101.

@rbouqueau
Copy link
Collaborator

Today's notes: @rbouqueau evaluate the situation tomorrow after JCCP call + @nicholas-fr to check with fractional frame rate. If ok, then generate asap.

rbouqueau added a commit to cta-wave/Test-Content-Generation that referenced this issue Apr 11, 2023
@rbouqueau
Copy link
Collaborator

See my comment in cta-wave/Test-Content-Generation#55

@rbouqueau
Copy link
Collaborator

Content updated.

@gitwjr
Copy link

gitwjr commented Jun 20, 2023

@FritzHeiden @louaybassbouss Fritz and Louay to check and then close if OK.

@rbouqueau
Copy link
Collaborator

@FritzHeiden @louaybassbouss Fritz and Louay to check and then close if OK.

Thx!

@gitwjr
Copy link

gitwjr commented Jul 18, 2023

Closed. This was checked during the HbbTV plugfest.

@gitwjr gitwjr closed this as completed Jul 18, 2023
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

5 participants