Debug output?

Asked by Jan Fuchsmann

OpenShot hangs very often on my system, but I can't file decent bug reports without a debug output on the console. Is there a --debug --verbose or similar command-line flag I can use?

Question information

Language:
English Edit question
Status:
Answered
For:
OpenShot Video Editor Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jonathan Thomas (jonoomph) said :
#1

Jan, thanks for the question! We don't have any verbose debugging in OpenShot at the moment, however many of our dependencies do have logging options... such as MLT. My advice would be to try and reproduce the same steps each time you use OpenShot, and see if it hangs in the same time and place. You might also watch the System Monitor while you use OpenShot... paying attention to CPU and memory. That might give you a clue. Good luck!

Revision history for this message
Helen McCall (wildnfree) said :
#2

Hello Jan Fuchsmann,

The only debug output at present is the small amount of information you get in the console that launches OpenShot.

You can get slightly more debug output if you open a console and launch OpenShot manually from that. But the additional information is mostly of segmentation errors if that happens.

If you can supply us with information on the following:

1) which version of OpenShot you are using
2) which operating system, version, and whether 32 or 64bit (eg Ubuntu 9.04 64bit)
3) which option you chose for ffmpeg
4) as much detail as you can give on when and what causes OpenShot to hang
5) what video formats and codecs used, and how those video files were first generated

Then I can look at linking this question to any known bugs, or alternatively convert it to a bug report in its own right.

Many thanks,

Helen McCall

Revision history for this message
Jan Fuchsmann (jan-spreemusik) said :
#3

I use the latest (today) build-wizard version on Ubuntu Jaunty 32bit, removed my previous MLT installation and chose option 3 for ffmpeg.
OpenShot hangs as soon as I play back a cut mpeg2 file (I know, they're not meant to be cut), or touch a dv file on the timeline. Basically, as soon as I start using it. It seems to run on 100% CPU (well, one of 4 (dual xeon HT)).
I'll try using some other files later.
But my system is an A/V development and testing mess, so my experience does not necessarily translate to other users.

Revision history for this message
Jan Fuchsmann (jan-spreemusik) said :
#4

On a MJPEG, it hangs after play-rewind-play. Play doesn't run, when I touch the time cursor, it goes into 100% cpu and stays there.

Revision history for this message
Jan Fuchsmann (jan-spreemusik) said :
#5

Another update:
I reverted to the standard ffmpeg (option1), reinstalled everything with the build-wizzard, now I can play the mjpeg a few times more before it hangs. This time, it get less and less responsive, before grinding to a halt.
Can't find a ffmpeg of mlt log anywhere though.

Revision history for this message
Helen McCall (wildnfree) said :
#6

Hello Jan,

I think ffmpeg and MLT have been configured to give debug output, but like you I have not yet found where they are logging it.

Certainly I checked the source code and config files for MLT and it says it is using the default for providing a debug log. But I have not yet found it.

I think I will ask Jonathan when I am on my computer next.

Helen McCall

Can you help with this problem?

Provide an answer of your own, or ask Jan Fuchsmann for more information if necessary.

To post a message you must log in.