Recherche avancée

Sur d’autres sites (5571)

• Error converting .flv to .avi with ffmpeg

  5 juillet 2012, par user1504396

  When i try the 2d code, with a 5 minutes 7 second video, I get a 28 minutes 29 seconds video, What did I do wrong ?

  Here is the ffmpeg output :

  [Me@Hewlett-Packard Downloads]$ ffmpeg -i "0042473.flv" -s 400x240 -aspect 2:1 -r 20 -vcodec mjpeg -qscale 1 -acodec adpcm_ima_wav -ac 2 "VID_0001.AVI"
  
  ffmpeg version 0.8.10, Copyright © 2000-2011 the FFmpeg developers
  
  built on Feb 29 2012 16:30:44 with gcc 4.6.2 20111027 (Red Hat 4.6.2-1)
  
  configuration: --prefix=/usr --bindir=/usr/bin --datadir=/usr/share/ffmpeg --incdir=/usr/include/ffmpeg --libdir=/usr/lib64 --mandir=/usr/share/man --arch=x86_64 --extra-cflags='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic' --enable-bzlib --enable-libcelt --enable-libdc1394 --enable-libdirac --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --enable-x11grab --enable-avfilter --enable-postproc --enable-pthreads --disable-static --enable-shared --enable-gpl --disable-debug --disable-stripping --shlibdir=/usr/lib64 --enable-runtime-cpudetect
  
  libavutil 51. 9. 1 / 51. 9. 1
  
  libavcodec 53. 8. 0 / 53. 8. 0
  
  libavformat 53. 5. 0 / 53. 5. 0
  
  libavdevice 53. 1. 1 / 53. 1. 1
  
  libavfilter 2. 23. 0 / 2. 23. 0
  
  libswscale 2. 0. 0 / 2. 0. 0
  
  libpostproc 51. 2. 0 / 51. 2. 0
  
  [flv @ 0x2165600] Estimating duration from bitrate, this may be inaccurate
  
  
  
  Seems stream 0 codec frame rate differs from container frame rate: 59.94 (2997/50) -> 29.97 (30000/1001)
  
  Input #0, flv, from '0042473.flv':
  
  Metadata:
  
  minor_version : 1
  
  stereo : true
  
  videocodecid : 7
  
  audiodatarate : 62
  
  audiosamplerate : 44100
  
  audiosize : 2476815
  
  canSeekToEnd : true
  
  creation_time : 2011-05-01 18:06:43
  
  copyright :
  
  compatible_brands: isomavc1
  
  datasize : 16589374
  
  duration : 308
  
  copyright-eng :
  
  encoder : Lavf52.104.0
  
  videodatarate : 351
  
  hasAudio : true
  
  hasCuePoints : false
  
  hasKeyframes : true
  
  hasMetadata : true
  
  hasVideo : true
  
  width : 480
  
  lasttimestamp : 308
  
  audiocodecid : 10
  
  metadatacreator : flvtool++ (Facebook, Motion project, dweatherford)
  
  major_brand : isom
  
  audiosamplesize : 16
  
  totalframes : 9225
  
  framerate : 30
  
  height : 272
  
  videosize : 13863389
  
  filesize : 16587742
  
  Duration: 00:05:07.94, start: 0.000000, bitrate: 423 kb/s
  
  Stream #0.0: Video: h264 (High), yuv420p, 480x272 [PAR 1:1 DAR 30:17], 359 kb/s, 29.97 tbr, 1k tbn, 59.94 tbc
  
  Stream #0.1: Audio: aac, 44100 Hz, stereo, s16, 63 kb/s
  
  Incompatible pixel format 'yuv420p' for codec 'mjpeg', auto-selecting format 'yuvj420p'
  
  [buffer @ 0x216b180] w:480 h:272 pixfmt:yuv420p tb:1/1000000 sar:1/1 sws_param:
  
  [scale @ 0x216bf40] w:480 h:272 fmt:yuv420p -> w:400 h:240 fmt:yuvj420p flags:0x4
  
  Output #0, avi, to 'VID_0001.AVI':
  
  Metadata:
  
  minor_version : 1
  
  stereo : true
  
  videocodecid : 7
  
  audiodatarate : 62
  
  audiosamplerate : 44100
  
  audiosize : 2476815
  
  canSeekToEnd : true
  
  creation_time : 2011-05-01 18:06:43
  
  ICOP :
  
  compatible_brands: isomavc1
  
  datasize : 16589374
  
  duration : 308
  
  copyright-eng :
  
  filesize : 16587742
  
  videodatarate : 351
  
  hasAudio : true
  
  hasCuePoints : false
  
  hasKeyframes : true
  
  hasMetadata : true
  
  hasVideo : true
  
  width : 480
  
  lasttimestamp : 308
  
  audiocodecid : 10
  
  metadatacreator : flvtool++ (Facebook, Motion project, dweatherford)
  
  major_brand : isom
  
  audiosamplesize : 16
  
  totalframes : 9225
  
  framerate : 30
  
  height : 272
  
  videosize : 13863389
  
  ISFT : Lavf53.5.0
  
  Stream #0.0: Video: mjpeg, yuvj420p, 400x240 [PAR 6:5 DAR 2:1], q=2-31, 200 kb/s, 20 tbn, 20 tbc
  
  Stream #0.1: Audio: adpcm_ima_wav, 44100 Hz, stereo, s16, 352 kb/s
  
  Stream mapping:
  
  Stream #0.0 -> #0.0
  
  Stream #0.1 -> #0.1
  
  Press [q] to stop, [?] for help
  
  frame= 43 fps= 0 q=1.0 size= 1330kB time=00:00:02.12 bitrate=5135.7kbits/sframe= 87 fps= 86 q=1.0 size= 2712kB time=00:00:04.35 bitrate=5097.2kbits/sframe= 135 fps= 89 q=1.0 size= 3579kB time=00:00:06.78 bitrate=4324.9kbits/sframe= 185 fps= 92 q=1.0 size= 4307kB time=00:00:09.27 bitrate=3805.9kbits/sframe= 231 fps= 92 q=1.0 size= 5208kB time=00:00:11.55 bitrate=3692.4kbits/sframe= 276 fps= 91 q=1.0 size= 6129kB time=00:00:13.83 bitrate=3628.5kbits/sframe= 318 fps= 90 q=1.0 size= 6978kB time=00:00:15.91 bitrate=3592.6kbits/sframe= 366 fps= 91 q=1.0 size= 7990kB time=00:00:18.33 bitrate=3570.2kbits/sframe= 408 fps= 90 q=1.0 size= 8912kB time=00:00:20.43 bitrate=3573.2kbits/sframe= 451 fps= 90 q=1.0 size= 9831kB time=00:00:22.55 bitrate=3570.9kbits/sframe= 495 fps= 89 q=1.0 size= 10827kB time=00:00:24.74 bitrate=3584.4kbits/sframe= 539 fps= 89 q=1.0 size= 11845kB time=00:00:26.91 bitrate=3605.5kbits/sframe= 583 fps= 89 q=1.0 size= 12939kB time=00:00:29.14 bitrate=3636.2kbits/sframe= 630 fps= 89 q=1.0 size= 13790kB time=00:00:31.52 bitrate=3583.5kbits/sframe= 676 fps= 89 q=1.0 size= 14710kB time=00:00:33.80 bitrate=3564.4kbits/sframe= 723 fps= 90 q=1.0 size= 15651kB time=00:00:36.16 bitrate=3545.7kbits/sframe= 767 fps= 90 q=1.0 size= 16589kB time=00:00:38.35 bitrate=3543.6kbits/sframe= 809 fps= 89 q=1.0 size= 17576kB time=00:00:40.42 bitrate=3561.7kbits/sframe= 852 fps= 89 q=1.0 size= 18598kB time=00:00:42.61 bitrate=3575.0kbits/sframe= 898 fps= 89 q=1.0 size= 19548kB time=00:00:44.90 bitrate=3566.6kbits/sframe= 940 fps= 89 q=1.0 size= 20666kB time=00:00:46.97 bitrate=3603.9kbits/sframe= 982 fps= 89 q=1.0 size= 21739kB time=00:00:49.12 bitrate=3625.5kbits/sframe= 1024 fps= 88 q=1.0 size= 22711kB time=00:00:51.25 bitrate=3630.2kbits/sframe= 1070 fps= 88 q=1.0 size= 23769kB time=00:00:53.47 bitrate=3640.9kbits/sframe= 1118 fps= 89 q=1.0 size= 24935kB time=00:00:55.90 bitrate=3654.2kbits/sframe= 1165 fps= 89 q=1.0 size= 26047kB time=00:00:58.22 bitrate=3664.3kbits/sframe= 1213 fps= 89 q=1.0 size= 27187kB time=00:01:00.62 bitrate=3673.5kbits/sframe= 1265 fps= 90 q=1.0 size= 27935kB time=00:01:03.23 bitrate=3619.0kbits/sframe= 1315 fps= 90 q=1.0 size= 28590kB time=00:01:05.79 bitrate=3559.7kbits/sframe= 1366 fps= 90 q=1.0 size= 29229kB time=00:01:08.30 bitrate=3505.3kbits/sframe= 1415 fps= 91 q=1.0 size= 29928kB time=00:01:10.75 bitrate=3465.2kbits/sframe= 1464 fps= 91 q=1.0 size= 30612kB time=00:01:13.25 bitrate=3423.5kbits/sframe= 1512 fps= 91 q=1.0 size= 31309kB time=00:01:15.64 bitrate=3390.8kbits/sframe= 1561 fps= 91 q=1.0 size= 31997kB time=00:01:18.06 bitrate=3357.8kbits/sframe= 1608 fps= 91 q=1.0 size= 32760kB time=00:01:20.36 bitrate=3339.3kbits/sframe= 1654 fps= 91 q=1.0 size= 33563kB time=00:01:22.69 bitrate=3324.7kbits/sframe= 1700 fps= 91 q=1.0 size= 34318kB time=00:01:24.98 bitrate=3308.2kbits/sframe= 1745 fps= 91 q=1.0 size= 35041kB time=00:01:27.24 bitrate=3290.4kbits/sframe= 1791 fps= 91 q=1.0 size= 35749kB time=00:01:29.56 bitrate=3269.6kbits/sframe= 1837 fps= 91 q=1.0 size= 36442kB time=00:01:31.85 bitrate=3250.1kbits/sframe= 1884 fps= 91 q=1.0 size= 37121kB time=00:01:34.20 bitrate=3228.0kbits/sframe= 1931 fps= 91 q=1.0 size= 37840kB time=00:01:36.53 bitrate=3211.1kbits/sframe= 1978 fps= 91 q=1.0 size= 38561kB time=00:01:38.90 bitrate=3193.8kbits/sframe= 2025 fps= 91 q=1.0 size= 39279kB time=00:01:41.28 bitrate=3176.9kbits/sframe= 2072 fps= 91 q=1.0 size= 40005kB time=00:01:43.59 bitrate=3163.6kbits/sframe= 2117 fps= 91 q=1.0 size= 40833kB time=00:01:45.87 bitrate=3159.5kbits/sframe= 2158 fps= 91 q=1.0 size= 41561kB time=00:01:47.90 bitrate=3155.3kbits/sframe= 2202 fps= 91 q=1.0 size= 42407kB time=00:01:50.14 bitrate=3154.1kbits/sframe= 2248 fps= 91 q=1.0 size= 43201kB time=00:01:52.42 bitrate=3147.9kbits/sframe= 2295 fps= 91 q=1.0 size= 43975kB time=00:01:54.75 bitrate=3139.3kbits/sframe= 2342 fps= 91 q=1.0 size= 44739kB time=00:01:57.10 bitrate=3129.7kbits/sframe= 2388 fps= 91 q=1.0 size= 45532kB time=00:01:59.43 bitrate=3123.0kbits/sframe= 2435 fps= 91 q=1.0 size= 46306kB time=00:02:01.80 bitrate=3114.5kbits/sframe= 2481 fps= 91 q=1.0 size= 47095kB time=00:02:04.02 bitrate=3110.7kbits/sframe= 2530 fps= 91 q=1.0 size= 47778kB time=00:02:06.49 bitrate=3094.3kbits/sframe= 2578 fps= 91 q=1.0 size= 48507kB time=00:02:08.91 bitrate=3082.5kbits/sframe= 2622 fps= 91 q=1.0 size= 49169kB time=00:02:11.08 bitrate=3072.9kbits/sframe= 2670 fps= 91 q=1.0 size= 49851kB time=00:02:13.54 bitrate=3057.9kbits/sframe= 2718 fps= 91 q=1.0 size= 50531kB time=00:02:15.92 bitrate=3045.5kbits/sframe= 2764 fps= 91 q=1.0 size= 51242kB time=00:02:18.18 bitrate=3037.8kbits/sframe= 2810 fps= 92 q=1.0 size= 51959kB time=00:02:20.51 bitrate=3029.3kbits/sframe= 2835 fps= 90 q=1.0 size= 52376kB time=00:02:21.78 bitrate=3026.2kbits/sframe= 2879 fps= 90 q=1.0 size= 53093kB time=00:02:23.94 bitrate=3021.5kbits/sframe= 2923 fps= 90 q=1.0 size= 53853kB time=00:02:26.18 bitrate=3017.8kbits/sframe= 2968 fps= 90 q=1.0 size= 54594kB time=00:02:28.39 bitrate=3013.7kbits/sframe= 3012 fps= 90 q=1.0 size= 55444kB time=00:02:30.63 bitrate=3015.2kbits/sframe= 3056 fps= 90 q=1.0 size= 56495kB time=00:02:32.78 bitrate=3029.2kbits/sframe= 3098 fps= 90 q=1.0 size= 57463kB time=00:02:34.90 bitrate=3039.0kbits/sframe= 3141 fps= 90 q=1.0 size= 58433kB time=00:02:37.04 bitrate=3048.0kbits/sframe= 3186 fps= 90 q=1.0 size= 59457kB time=00:02:39.33 bitrate=3057.0kbits/sframe= 3232 fps= 90 q=1.0 size= 60471kB time=00:02:41.59 bitrate=3065.6kbits/sframe= 3277 fps= 90 q=1.0 size= 61485kB time=00:02:43.82 bitrate=3074.5kbits/sframe= 3322 fps= 90 q=1.0 size= 62297kB time=00:02:46.11 bitrate=3072.3kbits/sframe= 3365 fps= 90 q=1.0 size= 63043kB time=00:02:48.27 bitrate=3069.0kbits/sframe= 3409 fps= 90 q=1.0 size= 63752kB time=00:02:50.46 bitrate=3063.7kbits/sframe= 3455 fps= 90 q=1.0 size= 64529kB time=00:02:52.75 bitrate=3060.0kbits/sframe= 3499 fps= 90 q=1.0 size= 65306kB time=00:02:54.96 bitrate=3057.7kbits/sframe= 3545 fps= 90 q=1.0 size= 66070kB time=00:02:57.24 bitrate=3053.6kbits/sframe= 3594 fps= 90 q=1.0 size= 66804kB time=00:02:59.71 bitrate=3045.1kbits/sframe= 3644 fps= 90 q=1.0 size= 67554kB time=00:03:02.18 bitrate=3037.6kbits/sframe= 3690 fps= 90 q=1.0 size= 68436kB time=00:03:04.48 bitrate=3038.8kbits/sframe= 3740 fps= 90 q=1.0 size= 69121kB time=00:03:07.00 bitrate=3028.0kbits/sframe= 3787 fps= 90 q=1.0 size= 69953kB time=00:03:09.33 bitrate=3026.7kbits/sframe= 3832 fps= 90 q=1.0 size= 70857kB time=00:03:11.59 bitrate=3029.7kbits/sframe= 3878 fps= 90 q=1.0 size= 71622kB time=00:03:13.92 bitrate=3025.6kbits/sframe= 3925 fps= 90 q=1.0 size= 72343kB time=00:03:16.25 bitrate=3019.8kbits/sframe= 3973 fps= 90 q=1.0 size= 73100kB time=00:03:18.64 bitrate=3014.5kbits/sframe= 4021 fps= 90 q=1.0 size= 73867kB time=00:03:21.07 bitrate=3009.5kbits/sframe= 4070 fps= 90 q=1.0 size= 74643kB time=00:03:23.53 bitrate=3004.2kbits/sframe= 4119 fps= 90 q=1.0 size= 75363kB time=00:03:25.95 bitrate=2997.6kbits/sframe= 4167 fps= 90 q=1.0 size= 76077kB time=00:03:28.35 bitrate=2991.1kbits/sframe= 4216 fps= 91 q=1.0 size= 76751kB time=00:03:30.77 bitrate=2983.0kbits/sframe= 4263 fps= 91 q=1.0 size= 77432kB time=00:03:33.15 bitrate=2975.9kbits/sframe= 4315 fps= 91 q=1.0 size= 78087kB time=00:03:35.73 bitrate=2965.1kbits/sframe= 4367 fps= 91 q=1.0 size= 78795kB time=00:03:38.34 bitrate=2956.3kbits/sframe= 4418 fps= 91 q=1.0 size= 79475kB time=00:03:40.90 bitrate=2947.2kbits/sframe= 4469 fps= 91 q=1.0 size= 80174kB time=00:03:43.46 bitrate=2939.1kbits/sframe= 4519 fps= 91 q=1.0 size= 80865kB time=00:03:45.90 bitrate=2932.4kbits/sframe= 4567 fps= 91 q=1.0 size= 81621kB time=00:03:48.32 bitrate=2928.4kbits/sframe= 4611 fps= 91 q=1.0 size= 82613kB time=00:03:50.56 bitrate=2935.2kbits/sframe= 4655 fps= 91 q=1.0 size= 83653kB time=00:03:52.80 bitrate=2943.7kbits/sframe= 4699 fps= 91 q=1.0 size= 84646kB time=00:03:54.97 bitrate=2951.1kbits/sframe= 4743 fps= 91 q=1.0 size= 85543kB time=00:03:57.20 bitrate=2954.3kbits/sframe= 4789 fps= 91 q=1.0 size= 86344kB time=00:03:59.42 bitrate=2954.3kbits/sframe= 4836 fps= 91 q=1.0 size= 87090kB time=00:04:01.79 bitrate=2950.6kbits/sframe= 4883 fps= 91 q=1.0 size= 87821kB time=00:04:04.17 bitrate=2946.4kbits/sframe= 4930 fps= 91 q=1.0 size= 88571kB time=00:04:06.50 bitrate=2943.5kbits/sframe= 4977 fps= 91 q=1.0 size= 89318kB time=00:04:08.85 bitrate=2940.3kbits/sframe= 5024 fps= 91 q=1.0 size= 90014kB time=00:04:11.18 bitrate=2935.7kbits/sframe= 5070 fps= 91 q=1.0 size= 90743kB time=00:04:13.55 bitrate=2931.8kbits/sframe= 5120 fps= 91 q=1.0 size= 91438kB time=00:04:16.00 bitrate=2926.0kbits/sframe= 5165 fps= 91 q=1.0 size= 92265kB time=00:04:18.28 bitrate=2926.4kbits/sframe= 5211 fps= 91 q=1.0 size= 93079kB time=00:04:20.56 bitrate=2926.3kbits/sframe= 5258 fps= 91 q=1.0 size= 93913kB time=00:04:22.87 bitrate=2926.6kbits/sframe= 5304 fps= 91 q=1.0 size= 94739kB time=00:04:25.20 bitrate=2926.4kbits/sframe= 5351 fps= 91 q=1.0 size= 95565kB time=00:04:27.60 bitrate=2925.5kbits/sframe= 5398 fps= 91 q=1.0 size= 96368kB time=00:04:29.90 bitrate=2924.9kbits/sframe= 5444 fps= 91 q=1.0 size= 97176kB time=00:04:32.16 bitrate=2924.9kbits/sframe= 5490 fps= 91 q=1.0 size= 98049kB time=00:04:34.54 bitrate=2925.6kbits/sframe= 5538 fps= 91 q=1.0 size= 98914kB time=00:04:36.91 bitrate=2926.1kbits/sframe= 5587 fps= 91 q=1.0 size= 99817kB time=00:04:39.36 bitrate=2927.0kbits/sframe= 5636 fps= 91 q=1.0 size= 100709kB time=00:04:41.83 bitrate=2927.3kbits/sframe= 5682 fps= 91 q=1.0 size= 101490kB time=00:04:44.11 bitrate=2926.3kbits/sframe= 5732 fps= 91 q=1.0 size= 102230kB time=00:04:46.60 bitrate=2922.0kbits/sframe= 5781 fps= 91 q=1.0 size= 102991kB time=00:04:49.07 bitrate=2918.6kbits/sframe= 5827 fps= 91 q=1.0 size= 103918kB time=00:04:51.35 bitrate=2921.8kbits/sframe= 5874 fps= 92 q=1.0 size= 104873kB time=00:04:53.73 bitrate=2924.9kbits/sframe= 5921 fps= 92 q=1.0 size= 105844kB time=00:04:56.08 bitrate=2928.5kbits/sframe= 5970 fps= 92 q=1.0 size= 106670kB time=00:04:58.50 bitrate=2927.4kbits/sframe= 6028 fps= 92 q=1.0 size= 108198kB time=00:05:01.43 bitrate=2940.5kbits/sframe= 6080 fps= 91 q=1.0 size= 109527kB time=00:05:03.99 bitrate=2951.5kbits/sframe= 6138 fps= 92 q=1.0 size= 110623kB time=00:05:06.85 bitrate=2953.3kbits/sframe= 6156 fps= 92 q=1.0 Lsize= 111017kB time=00:05:07.85 bitrate=2954.2kbits/s dup=0 drop=3067

  video:97193kB audio:13354kB global headers:0kB muxing overhead 0.425158%

  Where is my problem ?

