Re: [FFmpeg-user] DeckLink Output Controls

[Erik Dobberkau]

Am Dienstag, 11. Oktober 2016 schrieb Reuben Martin :
>
>
> I’m not sure there is a difference between 20 and 24 bit audio (in
> reguards to
> the bit allocation within the signal) since 20 bit is usually padded
> inside of
> a 24 or 32 bit word size.
>
>
Both SD and HD SDI video use AES-3 audio for PCM streaming, which again is
20bits by default, but one may occupy the 4 user bits in each frame to
allow for 24bits PCM word length. So yes, the bit allocation is the same
with or without the nibble of the four LSB.
___
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] DeckLink Output Controls

[Reuben Martin]

On Sunday, October 9, 2016 11:48:27 PM CDT Marcelo Boufleur wrote:
> > SDI is 20bit 48k audio only. There’s really no good reason for anything
> > else.
> > Technically SDI also supports 48048 and 47952 to allow for pull up/down,
> > but I
> > think that is done by manipulating the clock rather than explicitly
> > changing
> > the sample rate.
> 
> SD-SDI PCM Audio is 20 bits, but it can also support 24 bits according to
> SMPTE 272M.
> Sampling rate can also range from 32Khz to 48Khz.
> 
> For HD, there's also SMPTE 299M which mandates 24 bit audio, and also
> sampling rates range from 32Khz to 48Khz.

Although that is in the official spec, I have never seen any SDI equipment use 
anything other than 48k. Doesn’t mean any doesn’t exist, but if so it’s not 
very common.

I’m not sure there is a difference between 20 and 24 bit audio (in reguards to 
the bit allocation within the signal) since 20 bit is usually padded inside of 
a 24 or 32 bit word size. 

> 
> You can also have 20 bit in HD (and also SD) in the form of non-audio PCM
> Data, using SMPTE 337M format (for Dolby-E and other compressed formats
> described in SMPTE 338M).



___
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] Developer "cehoyos" closed my bug without any explanation, and without solving it

[Steven Liu]

2016-10-11 8:30 GMT+08:00 Alexey Eromenko :

> > Hello,
> >
> > sorry you feel this way, but looking at your bug report do you seem to
> have
> > a misunderstand regarding who is responsible for which bugs. You state
> that
> > it's Apple's decoder that cannot play the videos. And at the same time do
> > you state VLC does play them. VLC uses ffmpeg's libraries so it obviously
> > works with ffmpeg, just not with Apple's decoder. Further more do you
> state
> > that the videos were created with libx264, which if it was the source of
> > your problem, is also not part of ffmpeg but only an external library and
> > has its own project. In short, you have no case.
> >
> > You first need to accept that the problem is very likely with the Apple
> > decoder. Just because you cannot find anyone at Apple to listen to your
> > problem doesn't mean you can shove it onto ffmpeg. You have also reopened
> > the bug report several times, which suggest a certain stubbornness in
> > accepting these facts. You then have to provide evidence of this being an
> > ffmpeg bug, and you have so far only provided evidence against it.
> Cehoyos's
> > responses were also quite clear and not unfriendly at all, because he
> told
> > you how to solve your problem.
> >
> > I suggest that you change your stance in this matter and stop acting like
> > Cehoyos would owe you an apology.
> >
> > User problems are handled here on this maling list and not on the bug
> > tracker. Or do you disagree?
> >
>
> It well may be an Apple bug, but since I can't find anyone at Apple to
> fix it, I think fixing it in the encoder is way simpler, and it is the
> way to go. Especially because it's open-source and because Apple
> players are popular.
>
> Discovering after-the-fact that some of my videos are incompatible
> with Apple decoders is a no-no, and a total shock for me. And no
> documentation on such fundamental issues _AT ALL_. Even the workaround
> parameter he suggested is not documented either.
>
> Like I know for sure that a BMP file is a Bitmap and is displayed
> correctly every time, on all computers and operating systems, and MP3
> file is an audio file, and is played back correctly every time, on all
> supported platforms, I expect the same from MP4 video file -- it must
> be played perfectly on all supported platforms, and since those
> poipular decoders are well-known, the encoder can target their
> limitations too.
>
> For ffmpeg developers fixing this bug maybe simple, just parsing the
> container tags properly, and yes, testing resulting MP4 files with the
> popular media players is super-critical; This means at least Windows
> (Windows Media Player and VLC), Android (Google Nexus and Samsung
> Galaxy) and Apple (iOS + Mac OS). Perhaps not for every minor release,
> but for major releases QA is a must-have.
>
> I can do some of the testing myself, being a QA guy, I'm capable of
> this task, but when there is a severe and critical issue, alarms must
> be sounded. It's my duty. (+I can add testing on Chromebook and Debian
> Linux and other platforms)
>
> --
> -Alexey Eromenko "Technologov"
>

