Self-created skins function in standalone player; NOT on the web ...

I have just created some media skins for QT movies; they are digested properly by the latest QT 7.6 standalone player; when I embed those same QT movies in web pages, the QT movies occur normal, without any adapted skins ... This happens in Firefox 3.0.5 and IE 7.

The capability to use complex self-made media skins for QT movies embedded in web pages is a crucial feature for me; in order to consider using QT movies in web pages at all these days ...

IBM PC, Windows XP Pro, QT 7.6

Posted on Jan 23, 2009 4:48 PM

Reply
8 replies

Jan 23, 2009 6:39 PM in response to VerlSnake

The skin that come with quicktime doesn't embed into a web page. Media stand alone skins one makes for Quicktime don't work in web pages either.

I've been embedding Quicktime videos with a Flash flv player. Easy to make and can have a playlist along with many other options.

Here is one of the most popular flv player from Lontail, JW player:
http://www.longtailvideo.com/players/jw-flv-player/
You don't need the Flash program to make this flv work and it's skin able.

I believe youTube uses this player and I see it on the net all the time. One great thing, it's free!

Jan 24, 2009 5:05 AM in response to VerlSnake

A Web browser just can't display a skin track movie because the browser display requires a "box".
Your skinned movie actually does use a "box" but it is "masked" when play directly in the QuickTime Player.
Special html page code can "call" the QuickTime Player and bypass the browser plug-in allowing your skinned movies display in all their glory. Some of my pages as examples:
http://homepage.mac.com/kkirkster/D/
http://homepage.mac.com/kkirkster/F/
Another example that explains the issue:
http://homepage.mac.com/kkirkster/.Public/Owl.mov
A single click will load the file in a Web browser window. Looks rather ordinary.
But if you copy the link (highlight and right click) you can then paste the URL in the QuickTime Player app (Command-U to open the dialog window) and display the file showcasing the skinned movie features.

Jan 25, 2009 12:17 PM in response to QuickTimeKirk

Unfortunately I have marked this question as solved prematurely ...
But I still don't know how to bring the 'QT skinned movie glory' to web pages myself ...

When I load Your skinned QT movies directly into browsers, they ARE actually displayed as skinned ... For my own self-made skinned QT movies this is NOT the case ...

One of Your techniques seems to be to have one QT movie as platform for starting another, skinned QT movie; if I click once on the link to the skinned movie the QT player is invoked OUTSIDE of the webpage.

So could You please provide this 'Special html page code' You talked about ? And also tell us what's in Your skinned QT movies that makes them actually displayed as skinned in browsers when invoked directly in them ?

It would be great if You provided one very small example of a web page which has a skinned QT movie embedded which is displayed skinned when the web page is opened.

I still suppose that the QT skinning capability - which encompasses ARBITRARY shapes/masking - is a unique feature; but I am not exactly sure about that ... Can the same be done fo the Flash Player for example ? In any case I would really, really like to have this knowledge: How to bring all the 'QT skinned movie glory/goodness' to web pages ...

Jan 25, 2009 12:38 PM in response to VerlSnake

Skinned movies can be "dragged" when viewed in the QuickTime Player and other windows or the Desktop appears around the masked area. This is the "wow" factor.
The technique for launching the QuickTime Player is rather simple html code:
A QuickTime format (saved as .mov) acts as a placeholder and a clickable link. These "poster" movies could be small image files (or in my example pages, the entire browser window). When the poster movie is clicked the browser plug-in "calls" the QuickTime Player application and the file downloads and plays in a separate QuickTime Player window.
This is done with html code. The image file (now .mov) is the src="blah.mov" tag URL. This is what people view when your Web page opens.
The second file is your skinned .mov file and it uses the href="skinned.mov" tag URL. This is what will play when your poster movie is clicked. HREF is html code for a "linked" file.
The last html tag is target="quicktimeplayer". A target tag could be "_myself" (the same browser window) or " _blank" (a new browser window) or the "quicktimeplayer" (launches the QuickTime Player app). When using the href tag it is always best to use the complete URL.
http://www.qtbridge.com/pageot/pageot.html
Free software to help write the html page code.

