> I have two laptops. One is a 2.5GHz dual-core w/ 4G ram. It's running
> Ubuntu 9.10 and only auto-installs Pitivi 0.13.3. The other laptop is
> a single-core 1.6GHz w/ 1.5G ram. It's running Ubuntu 10.4 and
> auto-installs the newer version of Pitivi (not handy or I'd tell you
> the exact version number).
Beware that the latest version is 0.13.5, and older versions are
unsupported as we the project doesn't have the manpower to maintain
multiple simultaneous versions.
> That means working with a project and the rendering is all slower. I'm
> not complaining (esp about the rendering part, not much you can do to
> speed it up),
There's a couple of known performance issues, some of which may have
improved a little bit in 0.13.5; See also
http://pitivi.org/wiki/Performance_problems_in_0.13.4 (may be outdated)
> I think one adjustment could help on the compilation part: have a
> Edit->Preferences where you can turn off the "preview frames" in video
> and audio
There already is an option for that, exactly where you said it should
be :) look for "thumbnails"
They're quite a bit slow, there probably is something that could be done
to improve the performances of thumbnail generation, but afaik nobody is
working on it currently.
> Maybe when a source is added to the clips list it can be rt-clicked
> and selected to "not preview the framed-preview" so that a person can
> select which clips are important to be previewed in the timeline and
> which ones aren't. To build on that idea, a stream can be rt-clicked
> in the timeline and selected to preview or not preview in the
Nah. Adds ui complexity for nothing. It's a performance/optimization
problem, putting this onto the shoulders of the "user" is not a
solution, it's an excuse for poor performance :) I've seen software out
there that does thumbnailing for video and waveforms *really* fast, so
I'm sure something can be done here. To me, it's all or nothing.
> Another thing on the frame-preview in the timeline - while pitivi is
> actually rendering the project the timeline preview should be
> disabled, as pitivi advances through the frames and the timeline
> advances, it eats up cpu trying to build the newly viewed timeline
> segment's frame-previews. Why does it need to do that? It's just
> taking cpu away from the important process - the render.
Please test with pitivi 0.13.5, and if this is still the case I guess
you should comment asking to reopen
> The second issue I'd like to discuss is actually a bug. I have this
> one video that is 1:50 long (that's one hour and 50 minutes). The
> first 30 minutes I needed to overlay the video with still-shots. That
> worked just fine (except it takes about 2 hours to position the stills
> correctly because the timeline frame-preview issue discussed above).
> The render takes well over 24 hours (again, I can live with that, I'm
> on an older laptop), but when it's done the video and the audio don't
> match up.
Try with 0.13.5, there were significant problems with still-shots in
0.13.4... should be fixed now, if not, you should file bugs :)