Patch welcome.

> ___
> 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".
>
___
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] Developer "cehoyos" closed my bug without any explanation, and without solving it

[Alexey Eromenko]

> Hello,
>
> sorry you feel this way, but looking at your bug report do you seem to have
> a misunderstand regarding who is responsible for which bugs. You state that
> it's Apple's decoder that cannot play the videos. And at the same time do
> you state VLC does play them. VLC uses ffmpeg's libraries so it obviously
> works with ffmpeg, just not with Apple's decoder. Further more do you state
> that the videos were created with libx264, which if it was the source of
> your problem, is also not part of ffmpeg but only an external library and
> has its own project. In short, you have no case.
>
> You first need to accept that the problem is very likely with the Apple
> decoder. Just because you cannot find anyone at Apple to listen to your
> problem doesn't mean you can shove it onto ffmpeg. You have also reopened
> the bug report several times, which suggest a certain stubbornness in
> accepting these facts. You then have to provide evidence of this being an
> ffmpeg bug, and you have so far only provided evidence against it. Cehoyos's
> responses were also quite clear and not unfriendly at all, because he told
> you how to solve your problem.
>
> I suggest that you change your stance in this matter and stop acting like
> Cehoyos would owe you an apology.
>
> User problems are handled here on this maling list and not on the bug
> tracker. Or do you disagree?
>

It well may be an Apple bug, but since I can't find anyone at Apple to
fix it, I think fixing it in the encoder is way simpler, and it is the
way to go. Especially because it's open-source and because Apple
players are popular.

Discovering after-the-fact that some of my videos are incompatible
with Apple decoders is a no-no, and a total shock for me. And no
documentation on such fundamental issues _AT ALL_. Even the workaround
parameter he suggested is not documented either.

Like I know for sure that a BMP file is a Bitmap and is displayed
correctly every time, on all computers and operating systems, and MP3
file is an audio file, and is played back correctly every time, on all
supported platforms, I expect the same from MP4 video file -- it must
be played perfectly on all supported platforms, and since those
poipular decoders are well-known, the encoder can target their
limitations too.

For ffmpeg developers fixing this bug maybe simple, just parsing the
container tags properly, and yes, testing resulting MP4 files with the
popular media players is super-critical; This means at least Windows
(Windows Media Player and VLC), Android (Google Nexus and Samsung
Galaxy) and Apple (iOS + Mac OS). Perhaps not for every minor release,
but for major releases QA is a must-have.

I can do some of the testing myself, being a QA guy, I'm capable of
this task, but when there is a severe and critical issue, alarms must
be sounded. It's my duty. (+I can add testing on Chromebook and Debian
Linux and other platforms)

-- 
-Alexey Eromenko "Technologov"
___
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] Developer "cehoyos" closed my bug without any explanation, and without solving it

[Sven C. Dack]

On 10/10/16 23:23, Alexey Eromenko wrote:

Hello all,

Bug #5882; Certain x264 videos do not play on Apple decoders
(Quicktime/iTunes/iPad)

Today was closed by developer "cehoyos" without any explanation, and
without any resolution.
He treats all bugs like that ? Worse yet; he treats all people like bugs ?

--
-Alexey Eromenko "Technologov"
___
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".


Hello,

sorry you feel this way, but looking at your bug report do you seem to have a 
misunderstand regarding who is responsible for which bugs. You state that it's 
Apple's decoder that cannot play the videos. And at the same time do you state 
VLC does play them. VLC uses ffmpeg's libraries so it obviously works with 
ffmpeg, just not with Apple's decoder. Further more do you state that the videos 
were created with libx264, which if it was the source of your problem, is also 
not part of ffmpeg but only an external library and has its own project. In 
short, you have no case.


