Description of problem: There is a warning: "TOO SHORT The video have been saved but seems to be incomplete" Version-Release number of selected component (if applicable): avidemux-qt 2.6.6. 2.mga4 How reproducible: Take a video from TV about 2,3GB make a cut before and behind to take the main video and try to save it as a DVD compliant stream. "Mpeg PS Muxer (ff)" Steps to Reproduce: 1. using avidemux mga4 --> warning appears, you dont get a video 2. using avidemux3 suse 13.1 ---> the same procedere 3. using avidemux mga3 ---> enjoing without problems please make a backport of avidemux 2.5.tainted suse offers such a version as "avidemux" without the number "3" ITS ALSO WORKING. "gdb avidemux" doesnt offer a bug :( see the pictures https://forums.mageia.org/de/viewtopic.php?f=16&t=1948 they tell more than 1000 words ;) Reproducible: Steps to Reproduce:
Component: New RPM package request => RPM PackagesAssignee: bugsquad => fundawangSummary: you cannot save a DVD compliant stream => avidemux: you cannot save a DVD compliant streamSource RPM: (none) => avidemux-qtSeverity: major => normal
Jürgen: can you test with the Mageia 5 Beta? Funda Wang: do you have any workaround for this bug?
CC: (none) => olivier
(In reply to Olivier FAURAX from comment #1) > Jürgen: can you test with the Mageia 5 Beta? Hello! No, I'm still waitung for MGA5, the 2 Computers I'am using should not run with a Beta-soft. > Funda Wang: do you have any workaround for this bug? ...still not.
CC: (none) => doktor5000
Hello! You should take a look to this tread: https://forums.mageia.org/de/viewtopic.php?f=16&t=2382&p=26542#p26542 Crash Assert failed :O at line 313. file /home/iurt/rpmbuild/BUILD/avidemux_2.6.6/avidemux/qt4/common/ADM_editor/src/ADM_segment.cppADM_backTrack ADM_EditorSegment::getRefVideo(int) ADM_Composer::getVideoInfo(aviInfo*)
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD