iWeb and Quicktime Movie Upload 2013

Three or so years ago, I made a website using iWeb (the last version Apple produced; i.e. the current version), and I included some videos. The videos were from a digital (tape) video camera, edited with iMovie HD, and were old-format 640x480. I managed to work out how to set the movies to start quickly (before fully loading) using iMovie and QuickTime. I dropped the movie into a regular iWeb page, resized it, put the settings up with the iWeb inspector, and all was well. The movies played (and still play) on Safari and Firefox, on my Macs and on an Asus Windows machine I have. (They won't play on my iPad - if anyone can tell me why, I'd be grateful; I'll probably put the original DV through a more recent version of iMovie and QT, and upload again.)


I want to make another similar website. However, my camera is now a HD tape model, and I have made my peace with iMovie '11 and worked out how to use it. My machine is the latest Mac Mini, and so QT is the latest also. I run Mountain Lion.


I made a movie with iMovie '11, and exported a quality version. I opened it in QT and chose 'Export for Web' and selected the option which gives me three different sizes. After some struggles, I worked out how to put this into my uploaded iWeb (test) site (although I have to say that the instructions Apple's QT gives are not the clearest), and it works, even on my iPad.


My questions concern the code which QT says you should upload. The code in the <body>, I understand, and it's obviously necessary to play the movie.


But about the <head> tag QT says:


Please note, to properly validate as XHTML, the <style> tag and the first <script> tag should be placed within your page's <head> tag.


Here's the code QT says to paste into the <head>


<script src="scripts/prototype.js" language="JavaScript" type="text/javascript"></script>

<script src="scripts/qtp_poster.js" language="JavaScript" type="text/javascript"></script>

<link href="stylesheets/qtp_poster.css" rel="StyleSheet" type="text/css" />


However, the movie playback still seems to work without uploading the code for the <head> of the page. And there is NO <style> tag, and why only the FIRST <script> tag?


The <head> on the page iWeb produces for my test page already has a lot of code:


<head>

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

<meta name="Generator" content="iWeb 3.0.4" />

<meta name="iWeb-Build" content="local-build-20130116" />

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

<meta name="viewport" content="width=950" />

<title>Ed's Video Test</title>

<link rel="stylesheet" type="text/css" media="screen,print" href="Eds_Video_Test_files/Eds_Video_Test.css" />

<!--[if lt IE 8]><link rel='stylesheet' type='text/css' media='screen,print' href='Eds_Video_Test_files/Eds_Video_TestIE.css'/><![endif]-->

<!--[if gte IE 8]><link rel='stylesheet' type='text/css' media='screen,print' href='Media/IE8.css'/><![endif]-->

<style type="text/css">

/*<![CDATA[*/

@import "Scripts/Widgets/HTMLRegion/Paste.css";

/*]]>*/

</style>

<script type="text/javascript" src="Scripts/iWebSite.js"></script>

<script type="text/javascript" src="Scripts/iWebImage.js"></script>

<script type="text/javascript" src="Scripts/iWebMediaGrid.js"></script>

<script type="text/javascript" src="Scripts/Widgets/SharedResources/WidgetCommon.js"></script>

<script type="text/javascript" src="Scripts/Widgets/HTMLRegion/Paste.js"></script>

<script type="text/javascript" src="Eds_Video_Test_files/Eds_Video_Test.js"></script>

</head>


Questions:

1. Should I put the QT code in the <head> tag anyway, even though it seems to work without it?

2. If I don't put it in, does that mean the choice between the three movies doesn't take place? I don't have a smartphone, but the playback on my 27" screen, my Asus netbook, and on my iPad all look fine without the head code.

3. If I do put it in, where exactly do I put it, and do I need to replace any of the code that is already there?


4. The original iWeb drag and drop method still seems to work fine with movies direct from iMovie (and plays even on my iPad), but obviously you can only put one version of the movie on a page. Is there still a good reason for using the multi-size version which involves manually uploading the movie and opening the page after uploading and inserting code for every movie? For example, I have a very fast internet connection. Maybe it's kind to those with a slower connection to put up the smaller movies also?


And, since I'm here, I have a couple of slightly related questions:


