Giter Site home page Giter Site logo

abrizer's People

Contributors

dnoneill avatar jronallo avatar ssmirr avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

abrizer's Issues

set pixel format

Avoid this warning:

No pixel format specified, yuv422p for H.264 encoding chosen.
Use -pix_fmt yuv420p for compatibility with outdated media players.

canvas: video oral history use case with alternative audio file

How would I also include an audio file alongside a video? Are all the
items expected to be a video and the same content? Would it be alright
to also add an audio file or two to the items? My use case is that I
have a lot of video oral histories. Since they're mostly talking heads
some may prefer to just listen to the audio than to play the video.
How would I say that this is the audio content for the video?

See an example canvas here: https://gist.github.com/jronallo/b455a5ddab2ce4b28d55c7708603f85a

canvas: adding image service to canvas

For the IIIF canvas output how would you add an image service?

I'd eventually like to have an image service that can return frames
from the video, but for now I've just included a single static poster
image as a thumbnail. I'm not sure how I'd provide a service like that
yet, though I had prototyped something in my image server. One way to
start with creating an image service that just provides full images
for the various sizes that are provided with the various adaptations.
Or could a list of poster image choices with width & height just be
provided somehow? I'm not sure what an info.json would look like for
non-tiled images. Are there any Image API examples out in the wild
that only provide a few static images?

See an example canvas here: https://gist.github.com/jronallo/b455a5ddab2ce4b28d55c7708603f85a

canvas: WebVTT captions, subtitles, and chapters

I'm uncertain how with the seeAlso WebVTT captions I could say that they are captions rather than subtitles, descriptions, or chapters. Would it be possible to add a "kind" field that maps directly to an HTML5 track element attribute? Otherwise it could be ambiguous what the proper use for a WebVTT (or other captions format) file is. Players will sometimes have different controls for closed captions and subtitles.

See an example canvas here: https://gist.github.com/jronallo/b455a5ddab2ce4b28d55c7708603f85a

canvas: signal that DASH or HLS has captions

Manifests for DASH and HLS can include captions and subtitles. For instance HLS can have CEA-708 captions within the MPEG-2 video stream. A WebVTT file can also be pointed to from a DASH or HLS manifest. If there are sidecar captions (say WebVTT) in a seeAlso you won't need to use those sidecar captions if they're already included in the DASH or HLS manifest and you are using a video player than can use these captions. Including both the DASH/HLS manifest captions and the seeAlso captions to a player can cause problems or doubling up in controls.

Solution could be to have a way to show that the DASH or HLS stream includes captions. Or the shim to a player could first check whether the stream has captions and if not use the seeAlso captions.

canvas: video preview thumbnails

Several video players allow for preview thumbnails over the time rail
via a metadata WebVTT file that references thumbnail sprites with
media fragments. Is there any way to expose this kind of metadata
file on a canvas to where it is clear what the intended use of the
file is? Is this a service?

List of some players that support this already: https://github.com/jronallo/video_sprites#players

See an example canvas here: https://gist.github.com/jronallo/b455a5ddab2ce4b28d55c7708603f85a

Failed to find handler for \"/root/bento4.zip\

I'm receiving this error during when I start the vagrant box

TASK [bento4 : unzip bento4] ***************************************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Failed to find handler for \"/root/bento4.zip\". Make sure the required command to extract the file is installed. Command \"unzip\" not found. Command \"/bin/gtar\" could not handle archive."}
	to retry, use: --limit @/vagrant/ansible/development-playbook.retry

PLAY RECAP *********************************************************************
localhost                  : ok=60   changed=40   unreachable=0    failed=1   

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.