Author Topic: These get a 'too short'  (Read 2733 times)

twinsun

  • Jr. Member
  • **
  • Posts: 76
These get a 'too short'
« on: April 29, 2015, 10:01:55 PM »
Here is a sample of a video getting a “too short” ending.
As I regularly got few of them (I cut a frame before and after the culprit one to solve the situation), I submit these strange ones.
These "frames causing a crash, have a time ending by '1', ie 00, 40, 80, !!81, 120.
 
A sample :
    Munch_(AVDM sampled 20s).mp4 :
https://drive.google.com/open?id=0B7UOzqUbGLumVjBmVDdFZWZ1bDg&authuser=0

“Too short” ending, an edit example :
    Munch_(CropRes-Copy)_(gets too short @14s).mp4 :
https://drive.google.com/open?id=0B7UOzqUbGLumaGl6bWpIOFh0Z1U&authuser=0

Jan Gruuthuse

  • Hero Member
  • *****
  • Posts: 6051
Re: These get a 'too short'
« Reply #1 on: April 30, 2015, 05:56:21 AM »
I did test your sample with lavcodec and vdpau. It seems to me the issue is there when you choose in Output Format: MP4 muxer and not with MP4v2 muxer.
tested with current avidemux 2.6.8 (49dced1)

Take into account the source video has odd format 1920 x 1088 and swsResize is showing 724
Set  swsRisize filter in Resize Dimensions
[v] Round to the Nearest Multiple of 16
and select Width to 1280, Height should adjust to 720.

Resized sample to 1280 x 720: 3.5 MB download <- click (limited time available only)
« Last Edit: April 30, 2015, 05:57:58 AM by Jan Gruuthuse »

twinsun

  • Jr. Member
  • **
  • Posts: 76
Re: These get a 'too short'
« Reply #2 on: May 06, 2015, 05:01:36 AM »
Thanks for trying.

Quote
Take into account the source video has odd format 1920 x 1088 ...
No, the sample source format I provide is 1080.
The 1088 you see opening, is the rounding by 16 of 1080 by AVDM with some 1080 videos (still a issue).
But not a problem, since 'crop filter' hides it, cropping the 8 ghost bottom lines.

Quote
the issue is there when you choose in Output Format: MP4 muxer and not with MP4v2 muxer
Yes, 'MP4v2 Muxer' doesn't stop the encoding process on the 'bad' sequence :
 13.920, 21, 40, 80, 14.120, 160, 200, 240, 280, 320missing, 14.360 secondes).
Frame 14.320 is skipped (to much errors in the GOP ?, or resync decision due to 21 ?).

And finally the result is good, silently encoding the 'bad' sequence.
Mp4v2 is a good choice here.
_____________
Otherside, wanting to be aware of 'too much errors' somewhere in a video,
'MP4 Muxer' is my first choice for now.

If you know, in clean situation, what has 'MP4v2 Muxer' much to offer over 'MP4 Muxer' ...

Jan Gruuthuse

  • Hero Member
  • *****
  • Posts: 6051
Re: These get a 'too short'
« Reply #3 on: May 06, 2015, 05:20:36 AM »
mp4 is for devices not running the newer mp4v2: last 2 postings

http://en.wikipedia.org/wiki/MPEG-4
mp4      = Part  1      ISO/IEC 14496-1
mp4 v2   = Part 14      ISO/IEC 14496-14

the 2 iso links above take you @ iso.org Standards catalogue documentation.

like:
- dolby 5.1 is not allowed in mp4 part 1, it is in mp4v2 part 14
- mp4v2 chapter information
- ...
« Last Edit: May 06, 2015, 05:23:26 AM by Jan Gruuthuse »

mean

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10974
Re: These get a 'too short'
« Reply #4 on: May 06, 2015, 07:39:43 AM »
mp4v2 is just the name of the lib