[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57020] [octave-forge] (video): missing VideoW

From: Pantxo Diribarne
Subject: [Octave-bug-tracker] [bug #57020] [octave-forge] (video): missing VideoWriter
Date: Tue, 8 Oct 2019 07:59:05 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #1, bug #57020 (project octave):

This looks very promising. I tested the updated code, for VideoWriter only,
and it now works well for non synthetic data.
As for the roadmap, here are in IMHO the missing features that should not be
hard to have before a first realase for the VideoWriter:
* most properties should be read-only (SetAccess = "private"): ColorChannels
(codec specific), Duration, FileFormat (codec specific), FileName/Path (fixed
at object instantiation), FrameCount, Height/Width (fixed by the first
provided frame), VideoBitsPerPixel/VideoCompressionMethod/VideoFormat (codec
* increment FrameCount and Duration after each successful call to writeVideo,
* allow passing frames or frame arrays  directly to writeVideo, without having
to extract the "cdata" field manually,
* allow passing arbitrary image data types even if we end up converting them
internally to whatever is prefered for the chosen codec, e.g uint8 for RGB
24bits video formats.

As for the available output formats, I am no expert so in this area, I am
generally happy with whatever the default is. So we just need to make a
sensible choice of 1 or 2 widespread formats that can be read with the default
viewer for the main platforms. 


Reply to this item at:


  Message posté via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]