On 10/16/2020 10:14 PM, Carl Zwanzig wrote:
On 10/15/2020 1:44 AM, Mark Filipak (ffmpeg) wrote:
Got any suggestions how I should proceed?
I hate to say this, but you're rather reinventing the wheel (and building it
out of toothpicks).
You're absolutely right, Carl.
There are a fair number
On 10/15/2020 1:44 AM, Mark Filipak (ffmpeg) wrote:
Got any suggestions how I should proceed?
I hate to say this, but you're rather reinventing the wheel (and building it
out of toothpicks).
There are a fair number of mpeg-ts parsers already out there in a variety of
languages, and the kind
Moritz,
On Fri Oct 16 13:51:11 EEST 2020, FFmpeg user discussions wrote:
On Fri, Oct 16, 2020 at 20:26:16 +1100, FFmpeg user discussions wrote:
People,
I truncated a 14s file with:
ffmpeg -i 20201016_055828.mp4 -t 00:00:09 -async 1 cut.mp4
and although about 35% of the frames were removed
That worked, thank you. Also I was able to "fix" it by cutting off several
bytes using dd (like Micael Silva also suggested), although I'm not sure if
that keeps the file structure intact, so your solution is better.
On Sat, Oct 17, 2020 at 4:49 AM Carl Eugen Hoyos wrote:
> Am Sa., 17. Okt. 2020
Am Sa., 17. Okt. 2020 um 03:13 Uhr schrieb Ivan Gorin :
>
> Here is the link to a sample, it's the very beginning of the video, where I
> think the problem is. VLC says there is an indexing problem but it plays
> fine.
>
> https://drive.google.com/file/d/1hznkCKQWWbmxSSBQxwyKY-G3Kje_D9nh
I know th
On 10/16/2020 6:18 PM, Ivan Gorin wrote:
Yes, I've tried both of them, used different values from 1 million and
higher, no change. Was doing something like ffmpeg -probesize 10
-analyzeduration 10.Still sees only the video stream. Maybe I'm not
using them correctly, can you give
Here is the link to a sample, it's the very beginning of the video, where I
think the problem is. VLC says there is an indexing problem but it plays
fine.
https://drive.google.com/file/d/1hznkCKQWWbmxSSBQxwyKY-G3Kje_D9nh/view?usp=sharing
Attachments area
On Sat, Oct 17, 2020 at 3:57 AM Carl Euge
On Fri, Oct 16, 2020 at 10:13 PM Ivan Gorin wrote:
> Here is the link to a sample, it's the very beginning of the video, where I
> think the problem is. VLC says there is an indexing problem but it plays
> fine.
>
>
> https://drive.google.com/file/d/1hznkCKQWWbmxSSBQxwyKY-G3Kje_D9nh/view?usp=shar
Yes, I've tried both of them, used different values from 1 million and
higher, no change. Was doing something like ffmpeg -probesize 10
-analyzeduration 10.Still sees only the video stream. Maybe I'm not
using them correctly, can you give an example?
___
Here is the link to a sample, it's the very beginning of the video, where I
think the problem is. VLC says there is an indexing problem but it plays
fine.
https://drive.google.com/file/d/1hznkCKQWWbmxSSBQxwyKY-G3Kje_D9nh/view?usp=sharing
___
ffmpeg-user
On 10/16/2020 12:41 PM, Ivan Gorin wrote:
[avi @ 0x558097763700] New audio stream 0:1 at pos:18113032 and DTS:0s
[avi @ 0x558097763700] New audio stream 0:2 at pos:18113032 and DTS:0s
Have you tried using -analyzedurarion and -probesize with relative large
values to find the streams? See the
Am Sa., 17. Okt. 2020 um 02:31 Uhr schrieb Ivan Gorin :
>
> Here is the full output of ffprobe which i built from github (I hope I did
> it right). I don't know how to provide a sample input file since I can't
> cut the video - it loses the audio stream.
Use dd to cut the sample.
Carl Eugen
_
Here is the full output of ffprobe which i built from github (I hope I did
it right). I don't know how to provide a sample input file since I can't
cut the video - it loses the audio stream. The whole file is 9gb, so I
can't upload it.
ffprobe version N-99585-gfcec7a6848 Copyright (c) 2007-2020
Am Fr., 16. Okt. 2020 um 21:42 Uhr schrieb Ivan Gorin :
>
> I have several avi files I captured from miniDV cassettes, and now am
> trying to compress using ffmpeg. running ffprobe on one of the files yields
> this output:
Please (test current FFmpeg git head and) provide a sample input file.
Car
I have several avi files I captured from miniDV cassettes, and now am
trying to compress using ffmpeg. running ffprobe on one of the files yields
this output:
ffprobe thailand.avi
ffprobe version 4.2.4-1ubuntu0.1 Copyright (c) 2007-2020 the FFmpeg
developers
built with gcc 9 (Ubuntu 9.3.0-10ubun
On Fri, Oct 16, 2020 at 20:26:16 +1100, FFmpeg user discussions wrote:
> I truncated a 14s file with:
>
>ffmpeg -i 20201016_055828.mp4 -t 00:00:09 -async 1 cut.mp4
>
> and although about 35% of the frames were removed, the resulting mp4 was
> double the size - why is this?
You are reencoding t
People,
I truncated a 14s file with:
ffmpeg -i 20201016_055828.mp4 -t 00:00:09 -async 1 cut.mp4
and although about 35% of the frames were removed, the resulting mp4 was
double the size - why is this? I did a before and after mediainfo
comparison - see here:
http://pricom.com.au/Diff.ht
Hi James,
On Fri, Oct 16, 2020 at 03:11:36 -0500, jamesfowkes wrote:
> Further to this, I've managed to get a still frame to record into timestamped
> segments using:
>
> ffmpeg -loop 1 -i frame.png -reset_timestamps 1 -vcodec libx264 -f segment
> -segment_time 60 -strftime 1 +%Y-%m-%d_%H-%M-%S.mp
Further to this, I've managed to get a still frame to record into timestamped
segments using:
ffmpeg -loop 1 -i frame.png -reset_timestamps 1 -vcodec libx264 -f segment
-segment_time 60 -strftime 1 +%Y-%m-%d_%H-%M-%S.mp4
But while the segments are 60 seconds of wallclock time long, they are
recor
19 matches
Mail list logo