You first need to accept that the problem is very likely with the Apple decoder. 
Just because you cannot find anyone at Apple to listen to your problem doesn't 
mean you can shove it onto ffmpeg. You have also reopened the bug report several 
times, which suggest a certain stubbornness in accepting these facts. You then 
have to provide evidence of this being an ffmpeg bug, and you have so far only 
provided evidence against it. Cehoyos's responses were also quite clear and not 
unfriendly at all, because he told you how to solve your problem.


I suggest that you change your stance in this matter and stop acting like 
Cehoyos would owe you an apology.


User problems are handled here on this maling list and not on the bug tracker. 
Or do you disagree?



___
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".

[FFmpeg-user] Developer "cehoyos" closed my bug without any explanation, and without solving it

[Alexey Eromenko]

Hello all,

Bug #5882; Certain x264 videos do not play on Apple decoders
(Quicktime/iTunes/iPad)

Today was closed by developer "cehoyos" without any explanation, and
without any resolution.
He treats all bugs like that ? Worse yet; he treats all people like bugs ?

--
-Alexey Eromenko "Technologov"
___
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] Encoding Apple-Quicktime compatible videos ? - Broken videos on Apple

[Alexey Eromenko]

Sadly ffmpeg developers don't care about bugs, and close bugs without
any explanation.

https://trac.ffmpeg.org/ticket/5882#comment:10
___
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] Encoding Apple-Quicktime compatible videos ? - Broken videos on Apple

[Alexey Eromenko]

I have provided a new test case and a new evidence for this bug:
https://trac.ffmpeg.org/ticket/5882

-- 
-Alexey Eromenko "Technologov"
___
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] Configure does not find any dependencies anymore

[Nomis101 ]

Am 10.10.16 um 21:19 schrieb Cley Faye:
> ​Others might be more knowledgeable about the specifics of mac dev.
> environments, but it seems that pkg-config is not available.
> There seem to be support for pkg-config in homebrew.

Yes, I also found this out just now. Installing pkg-config via Macports
did the trick. Don't know at which point I lost my pkg-config. But now
it works just fine. Thanks for your support!

___
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] Configure does not find any dependencies anymore

[Cley Faye]

2016-10-10 19:57 GMT+02:00 Nomis101  :

> OK. Please find attached the config.log. The output of "pkg-config
> --list-all" is:
>
> $ pkg-config --list-all
> -bash: pkg-config: command not found
>

​Also in the config.log:
> WARNING: pkg-config not found, library detection may fail.​


​Others might be more knowledgeable about the specifics of mac dev.
environments, but it seems that pkg-config is not available.
There seem to be support for pkg-config in homebrew.
___
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] Selecting/dropping frames without re-encoding

[Mikhail V]

On 8 October 2016 at 00:31, Carl Eugen Hoyos  wrote:
> 2016-10-08 0:01 GMT+02:00 Mikhail V :
>> BTW after that manipulations a fair question arizes: why
>> ffmpeg does not support something like:
>>  "... -f image2 -i filelist.txt output"
>
> (This command tries to read a frame / imagefile called filelist.txt)
> It does, it is called -f concat and is just an alternative of your
> python script.
>
> Carl Eugen

Hi again.
Since you say that "-f concat" should work same as -f image2 to create
video from images,
probably you can pour some light on what I am doing wrong then.
Note that ideally I need an MOV file because Sony Vegas cannot open MXF files
 for some reason so MOV container is preferred.
So I have a file "concat.txt" in my case it holds following data:

file 'frame0001'
file 'frame0003'
file 'frame0005'
file 'frame0007'
file 'frame0009'
file 'frame0011'


So it is simply a list of odd frames  generated by my script.
Now to create a MXF I use this command:

$ffmpeg -f concat -r 25 -i concat.txt -vcodec copy out.mxf

Which is probably not correct?  but I don't know exact right command.
The result seems correct BUT ffmpeg spits out errors on each frame
(here is only last part of the output):



