I'm not a dev but can partially respond to some of the things you said,
if that can be of help:
> It looks like Pitivi unpacks the entire 4 hours from the transport
> stream and decodes the A52 audio to produce the audio level graph on
> the
> timeline (which did not contribute to my project). In my case this
> was
> expensive of CPU time, and the program seemed to do it over frequently
> when clips were moved around.
Try that with PiTiVi git (or 0.13.4 when it comes out in the coming
weeks). It uses 1) faster, different waveforms, I think 2) does not
regenerate waveforms for each zoom level 3) does the waveforms for all
the audio channels combined into one, instead of, say, 6 waveforms. Not
only does it look better, this also helps performance.
> It looks like some aspect of Pitivi was not able to do random access
> in
> the transport stream, or was not able to make effective use of the
> feature. Or possibly one of the codecs was unable to do random
> access.
> I don't know how to dump the exact pipeline that Pitivi was using.
Yeah, at the time I'm writing this, GStreamer doesn't yet handle
MPEG2-TS properly; see:
https://bugzilla.gnome.org/show_bug.cgi?id=585077
> PiTiVi looks like a very nice program that could do what I need, but
> I guess I choked it by giving it too big of a file for the resources
> available.
Maybe related: https://bugzilla.gnome.org/show_bug.cgi?id=593377
For a custom search query for performance/memory-related bugs, see also
http://www.pitivi.org/?go=bugs
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Pitivi-pitivi mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pitivi-pitivi
