PowerPoint upload rendered to video, with animations (slide images as fallback) #33
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage#33
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Convert .pptx to one image per slide at upload (LibreOffice headless, then the PDF path).
Done when
A .pptx upload becomes one item per slide.
Depends on
#15
Plan
plan/server/media-pipeline.md (Documents)
Routing/Hold: no agent is routed to this issue automatically. To take it yourself, assign yourself. Vivy removes the hold when it is handed to an agent.Created for GRI-1818 from
plan/overview/roadmap.mdand the MVP plan on GRI-1761.Field feedback on GRI-1960: users want PowerPoint with its animations and transitions. Page images lose those. Approach is an open question to the product owner on GRI-1960 (likely: video export from PowerPoint, played as video). Do not start until that is answered.
Product owner decision (GRI-1960, 2026-11-13):
So the requirement is: the user uploads a .pptx; no export step in PowerPoint. How the server shows it is our choice.
Proposed in two steps:
Still held: one active item per engineer.
PowerPoint conversion to page imagesto PowerPoint upload rendered to video, with animations (slide images as fallback)Scope change from the product owner (GRI-1967, 2026-11-13 17:58): "The only reason they want to use PowerPoint is because of the animation."
So slide images alone do not meet the need. The target of this issue is now:
.pptxupload becomes one MP4 (H.264) that keeps slide transitions and animations. Render it on the server: LibreOffice Impress slideshow on Xvfb, recorded by ffmpeg. The player already plays video (crates/client/src/renderer/video.rs, GStreamerplaybin), so this does not wait on #39 if the output is H.264 MP4 at the screen resolution.Points to measure and report here, on real decks:
soffice,Xvfb,ffmpeg), resolution and timeout from configuration, not hard-coded (GRI-1884).Report the fidelity result here before building the full upload flow. If LibreOffice is not good enough, the alternative is a render worker with real PowerPoint (Windows + Office,
Presentation.CreateVideo); that is a product-owner decision, not ours.Progress on the upload side, 2026-11-14 (GRI-1998 / this issue):
The step-1 slice of the two-step plan is implemented and green locally:
POST /api/v1/medianow accepts the OOXML presentation content type and converts a.pptxthrough LibreOffice headless (soffice --headless --convert-to pdf) into a PDF, which the existing PDF page renderer turns into one image per slide. The catalog then stores the original (kind = "document") plus onekind = "document_page"row per slide — the same shape a PDF upload already has, so a deck becomes one item per slide with no user-facing export step.Conversion failures (missing / failing / timing-out converter, or no PDF produced) come back as
400 invalid_pptx, and nothing is catalogued when conversion fails — the same no-half-playlist rule as PDF (AC-3-06).Real-world finding this run: LibreOffice 24.2.7.2 exits 0 even when it cannot load the source and writes no PDF; the "no output" case is now an explicit error instead of trusting the exit status.
Frontend: the upload picker now accepts
.pptx, and a PowerPoint upload is paged like a PDF.Gates:
cargo fmt --check, workspace clippy-D warnings, workspace rust tests, and the frontend check + build all pass locally.Open, per the GRI-1967 scope decision: the primary target is the animation-bearing MP4 (LibreOffice Impress slideshow on Xvfb recorded by ffmpeg, H.264 + AAC MP4), with slide images as fallback. The video render, its fallback wiring and fidelity measurement are the next slice; client H.264 playback already exists, so an H.264 MP4 at screen resolution should not wait on GRI-39.
@voidgazer — product owner decision (GRI-1960, 2026-11-14): work due by Monday moves to faster agents.
Your other issues (#39, #54) are not due Monday and stay with you.
All remaining work on this issue is on #189 (aetherforge, PR #190): the MP4 render, the slide-image fallback, the .pptx upload in the front end and the fidelity report. PR #191 closed as superseded. Closing this so there is one PowerPoint issue, not two.