A playlist’s total length is not its dwell time. Dwell or hold time concerns how long an individual message remains unchanged. Transition concerns the change to the next message. Animation concerns movement within a message or effect. Read all three parts of the applicable requirement before configuring the controller.
Translate the words into distinct settings
| Term to resolve | Controller question |
|---|---|
| Minimum hold | How long must each complete message remain still? |
| Transition duration | How long may the change between messages take? |
| Transition effect | Is a cut required, or is a fade, wipe, or other effect allowed? |
| Animation and video | Can any element move within a displayed message? |
| Partial updates | Does a changing clock, ticker, or price count as a new message? |
| Failure behavior | What must the display do if content or controller operation fails? |
These are questions to check, not a statement that every code regulates each feature. If a requirement does not define the start or end of a hold interval, obtain an interpretation instead of assuming the software’s “duration” field uses the same timing convention.
What the federal eight-second reference actually is
The FHWA memorandum of September 25, 2007 recommends an eight-second message duration in guidance concerning off-premise changeable-message signs on routes controlled under the Highway Beautification Act. It separately addresses transition, brightness, spacing, and location, and says it does not amend applicable legal requirements.
The memo is guidance for certain highway billboards, not a rule for storefront displays. Confirm the applicable local and, where relevant, state highway requirements for the actual sign. A matching number does not prove where an ordinance’s authors obtained it.
A real rule with a required pause
Richmond Heights, Ohio writes its timing rule into section 1179.065(a)(6):
“Each message shall remain fixed for a minimum of ten (10) seconds, and individual messages shall be separated by a three (3) second pause, during which pause a still image or blank screen shall be shown.”
The same paragraph adds that “The entire message shall change at once” and bans flashing, blinking, scrolling, rotating, and movable or animated text or images. On a controller, that is two slots per message: at least 10 seconds of content, then 3 seconds of a still image or blank. A three-message loop is therefore at least 39 seconds long, not the 30 you get by adding only the three holds. A fade or wipe is also hard to square with a rule that the whole message changes at once, so ask before programming one. (Ord. 23-2014, passed May 13, 2014. We read it on September 28, 2026.)
Fictional playlist: three messages, three holds
The following timing requirement is invented for this exercise.Assume each message must remain fully static for at least 12 seconds and changes must be cuts without animated effects. A three-message playlist is configured as follows:
| Time | Displayed content | Check |
|---|---|---|
| 0 to 12 seconds | Message A | All content stays still |
| 12 to 24 seconds | Message B | Cut at 12 seconds, then hold |
| 24 to 36 seconds | Message C | Cut at 24 seconds, then hold |
| At 36 seconds | Message A returns | Check the loop boundary too |
The cycle lasts 36 seconds, but each hold is 12 seconds. Three four-second messages do not satisfy this fictional requirement just because their combined cycle is 12 seconds. A scrolling line inside Message A would also defeat the assumed static condition even if the background stays on screen.
Check what the controller actually does
Some interfaces make a slide duration include its transition; others provide separate controls. Inspect the manufacturer’s documentation and observe the actual output. For a hypothetical 12-second slot containing a two-second fade, only 10 seconds remain fully static if the fade is included. Do not count that as a 12-second static hold.
- Load the final content, not just a vendor demonstration playlist.
- Observe several cycles and time individual messages, including the last-to-first change.
- Check small moving elements, templates, emergency overrides, and scheduled playlists.
- Demonstrate the specified failure behavior and confirm settings after a restart.
- Save a settings record and identify who may change the playlist.
Agree on acceptable timing evidence with the reviewer; controller settings alone may not describe the observed output. Build a margin into the configured hold when appropriate instead of relying on an unverified setting exactly at the threshold.
Document permitted content behavior with the owner at handover. Updating the advertisements should preserve the approved timing and effects. Check brightness separately: slowing the playlist does nothing for a light limit.