As I suspected (and noted in my post above), index.html is generated by the Juicebox skin but index2.html onwards have been created by a different skin (but I do not know which one).
It looks like you may have created an album with a certain (unknown) skin, then switched to the Juicebox skin and remade your album (without changing your output directory). The Juicebox skin generated a new index.html file (overwriting the original index.html file from having made the album with the original skin) and stopped there (as the Juicebox skin does not need any more HTML pages). The additional index2.html, index3.html, etc. files are redundant remnants from the use of the original skin and can safely be deleted (or just ignored). They do not play a part in the Juicebox album.
If you make a fresh album with the Juicebox skin (and use a new empty folder as your output directory), you'll see that index2.html, index3.html, etc. files are not generated.

As I noted above, just open your album's 'index.html' file and place the following code immediately after the function loadContent(galleryPath, galleryCount) { line:

if (jb) {
    $('.jb-bb-btn-audio').each(function() {
        if ($(this).hasClass('jb-status-playing')) {
            jb.toggleAudio();
        }
    });
}

This should hopefully work fine.

I have viewed your 'HMM Aerial Photography' gallery on my iPod Touch 6 running iOS 11.2.2 in Mobile Safari and Mobile Firefox 10.4 and the results look very similar in both browsers.

If you are referring to the browser address bar in horizontal orientation, then I think the difference you are seeing may simply be due to the different design choices that the browser developers have made. Apple (Safari) chooses to hide both the address bar and the navigation bar whereas Mozilla (Firefox) chooses to hide the navigation bar but not the address bar.

Also, please bear in mind that Juicebox is not tested on Mobile Firefox and so mobile Firefox is not an officially supported browser (although viewing galleries in Mobile Firefox should not normally cause any problems).
We support (and test in) the browsers which come bundled with mobile devices (Mobile Safari on iOS and the stock browser on Android) and also Mobile Chrome (both platforms).
Mobile Chrome is more mature (and thus more stable and predictable in its behavior) than Mobile Firefox currently is.

If you let me know some more about your problem, I might be able to help further.
Please let me know what iPhone you have, what version of iOS you are running and what version of Mobile Firefox you have installed.
Please also let me know what gallery you are referring to so that I can try to replicate the issue you are describing and see the problem for myself.
I cannot be sure that I'll be able to help further (what you are seeing might just be down to the different ways that different browsers work) but I'm certainly happy to help further if I can.

You're welcome!

You could use JavaScript to enable right-clicking within a gallery but you'd likely find that it would not make downloading a gallery image any easier. Chances are you'd right-click on a gallery image but you'd actually be clicking on an invisible overlay (including gallery elements such as the hit areas for navigation) so you'd not see the 'Save Image As...' option.
You'd need to use the Juicebox-Pro API (specifically the onInitComplete event) to wait for Juicebox-Pro to disable the right-click functionality before re-enabling it.
Try the following:

<script type="text/javascript" src="jbcore/juicebox.js"></script>
<script type="text/javascript">
    var jb = new juicebox({
        containerId: "juicebox-container",
        galleryHeight: "400",
        galleryWidth: "600"
    });
    jb.onInitComplete = function() {
        var element = document.getElementById('juicebox-container');
        element.oncontextmenu = null;
    };
</script>
<div id="juicebox-container"></div>

Please feel free to post suggestions for future versions in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked by the developers.
Thank you.

Unfortunately, as you are aware, JuiceboxBuilder has a maximum upper limit for the resolution of source images.
Just for clarification (and for any other users reading this thread), JuiceboxBuilder can handle images of no more than 4095px x 4095px when creating a gallery. This is a limitation of Adobe AIR (the platform on which JuiceboxBuilder runs). Adobe AIR uses Adobe Flash Player as its runtime environment and the largest image size which Adobe Flash Player can handle is 16,777,215 pixels. This equates to a square image of 4095 x 4095. Please see this web page for details.

If I discover any reason why the Juicebox Photoshop Plugin should work differently in CC2017 and CC2018, I'll be sure to post back in this thread.

Unfortunately, there are no configuration options available to enable the right-click context menu within a Juicebox gallery.

However, it should be possible to copy text within a gallery by highlighting it and using the Ctrl+C keyboard shortcut for the 'copy' action.

