-
Notifications
You must be signed in to change notification settings - Fork 5
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
video item not producing a valid manifest #82
Comments
Pretty sure this used to work, because I pulled it from another issue. |
We think this is because the original is this:
and we don't recognize/support "format": "h.264 HD", |
* Encoding thumbnail urls * Fixing missing video in #82 --------- Co-authored-by: Mek <[email protected]>
The Video now appears but the mimetype is: "application/octet-stream" which means none of the viewers can play it. |
Related recipe on audio choice: https://iiif.io/api/cookbook/recipe/0434-choice-av/ |
Even though the OGG appears like it should be
If you download the ogg and run
So, I think everything here is working as it should. The problem with this is manifest appears to be limited to the CORS issues on the |
I found this old issue on CORS and video: ArchiveLabs/iiif.archivelab.org#108 It looks like at the time it worked on all of the viewers but clover. Testing now it seems to work on most of them but I noitce an issue with Mirador now aswell. |
Things to test:
|
@glenrobson, here are my findings from last night:
Mirador chooses the ogg and the first three play the HD. Clover can play the ogg but not the others. I'm going to open an Issue with Clover. I'm also going to look at why our code is assigning this mime/type and see if I can do something about that. |
This items seems like it should be playable --there are derivatives in the right format for IIIF -- but our manifest doesn't seem to have any of them.
Item
downloadable derivatives
Item Manifest
It does have a bunch of Youtube attributes:
which we do surface in the manifest (and probably shouldn't??)
The text was updated successfully, but these errors were encountered: