Expected order of images

[kftb]

Describe

Setup immich kiosk and am unsure what the expected behavior is and whether what I am seeing is working as intended or a potential bug.

Expected behavior

• I provide the album UIDs in the config
• I set "album_order" to "oldest"
• immichkiosk picks the oldest album and then shows the images within sequentially. Once all images have been shown, it goes to the next album.

Actual behavior

• Immichkiosk is mixing images from both albums in an order without a clear pattern, e.g.
• Pic from Album A
• Pic from Album A
• Pic from Album B
• Pic from Album A
• Pic from Album B
• Pic from Album B
• Pic from Album A
• Pic from Album B

Your Kiosk version

v0.24.0
Immich: v1.41.1

Your Kiosk installation

• Docker Compose

Your Kiosk configuration (ENV / config file)

immich_users_api_keys: {}
immich_api_key: REDACTED
immich_url: REDACTED
immich_external_url: ""
menu_position: top
time_format: "24"
date_format: YYYY-MM-DD
clock_source: client
theme: fade
layout: single
sleep_start: ""
sleep_end: ""
album_order: oldest
date_filter: ""
image_fit: contain
image_effect: none
transition: none
progress_bar_position: top
custom_css_class: ""
image_time_format: ""
image_date_format: ""
user: []
people: []
excluded_people: []
albums:
    - REDACTED
    - REDACTED
excluded_albums: []
tags: []
excluded_tags: []
dates: []
hide_countries: []
like_button_action:
    - favorite
hide_button_action:
    - tag
weather: []
iframe: []
webhooks: []
blacklist: []
offline_mode:
    max_size: "0"
    number_of_assets: 100
    parallel_downloads: 1
    expiration_hours: 0
    enabled: false
kiosk:
    version: 0.24.0
    config_validation_level: error
    password: ""
    redirects: []
    port: 3000
    fetched_assets_size: 1000
    http_timeout: 20
    behind_proxy: false
    disable_url_queries: false
    disable_config_endpoint: false
    watch_config: false
    cache: true
    prefetch: true
    asset_weighting: true
    debug: false
    debug_verbose: false
duration: 30
font_size: 100
live_photo_loop_delay: 0
image_effect_amount: 120
background_blur_amount: 10
age_switch_to_years_after: 1
fade_transition_duration: 1
cross_fade_transition_duration: 1
show_user: false
show_owner: false
disable_navigation: false
disable_ui: false
frameless: false
show_time: false
show_date: false
disable_screensaver: false
hide_cursor: false
sleep_icon: true
sleep_dim_screen: false
disable_sleep: false
show_archived: false
require_all_people: false
album_video: false
memories: false
live_photos: false
use_original_image: false
background_blur: true
show_progress_bar: false
custom_css: true
show_album_name: true
show_person_name: false
show_person_age: false
show_age_year_unit: false
show_image_time: false
show_image_date: false
show_image_description: false
show_image_exif: false
show_image_location: false
show_image_id: false
show_image_qr: false
show_more_info: true
show_more_info_image_link: true
show_more_info_qr_code: true
optimize_images: false
use_gpu: false
use_offline_mode: false

Additional context

Add any other context about the problem here.

[damongolding]

It states on the documentation that the album order (if multiple albums are configured) that they are picked at random.

The album_order option refers to how the assets of the picked album are displayed.

[kftb]

I am still unclear what the expected order of images is. If it picks an album at random, is it still expected to first go through all pictures within that album before moving onto the next one?

[damongolding]

No, an album is randomly picked on each frame/asset.

[kftb]

So, on each frame:

• kiosk picks a random album from the provided ones
• then, within that album it picks an image based on the album_order property.
• assuming it is "oldest", once it comes back to that album, it will select the second oldest picture then. Is that correct?

That aside, any chance to add a config option that locks a single album in and then goes through all its pictures (random | oldest | newest), before it moves on to the next album?

[DonTorno]

Was curious about this too and would be very happy if this feature/config could be implemented.