Skip to content
This repository was archived by the owner on Jan 10, 2025. It is now read-only.
Frederik Ring edited this page May 19, 2018 · 8 revisions

I'm seeing a slightly foggy background behind all videos in Chrome

Apparently there are some machine setups where external color management software and video hardware will clash and mess with the gamma settings of m4v playback in Chrome (see issue #12 for an example), which will result in black pixels rendered as dark grey - therefore rendering the alpha information saved in RGB useless/incorrect.

If you experience similar problems, use webm-video sources for playback in Chrome, they seem to work just fine. Safari and other browsers using m4v don't show any issues like this.

I was looking for jquery-seeThru but somehow ended up here. What happened?

v2.0.0 is now completely dependency-free, so it would have made no sense to keep using the jquery-prefix. v2.0.0 and above will still work as a jQuery-plugin. Old 1.x.x releases can still be downloaded and you can also still access its README

I copied your demo page to my server and nothing happens! What's wrong?

Canvas manipulation is subject to cross domain security restrictions. This means: the video's source files have to be requested from the exact same domain as the host HTML document. Everything else will throw a DOM Exception (that you should also be able to see in your console). If you want to use the demo pages on your server / machine you will have to copy the media files as well (instead of still linking to the files from the demos). They are also available in the repo (/media).

How do you generate the source files?

This can be done using almost any GUI based editing package. An example of how to do it in Adobe After Effects is included in the main README. If you're a 1337 500p4 h4x0r you can probably do this using ffmpeg as well.

I'm trying to bind mouse events to the video, but it's not working!

Keep in mind that after initializing .seeThru you are dealing with a canvas representation of your actual video element (which is hidden!). The visible canvas element will route mouse events through to the video and make it echo these events, yet if you are having problems in this area it might be a very good starting point.

Why is Safari 6 on Mac so doggone slow when running the plugin? My cores are melting!

I'm sorry, but this seems to be a bug in Safari when using video as source for canvas operation. Changing your server settings might help though: http://stackoverflow.com/questions/9929546/canvas-to-video-is-very-slow-on-safari-lion-mountain-lion Nightly webkit builds are already free of this bug so we all can hope it finds its way into an official Safari release soon!