After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 603202 - PiTiVi can't load its own project format/file
PiTiVi can't load its own project format/file
Status: RESOLVED FIXED
Product: pitivi
Classification: Other
Component: General
0.13.x
Other Linux
: Normal critical
: 0.13.4
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks: 603209
 
 
Reported: 2009-11-28 07:13 UTC by Eugenia Loli-Queru
Modified: 2009-11-28 10:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
project file and debug info (1.60 KB, application/x-zip-compressed)
2009-11-28 07:13 UTC, Eugenia Loli-Queru 		Details

Description Eugenia Loli-Queru 2009-11-28 07:13:43 UTC 
Created attachment 148636 [details]
project file and debug info

Select XViD/mp3lame/AVI-muxer in the project settings' "export" dialog, and then load a clip in the timeline (it doesn't matter which), and then SAVE the project. Close down Pitivi. Now, try to reload that project file. It won't load anymore.

I am attaching here both the project file that doesn't work anymore, and the actual python errors.
Comment 1 Eugenia Loli-Queru 2009-11-28 07:14:57 UTC 
BTW, the only thing I changed in the XViD configuration panel was the bitrate: from 18 mbps, to 5 mbps. Maybe it's that that creates the project-reading problem.
Comment 2 Edward Hervey 2009-11-28 09:59:22 UTC 
For some reason... it stored a blank property (statsfile) from that encoder. I've just committed a fix in the loader to not try to load empty properties... but ideally we should figure out why it decided to store that empty property.

commit e92763592dc357cfc1c1acb4b3f03eb9291e5eb6
Author: Edward Hervey <bilboed@bilboed.com>
Date:   Sat Nov 28 10:57:27 2009 +0100

    ElementTreeFormatter: Don't attempt to deserialize blank properties.
    
    Fixes #603202
Comment 3 Eugenia Loli-Queru 2009-11-28 10:02:56 UTC 
If it was not the 5 mbps bitrate change that I did on the xvid dialog (from 18 mbps), then maybe it was the fact that I removed the xvid log filename. By default, xvid will litter my ~ with .log files, so I just took out the log filename from the xvid configuration dialog in order to not do that. Could it be it that created the empty property?