Jump to the full narration script · Download the original script (.txt)
Watch this tutorial on YouTube. Use the player’s CC control for English captions. The complete narration is also available below.
Full narration script
Every spoken line, verbatim, with the original scene timestamps.
Auto-KJ-Analytics-walkthrough
Source-rendered simulation of actual current main UI. Layout adapted for readability. All singers, songs and service outcomes are fictional. No native file, cloud or audio hardware operations are performed. AI-generated narration.
00:00:00.000 | analytics-01
Analytics helps you understand the show and prepare a report for the venue. It contains several kinds of information: the current show snapshot, permanent performance history, exports filtered by night and gig, and songs singers saved as favorites. The first step is to choose which question you are answering, because these controls do not all share one filter.
00:00:23.833 | analytics-02
At the top, Tonight's proof sheet describes the current show. Press Refresh and read any error before interpreting the cards. Completed counts finished performance events. Queued includes requests waiting and the currently in-progress request. Completion rate compares completed events with that combined total. For a simple fictional example, six completed and four queued or in progress gives sixty percent. The number is a worked example, not a result from a real show.
00:00:54.417 | analytics-03
Singers counts tracked show identities, with active and paused figures. It is not a venue attendance count. Average wait is an estimate from the current line and track durations. Peak hour is the local hour with the most completed performances. Applause counts taps attached to completed songs, rather than distinct audience members. Keep those labels when you explain the results to someone else.
00:01:20.583 | analytics-04
Top singers shows who completed songs, their group participation, and applause. Top songs shows tracked performed songs and applause. The screen limits each of those lists to twelve rows. Hourly activity shows the distribution of completed turns, and the Performance log lists the latest fifty events with singers, title, time, solo or group type, and applause. A duet is one completed turn, while both singers can receive participation credit.
00:01:49.250 | analytics-05
The header gives you quick ways to take the current snapshot away. Copy CSV copies the live performance rows. Copy Scoped CSV adds the date and current gig label, summary metrics, and hourly activity. Its name does not mean it uses the historical selectors below: it still reports the current show. Check the date if your show crossed midnight. Copy JSON copies the underlying live analytics object.
00:02:15.417 | analytics-06
Print Report opens a concise printable summary of the current show. It includes the scope, totals, estimated wait, hourly activity, and a staffing note. This differs from the historical HTML export we will use later. After copying, wait for the confirmation, paste into the intended destination, and inspect the result. A clipboard error means the copy did not complete. If the print window is blocked, read the pop-up message rather than assuming a report was created.
00:02:44.750 | analytics-07
Now open History and Venue Reports and find its History section. Use the History date picker to choose a single night or All time combined. You can also click one of the recent-night bars; the chart shows up to the latest thirty nights. Check the heading after selecting a date. A single night shows its set list chronologically, while the all-time view shows the latest one hundred history rows. The Source column helps distinguish imported records.
00:03:13.917 | analytics-08
Be careful comparing history totals with the live Completed card. Permanent history stores singer credits, so a duet can occupy two rows, one for each singer. The History browser counts those rows. The historical report export groups matching song and time credits back into a single event. Two figures can differ because they count different things, even when both come from the same show.
00:03:39.500 | analytics-09
Most sung answers which songs each singer actually performed. It groups the loaded history rows by singer, artist, and title, then sorts by count and recency. Search for a singer, artist, or song and read Times sung and Last Performed. This view follows the date already selected in History. It has no separate night selector of its own.
00:04:01.667 | analytics-10
There is an important limit in the all-time mode. Because the loaded log contains only the latest one hundred history rows, Most sung is not a complete lifetime leaderboard there. For a specific night's counts, select that night in History first and then open Most sung. The all-time History summary uses broader queries, so do not assume those summary totals and the Most sung counts have identical coverage.
00:04:28.333 | analytics-11
Saved favorites answers a different question: which songs singers deliberately starred in the phone app. It includes eligible account holders from this host's shows and songs in the host's catalog. Guests cannot save favorites. The table lists a song, the number of distinct singers who saved it, and their names. A song can be a favorite even if someone has never performed it.
00:04:52.917 | analytics-12
This view needs host sign-in and an internet connection. Read the error and use Retry if loading fails. It is not filtered to the selected history night or current gig. Once a successful result loads, it stays cached while this Analytics tab remains mounted. Header Refresh only reloads the live show. To fetch updated favorites, leave Analytics, return, and open Saved favorites again. Most sung and Saved favorites also share search text, so clear the filter if the next view seems unexpectedly sparse.
00:05:25.417 | analytics-13
For a venue handoff, return to History and Venue Reports and find Export a night or gig. Choose the report night, then choose the gig. Read both controls again. This export date is separate from the date used by the history browser, and the gig options come from gigs already represented in permanent history. Older untagged records appear under All gigs only.
00:05:48.167 | analytics-14
Choose Export CSV for a spreadsheet report or Export Printable Report for a self-contained HTML file. Pick the native save destination and wait for the saved-path message. Then open the file. Check the date and gig heading, a few familiar songs and singers, the completed-song total, and the hourly activity. If you need a PDF, open the HTML in a browser and print it to PDF. The export itself produces HTML rather than a PDF.
00:06:16.000 | analytics-15
Historical wait is an estimate too, but it uses a different method from the live card. It takes the average spacing between completed events and multiplies by the number of singers minus one. There are no historical queue timestamps behind that estimate. A multi-night scope can include long gaps between shows, so a single night and gig is usually the useful choice for explaining one venue session. Staffing text is a rule-based suggestion, not a measurement of how many staff the venue actually needed.
00:06:48.833 | analytics-16
Finish by checking the report's intended scope and the actual output. A copied confirmation, a saved file that opens, and sample rows matching the selected night give you concrete checks. If a historical section or gig list unexpectedly disappears, do not call it zero history without investigating; some load failures are only logged in this source. Keep completed turns, singer credits, estimated waits, and saved favorites distinct in the final explanation. This is a source-reviewed version 1.30 guide, and real native export, printing, clipboard, and cloud checks remain to be completed on the intended host.