On 07/13/2017 02:34 PM, Kieran O Leary wrote:
Woah
On Thu, Jul 13, 2017 at 8:56 PM, JD <jd1...@gmail.com> wrote:
I uploaded the full screen out put to:
https://www.sendspace.com/file/l5jdvs
it is called FFMPEG_ERRORS
I only looked through some as you posted the output of loads of
videos!???? It might help to pick just one that fails, and copy paste the
complete terminal output of just that one to the mailing list. You will get
more help that way.
Anyhow it looks like a lot of these are successfully processing.
However, some of these are failing simply because your paths are incorrect.
It looks like you are only using the filename only, with not path, and
ffmpeg just can't find the file. This is probably because the file you are
trying to process is not in your current directory. I'm copy pasting one of
these examples
/bin/ffmpeg.d/ffmpeg -i FdaVGRew.mkv -vn -c:a libmp3lame -ab 320k -ac 2 -y
/thumbdrive-A/The_Smiths/MP3/FdaVGRew.mp3
ffmpeg version 3.0.2-static http://johnvansickle.com/ffmpeg/ Copyright (c)
2000-2016 the FFmpeg developers
built with gcc 5.3.1 (Debian 5.3.1-16) 20160424
configuration: --enable-gpl --enable-version3 --enable-static
--disable-debug --enable-libmp3lame --enable-libx264 --enable-libx265
--enable-libwebp --enable-libspeex --enable-libvorbis --enable-libvpx
--enable-libfreetype --enable-fontconfig --enable-libxvid
--enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libtheora
--enable-libvo-amrwbenc --enable-gray --enable-libopenjpeg --enable-libopus
--enable-libass --enable-gnutls --enable-libvidstab --enable-libsoxr
--enable-frei0r --enable-libfribidi --disable-indev=sndio
--disable-outdev=sndio --enable-librtmp --enable-libmfx --enable-libzimg
--cc=gcc
libavutil 55. 17.103 / 55. 17.103
libavcodec 57. 24.102 / 57. 24.102
libavformat 57. 25.100 / 57. 25.100
libavdevice 57. 0.101 / 57. 0.101
libavfilter 6. 31.100 / 6. 31.100
libswscale 4. 0.100 / 4. 0.100
libswresample 2. 0.101 / 2. 0.101
libpostproc 54. 0.100 / 54. 0.100
FdaVGRew.mkv: No such file or directory
On a side note, you seem to be getting a very verbose console display
which might be confusing matters. I think some keyboard shortcut causes
this to happen - it's happened to me by accident a few times.
Best,
Kieran.
The problem of file not found is caused by the naming conventions
used by youtube-dl - so that even if I enclose the filename in double
quotes,
ffmpeg is UNABLE to parse the name correctly
I don't know whether to blame youtube-dl or ffmpeg.
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
