On 30-07-2015 13:06, Steve Boyer wrote:
On Jul 30, 2015 10:24 AM, "André Luís Duarte" <
andrelduarte-at-yahoo.com...@ffmpeg.org> wrote:
Hi Guys. Thanks for the feedback. Steve, I initially tried the following
command, and the result was as follows:
linux@linux-Capella-IbexPeak-M-Chipset:~/Vídeos$ sudo ffmpeg -i
Video1.264 -vcodec copy Video1.avi
ffmpeg version N-73895-g323ec6b Copyright (c) 2000-2015 the FFmpeg
developers
built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04)
configuration: --extra-libs=-ldl --prefix=/opt/ffmpeg --enable-avresample
--disable-debug --enable-nonfree --enable-gpl --enable-version3
--enable-libopencore-amrnb --enable-libopencore-amrwb
--disable-decoder=amrnb --disable-decoder=amrwb --enable-libpulse
--enable-libdcadec --enable-libx264 --enable-libx265 --enable-libfdk-aac
--enable-libvorbis --enable-libmp3lame --enable-libopus --enable-libvpx
--enable-libspeex --enable-libass --enable-avisynth --enable-libsoxr
--enable-libxvid --enable-libvo-aacenc --enable-libvidstab
libavutil      54. 28.100 / 54. 28.100
libavcodec     56. 50.101 / 56. 50.101
libavformat    56. 40.101 / 56. 40.101
libavdevice    56.  4.100 / 56.  4.100
libavfilter     5. 25.100 /  5. 25.100
libavresample   2.  1.  0 /  2.  1.  0
libswscale      3.  1.101 /  3.  1.101
libswresample   1.  2.101 /  1.  2.101
libpostproc    53.  3.100 / 53.  3.100
Video1.264: Invalid data found when processing input

This is curious - it's almost as if ffmpeg doesn't recognize this as a
valid video. Can you run "file video1.264" for us? Or even better, can you
provide a small sample for us to take a look at and see for ourselves?

I  tried running the  video and  I obtained  this output. Now I ran the command 
as root (sudo su).

root@linux-Capella-IbexPeak-M-Chipset:/home/linux/Vídeos# ffplay Video1.264

ffplay version N-73895-g323ec6b Copyright (c) 2003-2015 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04)
  configuration: --extra-libs=-ldl --prefix=/opt/ffmpeg --enable-avresample 
--disable-debug --enable-nonfree --enable-gpl --enable-version3 
--enable-libopencore-amrnb --enable-libopencore-amrwb --disable-decoder=amrnb 
--disable-decoder=amrwb --enable-libpulse --enable-libdcadec --enable-libx264 
--enable-libx265 --enable-libfdk-aac --enable-libvorbis --enable-libmp3lame 
--enable-libopus --enable-libvpx --enable-libspeex --enable-libass 
--enable-avisynth --enable-libsoxr --enable-libxvid --enable-libvo-aacenc 
--enable-libvidstab
  libavutil      54. 28.100 / 54. 28.100
  libavcodec     56. 50.101 / 56. 50.101
  libavformat    56. 40.101 / 56. 40.101
  libavdevice    56.  4.100 / 56.  4.100
  libavfilter     5. 25.100 /  5. 25.100
  libavresample   2.  1.  0 /  2.  1.  0
  libswscale      3.  1.101 /  3.  1.101
  libswresample   1.  2.101 /  1.  2.101
  libpostproc    53.  3.100 / 53.  3.100
Video1.264: Invalid data found when processing input=    0B f=0/0
    nan    :  0.000 fd=   0 aq=    0KB vq=    0KB sq=    0B f=0/0


The video  has  377  MB  and  as  I can not  handle it  do not know  how to 
edit  and  cut a piece  for you to analyze.

"I ran the command after giving full permission to access the file.
(chmod 777 Video1.264)"
Again, your commands use sudo to run ffmpeg as root. You shouldn't have to
do this. With a 777 permission, the file is wide open for anyone. Your
restriction would then be the directory permissions.

After searching the internet, I saw a post suggesting use -f to force
ffmpeg h264 treat Video1.264 file in h264 format. As I understand the error
in the first command it was that ffmpeg could not identify the file type.
Once put -f H264 format was identified. I did not know that the h264 format
does not have audio.
Moritz, if I do not put -f H264, in the example I posted without the -f
option h264 in the end we can see that ffmpeg could not identify the file
format.
I tried to check the audio as you suggested to see the result and ffmpeg
still not identifying the file format.
linux@linux-Capella-IbexPeak-M-Chipset:~/Vídeos$ sudo ffmpeg -i
Video1.264 -vn -af volumedetect -f null -
ffmpeg version N-73895-g323ec6b Copyright (c) 2000-2015 the FFmpeg
developers
built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04)
configuration: --extra-libs=-ldl --prefix=/opt/ffmpeg --enable-avresample
--disable-debug --enable-nonfree --enable-gpl --enable-version3
--enable-libopencore-amrnb --enable-libopencore-amrwb
--disable-decoder=amrnb --disable-decoder=amrwb --enable-libpulse
--enable-libdcadec --enable-libx264 --enable-libx265 --enable-libfdk-aac
--enable-libvorbis --enable-libmp3lame --enable-libopus --enable-libvpx
--enable-libspeex --enable-libass --enable-avisynth --enable-libsoxr
--enable-libxvid --enable-libvo-aacenc --enable-libvidstab
libavutil      54. 28.100 / 54. 28.100
libavcodec     56. 50.101 / 56. 50.101
libavformat    56. 40.101 / 56. 40.101
libavdevice    56.  4.100 / 56.  4.100
libavfilter     5. 25.100 /  5. 25.100
libavresample   2.  1.  0 /  2.  1.  0
libswscale      3.  1.101 /  3.  1.101
libswresample   1.  2.101 /  1.  2.101
libpostproc    53.  3.100 / 53.  3.100
Video1.264: Invalid data found when processing input

It would be really cool if I could generate the graphics, I'll keep
trying and researching.
Just a note, I am new to using ffmpeg, so I can post things that are my
interpretation of what I have read.



Em Quarta-feira, 29 de Julho de 2015 17:46, Moritz Barsnick <
barsn...@gmx.net> escreveu:
(André, your subject is wrong. ;-))

On Wed, Jul 29, 2015 at 15:33:31 -0500, Steve Boyer wrote:
On Wed, Jul 29, 2015 at 3:09 PM, André Luís Duarte
<andrelduarte-at-yahoo.com...@ffmpeg.org> wrote:
Probably shouldn't run ffmpeg as root, as your resulting video will be
owned by root and can easily cause all kinds of permission issues.
There should _never_ be a need for this. If ffmpeg can't access a
device or file, fix that file's permissions.

What I'm guessing is that the "-f H264" is telling ffmpeg that you
want to export a .264 container format - which only contains video
No, it was given as an option _before_ "-i", so it's telling ffmpeg to
_import_ the given file as a raw H.264 stream. And that doesn't work
too well, because it can't be such a raw video if it contains audio.

As Steve suggested, just let ffmpeg detect the input itself.

To analyze the overall audio volume:
$ ffmpeg -i inputfile -vn -af volumedetect -f null -

(ffmpeg can also create graphs of the audio levels or waveforms over
time. Otherwise, you may want something like audacity.)

Moritz
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Reply via email to