logo

Live Production Software Forums


Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
bpscarbrough  
#1 Posted : Saturday, September 6, 2025 3:58:43 AM(UTC)
bpscarbrough

Rank: Member

Groups: Registered
Joined: 1/11/2024(UTC)
Posts: 25
United States
Location: Mississippi

Thanks: 3 times
Was thanked: 1 time(s) in 1 post(s)
I have a use case for a church service where we have 2 hymn books with about 500 songs.
The operator is currently typing in the song title into a lower third title to display on the screen during the live service.
No, we do not know what the songs are beforehand.

My first solution was to build a spreadsheet with hymn book name, page number, song title. So the operator would just select by page number, but the Data Source is done by row number and that doesn't work. Plus, we found there's a hard limit of 300 rows in the data source. So, you have to split the table into two for rows 1 through 300, then 300 to the end (say 550).

My workaround is to build 4 spreadsheets: 2 for each hymn book to cover the 300 row limit. Each spreadsheet has a column where I concatenated the page number ":" song title so as you get past 300 pages you can see what row has the correct song. For example, on song pages 301 and above you start over with row 1, 2, 3, ...

The operator just has to change the data source, then pick the row.

I think it will work, but it isn't very smooth.

Does anyone have any better solutions?

Thanks in advance,
Brian
nikosman88  
#2 Posted : Saturday, September 6, 2025 5:46:03 AM(UTC)
nikosman88

Rank: Advanced Member

Groups: Registered
Joined: 12/24/2021(UTC)
Posts: 728
Greece
Location: athens

Thanks: 165 times
Was thanked: 92 time(s) in 88 post(s)
Hi.i dont know how the hymn books are readable in your pc so my best bet would be to create something like a "middleman" that will read the info that book creates and then point data source to permanent read this info and pass it to vmix title.a script,a python external script,something like this.
What AI gpt says after i send your case and it after some time
Of "thinking" says
Solution 1 — Single-row “NOW” sheet lookup (no row switching)
Idea: Keep one master list, and one tiny “NOW” sheet with a single live row. vMix binds to that one row only. The operator types Book + Page, and a lookup formula returns the Title; the lower third updates automatically.
How to set it up
• In your master sheet (tab DATA) keep columns: Book | Page | Title | Key.
In Key use: =Book&":"&Page (e.g., A:301).
• In a second tab (NOW), make input cells for the operator:
• A2 = Book (A or B)
• B2 = Page (number)
• C2 = Key → =A2&":"&B2
• D2 = Title
• Lookup the title in DATA using the key:
• Excel (XLOOKUP): =XLOOKUP(C2, DATA!D:D, DATA!C:C, "Not found")
• Excel/Sheets (INDEX/MATCH): =INDEX(DATA!C:C, MATCH(C2, DATA!D:D, 0))
• In vMix → Data Sources, point your title to the NOW tab and map fields (Book/Page/Title) from that single row (e.g., row 2). You never change rows during the show.
Operator flow: Type Book and Page → the Title cell fills → lower third updates. No 300-row juggling, no source switching.
Solution 2 — vMix UTC mini-panel with search (operator-friendly)
Idea: Use vMix UTC (Universal Title Controller) to load your full hymn list and give the operator a searchable list. They type part of the page number or title, hit Enter, and UTC pushes the text to your lower third.
How to set it up
• Export your master list to CSV (or use a published Google Sheet).
• In vMix UTC:
• Set the vMix connection (IP/port).
• Add a List/Table widget bound to your CSV/Sheet.
• Add a Search box / filter so the operator can type 301 or a word from the title.
• On row select (double-click or a “Send” button), configure actions to SetText on your GT title fields (e.g., Title, Book, Page) for the target input.
• Optional: show both hymn books in one list with a Book column, or make two tabs/lists and keep a single search field.
Operator flow: Start typing → filtered list → select → lower third fills instantly. No row limits, no data-source swapping inside vMix.
Why these feel smoother:
• #1 keeps vMix fixed on one data row; the operator only changes two cells.
• #2 gives a fast, searchable picker built for live use, ideal when you don’t know the songs in advance.
Both solutions seem to me to be real and not "illussions" that's why i post them.
bpscarbrough  
#3 Posted : Saturday, September 6, 2025 6:18:09 AM(UTC)
bpscarbrough

Rank: Member

Groups: Registered
Joined: 1/11/2024(UTC)
Posts: 25
United States
Location: Mississippi

Thanks: 3 times
Was thanked: 1 time(s) in 1 post(s)
thanks. Worth a shot of exploring further. My workaround seems doable for now. I just did a short training session with the operator and she says this is easy enough.
What I knew about python I've probably forgotten by now. I wasn't aware of the vMix university title controller though. Might be a quicker path.

Appreciate your time.
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.