Free, open-source AI video generator for Mac. Run LTX-2.5 and MiniMax H3 (Hailuo) locally on Apple Silicon: text-to-video and image-to-video with sound, lip-sync, character LoRA training, songs from lyrics (YuE2) and image editing (Qwen-Image-Edit). One-click install via Pinokio. Offline: no cloud, no API key, no NVIDIA GPU.
Python ai-filmmakingai-videoai-video-generatorapple-siliconhailuoimage-to-videolip-synclocal-ailora-trainingltx-2ltx-2-5ltx-videomacosminimax-h3mlxmusic-generationoffline-aipinokiotext-to-videovideo-generation
fix(civitai): browse-image-LoRAs returned zero because the API filter was wrong
mrbizarro187cfb44971e
diff --git a/ROADMAP.md b/ROADMAP.mdindex 6ddd533..9314544 100644--- a/ROADMAP.md+++ b/ROADMAP.md@@ -117,37 +117,82 @@ The new default TC=1.8 (reverted from a wrongly-calibrated 1.0 onmay want to dial it for specific scenes. Expose `teacache_thresh`as a slider on the advanced section of the Generate form.-### `[ ]` HDR via IC-LoRA pipeline--The HDR toggle shipped in v2 (commit 2d5e0ad) but never worked: it was-wired through the regular `_pending_loras` fusion hook on the standard-T2V/I2V/HQ pipelines. The Lightricks HDR LoRA is actually an **IC-LoRA**-(in-context LoRA) — it needs the dedicated `ICLoraPipeline`-(`ltx_pipelines_mlx.ic_lora`), a reference video for the conditioning-input, AND a LogC3 pre/post transform to land 16-bit dynamic range in-the normal number range. Without all three pieces, the LoRA fuses-silently and produces no HDR effect. The UI toggle was removed in v3.0-to stop misleading users.--Proper implementation lands when we wire:-1. The `ICLoraPipeline` class into `mlx_warm_helper.py` (it exists- upstream — just needs to be hooked).-2. A reference-video source. For pure T2V/I2V, run a low-res Stage 1- render first and use that as the IC reference (matches what the- Lightricks ComfyUI workflow does).-3. LogC3 transform application in the post-process step.-4. Re-expose the HDR pill in the UI (commented out HTML at- `mlx_ltx_panel.py:17310`).--The HDR LoRA repo also ships a companion `scene-emb.safetensors` file —-need to investigate whether it's required or optional.--### `[ ]` Motion-Track and Union Control IC-LoRAs--Both are listed in `CURATED_LORAS` and pass the same gated-repo-machinery as HDR — they're also IC-LoRAs and won't work until the-above IC-LoRA pipeline plumbing lands. Add toggles + a "reference-video" picker to expose them properly once the infrastructure is in.+### `[~]` IC-LoRA pipeline support — HDR ships first, generic infra follows++Research summary (`/tmp/phosphene-walk/ic_vs_id_lora_research.md`):+IC-LoRA is just a regular LoRA delta + a training-data trick + an+inference-time input contract. The DiT itself isn't modified — what+changes is that reference frames are concatenated to noise tokens along+the sequence axis at negative RoPE positions, and the LoRA learns to+copy structure / identity / look from one half to the other via+attention. The HDR LoRA additionally bakes a LogC3 inverse transform+into the decode path to recover 16-bit linear HDR from the VAE's+`[-1, 1]` output range. The upstream MLX port already has the pieces:++- `ltx_pipelines_mlx.ic_lora.ICLoraPipeline` — generic IC-LoRA pipeline+- `ltx_pipelines_mlx.hdr_ic_lora.HDRICLoraPipeline` — HDR subclass that+ auto-detects the LogC3 config from LoRA safetensors metadata and+ saves both an SDR MP4 preview + a companion `.hdr.npz` float32 HDR+ tensor (F, H, W, 3 linear scene-light)+- `ltx_pipelines_mlx.iclora_utils.append_ic_lora_reference_video_conditionings`+ — handles reference-video encoding + RoPE positioning. Tolerates an+ empty `video_conditioning=[]` (text-driven mode: LoRA delta still+ applies, no IC reference needed).++Plan in phases, each shippable on its own:++**Phase 1 — HDR text-driven mode (v3.x).** Re-expose the HDR pill in+the UI. When checked, route the job to a new `generate_hdr` helper+action that instantiates `HDRICLoraPipeline` with the Lightricks HDR+LoRA and an empty `video_conditioning`. Output is the standard SDR+MP4 (LoRA still influences the look via weight delta) plus a sidecar+`.hdr.npz`. Force `quality=balanced` (distilled Q4) since IC-LoRAs+require the distilled checkpoint per upstream docs. Block HDR ++character LoRA stacking with a clear error message (validated as+non-functional combo for v3.x).++**Phase 2 — Reference-video conversion mode (v3.x+).** Add a+reference-video picker that appears when HDR is on, populated by:+(a) recent video outputs from the gallery, or+(b) a fresh file drop.+The reference goes into `video_conditioning=[(path, 1.0)]`. This is+the SDR → HDR re-grade path: take an existing video output, re-encode+through HDR for 16-bit linear output.++**Phase 3 — Motion-Track and Union-Control IC-LoRAs.** Two more+Lightricks IC-LoRAs at `Lightricks/LTX-2.3-22b-IC-LoRA-Motion-Track-Control`+and `Lightricks/LTX-2.3-22b-IC-LoRA-Union-Control`. Both need a+reference video with specific conditioning content (motion-track+needs sparse colored splines from a tracker like SpatialTrackerV2;+union-control needs canny+depth+pose). For Phosphene users this+means we need to either (a) ship spline/depth/pose extractors as a+pre-processing pass, or (b) accept user-provided reference videos.+Likely (b) for v3.x, (a) as a stretch.++**Phase 4 — IC-LoRA training.** Extend `lora_lab` with a paired-dataset+trainer. Each sample is `(reference_clip, target_clip)`. Training loop+builds `concat(ref_tokens_at_negative_RoPE, target_tokens)` and+computes loss only on the target half. LoRA weights file stays a+normal `.safetensors`. Add `train_type='iclora'` to the trainer UI.++**Phase 5 — Character + IC-LoRA stacking.** The prize: stack a+character LoRA (face identity) with an IC-LoRA (e.g. Union-Control)+on the same DiT. Both are weight deltas so it's mechanically possible,+but untested upstream — deltas may fight, distilled-only constraint+limits to balanced quality. Experimental; gate behind a flag until+results are validated.++**Naming note.** Don't conflate "ID-LoRA" with "character LoRA".+The published ID-LoRA (arXiv 2603.10256) is actually an IC-LoRA that+conditions on a reference image + ~5s audio for talking-head video.+Phosphene's character LoRAs are plain weight-delta LoRAs trained on+15-50 photos with a trigger word — Lightricks calls these "character+LoRAs" formally, never "ID-LoRA". Keep "character LoRA" in code and+UI to avoid the collision.++Tracking: the HDR-specific Phase 1 work landed via re-exposing the+hdr toggle (commit `<hdr-ship>`); the generic Phases 2–5 stay open+in this entry.## Mid termdiff --git a/mlx_ltx_panel.py b/mlx_ltx_panel.pyindex e0dcfd4..641eb2f 100644--- a/mlx_ltx_panel.py+++ b/mlx_ltx_panel.py@@ -2674,12 +2674,38 @@ def _civitai_request(path: str, params: dict | None = None,_CIVITAI_BASE_MODELS_BY_CONTEXT = {# Video LoRAs — the default. LTX-2.3 is the only video base we support.- "video": "LTXV 2.3",- # Image LoRAs — covers the four engines exposed in the Images tab:- # mflux (Flux.1 family), FLUX.2 Klein-Edit, Qwen-Image / Qwen-Image-Edit,- # and the HiDream-i1 family. Comma-separated lets the CivitAI API- # filter on any of these. Order doesn't matter to the API.- "image": "Flux.1 D,Flux.1 S,Flux.1 Kontext,Flux.2,Qwen-Image,Qwen-Image-Edit,HiDream-i1",+ # Verified 2026-05-20 by probing the CivitAI API: "LTXV 2.3" is the+ # only spelling that returns hits; "LTX 2.3", "LTX-Video 2.3", and+ # "LTXV2.3" all return zero.+ "video": ["LTXV 2.3"],+ # Image LoRAs — covers the families exposed in the Images tab.+ # CivitAI's baseModel taxonomy uses different names than what's on+ # their model-card UI — verified by direct API probing 2026-05-20:+ #+ # our engine CivitAI baseModel+ # ------------------ ----------------------------------+ # Qwen-Image-Edit "Qwen 2" (NOT "Qwen-Image-Edit")+ # Qwen-Image (2509) "Qwen" (NOT "Qwen-Image")+ # HiDream-O1 "HiDream-O1" (NOT "HiDream-i1")+ # Flux.1 D/S/Kontext "Flux.1 D" / "Flux.1 S" / "Flux.1 Kontext"+ # Flux.2 Klein "Flux.2 Klein 9B" / "Flux.2 Klein 4B" / "Flux.2 Klein 9B-base"+ #+ # The previous comma-separated string ("Flux.1 D,Flux.1 S,...") was+ # silently dropped by the CivitAI API — the docs accept multiple+ # baseModels via repeated query params, not commas. urlencode with+ # doseq=True (in _civitai_request) emits a list as repeated params,+ # which IS the documented multi-value format.+ "image": [+ "Qwen 2", # Qwen-Image-Edit-2511 (active engine)+ "Qwen", # Qwen-Image-Edit-2509 (legacy)+ "HiDream-O1", # HiDream-O1-Image-Dev (active engine)+ "Flux.1 D", # FLUX.1 dev (mflux)+ "Flux.1 S", # FLUX.1 schnell (mflux)+ "Flux.1 Kontext", # FLUX.1 Kontext (mflux)+ "Flux.2 Klein 9B", # FLUX.2 Klein-Edit 9B+ "Flux.2 Klein 4B", # FLUX.2 Klein-Edit 4B+ "Flux.2 Klein 9B-base", # FLUX.2 Klein base+ ],}def _civitai_search(query: str = "", nsfw: bool = False,@@ -2715,6 +2741,10 @@ def _civitai_search(query: str = "", nsfw: bool = False,base_models_filter = _CIVITAI_BASE_MODELS_BY_CONTEXT.get(context, _CIVITAI_BASE_MODELS_BY_CONTEXT["video"])+ # The CivitAI API accepts multi-value baseModels as repeated query+ # params (`baseModels=X&baseModels=Y`), not comma-separated. Passing+ # a list here triggers `urlencode(..., doseq=True)` in _civitai_request+ # to emit the repeated form.params: dict[str, object] = {"types": "LORA","baseModels": base_models_filter,