Description of problem: There is a difference between indexing with 2.7 and the new 2.8 version. The version 2.7 comming with MGA8 cannot read index-files from 2.8, this is normal. But 2.8 (comming with cauldron) cannot raed the old index-files, that's awfull. Version-Release number of selected component (if applicable): How reproducible: Cut a *mp4 movie first with 2.7 and then try to fullfill your work with the new avidemux, you must re-index the movie Steps to Reproduce: 1. 2. 3.
I cannot judge that this problem is ours. Is re-indexing a big deal? Can you please first ask about it in their usability forum: https://avidemux.org/smif/index.php/board,7.0.html The simple question being "Should you expect to re-index a movie migrating from 2.7 to 2.8?" and if not - where might the problem lie? TIA
CC: (none) => lewyssmithSource RPM: avidemux-qt-2.7.6-3.mga8.x86_64.rpm => avidemux-qt-2.8Version: 8 => CauldronStatus: NEW => NEEDINFO
Hello! [quote]where might the problem lie?[/quote] The new version (2.7.8) is not backward compatible (by indexing a movie) to the version, that is distributed with MGA8 (2.7.6.). I can not cooperate with other people, who use another system that can use avidemux 2.7.8 Is it a serious problem? Cauldron offers (2021-03-09): 2.7.8. and makeing a backport for MGA8? mit freundlichen Gruessen Jürgen
I have opened a query chez avidemux: https://avidemux.org/smif/index.php/topic,19618.0.html Await a reply before pursuing further.
URL: (none) => https://avidemux.org/smif/index.php/topic,19618.0.htmlStatus: NEEDINFO => UPSTREAM
(In reply to Lewis Smith from comment #3) > I have opened a query chez avidemux: > https://avidemux.org/smif/index.php/topic,19618.0.html > Await a reply before pursuing further. Thanks doing this. Upstream answer from eumagga0x2a (Moderator): > There is no v2.8. I cannot rule out that v2.7.9 won't be relabled as v2.8, but > for now we are at v2.7.x (2.7.9 with the last release being 2.7.8 ). > > We need to force re-indexing of MPEG-TS files because old index files reflected > and perpetuated bugs in previous releases which are now fixed. Additionally, > there have been minor format changes to deal better with interlaced video. > > There should not be any reason to keep using anything older than 2.7.8. Per this, and per http://fixounet.free.fr/avidemux/download.html, Upstream latest version is 2.7.8. This is worth the upgrade. Assigning to all packagers and CC'd latest committer on this.
CC: (none) => luigiwalser, ouaurelienAssignee: bugsquad => pkg-bugsSource RPM: avidemux-qt-2.8 => avidemux-2.7.6-3.mga8.src.rpm, avidemux-2.7.6-3.mga8.tainted.src.rpmSummary: Avidemux uses a old kind of indexing => Update request: newer version of Avidemux resolves bugs in file indexingVersion: Cauldron => 8
Status: UPSTREAM => NEW
Collision! Aurélien has just launched this onwards, but here is what I was going to say - redundant, but for the record: Got the answer. 1) Versions were confused: our current normal one is 2.7.6, the latest in Cauldron is 2.7.8 - as per your comment 2. Initial reference (comment 0, SRPM) to 2.7 & 2.8 clouded the issue. 2) From upstream: > We need to force re-indexing of MPEG-TS files because old index files > reflected and perpetuated bugs in previous releases which are now fixed. > Additionally, there have been minor format changes to deal better with > interlaced video. Closing this fixed (by that explanation). If you really want to see 2.7.8 in Mageia 8, please re-open the bug setting Component to Backport
We probably should update it. It does fix CVE-2020-13904 in the bundled ffmpeg. It would be nice to get a new upstream release that updates to a newer ffmpeg branch. Does upstream have anything to say about when that might be happening?
CC: lewyssmith => (none)
Does this help? : https://avidemux.org/smif/index.php?msg=92355 worth a read for packager. -> https://github.com/mean00/avidemux2/commits/support_2.7.8 "contains only quality and stability fixes backported from the master branch onto the codebase of the 2.7.8" https://avidemux.org/smif/index.php?msg=92357 "videmux doesn't use libavformat demuxers thus an issue in playlist parsing in libavformat should not matter for Avidemux."
CC: (none) => lewyssmith
In 2021-07-17 16:05:24 CEST I asked for a new version AVIDEMUX within MGA8. Problem last year was the index. Now I found a new problem using/converting files from internet [code] Codec Internal error finding codec 0x31307661[/code] For a tryout I used avidemux_2.8.0.appImage*, not the best choise in MGA8, indexing is good, no problems with the codec, but you can hear no sound. I hope for a second chance for 2.8.0 as update/backport within MGA8 viele Grüße Jürgen
Please test v2.8 in cauldron. If everything works well we can propably update in MGA8 too.
2.8.0 updates the bundled ffmpeg 4.4.1, fixing several security issues, so yes let's update it now. It's building for Mageia 8.
Source RPM: avidemux-2.7.6-3.mga8.src.rpm, avidemux-2.7.6-3.mga8.tainted.src.rpm => avidemux-2.7.6-3.mga8.src.rpm
Note that there are core and tainted builds. libavidemux-2.8.0-1.mga8 avidemux-qt-plugins-2.8.0-1.mga8 avidemux-qt-2.8.0-1.mga8 avidemux-cli-2.8.0-1.mga8 avidemux-plugins-2.8.0-1.mga8 avidemux-devel-2.8.0-1.mga8 avidemux-cli-plugins-2.8.0-1.mga8 from avidemux-2.8.0-1.mga8.src.rpm References: http://fixounet.free.fr/avidemux/news.html http://ffmpeg.org/security.html
Assignee: pkg-bugs => qa-bugs
mga8, x86_64 Played with the application before updating. Found that the command line invocation required avidemux3_cli. Could not get that to run. Updated to the core version. The cli command worked up to a point, logging everything that was happening under the hood but crashing eventually with the message - [ADM_audioByName] 19:40:05-472 Device not found :PulseAudioS [...] [destroy] 19:40:05-473 Destroying preview [deleteAll] 19:40:05-473 [Editor] Deleting all videos [deleteAll] 19:40:05-473 [Editor] Deleting all videos Normal exit [uninstallSigHandler] 19:40:05-473 Removing signal handler [abortExitHandler] 19:40:05-473 already done, nothing to do 19:40:05 Call terminate!!! No such problems running it from the application menu. Loaded an MP4 file, chopped sections off the front and back of the video and saved the middle bit as an MKV file, which played fine in totem or vlc. Trying the tainted version later.
CC: (none) => tarazed25
Continuing from comment 12: After updating all packages avidemux3_cli crashed again. The menu invocation worked perfectly for removing a section of an MP4 film. The files saved as MKV played fine in vlc. From my point of view there is no regression but it is possible that the cli failure is a user problem.
Ugh! That last remark applied to the tainted version.
MGA8-64 Plasma on Lenovo B50 in Dutch Loaded the names in QArepo, and that has both core and tainted selected, core cannot be switched off. So i really don't have any idea what I've really installed, I prresume the core since tainted appeared nowhere in the names. Tested by running the avidemux3_qt5 and I could resize a videoclip OK. Went for help on the CLI and found some example in http://avidemux.sourceforge.net/doc/en/command.xml.html So launched from CLI: $ avidemux3_cli --load noor20112008.11.21_10-44-30.avi -audio-process --audio-normalize --audio-resample 44100 --audio-codec MP2 --audio-bitrate 224 --output-format PS --video-process --vcd-res --video-codec VCD --save testavodemux.mpg --quit and the reulting mpg file plays OK. Now removing the insstalled packages and select Tainted Updates Testing in MCC, disabling QARepo. Contnuing......
CC: (none) => herman.viaene
Tested Tainted (after deleting the result files from above) and found: one minor difference in avidemux3_qt5: in the core version when saving a section of a clip it automatically proposes to save as <filename>_edit.avi, while in the tainted versions it proposes the plain filename and you have to adjust the filename if you want to preserve the original file. The avidemux3_cli test produced the same result as with the core version. As far as I am concerned, this is OK, but I prefer Len reviewing this result to give the OK.
@Herman, re comment 5: I added the .tainted string after mga8 and that seemed to work OK. $ rpm -qa | grep avidemux would show which RPMs are installed.
And of course you can also look at <local repo>/x86_64 or i586. (This is called "teaching your grandmother how to suck eggs")
About the OK. I am reluctant to go ahead because of the problem with command line invocation. Maybe something more is required on the command line. Dunno.
Wrong command, that's what. $ avidemux3_qt5 YosemiteII.mp4 brings up the gui as required. Sending this on.
Whiteboard: (none) => MGA8-64-OK
Glad you found what the issue was, Len. Validating.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => advisoryCC: (none) => davidwhodgins
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2022-0039.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED