YouTube export - Incorrect clip start points

Bug #482107 reported by Pixtu
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenShot Video Editor
Fix Released
Undecided
Unassigned

Bug Description

Ubuntu Karmic 9:10, Openshot 0.9.53 via PPA (Nov 5th)

I created a video with 4 tracks playing in each of the 4 1/4 corners. Exported to YouTube preset with settings:
Project Type - Web, Target - YouTube, Video Profile - Square NTSC (should there be a PAL option?), Quality - High.

Video exported and file created. However, when the exported video is played back all the clips have started earlier than set in the timeline by varying amounts (1 was 4 secs, another was about 10 secs).

Revision history for this message
Pixtu (mail4pixtu) wrote :

Have tried the DVD pre-set and have the same problem. However, where before the clips all started early, in this case some started later than intended.

Revision history for this message
Pixtu (mail4pixtu) wrote :

I have now carried out the same exercise again and it appears to have recorded correctly. It definitely didn't before but as it now seems OK I can only assume it was a problem with my system rather than Openshot.

I suggest that this 'bug' is removed or put on hold until/if it can be repeated and maybe more info obtained to explain the issue.

My apologies for raising this as an issue at this time.

Revision history for this message
Daniel Ellis (danellisuk) wrote :

I think I am experiencing the same issue. I have imported dv video (imported from dv camera using kino). The exported video does not line up with the sound track that I was aligning the clips to. It is fine when played back during edit mode, but after export, it seems the clips are starting early.

This is the output when run from a terminal:-

on_tlbPrevious_clicked called with self.tlbPrevious
on_tlbPlay_clicked called with self.tlbPlay
on_tlbPlay_clicked called with self.tlbPlay
on_tlbPrevious_clicked called with self.tlbPrevious
on_mnuMakeMovie1_activate called with self.mnuMakeMovie
on_tlbMakeMovie_clicked called with self.mnuMakeMovie
on_cboProjectType_changed
on_cboExportTo_changed
on_cboProjectType_changed
on_btnExportVideo_clicked
AC EOB marker is absent pos=64
AC EOB marker is absent pos=72
AC EOB marker is absent pos=64
    Last message repeated 3 times
AC EOB marker is absent pos=65
AC EOB marker is absent pos=64
AC EOB marker is absent pos=102
AC EOB marker is absent pos=64
on_btnCancel_clicked
on_frmExportVideo_destroy

I think the message "AC EOB marker is absent" might have something to do with it. Looking around I found this issue in ffmpeg https://roundup.ffmpeg.org/roundup/ffmpeg/issue1060

This issue is about frames being dropped due to missing "AC EOB marker" message, and states that it was fixed in June 2009. Therefore I am not certain if the fix is included in Karmic or not.

It would be interesting to see if you are getting the same messages when exporting. I have tested exporting to DVD-PAL, DVD-NTSC and Youtube-NTSC-Square, all with the same results.

Revision history for this message
Daniel Ellis (danellisuk) wrote :

I have just exported the same video this afternoon, and just like Pixtu the issue is not occurring in my latest export. It is still the same version of software, so the issue must of occurred due to the state of the application when I last observed this issue.

I will monitor and see if this issue re-occurs and try to discover what I did in the application to cause the state. I cannot remember if I restarted OpenShot last night when I was experiencing the issue. By the way, the terminal stills includes the "AC EOB marker" messages, so they may be a red herring.

Revision history for this message
Pixtu (mail4pixtu) wrote :

My experiences are similar to Daniel.

My original output files had incorrect clip start points. On re-exporting things appeared OK.

However, I have repeated the exercise and have again experienced both incorrect and correct clip in point settings.

It seems almost random, which of course makes it very difficult to pin down and unfortunately, I do not have any concrete information to help.

Revision history for this message
Jonathan Thomas (jonoomph) wrote :

This has been fixed in the 1.0 version.

Changed in openshot:
status: New → Fix Committed
moimael (moimael)
Changed in openshot:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.