Started by mederi, July 22, 2019, 01:58:44 PM
Quote from: mederi on August 08, 2019, 09:46:08 AMJust one more catch: Avidemux reports wrong frame type of several frames in P-FRM (04) row of frames in provided video sample. There are 5 more I-FRM (04) frames recognised (each 16 frames) when moved manually frame-by-frame.
Quote from: mederi on August 10, 2019, 11:51:17 AMI have just suggested that Xvid encoder deserves its own XVID FourCC by default and a fix would be probably simple (false -> true) somewhere in Avidemux code.
QuoteI can nonfirm that avidemux_2.7.4 r190810_win32 has solved the reported issues.
QuoteNext I would like to ask you, whether it is a correct behaviour (not a bug) that Avidemux is always "Unpacking bitstream" when loading an mpeg4 video even if it does not contain a packed bitstream. Avidemux 2.5 contains a detection of PB.
Quote from: eumagga0x2a on August 10, 2019, 04:47:09 PMWhile we're at it, it would rather make sense IMHO to add an option to the xvid plugin to enable frame dropping.
QuoteIndicates presence of AVI"[D]" (dup or dropped) frames: zero length AVI chunks that instruct the player to "repeat previous frame".
QuoteIt is just a debug message which is always printed when the function which checks for PB is not about to return an error.
QuoteI confirm the issue, it is a bad one (crash on Win10 too), trying to fixthat ASAP.
Quote from: mederi on August 15, 2019, 10:43:27 AMThere is just another version of AVI that other softwares have to cope with.
QuoteSo it seem that there are 2 types of frame dropping: Xvid stream (NVOP DF) and AVI container related (AVID). Probably AVID is better supported nowadays.