• ffmpeg neon compilation on android - assembler errors

  11 juillet 2012, par Android007

  I am trying to compile ffmpeg for android with neon support , but I am getting following assembler errors. Please let me know if anybody has any clue about this ?

  /home/user1/android-ndk-r5b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc -MMD -MP -MF /home/user1/workspace/FFMPEGFinal/obj/local/armeabi-v7a/objs/ffmpeg/libavcodec/arm/rdft_neon.o.d.org -fpic -ffunction-sections -funwind-tables -fstack-protector -D__ARM_ARCH_5__ -D__ARM_ARCH_5T__ -D__ARM_ARCH_5E__ -D__ARM_ARCH_5TE__  -Wno-psabi -march=armv7-a -mfloat-abi=softfp -mfpu=vfp -O2 -fomit-frame-pointer -fstrict-aliasing -funswitch-loops -finline-limit=300 -I/home/user1/workspace/FFMPEGFinal/jni/SDL/include -I/home/user1/workspace/FFMPEGFinal/jni -DANDROID -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DPIC -DCMP_HAVE_NEON -DCMP_HAVE_VFP -fasm -Wa,--noexecstack -O2 -DNDEBUG -g -I/home/user1/android-ndk-r5b/platforms/android-8/arch-arm/usr/include -c  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S -o /home/user1/workspace/FFMPEGFinal/obj/local/armeabi-v7a/objs/ffmpeg/libavcodec/arm/rdft_neon.o && rm -f /home/user1/workspace/FFMPEGFinal/obj/local/armeabi-v7a/objs/ffmpeg/libavcodec/arm/rdft_neon.o.d && mv /home/user1/workspace/FFMPEGFinal/obj/local/armeabi-v7a/objs/ffmpeg/libavcodec/arm/rdft_neon.o.d.org /home/user1/workspace/FFMPEGFinal/obj/local/armeabi-v7a/objs/ffmpeg/libavcodec/arm/rdft_neon.o.d
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S: Assembler messages:
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:54: Error: bad instruction `vld1.32 {d0},[r0,:64]!'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:55: Error: bad instruction `vld1.32 {d1},[r1,:64],r8'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:56: Error: bad instruction `vld1.32 {d4},[r2,:64]!'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:57: Error: bad instruction `vld1.32 {d5},[r3,:64]!'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:58: Error: bad instruction `vmov.f32 d18,#0.5'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:59: Error: bad instruction `vdup.32 d19,r6'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:61: Error: selected processor does not support `veor d19,d18,d19'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:62: Error: bad instruction `vmov.i32 d16,#0'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:63: Error: bad instruction `vmov.i32 d17,#1<<31'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:65: Error: bad instruction `vtrn.32 d16,d17'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:67: Error: bad instruction `vrev64.32 d16,d16'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:70: Error: selected processor does not support `veor q1,q0,q8'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:71: Error: bad instruction `vld1.32 {d24},[r0,:64]!'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:72: Error: bad instruction `vadd.f32 d0,d0,d3'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:73: Error: bad instruction `vld1.32 {d25},[r1,:64],r8'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:74: Error: bad instruction `vadd.f32 d1,d2,d1'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:75: Error: selected processor does not support `veor q3,q12,q8'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:77: Error: bad instruction `vmul.f32 q10,q0,q9'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:79: Error: bad instruction `vadd.f32 d0,d24,d7'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:80: Error: bad instruction `vadd.f32 d1,d6,d25'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:81: Error: bad instruction `vmul.f32 q11,q0,q9'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:82: Error: selected processor does not support `veor d7,d21,d16'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:83: Error: bad instruction `vrev64.32 d3,d21'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:84: Error: selected processor does not support `veor d6,d20,d17'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:85: Error: selected processor does not support `veor d2,d3,d16'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:86: Error: bad instruction `vmla.f32 d20,d3,d4[1]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:87: Error: bad instruction `vmla.f32 d20,d7,d5[1]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:88: Error: bad instruction `vmla.f32 d6,d2,d4[1]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:89: Error: bad instruction `vmla.f32 d6,d21,d5[1]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:90: Error: bad instruction `vld1.32 {d4},[r2,:64]!'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:91: Error: selected processor does not support `veor d7,d23,d16'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:92: Error: bad instruction `vld1.32 {d5},[r3,:64]!'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:93: Error: selected processor does not support `veor d24,d22,d17'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:94: Error: bad instruction `vrev64.32 d3,d23'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:96: Error: selected processor does not support `veor d2,d3,d16'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:98: Error: bad instruction `vmla.f32 d22,d3,d4[0]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:99: Error: bad instruction `vmla.f32 d22,d7,d5[0]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:100: Error: bad instruction `vmla.f32 d24,d2,d4[0]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:101: Error: bad instruction `vmla.f32 d24,d23,d5[0]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:102: Error: bad instruction `vld1.32 {d0},[r0,:64]!'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:103: Error: bad instruction `vld1.32 {d1},[r1,:64],r8'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:104: Error: bad instruction `vst1.32 {d20},[r7,:64]!'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:105: Error: bad instruction `vst1.32 {d6},[lr,:64],r8'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:106: Error: bad instruction `vst1.32 {d22},[r7,:64]!'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:107: Error: bad instruction `vst1.32 {d24},[lr,:64],r8'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:111: Error: selected processor does not support `veor q1,q0,q8'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:112: Error: bad instruction `vadd.f32 d0,d0,d3'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:113: Error: bad instruction `vadd.f32 d1,d2,d1'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:115: Error: bad instruction `vmul.f32 q10,q0,q9'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:118: Error: bad instruction `vld1.32 {d0[0]},[r0,:32]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:119: Error: selected processor does not support `veor d7,d21,d16'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:120: Error: bad instruction `vrev64.32 d3,d21'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:121: Error: selected processor does not support `veor d6,d20,d17'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:122: Error: bad instruction `vld1.32 {d22},[r5,:64]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:123: Error: bad instruction `vdup.32 d1,r2'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:124: Error: selected FPU does not support instruction -- `vmov d23,d22'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:125: Error: selected processor does not support `veor d2,d3,d16'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:126: Error: bad instruction `vtrn.32 d22,d23'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:127: Error: selected processor does not support `veor d0,d0,d1'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:128: Error: selected processor does not support `veor d23,d23,d17'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:129: Error: bad instruction `vmla.f32 d20,d3,d4[1]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:130: Error: bad instruction `vmla.f32 d20,d7,d5[1]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:131: Error: bad instruction `vmla.f32 d6,d2,d4[1]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:132: Error: bad instruction `vmla.f32 d6,d21,d5[1]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:133: Error: bad instruction `vadd.f32 d22,d22,d23'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:134: Error: bad instruction `vst1.32 {d20},[r7,:64]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:135: Error: bad instruction `vst1.32 {d6},[lr,:64]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:136: Error: bad instruction `vst1.32 {d0[0]},[r0,:32]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:137: Error: bad instruction `vst1.32 {d22},[r5,:64]'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:142: Error: bad instruction `vmul.f32 d22,d22,d18'
  
  /home/user1/workspace/FFMPEGFinal/jni/libavcodec/arm/rdft_neon.S:143: Error: bad instruction `vst1.32 {d22},[r5,:64]'
  
  make: *** [/home/user1/workspace/FFMPEGFinal/obj/local/armeabi-v7a/objs/ffmpeg/libavcodec/arm/rdft_neon.o] Error 1

• The use cases for a element in HTML

  27 novembre 2012, par silvia

  The W3C HTML WG and the WHATWG are currently discussing the introduction of a <main> element into HTML.

  The <main> element has been proposed by Steve Faulkner and is specified in a draft extension spec which is about to be accepted as a FPWD (first public working draft) by the W3C HTML WG. This implies that the W3C HTML WG will be looking for implementations and for feedback by implementers on this spec.

  I am supportive of the introduction of a <main> element into HTML. However, I believe that the current spec and use case list don’t make a good enough case for its introduction. Here are my thoughts.

  Main use case : accessibility

  In my opinion, the main use case for the introduction of <main> is accessibility.

  Like any other users, when blind users want to perceive a Web page/application, they need to have a quick means of grasping the content of a page. Since they cannot visually scan the layout and thus determine where the main content is, they use accessibility technology (AT) to find what is known as “landmarks”.

  “Landmarks” tell the user what semantic content is on a page : a header (such as a banner), a search box, a navigation menu, some asides (also called complementary content), a footer, …. and the most important part : the main content of the page. It is this main content that a blind user most often wants to skip to directly.

  In the days of HTML4, a hidden “skip to content” link at the beginning of the Web page was used as a means to help blind users access the main content.

  In the days of ARIA, the aria @role=main enables authors to avoid a hidden link and instead mark the element where the main content begins to allow direct access to the main content. This attribute is supported by AT – in particular screen readers – by making it part of the landmarks that AT can directly skip to.

  Both the hidden link and the ARIA @role=main approaches are, however, band aids : they are being used by those of us that make “finished” Web pages accessible by adding specific extra markup.

  A world where ARIA is not necessary and where accessibility developers would be out of a job because the normal markup that everyone writes already creates accessible Web sites/applications would be much preferable over the current world of band-aids.

  Therefore, to me, the primary use case for a <main> element is to achieve exactly this better world and not require specialized markup to tell a user (or a tool) where the main content on a page starts.

  An immediate effect would be that pages that have a <main> element will expose a “main” landmark to blind and vision-impaired users that will enable them to directly access that main content on the page without having to wade through other text on the page. Without a <main> element, this functionality can currently only be provided using heuristics to skip other semantic and structural elements and is for this reason not typically implemented in AT.

  Other use cases

  The <main> element is a semantic element not unlike other new semantic elements such as <header>, <footer>, <aside>, <article>, <nav>, or <section>. Thus, it can also serve other uses where the main content on a Web page/Web application needs to be identified.

  Data mining

  For data mining of Web content, the identification of the main content is one of the key challenges. Many scholarly articles have been published on this topic. This stackoverflow article references and suggests a multitude of approaches, but the accepted answer says “there’s no way to do this that’s guaranteed to work”. This is because Web pages are inherently complex and many <div>, <p>, <iframe> and other elements are used to provide markup for styling, notifications, ads, analytics and other use cases that are necessary to make a Web page complete, but don’t contribute to what a user consumes as semantically rich content. A <main> element will allow authors to pro-actively direct data mining tools to the main content.

  Search engines

  One particularly important “data mining” tool are search engines. They, too, have a hard time to identify which sections of a Web page are more important than others and employ many heuristics to do so, see e.g. this ACM article. Yet, they still disappoint with poor results pointing to findings of keywords in little relevant sections of a page rather than ranking Web pages higher where the keywords turn up in the main content area. A <main> element would be able to help search engines give text in main content areas a higher weight and prefer them over other areas of the Web page. It would be able to rank different Web pages depending on where on the page the search words are found. The <main> element will be an additional hint that search engines will digest.

  Visual focus

  On small devices, the display of Web pages designed for Desktop often causes confusion as to where the main content can be found and read, in particular when the text ends up being too small to be readable. It would be nice if browsers on small devices had a functionality (maybe a default setting) where Web pages would start being displayed as zoomed in on the main content. This could alleviate some of the headaches of responsive Web design, where the recommendation is to show high priority content as the first content. Right now this problem is addressed through stylesheets that re-layout the page differently depending on device, but again this is a band-aid solution. Explicit semantic markup of the main content can solve this problem more elegantly.

  Styling

  Finally, naturally, <main> would also be used to style the main content differently from others. You can e.g. replace a semantically meaningless <div id=”main”> with a semantically meaningful <main> where their position is identical. My analysis below shows, that this is not always the case, since oftentimes <div id=”main”> is used to group everything together that is not the header – in particular where there are multiple columns. Thus, the ease of styling a <main> element is only a positive side effect and not actually a real use case. It does make it easier, however, to adapt the style of the main content e.g. with media queries.

  Proposed alternative solutions

  It has been proposed that existing markup serves to satisfy the use cases that <main> has been proposed for. Let’s analyse these on some of the most popular Web sites. First let’s list the propsed algorithms.

  Proposed solution No 1 : Scooby-Doo

  On Sat, Nov 17, 2012 at 11:01 AM, Ian Hickson <ian@hixie.ch> wrote :
  | The main content is whatever content isn’t
  | marked up as not being main content (anything not marked up with <header>,
  | <aside>, <nav>, etc).
  

  This implies that the first element that is not a <header>, <aside>, <nav>, or <footer> will be the element that we want to give to a blind user as the location where they should start reading. The algorithm is implemented in https://gist.github.com/4032962.

  Proposed solution No 2 : First article element

  On Sat, Nov 17, 2012 at 8:01 AM, Ian Hickson <ian@hixie.ch> wrote :
  | On Thu, 15 Nov 2012, Ian Yang wrote :
  | >
  | > That’s a good idea. We really need an element to wrap all the <p>s,
  | > <ul>s, <ol>s, <figure>s, <table>s ... etc of a blog post.
  |
  | That’s called <article>.
  

  This approach identifies the first <article> element on the page as containing the main content. Here’s the algorithm for this approach.

  Proposed solution No 3 : An example heuristic approach

  The readability plugin has been developed to make Web pages readable by essentially removing all the non-main content from a page. An early source of readability is available. This demonstrates what a heuristic approach can perform.

  Analysing alternative solutions

  Comparison

  I’ve picked 4 typical Websites (top on Alexa) to analyse how these three different approaches fare. Ideally, I’d like to simply apply the above three scripts and compare pictures. However, since the semantic HTML5 elements <header>, <aside>, <nav>, and <footer> are not actually used by any of these Web sites, I don’t actually have this choice.

  So, instead, I decided to make some assumptions of where these semantic elements would be used and what the outcome of applying the first two algorithms would be. I can then compare it to the third, which is a product so we can take screenshots.

  Google.com

  http://google.com – search for “Scooby Doo”.

  The search results page would likely be built with :

  • a <nav> menu for the Google bar
  • a <header> for the search bar
  • another <header> for the login section
  • another <nav> menu for the search types
  • a <div> to contain the rest of the page
  • a <div> for the app bar with the search number
  • a few <aside>s for the left and right column
  • a set of <article>s for the search results

  “Scooby Doo” would find the first element after the headers as the “main content”. This is the element before the app bar in this case. Interestingly, there is a <div @id=main> already in the current Google results page, which “Scooby Doo” would likely also pick. However, there are a nav bar and two asides in this div, which clearly should not be part of the “main content”. Google actually placed a @role=main on a different element, namely the one that encapsulates all the search results.

  “First Article” would find the first search result as the “main content”. While not quite the same as what Google intended – namely all search results – it is close enough to be useful.

  The “readability” result is interesting, since it is not able to identify the main text on the page. It is actually aware of this problem and brings a warning before displaying this page :

  

  Facebook.com

  https://facebook.com

  A user page would likely be built with :

  • a <header> bar for the search and login bar
  • a <div> to contain the rest of the page
  • an <aside> for the left column
  • a <div> to contain the center and right column
  • an <aside> for the right column
  • a <header> to contain the center column “megaphone”
  • a <div> for the status posting
  • a set of <article>s for the home stream

  “Scooby Doo” would find the first element after the headers as the “main content”. This is the element that contains all three columns. It’s actually a <div @id=content> already in the current Facebook user page, which “Scooby Doo” would likely also pick. However, Facebook selected a different element to place the @role=main : the center column.

  “First Article” would find the first news item in the home stream. This is clearly not what Facebook intended, since they placed the @role=main on the center column, above the first blog post’s title. “First Article” would miss that title and the status posting.

  The “readability” result again disappoints but warns that it failed :

  

  YouTube.com

  http://youtube.com

  A video page would likely be built with :

  • a <header> bar for the search and login bar
  • a <nav> for the menu
  • a <div> to contain the rest of the page
  • a <header> for the video title and channel links
  • a <div> to contain the video with controls
  • a <div> to contain the center and right column
  • an <aside> for the right column with an <article> per related video
  • an <aside> for the information below the video
  • a <article> per comment below the video

  “Scooby Doo” would find the first element after the headers as the “main content”. This is the element that contains the rest of the page. It’s actually a <div @id=content> already in the current YouTube video page, which “Scooby Doo” would likely also pick. However, YouTube’s related videos and comments are unlikely to be what the user would regard as “main content” – it’s the video they are after, which generously has a <div id=watch-player>.

  “First Article” would find the first related video or comment in the home stream. This is clearly not what YouTube intends.

  The “readability” result is not quite as unusable, but still very bare :

  

  Wikipedia.com

  http://wikipedia.com (“Overscan” page)

  A Wikipedia page would likely be built with :

  • a <header> bar for the search, login and menu items
  • a <div> to contain the rest of the page
  • an &ls; article> with title and lots of text
  • <article> an <aside> with the table of contents
  • several <aside>s for the left column

  Good news : “Scooby Doo” would find the first element after the headers as the “main content”. This is the element that contains the rest of the page. It’s actually a <div id=”content” role=”main”> element on Wikipedia, which “Scooby Doo” would likely also pick.

  “First Article” would find the title and text of the main element on the page, but it would also include an <aside>.

  The “readability” result is also in agreement.

  

  Results

  In the following table we have summarised the results for the experiments :

  Site	Scooby-Doo	First article	Readability
  Google.com	FAIL	SUCCESS	FAIL
  Facebook.com	FAIL	FAIL	FAIL
  YouTube.com	FAIL	FAIL	FAIL
  Wikipedia.com	SUCCESS	SUCCESS	SUCCESS

  Clearly, Wikipedia is the prime example of a site where even the simple approaches find it easy to determine the main content on the page. WordPress blogs are similarly successful. Almost any other site, including news sites, social networks and search engine sites are petty hopeless with the proposed approaches, because there are too many elements that are used for layout or other purposes (notifications, hidden areas) such that the pre-determined list of semantic elements that are available simply don’t suffice to mark up a Web page/application completely.

  Conclusion

  It seems that in general it is impossible to determine which element(s) on a Web page should be the “main” piece of content that accessibility tools jump to when requested, that a search engine should put their focus on, or that should be highlighted to a general user to read. It would be very useful if the author of the Web page would provide a hint through a <main> element where that main content is to be found.

  I think that the <main> element becomes particularly useful when combined with a default keyboard shortcut in browsers as proposed by Steve : we may actually find that non-accessibility users will also start making use of this shortcut, e.g. to get to videos on YouTube pages directly without having to tab over search boxes and other interactive elements, etc. Worthwhile markup indeed.