[mxf @ 028f2461b200] Application provided invalid, non
monotonically increasing dts to muxer in stream 0: 1 >= 0
Last message repeated 62 times
frame=  813 fps= 46 q=-1.0 size=  365042kB time=00:00:00.08
bitrate=37380251.6kbits/s
[mxf @ 028f2461b200] Application provided invalid, non
monotonically increasing dts to muxer in stream 0: 1 >= 0
Last message repeated 140 times
frame=  954 fps= 52 q=-1.0 size=  428351kB time=00:00:00.08
bitrate=43863093.2kbits/s
[mxf @ 028f2461b200] Application provided invalid, non
monotonically increasing dts to muxer in stream 0: 1 >= 0
Last message repeated 138 times
frame= 1093 fps= 58 q=-1.0 size=  490762kB time=00:00:00.08
bitrate=50253979.6kbits/s
[mxf @ 028f2461b200] Application provided invalid, non
monotonically increasing dts to muxer in stream 0: 1 >= 0
Last message repeated 142 times
frame= 1236 fps= 64 q=-1.0 size=  554969kB time=00:00:00.08
bitrate=56828776.4kbits/s
 [mxf @ 028f2461b200] Application provided invalid, non
monotonically increasing dts to muxer in stream 0: 1 >= 0
Last message repeated 142 times
frame= 1379 fps= 70 q=-1.0 size=  619176kB time=00:00:00.08
bitrate=63403573.2kbits/s
 [mxf @ 028f2461b200] Application provided invalid, non
monotonically increasing dts to muxer in stream 0: 1 >= 0
Last message repeated 120 times
frame= 1500 fps= 74 q=-1.0 Lsize=  673506kB time=00:00:00.08
bitrate=68966967.7kbits/s speed=0.00395x
video:672000kB audio:0kB subtitle:0kB other streams:0kB global
headers:0kB muxing overhead: 0.224039%


As said the resulting file is correct, but what does these errors mean
I am not sure.
Anyway if I use -f image2 to generate a same video no errors appear -
how is that?
What is correct command then for concat if I am doing it wrong?

Now the same command for mov container. MOV is also valid for DNxHD codec and
 actually is preferred in my case since MXF files cannot be opened by
Sony Vegas.

$ffmpeg -f concat -r 25 -i concat.txt -vcodec copy out.mxf

And the output (last part of it, since it also spits out errors on each frame):

[mov @ 014afd95b200] Non-monotonous DTS in output stream 0:0;
previous: 1258, current: 0; changing to 1259. This may result in
incorrect timestamps in the output file.
[mov @ 014afd95b200] Non-monotonous DTS in output stream 0:0;
previous: 1259, current: 512; changing to 1260. This may result in
incorrect timestamps in the output file.
[mov,mp4,m4a,3gp,3g2,mj2 @ 014aff2a0420] moov atom not found
[concat @ 014afd956640] Impossible to open 'out.mov'
concat.txt: Invalid data found when processing input
frame=  750 fps= 43 q=-1.0 Lsize=  336002kB time=00:00:00.13
bitrate=19882772.1kbits/s speed=0.00788x
video:336000kB audio:0kB subtitle:0kB other streams:0kB global
headers:0kB muxing overhead: 0.000698%

In this case it produces a file but it is _incorrect_
See FFPROBE for mov file - fps is nonsense:

$ffprobe out.mov

ffprobe version N-79107-g30d1213 Copyright (c) 2007-2016 the FFmpeg developers
  built with gcc 5.3.0 (GCC)
  configuration: --enable-gpl --enable-version3 --disable-w32threads
--enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r
--enable-gnutls --enable-iconv --enable-libass --enable-libbluray
--enable-libbs2b --enable-libcaca --enable-libdcadec
--enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc
--enable-libmodplug --enable-libmfx --enable-libmp3lame
--enable-libopencore-amrnb --enable-libopencore-amrwb
--enable-libopenjpeg --enable-libopus --enable-librtmp
--enable-libschroedinger --enable-libsnappy --enable-libsoxr
--enable-libspeex --enable-libtheora --enable-libtwolame
--enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis
--enable-libvpx