Also, if you want to allow users to download images within a gallery, then you can either:
(1) Set showOpenButton="TRUE" (in JuiceboxBuilder-Pro's 'Customize -> Lite' section) so that visitors can click the 'Open Image Button' on the gallery's Button Bar to open the currently displayed image in a new tab where it can easily be saved.
... or:
(2) Set showDownloadButton="TRUE" (in JuiceboxBuilder-Pro's 'Customize -> Button Bar' section) so that visitors can click the 'Download Button' on the gallery's Button Bar to directly download the currently displayed image.
Please see this FAQ:
How do I allow or prevent users from saving gallery images?

You're welcome!

I'm not exactly sure what you mean by this. Are you referring to the Juicebox Photoshop Plugin's interface?
If this is fuzzy (as well as your images), then maybe the problem is a graphics driver issue.
Please check that your graphics drivers are up to date.
Also, make sure that your computer is using a display scale of 100% and is not scaling content up or down at a percentage other than 100%.

Do you get the same fuzzy photos when creating a gallery by another method (for example, JuiceboxBuilder-Pro)?

Maybe you could provide a link to your gallery so that I could take a look at it for myself.
Also, if possible, please upload a couple of screenshots so that I can see what you are seeing. (You can attach them to a post here in the forum of upload them to a file sharing service such as Dropbox and provide links.)
Thank you.

With Juicebox-Pro, you can set the thumbsPosition (TOP, BOTTOM, LEFT or RIGHT) and you can also specify the maxThumbColumns and maxThumbRows.
As an example, you could set thumbsPosition="LEFT", maxThumbColumns="2" and maxThumbRows="6" to have 2 columns of thumbnails to the left of the main image.
In such a configuration, there will always be 2 columns on thumbnails but the actual number of rows will depend on the space available in the user's browser window.

Here's a sample gallery with this configuration:

For reference, a complete list of Thumbnail Options can be found here.

I've never a great deal of luck with frames on mobile devices and there are also drawbacks to loading Juicebox galleries into frames (such as the inability to expand galleries beyond the frames) so I'd avoid frames if at all possible.
For other disadvantages of loading Juicebox galleries into iframes, please see the Using an External Gallery Folder support section (scroll down to "2) Using an iframe").
Thankfully, there are several alternatives that you might like to consider.

Suggestion #1

Take a look at the Side Menu Example in the Embedding Multiple Galleries support section.
The web page is laid out using CSS (instead of frames) and the gallery index is housed in a side menu.
In this example, there is a separate web page (including the side menu) for each gallery but you could perhaps use this layout in conjunction with the Switching between Multiple Galleries using JavaScript technique so that there is only ever one web page and the galleries are loaded into a <div> container (similar to targeting an iframe) on demand.
You can view the source of the example pages in your web browser and copy/modify them as required.

Suggestion #2

You might like to take a look at the Juicebox skin for jAlbum.
jAlbum is not free but the program is quite powerful in that you can point it towards an entire directory structure and the program will create a Juicebox gallery for each and every folder in the input, all at once. All galleries will be linked together by a navigation tree in a side menu. The resulting web page does not use frames (or iframes) and also uses the JavaScript baseUrl switching mechanism to load the galleries when the tree nodes (each representing a different gallery) are clicked.

Suggestion #3

Perhaps the easiest and best option for creating a complete portfolio website from scratch would be to use Showkase.

Showkase is a PHP web application which in installed on your web server and whose interface is accessed via a web browser.
Showkase has full support for Juicebox-Pro and the galleries can be created within the application itself via its interface (or created with JuiceboxBuilder-Pro and imported).

You can create Gallery Index pages and have as many galleries listed on each Gallery Index page as you wish.
Each gallery is represented by a thumbnail image with the gallery title displayed below and the gallery is opened when the user clicks on the image.
Demo sites created with Showkase can be found here and a sample Gallery Index page can be found here.

Showkase can also create non-gallery pages (About, Basic and Contact pages) where you can add information about yourself (or any other content you like).
All of this is done automatically within the Showkase interface without the need for any manual coding at all.
You can take a look around the Showkase interface by logging into the Live Demo Admin.

Showkase can be purchased as Showkase-Standard (which comes with Juicebox-Lite) or Showkase-Pro (which comes with Juicebox-Pro).
The only difference between Showkase-Standard and Showkase-Pro is the bundled viewer (Juicebox-Lite vs Juicebox-Pro).

I hope you find this information useful.
If you have any further queries, please let me know.

A Juicebox gallery is embedded into a regular HTML <div> container (see the Embedding Guide for details) at dimensions specified by the galleryWidth and galleryHeight configuration options in the embedding code. If the gallery <div> is the only container on the web page and the gallery has a width of 100% and a height of 100%, then the gallery will fill the page.

However, the gallery does not need to be the only <div> on the web page (and the gallery's dimensions do not need to be '100%', you can use other percentage values or fixed pixel values such as '600px').
Take a look at the Side Menu and Top Menu sample pages in the Resizable Gallery support section for examples of galleries with other <div> containers on the page. These examples are full page demos (where everything is visible without the need for scroll bars) but Juicebox galleries can be embedded in regular scrolling pages, too (see here for an example). It just depends on the layout of your web page and where you position your gallery <div> (and the dimensions of the gallery) as to how the gallery will look on your page.
You can view the source of the demos in your browser and copy/modify them to suit your own needs if you like.

I hope this helps to clarify things.