Skip to content

fix(models): correct lucy-2.5 resolution (720p) and realtime fps#60

Merged
AdirAmsalem merged 1 commit into
mainfrom
atlanta-v3
Jul 7, 2026
Merged

fix(models): correct lucy-2.5 resolution (720p) and realtime fps#60
AdirAmsalem merged 1 commit into
mainfrom
atlanta-v3

Conversation

@AdirAmsalem

@AdirAmsalem AdirAmsalem commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

What

Corrects the lucy-2.5 model metadata so it reflects the model's actual output. It now reports 1280×720 for both realtime and video, and realtime runs at 30fps (video stays at 20fps).

Why

lucy-2.5 is a 720p, 30fps-realtime model, but the SDK was reporting the older Lucy sizing (1088×624) and a 20fps realtime rate. Anyone reading these values — or relying on them to size their capture/render pipeline — was getting the wrong resolution and frame rate.

Usage

from decart import models

rt = models.realtime("lucy-2.5")
# rt.width == 1280, rt.height == 720, rt.fps == 30

vid = models.video("lucy-2.5")
# vid.width == 1280, vid.height == 720, vid.fps == 20

Note

Low Risk
Metadata-only registry and test changes; realtime fps alignment may change LiveKit timing for existing lucy-2.5 integrations that relied on the old 20fps value.

Overview
Updates lucy-2.5 registry metadata so it matches the model’s real output instead of legacy Lucy 2.1 sizing.

For realtime (models.realtime("lucy-2.5")), fps goes from 20 → 30 and dimensions from 1088×624 → 1280×720. For video jobs (models.video("lucy-2.5")), only resolution changes to 1280×720; job fps stays at 20.

Tests in test_models.py are updated to assert the new values. Because the realtime client wires model.fps into LiveKit, this also corrects frame-rate configuration for lucy-2.5 streams.

Reviewed by Cursor Bugbot for commit a8756e6. Bugbot is set up for automated code reviews on this repo. Configure here.

@AdirAmsalem AdirAmsalem merged commit a7df22a into main Jul 7, 2026
9 checks passed
@AdirAmsalem AdirAmsalem deleted the atlanta-v3 branch July 7, 2026 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant