Re: [FFmpeg-user] FFmpeg RTSP crash
On Sat, Sep 17, 2016 at 2:14 AM Carl Eugen Hoyoswrote: > 2016-09-16 15:39 GMT+02:00 Yu Ang Tan : > > I tried:this: > > > > $ git checkout master > > $ git fetch > > > > Then compile as usual. > > My knowledge of git is very limited but I believe you also need "git pull". > > Carl Eugen > ___ > 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". I'm happy to report that it's now working for both Linux and Windows. Seems like #5844 has been fixed a few days ago. Thanks for the help! ytan ___ 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".
Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API
Am 18.09.2016 um 00:49 schrieb Kieran O Leary: Hi On 17 Sep 2016 11:42 p.m., "Carl Eugen Hoyos"wrote: Unrelated: Am I the only one who has serious trouble receiving Phil's emails? Yes, on Gmail they go straight to spam, and are only included in a thread when someone replies pretty sure DMIM/DMARC and the wrong mail provider for using a mailing-list, many RCPT's these days are very strict ___ 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".
Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API
Hi On 17 Sep 2016 11:42 p.m., "Carl Eugen Hoyos"wrote: > > > > Unrelated: Am I the only one who has serious trouble receiving > Phil's emails? > Yes, on Gmail they go straight to spam, and are only included in a thread when someone replies. ___ 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".
Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API
On 9/18/16, Carl Eugen Hoyoswrote: > 2016-09-17 21:12 GMT+02:00 Phil Rhodes : >>> We are not Apple. >> >> Well, no, but someone on the list might have experience of doing this. >> In fact, I know for a fact that someone on the list has experience of >> doing this. > >> So why not let the conversation continue? > > Why do you believe that this conversation may not continue? > > Unrelated: Am I the only one who has serious trouble receiving > Phil's emails? You are not only one. ___ 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".
Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API
2016-09-17 2:54 GMT+02:00 muruganandh: > Apple is rejecting whatever i do. > > 1. I tried to use the static ffmpeg (3.1.3) by tessus. They rejected it. I would expect that this build includes SecureTransport (which is useful), we already know (thanks to you) that this is not accepted by Apple. > 2. I tried to build myself using this ./configure > --disable-protocol=tls_securetransport. They rejected it. This is not the option we discussed in this email thread. > 3. I have no idea how to build ffmpeg so that Apple guys accept it. But you also do not share why Apple refused it: Maybe they found out that the LGPL is not compatible with Apple's requirements for the App Store - I hope you agree that there is nothing that we can do to fix this;-( Carl Eugen ___ 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".
Re: [FFmpeg-user] ffmpeg and webm format and mkv format
2016-09-18 0:17 GMT+02:00 jd1008: >> Please try the option "-nostdin", whether >> that surpresses it. > I will try the option. While this will certainly help, I am still curious why you see this issue (that apparently nobody else sees). > But as you could see from the 1st 100 lines, it was a > private build by one of the ffmpeg developers. No. johnvansickle.com is not the page of an FFmpeg developer, it is a site to support you (assuming you don't know how to compile FFmpeg), I don't think it is "private" (in any way). As said, please download the current binary there (this should not be a release, releases are only for distributors, you are not a distributor). Note that many people use these binaries, I am sure they do not get the debug output that you posted. Please test again and share a few details about your system, maybe somebody understands what is going wrong. > I have tried official release of 3.x with similar failures. There is nothing "official" or "stable" about an FFmpeg release: It is a snapshot for Linux distributions that occasionally gets security updates. Users (and particularly users who need support on this mailing list) are recommended to use current FFmpeg which has less bugs and more features than any release. Carl Eugen ___ 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".
Re: [FFmpeg-user] ffmpeg and webm format and mkv format
On 09/17/2016 04:10 PM, Moritz Barsnick wrote: On Sat, Sep 17, 2016 at 11:59:48 -0600, jd1008 wrote: So, which "release" or "private build" should I use in order to properly transcode WEBM to MP4 ? Is WEBM a container arrangement? If so, why should it be a problem for ffmpeg to just extract the content? Your ffmpeg is behaving as if some keyboard interaction or other stuff on stdin is disturbing it. Please try the option "-nostdin", whether that surpresses it. This happens with every build of ffmpeg you have tried? Moritz I will try the option. But as you could see from the 1st 100 lines, it was a private build by one of the ffmpeg developers. I have tried official release of 3.x with similar failures. What's about webm thatis causing so much trouble? Is it a non-standard organization of the contents? ___ 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".
Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API
On Fri, Sep 16, 2016 at 17:54:38 -0700, muruganandh wrote: > Apple is rejecting whatever i do. [...] > 3. I have no idea how to build ffmpeg so that Apple guys accept it. Does Apple not provide any reason for rejection? Moritz ___ 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".
Re: [FFmpeg-user] ffmpeg and webm format and mkv format
On Sat, Sep 17, 2016 at 11:59:48 -0600, jd1008 wrote: > So, which "release" or "private build" should I use in order to properly > transcode WEBM to MP4 ? > Is WEBM a container arrangement? If so, why should it be a problem > for ffmpeg to just extract the content? Your ffmpeg is behaving as if some keyboard interaction or other stuff on stdin is disturbing it. Please try the option "-nostdin", whether that surpresses it. This happens with every build of ffmpeg you have tried? Moritz ___ 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".
Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API
> We are not Apple. Well, no, but someone on the list might have experience of doing this. In fact, I know for a fact that someone on the list has experience of doing this. So why not let the conversation continue? P ___ 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".
Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API
On 9/17/16, muruganandhwrote: > Apple is rejecting whatever i do. > > 1. I tried to use the static ffmpeg (3.1.3) by tessus. They rejected it. > 2. I tried to build myself using this ./configure > --disable-protocol=tls_securetransport. They rejected it. > 3. I have no idea how to build ffmpeg so that Apple guys accept it. > We are not Apple. ___ 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".
Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API
Where are you providing the source code of your app? I am trying to submit the app to mac app store. Should i post it somewhere and link it here? -- View this message in context: http://ffmpeg-users.933282.n4.nabble.com/Compiling-FFmpeg-without-SecIdentityCreate-API-tp4676487p4677598.html Sent from the FFmpeg-users mailing list archive at Nabble.com. ___ 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".
Re: [FFmpeg-user] Compiling FFmpeg without SecIdentityCreate API
Apple is rejecting whatever i do. 1. I tried to use the static ffmpeg (3.1.3) by tessus. They rejected it. 2. I tried to build myself using this ./configure --disable-protocol=tls_securetransport. They rejected it. 3. I have no idea how to build ffmpeg so that Apple guys accept it. -- View this message in context: http://ffmpeg-users.933282.n4.nabble.com/Compiling-FFmpeg-without-SecIdentityCreate-API-tp4676487p4677599.html Sent from the FFmpeg-users mailing list archive at Nabble.com. ___ 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".
Re: [FFmpeg-user] ffmpeg and webm format and mkv format
On 09/16/2016 01:43 PM, jd1008 wrote: On 09/16/2016 12:09 PM, Moritz Barsnick wrote: On Fri, Sep 16, 2016 at 19:56:26 +0200, Carl Eugen Hoyos wrote: The following lines are shown if you press "h" while encoding. Interesting. This line from the originally posted output also hints at keyboard interaction, in this case 'c': Parse error, at least 3 arguments were expected, only 1 given in string 'h-s66yCNu-sbk.webm' Do you have a cat? LOL! That comment took a while to sink in with me. (Even though I have a cat on my lap.) Moritz _ I had absolutely zero KB intgeraction as I started the transcode and went out for a coffee break. P.S: I have no pets and no one else shares the apt. :) :) So, which "release" or "private build" should I use in order to properly transcode WEBM to MP4 ? Is WEBM a container arrangement? If so, why should it be a problem for ffmpeg to just extract the content? ___ 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".
Re: [FFmpeg-user] "-acodec copy -vcodec copy" output smaller than original
Olexandr Melnyk wrote: >ffmpeg version 2.8.4 Copyright (c) 2000-2015 Please update to the last release or the current HEAD. ___ 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".
Re: [FFmpeg-user] "-acodec copy -vcodec copy" output smaller than original
> On Fri, Sep 16, 2016 at 20:29:20 EEST, Moritz Barsnick wrote: > Please do show us the complete, uncut console output of your command. Thanks for all the answers! Carl and Bertram were spot on. The number of zeroed bytes in the end of the source file roughly matches the difference in file size -- also on another sample file I checked. The number of streams checks out. Could you guys have a look at the console output to see if there might be anything else important I might be missing? smurf:Desktop kynlem$ ffmpeg -i Svalbard2016_g04033.mp4 -acodec copy -vcodec copy -map 0 output.mp4 ffmpeg version 2.8.4 Copyright (c) 2000-2015 the FFmpeg developers built with Apple LLVM version 7.0.0 (clang-700.1.76) configuration: --prefix=/usr/local/Cellar/ffmpeg/2.8.4 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-opencl --enable-libx264 --enable-libmp3lame --enable-libvo-aacenc --enable-libxvid --enable-libtheora --enable-libvorbis --enable-libvpx --enable-librtmp --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libass --enable-ffplay --enable-libspeex --enable-libschroedinger --enable-libfdk-aac --enable-libopus --enable-frei0r --enable-libopenjpeg --disable-decoder=jpeg2000 --extra-cflags=-I/usr/local/Cellar/openjpeg/1.5.2_1/include/openjpeg-1.5 --enable-nonfree --enable-vda libavutil 54. 31.100 / 54. 31.100 libavcodec 56. 60.100 / 56. 60.100 libavformat56. 40.101 / 56. 40.101 libavdevice56. 4.100 / 56. 4.100 libavfilter 5. 40.101 / 5. 40.101 libavresample 2. 1. 0 / 2. 1. 0 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 2.101 / 1. 2.101 libpostproc53. 3.100 / 53. 3.100 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f974a00d800] unsupported color_parameter_type aclc Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Svalbard2016_g04033.mp4': Metadata: major_brand : avc1 minor_version : 0 compatible_brands: avc1isom creation_time : 2016-07-13 18:03:54 Duration: 00:00:34.83, start: 0.00, bitrate: 19279 kb/s Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuvj420p(pc), 1920x1080 [SAR 1:1 DAR 16:9], 17992 kb/s, 29.97 fps, 29.97 tbr, 240k tbn, 59.94 tbc (default) Metadata: creation_time : 2016-07-13 18:03:54 handler_name: Ambarella AVC encoder : Ambarella AVC encoder Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 128 kb/s (default) Metadata: creation_time : 2016-07-13 18:03:54 handler_name: Ambarella AAC [mp4 @ 0x7f974a011600] Codec for stream 0 does not use global headers but container format requires global headers [mp4 @ 0x7f974a011600] Codec for stream 1 does not use global headers but container format requires global headers Output #0, mp4, to 'output.mp4': Metadata: major_brand : avc1 minor_version : 0 compatible_brands: avc1isom encoder : Lavf56.40.101 Stream #0:0(eng): Video: h264 ([33][0][0][0] / 0x0021), yuvj420p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 17992 kb/s, 29.97 fps, 29.97 tbr, 240k tbn, 240k tbc (default) Metadata: creation_time : 2016-07-13 18:03:54 handler_name: Ambarella AVC encoder : Ambarella AVC encoder Stream #0:1(eng): Audio: aac ([64][0][0][0] / 0x0040), 48000 Hz, stereo, 128 kb/s (default) Metadata: creation_time : 2016-07-13 18:03:54 handler_name: Ambarella AAC Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (copy) Press [q] to stop, [?] for help frame= 366 fps=0.0 q=-1.0 size= 27151kB time=00:00:12.22 bitrate=18195.6kbitsframe= 637 fps=630 q=-1.0 size= 47138kB time=00:00:21.26 bitrate=18155.5kbitsframe= 917 fps=600 q=-1.0 size= 67593kB time=00:00:30.57 bitrate=18112.8kbitsframe= 1044 fps=585 q=-1.0 Lsize= 77086kB time=00:00:34.81 bitrate=18138.0kbits/s video:76511kB audio:544kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.040283% And as for metadata, I ran diff on the metadata of the source and output files, and here's what I got: smurf:Desktop kynlem$ exiftool -G Svalbard2016_g04033.mp4 > Svalbard2016_g04033.exif smurf:Desktop kynlem$ exiftool -G output.mp4 > output.exif smurf:Desktop kynlem$ diff Svalbard2016_g04033.exif output.exif 2c2 < [File] File Name : Svalbard2016_g04033.mp4 --- > [File] File Name : output.mp4 4,8c4,8 < [File] File Size : 80 MB < [File] File Modification Date/Time : 2016:09:17 15:27:01+00:00 < [File] File Access Date/Time : 2016:09:17 15:27:43+00:00 < [File] File Inode Change Date/Time : 2016:09:17 15:27:01+00:00 < [File] File Permissions: rwxrwxrwx --- > [File] File Size : 75 MB > [File] File
Re: [FFmpeg-user] Running ffmpeg on AWS Lambda
As I said I'm trying to run it on AWS Lambda not quite sure how to do that! But I tried to run it with '-v 9 -loglevel 99' and strangely it worked this time without crashing!! How could it be possible I have also move -y option to the end before output file name. how could it be possible?! 2016-09-17T06:46:28.510Z 71186893-7ca2-11e6-851c-39c7834dac2d ffmpeg err ffmpeg version N-81664-g6f062eb-static http://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2016 the FFmpeg developers built with gcc 5.4.1 (Debian 5.4.1-2) 20160904 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-5 libavutil 55. 29.100 / 55. 29.100 libavcodec 57. 55.101 / 57. 55.101 libavformat 57. 49.100 / 57. 49.100 libavdevice 57. 0.102 / 57. 0.102 libavfilter 6. 62.100 / 6. 62.100 libswscale 4. 1.100 / 4. 1.100 libswresample 2. 1.100 / 2. 1.100 libpostproc 54. 0.100 / 54. 0.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ... matched as input file with argument '/tmp/724a58c0-7ca2-11e6-88ec-db376fcfe187/%03d.jpg'. Reading option '-framerate' ... matched as AVOption 'framerate' with argument '1'. Reading option '-c:v' ... matched as option 'c' (codec name) with argument 'libx264'. Reading option '-r' ... matched as option 'r' (set frame rate (Hz value, fraction or abbreviation)) with argument '30'. Reading option '-pix_fmt' ... matched as option 'pix_fmt' (set pixel format) with argument 'yuv420p'. Reading option '-y' ... matched as option 'y' (overwrite output files) with argument '1'. Reading option '/tmp/72d8dd20-7ca2-11e6-88ec-db376fcfe187.mp4' ... matched as output file. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument 9. Applying option y (overwrite output files) with argument 1. Successfully parsed a group of options. Parsing a group of options: input file /tmp/724a58c0-7ca2-11e6-88ec-db376fcfe187/%03d.jpg. Successfully parsed a group of options. Opening an input file: /tmp/724a58c0-7ca2-11e6-88ec-db376fcfe187/%03d.jpg. Probing image2 score:100 size:0 [file @ 0x5562200] Setting default whitelist 'file,crypto' [AVIOContext @ 0x5562380] Statistics: 9804675 bytes read, 0 seeks [mjpeg @ 0x555ee80] marker=d8 avail_size_in_buf=9804673 [mjpeg @ 0x555ee80] marker parser used 0 bytes (0 bits) [mjpeg @ 0x555ee80] marker=e1 avail_size_in_buf=9804671 [mjpeg @ 0x555ee80] marker parser used 20785 bytes (166280 bits) [mjpeg @ 0x555ee80] marker=db avail_size_in_buf=9783883 [mjpeg @ 0x555ee80] index=0 [mjpeg @ 0x555ee80] qscale[0]: 0 [mjpeg @ 0x555ee80] index=1 [mjpeg @ 0x555ee80] qscale[1]: 0 [mjpeg @ 0x555ee80] marker parser used 132 bytes (1056 bits) [mjpeg @ 0x555ee80] marker=c0 avail_size_in_buf=9783749 [mjpeg @ 0x555ee80] Changing bps from 0 to 8 [mjpeg @ 0x555ee80] sof0: picture: 5312x2988 [mjpeg @ 0x555ee80] component 0 2:2 id: 0 quant:0 [mjpeg @ 0x555ee80] component 1 1:1 id: 1 quant:1 [mjpeg @ 0x555ee80] component 2 1:1 id: 2 quant:1 [mjpeg @ 0x555ee80] pix fmt id 2200 [mjpeg @ 0x555ee80] marker parser used 17 bytes (136 bits) [mjpeg @ 0x555ee80] marker=c4 avail_size_in_buf=9783730 [mjpeg @ 0x555ee80] marker parser used 0 bytes (0 bits) [mjpeg @ 0x555ee80] escaping removed 36375 bytes [mjpeg @ 0x555ee80] marker=da avail_size_in_buf=9783310 [mjpeg @ 0x555ee80] marker parser used 0 bytes (0 bits) [mjpeg @ 0x555ee80] marker=d9 avail_size_in_buf=0 [mjpeg @ 0x555ee80] decode frame unused 0 bytes [image2 @ 0x555d760] Probe buffer size limit of 500 bytes reached [image2 @ 0x555d760] stream 0: start_time: 0.000 duration: 0.160 [image2 @ 0x555d760] format: start_time: 0.000 duration: 0.160 bitrate=0 kb/s Input #0, image2, from '/tmp/724a58c0-7ca2-11e6-88ec-db376fcfe187/%03d.jpg': Duration: 00:00:00.16, start: 0.00, bitrate: N/A Stream #0:0, 1, 1/25: Video: mjpeg, 1 reference frame, yuvj420p(pc, bt470bg/unknown/unknown, center), 5312x2988, 0/1, 25 tbr, 25 tbn, 25 tbc Successfully opened the file. Parsing a group of options: output file /tmp/72d8dd20-7ca2-11e6-88ec-db376fcfe187.mp4. Applying option c:v (codec name) with argument libx264. Applying option r (set frame rate (Hz value, fraction or abbreviation)) with argument 30. Applying option pix_fmt (set pixel format) with argument yuv420p. Successfully parsed a group of