PowerPoint upload rendered to video, with animations (slide images as fallback) #33

Closed
opened 2026-11-07 18:58:06 +00:00 by vivy · 6 comments
Owner

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.md and the MVP plan on GRI-1761.

## 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.md` and the MVP plan on GRI-1761.
Author
Owner

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.

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.
Author
Owner

Product owner decision (GRI-1960, 2026-11-13):

the user need to be able to upload a PowerPoint. If it is rendered as a video in the backend, that doesn't matter. But we will also still accept video uploads. But are not needed yet in this phase.

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:

  1. Now: .pptx → slide images on the server (LibreOffice headless), shown like PDF pages. Upload works for the campus test. No animations.
  2. Next, a spike: .pptx → MP4 on the server, so animations and transitions play. Candidate: LibreOffice Impress slideshow under Xvfb, recorded with ffmpeg. Fidelity for PowerPoint animations is partial and must be measured on real decks from the campus before we promise it. Needs video playback on the client (#39) — video upload is not needed in this phase.

Still held: one active item per engineer.

**Product owner decision (GRI-1960, 2026-11-13):** > the user need to be able to upload a PowerPoint. If it is rendered as a video in the backend, that doesn't matter. But we will also still accept video uploads. But are not needed yet in this phase. 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: 1. **Now:** .pptx → slide images on the server (LibreOffice headless), shown like PDF pages. Upload works for the campus test. No animations. 2. **Next, a spike:** .pptx → MP4 on the server, so animations and transitions play. Candidate: LibreOffice Impress slideshow under Xvfb, recorded with ffmpeg. Fidelity for PowerPoint animations is partial and must be measured on real decks from the campus before we promise it. Needs video playback on the client (#39) — video upload is not needed in this phase. Still held: one active item per engineer.
vivy changed title from PowerPoint conversion to page images to PowerPoint upload rendered to video, with animations (slide images as fallback) 2026-11-13 17:59:51 +00:00
Author
Owner

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:

  1. Primary: a .pptx upload 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, GStreamer playbin), so this does not wait on #39 if the output is H.264 MP4 at the screen resolution.
  2. Fallback: when the render fails or times out, fall back to one image per slide (the original plan), and say so in the panel.

Points to measure and report here, on real decks:

  • Which effects render correctly, which differ, which are missing.
  • Click-triggered animations. A screen has nobody to click. Decide: use the deck's own timings, or advance each click step after a fixed delay. Report what LibreOffice does with each.
  • Render time per deck and peak memory on the build host.
  • Every path and binary (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.

**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: 1. **Primary:** a `.pptx` upload 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`, GStreamer `playbin`), so this does **not** wait on #39 if the output is H.264 MP4 at the screen resolution. 2. **Fallback:** when the render fails or times out, fall back to one image per slide (the original plan), and say so in the panel. Points to measure and report here, on real decks: - Which effects render correctly, which differ, which are missing. - **Click-triggered animations.** A screen has nobody to click. Decide: use the deck's own timings, or advance each click step after a fixed delay. Report what LibreOffice does with each. - Render time per deck and peak memory on the build host. - Every path and binary (`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.
Member

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/media now accepts the OOXML presentation content type and converts a .pptx through 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 one kind = "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.

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/media` now accepts the OOXML presentation content type and converts a `.pptx` through 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 one `kind = "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.
Author
Owner

@voidgazer — product owner decision (GRI-1960, 2026-11-14): work due by Monday moves to faster agents.

  • This issue is now step 1 only (.pptx → slide images). You have it green locally, but no branch is on the forge. Push it and open the PR now, with no further work on it. That is all that is left for you here.
  • The MP4 / animation render moves to #189 (aetherforge). Do not start it.

Your other issues (#39, #54) are not due Monday and stay with you.

@voidgazer — product owner decision (GRI-1960, 2026-11-14): work due by Monday moves to faster agents. - **This issue is now step 1 only** (.pptx → slide images). You have it green locally, but no branch is on the forge. **Push it and open the PR now**, with no further work on it. That is all that is left for you here. - **The MP4 / animation render moves to #189 (aetherforge).** Do not start it. Your other issues (#39, #54) are not due Monday and stay with you.
Author
Owner

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.

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.
vivy closed this issue 2026-11-14 10:28:56 +00:00
Sign in to join this conversation.
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grimoirix/grimoire-of-digital-signage#33
No description provided.