Re: [FFmpeg-user] 'moov atom not found' during concat for mp4s that seem fine

2016-11-18 Thread Moritz Barsnick
On Fri, Nov 18, 2016 at 10:41:22 -0800, Zamir Khan wrote: > /$ ffmpeg -f concat -safe 0 -protocol_whitelist file,http,https,tcp,tls -f > mp4 -i segments.txt -c copy output [...] > [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f9b99010600] moov atom not found > segments.txt: Invalid data found when processing inpu

Re: [FFmpeg-user] Specifying lib path when building ffmpeg

2016-11-18 Thread Andy Furniss
Matteo Naccari wrote: Hi Andy, Are the source vids publicly available anywhere? Unfortunately no, we couldn’t clear the right for the content we used in our tests. Is turing-exe expected to work on non avx CPUs? I just get an illegal instruction on a Phenom II x4. Yes we expect it to wor

[FFmpeg-user] 'moov atom not found' during concat for mp4s that seem fine

2016-11-18 Thread Zamir Khan
Hi all, I'm a developer, but FFmpeg and video n00b, so please excuse my lack of experience there. I wanted to test out the FFmpeg 'concat' command today on some very short videos I have. The test batch is 3 MP4 files, each less than 10 seconds long. I followed the steps here (https://trac.ffmpeg.o

Re: [FFmpeg-user] Specifying lib path when building ffmpeg

2016-11-18 Thread Matteo Naccari
Hi Andy, > Are the source vids publicly available anywhere? Unfortunately no, we couldn’t clear the right for the content we used in our tests. > Is turing-exe expected to work on non avx CPUs? I just get an illegal > instruction on a Phenom II x4. Yes we expect it to work on non avx CPUs. Can

Re: [FFmpeg-user] Specifying lib path when building ffmpeg

2016-11-18 Thread Matteo Naccari
> Not sure I understand. > (Please correct me if the following is wrong / is not what you are saying:) > You > argue that to measure the quality of an encoder, it is not necessary to > decode the output bitstream and compare with the decoded bitstream of > other encoders but that it is sufficient

[FFmpeg-user] gdigrab on Windows 10 crashing the OS

2016-11-18 Thread Andrew
Im using gdigrab on Windows 10 (64bit) to capture the screen like this ffmpeg -f gdigrab -video_size 1620x917 -offset_x 4 -offset_y 90 -i desktop -b:v 1000k out.mp4 I can record short clips fine but if I leave it running for more than about 30 seconds the entire UI freezes then Windows reboot

Re: [FFmpeg-user] ffmpeg slowly get out of sync

2016-11-18 Thread Luo Xin
Yes, that's my first guess, and I try to fix it with "-async num" or "-vsync 1", I get the idea from: http://lzone.de/cheat-sheet/ffmpeg while for my case, it didn't related with different clock crystal (actually the two stream comes from same capture device), it is because I incorrectly use

Re: [FFmpeg-user] ffmpeg slowly get out of sync

2016-11-18 Thread Luo Xin
Hi Carl, This problem was solved, the root cause is big difference between audio and video start time, thanks for your help. BR, Xin Luo On 2016年11月16日 20:08, Carl Eugen Hoyos wrote: 2016-11-16 12:59 GMT+01:00 Luo Xin : - output hls segments Don't you agree that the issue would be easier