I am trying to build a new album. The source folders contain (among other things) several WMV and MP4 files. The Make Album (all) process seems to built the website just fine. But when I go into the website and select any of my WMV files, they all just hang. The MP4 files play just fine, but the WMV files hang.
You will see two video files:
- The first is named "101117af Autumn Sunrise in Fox Hollow" and was built from a .wmv. It hangs.
- The second is named "190513ac Dinner wCalin at Bebederos" and was built from an MP4. It plays just fine.
I have bought and installed the latest jAlbum and PhotoBlogger skin. See attached for "about" info.
Also attached is an image of my jAlbum video settings.
I am running Apache server on the latest build of Windows 10 Pro.
Unfortunately, I have no idea where to begin solving this issue.
Oh, and in the future, please ensure that the lifeboat.zip file is created and uploaded. It makes it much easier for us to help, since there are many things we can then check. See Tools, Preferences, Album, Include lifeboat file.
The first video is not converted. The browser tries to play the original WMV file, which is not supported by browsers. You probably told jAlbum to not "reencode" the video, effectively leave it as it is. Right click the video's thumbnail and turn off "Do not reencode".
However, please note, today browsers don't allow auto playing of video and audio files, only after the user has started at least one of them manually on a site, so "Auto start videos" might not work as expected at the beginning.
Thanks for trying to be helpful, but I fear I may have not framed my problem clearly.
I think you've responded to my initial post (25-Jul-2019 17:01), but have not seen my later post of 26-Jul-2019 02:33 wherein I provide some additional information.
Your observation that my "2nd video" (whose file name starts with "190513ac") "plays fine" is neither at issue nor in dispute. That file's original format is MP4. My contention is that I do not have problems with original MP4s, but that I do have problems with original WMVs.
Your observation that my "first video" "is not converted" contradicts what I am seeing. My WMVs are being converted to MP4s, and in my post of 26-Jul-2019 02:33, I provided a link to an example of one such conversion.
Let me try to clarify. As an example, I have a WMV video named "101117af Autumn Sunrise in Fox Hollow.wmv".
2) The final album that I will be converting to PhotoBlogger is HUGE! It contains nearly 60 thousand images and over 600 videos. Its total size approaches 200 gigabytes. Making duplicates of all that is just not feasible.
3) The original album (now deleted in prep for rebuild) had been up for over a decade with "copy originals if needed" UNchecked, and it worked just fine.
As I'm sure you know, your doc for "copy originals if needed" reads:
"If one of the link to originals settings above is selected (and one is) then checking this will add a full size copy of the original file to the album, and links to the originals point to those copies. If any originals are being used in the album and this option is not selected then broken links could appear unless the 'true' originals are accessible from the album’s location(which they are). For example the local album might work but if uploaded to the web the originals will not be accessible. It may also need to be set if linking is not to originals but some originals are included within the album.
The default is, and it is always safer to have, Copy originals if needed checked. Only uncheck this if you fully understand how linking works and you have arranged for all originals used to be accessible from the published album(which I have).
I'll go ahead and try this for my test album, but in light of my concerns, would you be willing to provide more information about why this is a good idea?
That's exactly what I was afraid you were going to say.
In brief, when David introduced video support to jAlbum, many years ago, he took a shortcut, in an attempt to make it possible for skins to support videos without having to recode the skins. In short, he hijacked a jAlbum variable, originalPath, so that it would also point to processed videos. Some of us, me in particular, warned about this choice, knowing that it would come back to haunt us. And it has. Repeatedly. Alterations in the scheme designed to straighten out the mess have helped most situations, but not the one you're in.
I'm going to suggest something that will seem completely counterintuitive, but in a little test, it seems to work, and only because of the screwy definition of originalPath. Stick to your chosen settings - Link to originals via scaled images, and leave Copy originals if needed unchecked. But now, for each of your videos (even the ones that are already MP4's), right-click on its thumbnail and choose Use original. Believe it or not, jAlbum will still process the video so you end up with an MP4 in the slides directory of the output, and the link on the album page will actually point to it.
ETA: Yes, I realize that if this is the only solution, dealing with 600 videos will be somewhat awful. But not as awful as the alternative.
I've asked David to have a look at this (he's on vacation). He might have a better solution, so before you wade into an extensive manual effort, let's see what he's got to say about it. The notion that the only way to get jAlbum to use the processed video is to tell it to use the original is more than a little crazy.
ETA: GIF's are a different problem. In short, jAlbum converts them to PNG's, so they lose their animation. Offhand, I'm not sure what happens in this "don't copy the originals" situation - I'll have to experiment a bit.
ETA: In this "don't copy originals" environment, I don't think there's any way to get the album to show the original animated GIF, I'm afraid. If you let jAlbum copy originals, choosing Use original works just fine, but that doesn't work in this case. But I'm having trouble puzzling out the structure - the resulting path if you choose Use original is off by a couple of levels.