Jan 25, 2009 4:27 PM in response to QuickTimeKirk

O.K., many thanks QuickTimeKirk 🙂 ! Now I got it, I suppose ...
When I use
- target="quicktimeplayer", a skinned QT movie is displayed skinned in a separate QT player app window
- target="myself", a skinned QT movie is displayed WITHOUT the skinning embedded in the web page

My earlier statement 'When I load Your skinned QT movies directly into browsers, they ARE actually displayed as skinned ...' was obviously wrong; I had been deceived by the web page background and the QT movie masked areas both having the same color white ...

So there is NO way to have skinned QT movies embedded in web pages ...
Well, Your solution to use the QT player app itself to leverage skinned movies should be an usable one for many use cases from my point of view 🙂 !

BUT: Then arises the question of bidirectional communication 'QT content - embedding web page'; for QT movies embedded in web pages I have already done that; but is this also possible when an external QT player app instance is invoked ? If bidirectional communication 'QT player app content - invoking web page' is NOT possible, then Your solution is unfortunately not feasible for all those use cases which need this communication ...

Jan 25, 2009 8:10 PM in response to VerlSnake

There are two applications that play QuickTime movies. One is the QuickTime Player, which is skinnable, and the other is the QuickTime Browser Plugin, which is not.

QuickTime Player gives you all kinds of flexibility because you can opt not to display the player itself, displaying instead another video track with sprite controls (the "skin"). That means the player itself can appear to be any arbitrary shape, although it is worth noting that the movie itself is still going to be rectangular.

You can use this to your advantage on the Web, because while you can't apply a skin to the web plugin directly, you can simulate it by cleverly positioning the movie on the page and blending the movie background with the page background. If you had a movie, for instance, playing in an oval cutout, you could apply a masking track to that movie so that the border of that cutout out to the rectangular extent of the movie was a part of the movie, and then carefully match that track to the graphic on the web page positioned behind the QuickTime plugin. Then for controls you use JavaScript controls on the web page so that you can control the movie with controls other than the usual boring controller (set "CONTROLLER=FALSE" to make the normal controls not appear).

To launch a skinned (or not skinned) movie in QuickTime Player, you have to first get control passed to the browser plugin, since it knows how to start the player. So your image link is a poster movie, as Kirk described, and when clicked its target is the standalone player.

I have an example of this at http://capital2.capital.edu/admin-staff/dalthoff/patrons.html. The link on the left links to a web page with a movie embedded in it. The link on the right is a QuickTime movie which launches the *same movie* as the one that plays in the left-hand link. The difference is that the movie launches in the standalone player, where it is instructed to open at full screen and to quit the player when it finishes.

You then want to return control to the web page when the movie finishes playing, correct? There are two ways to do that. The simplest is to set your movie to close when it finishes. The other option is to include an HREF track in the movie which can pass certain commands (or URLs at least) back to the browser. Experiment with that one, as Apple has dumbed down the feature a little bit in response to the shoddy programming over at MySpace that allowed QuickTime movies to reprogram peoples' personal pages. I don't know what the limitations are now, but it does still sort-of work.

--Dave Althoff, Jr.

Jan 26, 2009 4:56 PM in response to Dave Althoff

Thanks so far ! BUT: I couldn't figure out how to accomplish the following:
- Bidirectional communication between
- a poster movie played back by the QT browser plugin embedded in a web page
- a movie specified via the HREF technique that is played back by the QT player standalone app

I know that movies played back by the QT player standalone app can communicate with each other; but maybe communication between the QT browser plugin and the QT player app is not possible at all ? My hope is that at least movies invoked via the HREF technique can communicate with their invoking poster movie - even if it ís played back by the QT browser plugin ...

Can this communication gap be filled ? Or is the poster movie technique only good for QT movies which don't need any further communication ?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Self-created skins function in standalone player; NOT on the web ...

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.