Add stitched stereo import - #2019
Merged
Merged
Conversation
Load side-by-side stereo media as a left/right stereo dataset. Desktop reads the shared media in place and crops per camera; VIAME jobs and the interactive service get split halves on demand. Web uploads to each camera and a server job keeps that camera's half.
Jobs pass the stitched media with VIAME's stitched_side reader settings; tagged paths go to the interactive services unchanged. Removes the ffmpeg split cache and per-frame crops.
Jobs set inputN:video_reader:image_list:crop_left/right, keeping each pipe's own reader config. Pipelines and indexing on stitched video are refused until VIAME's video reader can crop.
Member
Author
|
Example imagery - https://data.kitware.com/api/v1/item/595a80058d777f16d01e993d/download |
…ions Sets crop_left/right on both the image-list and vidl_ffmpeg readers of each input.
BryonLewis
force-pushed
the
dev/stitched-stereo
branch
from
October 5, 2026 18:45
fb48b25 to
2a2c985
Compare
BryonLewis
force-pushed
the
dev/stitched-stereo
branch
from
October 5, 2026 18:52
2a2c985 to
3f09a6a
Compare
BryonLewis
self-requested a review
October 5, 2026 19:48
BryonLewis
approved these changes
Oct 5, 2026
BryonLewis
left a comment
BryonLewis
left a comment
Collaborator
There was a problem hiding this comment.
esktop vs Web processing for stitched stereo / multicam
On desktop, we keep the local files in place and pass a crop parameter into VIAME when pipelines run against each camera. That works well for the single-user desktop case.
On web, that work runs as a post-processing step instead. I also updated the other multicamera imports to follow the same pattern. Previously, the browser UI blocked while multicam datasets were being transcoded or processed. Import now returns the dataset list immediately and shows a processing indicator.
This should also make future import-related tasks easier to plug into the same flow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stitched stereo = one image sequence or video whose frames hold the left camera in the left half and the right camera in the right half. New Stitched option in the Stereo import dialog loads it as a normal
left/rightstereo dataset.Desktop (media is never copied or re-encoded)
stitchedSide.inputN:video_reader:image_list:crop_<side>=trueandinputN:video_reader:vidl_ffmpeg:crop_<side>=true, so the same pipes run on stitched and separate-camera data and keep their own reader config.#stitched=<side>, which VIAME's services crop on load.crop_left/crop_rightoptions on kwiver's image-list and vidl_ffmpeg readers and VIAME'sviame.core.stitched_media(in progress, not yet merged).Web
postprocesstakesstitchedSideand a newsplit_stitched_mediajob crops/transcodes in place, so the stored dataset is ordinary stereo.Notes
🤖 Generated with Claude Code