none: The video won’t resize to fit its parent container.fill: The video will stretch to fill the container.Anything that doesn’t fit within the container will be cut off. cover: The video will maintain its aspect ratio and resize to completely fill its parent container.This will create a “letterboxing” effect. contain: The video will resize to fit within the parent container and maintain its aspect ratio.It has the effect of resizing the video independently of the Wistia player. This is used to resize a video when there’s a discrepancy between its aspect ratio and that of its parent container. However, this will not prevent the viewer from clicking on the fullscreen button if it’s available. You can get around this by setting this option to true.Īn alternative is to set the fullscreenOnRotateToLandscape option to false. This means that customizations which come with our player do not appear. We do this because forcing our player to go fullscreen can cause issues with formatting, which can be a jarring experience for the viewer. iOS), we pass the video to the native player. loop: The video plays again from the beginning.ĭefault is false.reset: The video shows the thumbnail and controls if they are set to be visible on load.
![movie thumbnailer script movie thumbnailer script](https://i.pinimg.com/originals/e2/98/18/e298187d5230d01ce422d8c4032ce52d.jpg)
#Movie thumbnailer script update#
NOTE: When using the Customize API to update embed options, you don’t need to percent encode any option names or values. Visit the Customize API documentation to see how. This way, wherever you embed your video, it will inherit the customizations you’ve defined. You can update embed options saved within the Wistia app using the API.
![movie thumbnailer script movie thumbnailer script](https://nationalgriefawarenessday.com/wp-content/uploads/2018/01/sample-movie-script-grandbudapest-script.jpg)
Note that, if you have mykey=myvalue, you must encode both mykey and myvalue separately you don’t want to include the = in your percent encoding! Setting options using the Customize API Need a quick way to percent encode some values? Look no further! Type your value in the box below and copy the percent encoded version. The first character after the video’s hashed ID must be a ?. It is similar to the option=value syntax of Standard embeds, but every option and value must be percent encoded and separated by an &. Options can only be set one way with iframe embeds. If you’d like to use embed options on all videos on your page, you can use the special “_all” matcher: window._wq = window._wq || You can also target all the videos on a page. Options defined this way will only take effect if they are pushed onto _wq before the video is embedded. If you have more complex options or need to generate them on the client side, you can use window._wq to set them with a javascript object literal: If an option value has spaces, you can percent encode it.
![movie thumbnailer script movie thumbnailer script](http://www.pisitoenmadrid.com/blog/wp-content/uploads/2011/03/movie-barcode-3.jpg)
Multiple options are separated by spaces. First, the most common method is to add class in the form option=value. Options can be set in two ways on Standard embeds and Popover embeds (which are actually just Standard Embeds with a special option). Setting options on Standard and Popover embeds If you would like to add embed options to Channels head over to the Channel Embed Options guide. For the most reliable experience, we recommend continuing to use these for videos in projects. We do not formally support using our APIs for audio files in projects, or audio or video episodes in Channels at this time. The Wistia APIs were specifically built for videos in projects.