2018-02-07 14:06 GMT+01:00 Ronan Ricou :
> The video itself seems fine (same duration, frame accurate), it's
> just that I don't know where the size difference come from and
> what information are lost.
Which size difference?
> I tried to open the file created by FFMPEG
Hello gus:
I want to use ffmpeg for iOS,but I can`t find the docment aobut Ios .so please
tell how to use it into my iOS project,
I want to realize function of live telecast
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
2018-02-06 14:25 GMT+01:00 Thomas Schmiedl :
> ffmpeg version 3.4.1 Copyright (c) 2000-2017 the FFmpeg developers
Please test current FFmpeg git head, nothing else is supported here.
> Error message on TV is "file not readable" and in ffmpeg "Broken pipe".
Assuming this
> The needed options for this test are:
> $ ./configure && make ffmpeg
Hi again,
Just had a look at it, I think that I could as well add this line after line
1165 :
case 2160: f1 = 42; f2 = 0; break; // progressive
Right ?
Fred
___
2018-02-07 17:18 GMT+01:00 Frédéric Busnel-Joncour :
>> The needed options for this test are:
>> $ ./configure && make ffmpeg
>
>
> Hi again,
>
>
> Just had a look at it, I think that I could as well add this line after line
> 1165 :
>
> case 2160: f1 = 42; f2 = 0;
i am working on an FFmpeg Bash script in linux.
I am currently using HD Homerun which downloads ,TS files or transport
stream which is a container with an mpeg2 inside with a closed caption
steam for the subtitles. Plex media server will not recognize the closed
caption though VLC will.
my
OS: Ubuntu 16.04 64bit
CPU: intel i7 6700
H264:
ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -hwaccel_device
/dev/dri/renderD128 -i a.h264 -c:v h264_vaapi -f h264 t.h264 -y
108fps
H265:
ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -hwaccel_device
/dev/dri/renderD128 -i a.h265 -c:v
> 2018-02-06 20:29 GMT+01:00 Jason Player :
>
>> ffprobe version 3.0.2 Copyright (c) 2007-2016 the FFmpeg developers
>
> Please test current FFmpeg git head and please do not top-post here.
>
> Carl Eugen
The old version was the problem. I¹m all set now, thanks for the help!
>
> Took a bit more than a few minutes, but I managed to compile using MSYS2.
> It means that some dependencies aren't included, but for testing it's ok.
>
> I changed the BLKSIZE constant to 512 and it still didn't work with XAudio.
>
> So I took a closer look at the code. Turns out that the
On Wed, Feb 7, 2018 at 9:24 PM, Steve Boyer wrote:
>
> On Feb 7, 2018 6:37 PM, "Shaun Nixon" wrote:
>
> i am working on an FFmpeg Bash script in linux.
> I am currently using HD Homerun which downloads ,TS files or transport
> stream which is a
Hello Shi Qiu,
I have two thoughts:
1. Is that the best possible experiment with only one variable changed
between the two cases? It looks like the input format changed, too,
although the filenames are possibly fake simple examples (simplicity is
good). The H264 output has a.h264 as the
Thanks Zak,
I think the problem may related to the OS or the driver. I used the same
input media (1080P video) on Windows 7, H264 encoder(240fps) is much faster
than H265 encoder(80fps).
After some tests, I've found that the problem is that SKL H264 encoder
(100fps) is quite slow with old vaapi
On Feb 7, 2018 6:37 PM, "Shaun Nixon" wrote:
i am working on an FFmpeg Bash script in linux.
I am currently using HD Homerun which downloads ,TS files or transport
stream which is a container with an mpeg2 inside with a closed caption
steam for the subtitles. Plex media
Hi,
I know this because the size of the video stream isn't the same on the remuxed
file. As its duration is the same as I can play it without any problem, I think
some metadata were stripped off, but I don't know which and why. You can also
see this in the MediaInfo report I included in my
>> Thanks for support again !
>> As I'm not the end user, it's difficult to tell you exactly, but the problem
>> occurs with Avid Media Composer.
>> Video Line Map should be at 42, and it's at 0.
>
> Sorry, I am not sure I understand correctly:
> If you change the value "0" for Video Line Map in
2018-02-07 9:30 GMT+01:00 Ronan Ricou :
> I know this because the size of the video stream isn't the same on the
> remuxed file.
How did you check this?
Please do not top-post here, Carl Eugen
(And please do not use external resources for the console output,
they can
2018-02-07 10:32 GMT+01:00 Frédéric Busnel-Joncour :
>>> Thanks for support again !
>>> As I'm not the end user, it's difficult to tell you exactly, but the problem
>>> occurs with Avid Media Composer.
>>> Video Line Map should be at 42, and it's at 0.
>>
>> Sorry, I am not sure I
2018-02-07 7:03 GMT+01:00 qw :
> ffmpeg version 3.4.1 Copyright (c) 2000-2017 the FFmpeg developers
Please remember that only current FFmpeg git head is supported here.
[...]
> Input #0, mpegts, from './hanma.ts':
> Duration: 00:02:39.78, start: 1.40, bitrate: 10913
Media info output, as I included in my initial question. Stream size in
original file is 15.9GiB and 15.8GiB on ffmpeg remuxed one. Stream size for all
audio element is the exact same on both files.
In addition, if you look at the report I linked, you will also see that the
overall bitrate
>>> Sorry, I am not sure I understand correctly:
>>> If you change the value "0" for Video Line Map in a 3840x2160 file
>>> created with FFmpeg to "42", the file works with Avid Media Composer?
>>
>> As far as I know, yes.
>
> How do you know?
Technical advise of the TV Network that handled the
The video itself seems fine (same duration, frame accurate), it's just that I
don't know where the size difference come from and what information are lost.
I tried to open the file created by FFMPEG to BlackMagic Design Resolve
software, and it won't.
As I don't have any problem with the
> The needed options for this test are:
> $ ./configure && make ffmpeg
Yes, but I sometimes need some additional features and codecs. ;-)
Best regards,
Fred
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
2018-02-07 12:47 GMT+01:00 Frédéric Busnel-Joncour :
Sorry, I am not sure I understand correctly:
If you change the value "0" for Video Line Map in a 3840x2160 file
created with FFmpeg to "42", the file works with Avid Media Composer?
>>>
>>> As far as I know, yes.
2018-02-07 12:21 GMT+01:00 Ronan Ricou :
> Media info output, as I included in my initial question.
I don't think FFmpeg drops video data for your command
line and I don't think MediaInfo would be able to show
you such a drop.
Feel free to use third-party tools to
24 matches
Mail list logo