5. I designed my site (it's non-commercial, just a trip report, but with a lot of pages) to not need any scrolling even on quite a small desktop screen (you click on from page to page like a book, but you can also navigate around sections more easily this way; anyway that's how I like it). But on the iPad, held horizontally, the width is resized to take up the full width of the sceen, so you then need to scroll down. It's really annoying me. Is there some code I could put in to tell the iPad not to do this (there are plenty fewer vertical pixels on my website's pages than on the iPad screen)? (I don't care about phones, because the site is photo-based so looking at it on a phone is pointless in my opinion. And netbooks with only 768 vertical pixels are not particularly important to me either, but the iPad screen is plenty big enough for the site to work the way I want it to.)


6. And I want to include slideshows of photos without using the iWeb/iPhoto system (which brings up an external window in a different colour). I want the user to be able to see the thumbnails, to start and stop an on-page slideshow, and for me to be able to put captions (descriptions) with the slides. There seem to be a lot of options, and I still haven't finished looking at all the ones I got from the web. But does anyone have a good recommendation - paid or free?


Thanks for reading this long thread, and for any advice.

Posted on Jan 22, 2013 9:46 PM

Reply
14 replies

Jan 23, 2013 2:15 AM in response to Karl Wittgenstein

See the second method described on this page for how to add the code to an HTML Snippet...


http://www.iwebformusicians.com/Website-Movie-Video/Poster-Movie.html


The prefered method of playing movies on websites is to use an HTML5 player with flash fallback for older browsers. Using this method, you can get away with only one video file - an MP4.


In this section of iWeb for Musicians you can see examples of several different types of flash fallback players...


http://www.iwebformusicians.com/Website-Movie-Video/Poster-Movie.html


The latest version of flowplayer has all the features that I want in a player and allows several movies on a page by loading only the poster image. It has the added advantage of turning off one player when another is selected...


http://www.iwebformusicians.com/Website-Movie-Video/Flow-Player-5-2.html


iWeb uses a fixed width page so it is not possible to use it to create a page that will respond to different browser widths. You need to create a version of your site to suit each type of device or use a responsive design like this...


http://www.ezmacwebdesign.com/responsive-sidebar/


As far as slideshows are concerned there are just so many of them. See this section of iWeb for Musicians for examples...


http://www.iwebformusicians.com/Banner-Slideshow/Slideshow-Showcase.html


Some more examples using iWeb....


http://www.iwebformusicians.com/iweb-snippets/gallery.html


http://www.iwebformusicians.com/iweb-snippets/slider.html


An example of a dual slideshow with a separate window for the image and the caption...


http://www.iwebformusicians.com/iweb-snippets/map-tutorial.html


Finer swiping for mobile devices...


http://www.iwebformusicians.com/iweb-snippets/swipe.html


A modern slider that uses no javascript and makes use of the new(ish) CSS transitions...


http://www.iwebformusicians.com/iweb-snippets/flux.html


Shadowbox is a very versatile version of the Lightbox style...


http://ezmacwebdesign.com/Demo/shadowbox/shadowbox.html


... and can be used as a standalone or along with jQuery, Mootools etc...


http://ezmacwebdesign.com/Demo/shadowbox/shadowbox.html

Jan 23, 2013 2:50 AM in response to Wyodor

I've looked around these discussions and other sites including the iwebformusicians site, but no-one gives the information I asked for clearly (or at all). Therefore, I tried to give the background information that would make my question precise.


What I want to know is where I should put the <head> and the <body> code that is produced by QuickTime 10.2 (the latest 2013 version, and not QuickTime Pro or X or 7, although the code is similar) if I use use its Export for Web function.


If I understand the page you linked to (Discussions 2; Lots of Water), in iWeb I should put the whole lot, <head> and <body> in a lump in the HTML Snippet, and not attempt to put the <head> stuff in the actual head of the page iWeb creates, even though this is what Quicktime tells me to do? Will this then support the functionality of the various options as to size for different machines and speeds?


Thanks for the iPad stuff. However, my problem is with horizontal orientation. Vertical is fine. Horizontal would have the photos come out larger, which is why I would like it to work that way, too, just as it does on regular computers.

Jan 23, 2013 3:02 AM in response to Roddy

Thanks for the info. The link to ezmacwebdesign looks very interesting and useful.


As for the video, since Apple provides an apparent simple solution via QT, and I want to keep using iWeb as long as possible, I would like to use this simple solution. So my question was about how to use the <head> and <body> code that QT produces in combination with iWeb. It seems to work without the <head> code at all, but I'll try putting it all in the HTML snippet and see what happens.


I'll have a look at Flowplayer, thanks for the recommendation, but I did look at the iwebformusicians site before. I'm just trying to keep everything as simple as possible for me. It's not commercial, so I'm not worried about people with out-of-date software or old browsers. I just give a link to a Quicktime download, and if people can't be bothered, then that's OK.


Thanks again.

Jan 23, 2013 4:33 AM in response to Karl Wittgenstein

Apple's instructions for are those who are creating their web page using HTML - not using an app like iWeb.


When you paste code into an iWeb HTML Snippet it creates a new HTML doc - a page within a page.


The code in the Snippet would look something like this....


<head>

<script src="http://www.apple.com/library/quicktime/2.0/scripts/prototype.js" language="JavaScript" type="text/javascript"></script>

<script src="http://www.apple.com/library/quicktime/2.0/scripts/qtp_poster.js" language="JavaScript" type="text/javascript"></script>

<link href="http://www.apple.com/library/quicktime/2.0/stylesheets/qtp_poster.css" rel="StyleSheet" type="text/css" />

</head>


<body>

<a href="URL to the movie file" rel="qtposter">

<img src=URL to the poster image" width="640" height="490" />

</a>

</body>


If you are previewing the movie with Safari it will run OK without the links to the javascript and CSS files in the documnet head. It probably won't work so good for those who don't have the QuickTime Player plugin. Its also pointless providing a download to a .MOV file if the end user doesn't have QuickTime player installed on their computer. Many WIndows users don't.


Its difficult to comment on the iPad landscape mode thing without out seeing you actual web page. You could try using a smaller sized movie that will display properly on an iPad in landscape mode and offer a full screen option for those with bigger screens.


There's not really a lot of point to creating an iPad version of a website. All you need to do is make sure the navigation and other links are big enough for finger stabbing and that forms use the input types designed for mobile devices.


Here's an example of a form designed for both mobile devices and desktops for those who want to make their sites more mobile friendly...


http://www.ezmacwebdesign.com/Demo/Responsive-Form-Inputs/datepicker-form.html

Jan 24, 2013 12:27 AM in response to Roddy

Roddy, thank you. This essentially tells me what I was trying to find out about the QT Web movie output.


What I understand from this post of yours and various other bits I've looked at on the internet is that: the 'HTML Snippet' in iWeb actually creates another page which appears inside the page you think you are creating (via iFrame), and looks like one page to the viewer and the naive iWeb user like me. Therefore if I paste all the QT output code into the HTML Snippet, iWeb will sort it into <head> and <body> for me. Then I upload the videos, and change the code manually so the paths are right. And this will look fine for viewers with QT installed. OK.


I take your point about wide reach, and last night (I live in Japan, so we are nine hours ahead of you if you are actually in Scotland) I looked in more detail at the HTML5 stuff as you recommended. I had looked at it before, but I basically want to keep things simple for me, and therefore using the Apple route as much as possible seemed sensible. But the HTML5 route doesn't look much more complex. It seems to involve creating an Ogg version for Firefox and an MP4 version for everything else and then linking to or installing a player. I'm going to try that this evening on my private test page.


As regards the iPad thing, the annoyance for me is that WebKit on iPad goes super-full-screen automatically in horizontal, i.e. it fills the full width regardless of how much of the page is cut off vertically. I designed the site in a way that would be OK for even fairly small desktop screens. It looks fine in portrait on the iPad, but I would like there to be a piece of code you could insert to tell WebKit to fit the whole page on the screen if possible (i.e. stop expanding the page when either of the sides reaches the edge of the visible. As you said, iWeb produces fixed size pages, so I don't see why this isn't possible.


The site is just a holiday report at:


http://kenyaview.earthworldview.com


However, it has more than 200 pages and I think it shows the huge power that iWeb has if you put some effort in, and what a shame it is (would be) if Apple abandon it completely, and how wonderful it would be if they put some effort into making it really great. I thought the site might be useful for people who are thinking of visiting Kenya, and birdwatchers and animal-lovers in general beyond my friends and family for whom I made it in the first place. The videos are also broken in iWeb, as are the signs for the forward, backward and home page buttons (although they still work, they have become simple squares), and this is why I didn't want to put up the link in my original post. The Lodge page (effective Home page) on the site as it stands says QT is necessary, and gives a link. But, as I said, I'll try HTML5. I might try Video-js first and not Flowplayer.


I had planned to add sites about trips to other places, but almost as soon as I finished the site, it became clear that Apple was going to stop developing iWeb, and this depressed me, and put me off doing it. I trialled other WYSIWYG software, but none was anything like as good as iWeb even in its current state. Just recently, I got the latest Mac Mini with Mountain Lion. iWeb still works, as does my trusty iView Media Pro, and so I reckon I am good for another five years at least, and have started to look at adding all these other trip sites I have partially prepared.


On the photo slideshow thing, there are, as you say, lots around. But I tried quite a few of the jAlbum ones, and I still haven't found a simple and clear slideshow with captions (not just titles) which links into the page neatly. I was hoping that someone on the thread would say, "I'm using X software and it's simple and does just this." I'll also continue experimenting here.


Thanks for taking the trouble and giving the time to look at my long posts. I think I've now worked out what's going on in some detail. If only Apple spent a bit of their spare cash on manuals and support for their own software, and also thought of people who want to go a bit beyond the surface possibilities.

Jan 24, 2013 4:31 AM in response to Karl Wittgenstein

The advantage of using an HTML5 player with flash fallback is that you only need to provide one movie file - an MP4.


VideoJS is OK if you only need to put one movie per page. Otherwise use Flowplayer or Mediaelement since they can be set up to turn one movie off when the next is selected.


With regard to the iWeb built in slideshow, Old Toad and I modified it way back when Apple announced that MobileMe was closing down. Here's a page about it and how to get the controls back...


http://www.iwebformusicians.com/Banner-Slideshow/iWeb-Slideshow-Assets.html


You'll find a link to OT's tutorial somewhere on the above page.


With regard to the iPad, no matter what width you make the page in iWeb, the iPad will stretch it out to fit the screen width. In Wyodor's example of a site created to suit the iPad, the width is set to 768px and it views nicely in portrait mode. In landscape however, it stretches out over the full screen width. I don't see this as a great problem since its down to the user to decide whether to use landscape or portrait mode to suit their viewing needs. To prevent this in a responsive design its just a question of setting a maximum width for the content wrapper.


This is the main reason I stopped using iWeb for designing sites about two years ago and got into responsive designs. Its getting to the point where more people are surfing using mobile devices and it won't be too long before we start ignoring how websites look on a computer! What a lot of web designers seem to forget is that there is a growing number of potential visitors who don't even own a personal computer.


I am actually in Scotland just now and it seems a little strange after 18 years in Californai!

Jan 24, 2013 3:47 PM in response to Roddy

Roddy, thanks for that. When I was making my site a few years ago, tweaking iWeb was an essential part of the process. Old Toad helped me, and I thanked him. I also got very useful information from iWeb for Musicians. I hadn't realised it was your site, but I would now like to thank you for the help I got from it. And I just bought your e-book! Even though it may not be iWeb centred, I'm sure it has lots of useful tips. I really want to put up the other stuff I have.


You say:

It's getting to the point where more people are surfing using mobile devices and it won't be too long before we start ignoring how websites look on a computer! What a lot of web designers seem to forget is that there is a growing number of potential visitors who don't even own a personal computer.


Well, surprisingly perhaps, here in Japan there are a lot of (young) people who don't own a computer and do all their computing on a (non-smart) phone because all they want is the ability to text (Japanese phones have had full e-mail (not SMS) built in from the beginning) and to get information about train times and suchlike.


But, on the other hand, a lot of people here who look adult in other ways read comics and never books. In the same way, if you run a business you may want as many 'potential visitors' as possible; but if you just want to share something, then you may need or wish to set the framework in which the viewer looks at (or listens to, if you are a musician) your work. In the case of my site, which wants to share photos and information about the background to the photos, there's a minimum size of screen which is necessary in my opinion, and there's simply no point in looking at it on a mobile phone, or in me preparing a version which would look OK on the phone.


But the iPad, which does a great job in portrait mode, could do a good job horizontally, too, if I could tell it to preserve the whole page.


Anyway, I'll look into the HTML5 stuff (I got distracted last night by something called 'beer').


You say:

I am actually in Scotland just now and it seems a little strange after 18 years in California!

Strangely strange, but oddly normal, perhaps. Thanks again and best wishes.

Jan 27, 2013 11:47 AM in response to Karl Wittgenstein

I'm adding a tutorial about Flowplayer Designer to the Custom Website ebook and have sent you a copy.


This really simplifies the task of getting movies to work in all browsers and on mobile devices.


The tutorial goes one step further than the developer's website and explains how to add a poster image, stop the movis from loading with the web page and how to get one movie to stop when another on the same page is started.

Jan 28, 2013 7:53 PM in response to Roddy

Thank you all.


I started to look at HTML5 and I remembered that one reason I hadn't tried harder before is that I wasn't able to make an Ogg movie that worked. I tried again yesterday with Miro Video Converter. It produced a movie that is almost pure pixels. The movie was only 3MB for an 80MB original, and nothing was identifiable in the movie. The webm conversion with the same software was fine.


I came across this post about Firefox (it's the only browser I use myself for various reasons) which suggests that Mozilla/Firefox may have decided to support h.264/mp4 after all. If so, that would solve all my problems. I get the impression that Ogg hasn't been developed for several years.


Old Toad: Glad to see you are still around. Your various posts and sites helped me a lot when I was getting started with iWeb. When you get to 100,000 points do you get lunch with Tim Cook, or is it 1% of Apple stock?

Jan 30, 2013 3:05 AM in response to Karl Wittgenstein

Firefox doesn't have support for MP4. Older versions can use OGV and newer ones a WebM. WebM will be chosen by Google Chrome, if available, and doesn't play well in that browser.


I have had no problems with Miro for OGV. Try using a .mov file to convert rather than an MP4. I have found that QuickTime Pro is actually not too good for converting and that Miro is much better!


I use an MP4 only (no OGV or WebM) with flash fallback which you need for IE users anyway.


Here's some info about browsers and supported formats...


User uploaded file

Jan 31, 2013 12:22 AM in response to Roddy

Thanks for the reply, Roddy. Apologies for not replying to your (personal) mail about HTML5 players. I've been busy and not had a chance to test Flowplayer yet.


However, I can't get any ogg movies to work.


I've tried Miro with a .mov file and the result is junk (on Firefox and on VLC). Not quite as junk as a .mp4 file, but still totally unusable junk. It looks like these converters can only cope with very small original files which will of course produce very small (and for me pointless) final files.


I'm using the latest Mac OS on the latest Mac Mini which comes with QuickTime Player 10.2. My QuickTime Pro disappeared when I updated, and the QT 10.2 doesn't appear to have any conversion options at all (if it does, I'd be grateful if you could tell me where). I guess this is part of the Apple move to a walled-garden system which is increasingly annoying me, I guess. But that's a different rant.


Anyway, I think I'll give up on ogg. I'll try HTML5 with .mp4 and with and without WebM and see what happens. If I don't like it, I think I'll go back to the Apple solution which was working fine for me on Firefox and Safari on both Mac and Windows. I can also try it on my wife's Windows IE whatever the latest version is, if she brings her machine home from work.


Anyway, I hope to have free time over the weekend to try things out. Thanks again. But I really think Mozilla/Firefox will have to support h.264 or die. For a whole pile of reasons, Firefox is the only browser I use, and I'd pay them money to keep going, so I hope they don't die out due to being too loyal to open source principles.

Jan 31, 2013 12:53 AM in response to Karl Wittgenstein

QuickTIme 10 doesn't do conversion. You can still download QT 7...


http://support.apple.com/downloads/#quicktime


... and apply your Pro license.


I simply use an MP4 with flash fallback for Firefox and older versions of IE. Since more and more people are using mobile devices I would say that MP4 is the "go to" format and .mov (and the need for the QuickTime plugin) should be avoided.


My main reason for avoiding using OGV and WebM is that, in a perfect world, we should supply each video file in at least three sizes. The math is simple and means we would need 9 different versons of each movie file. See this page for an example of how different poster images and movie file sizes are served up for different device widths using media queries.


I know that all this is a lot more than the average iWeb user wants to hear but its one good reason why the application is dead in the water. People expect movies on websites and they have to be downloaded and playable fast on mobile devices.


In the household I'm living in just now, I'm the only one who actually uses a computer. All the internet surfing is done on an iPad, iPad Mini, iPhone and an iPod!

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.

iWeb and Quicktime Movie Upload 2013

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