Specify FC instead of mono‏

classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Specify FC instead of mono‏

speedyrazor
Sent again to correct formatting.
Hi, I am trying to specify a single mono channel to be named 'Center' when viewed in Quicktime player, I know that technically specifying FC is mono, but in my user case I need it to actually be named 'Center', not 'Mono'. Is there someone who would kindly help me resolve this issue please, as I have searched everywhere to keep this work inside of ffmpeg without having to resort to a 3rd party application. I am used to applying ffmpeg patches, so if there is anyone who could easily write a patch, that would be amazing and very much appreciated.So I am specifying the 3rd audio channel to be labeled 'FC', so when viewing the file in Quicktime player, I want it to be labeled as 'center', not 'mono'. All the other channel labels are coming out named as I have specified, so I just want the center to come out. Here is my code, you'll see what I am trying to achieve:

 ffmpeg -i /Users/kev/Movies/Test_descrete.mov -ss 45 -to 50 -filter_complex \

> "[0:1]pan=FL|c0=c0[FL]; \
>  [0:1]pan=FR|c0=c1[FR]; \
>  [0:1]pan=FC|c0=c2[FC]; \
>  [0:1]pan=LFE|c0=c3[LFE]; \
>  [0:1]pan=BL|c0=c4[BL]; \
>  [0:1]pan=BR|c0=c5[BR]; \
>  [0:1]pan=DL+DR|c0=c6|c1=c7[stereo]" \
> -map v:0 \
> -map "[FL]" \
> -map "[FR]" \
> -map "[FC]" \
> -map "[LFE]" \
> -map "[BL]" \
> -map "[BR]" \
> -map "[stereo]" \
> -vcodec prores -profile:v 3 -vtag apcn -f mov -y -c:a pcm_s24le /Users/kev/Movies/5_1_Sterero.mov
ffmpeg version 2.8.1-tessus Copyright (c) 2000-2015 the FFmpeg developers
  built with Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn)
  configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --as=yasm --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libass --enable-libbluray --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopus --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzmq --enable-version3 --disable-ffplay --disable-indev=qtkit --disable-indev=x11grab_xcb
  libavutil      54. 31.100 / 54. 31.100
  libavcodec     56. 60.100 / 56. 60.100
  libavformat    56. 40.101 / 56. 40.101
  libavdevice    56.  4.100 / 56.  4.100
  libavfilter     5. 40.101 /  5. 40.101
  libswscale      3.  1.101 /  3.  1.101
  libswresample   1.  2.101 /  1.  2.101
  libpostproc    53.  3.100 / 53.  3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Users/kev/Movies/Test_descrete.mov':
  Metadata:
    major_brand     : qt  
    minor_version   : 537199360
    compatible_brands: qt  
    creation_time   : 2015-10-17 18:55:33
  Duration: 00:01:58.04, start: 0.000000, bitrate: 170075 kb/s
    Stream #0:0(eng): Video: prores (apch / 0x68637061), yuv422p10le, 1920x1080, 160844 kb/s, 24 fps, 24 tbr, 24 tbn, 24 tbc (default)
    Metadata:
      creation_time   : 2015-10-17 18:55:33
      handler_name    : Apple Alias Data Handler
      encoder         : Apple ProRes 422 HQ
    Stream #0:1(eng): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 8 channels (FL+FR+FC+LFE+SL+SR+DL+DR), s32 (24 bit), 9216 kb/s (default)
    Metadata:
      creation_time   : 2015-10-17 19:13:26
      handler_name    : Apple Alias Data Handler
[Parsed_pan_6 @ 0x7f8d30419900] Pure channel mapping detected: 6 7
[Parsed_pan_5 @ 0x7f8d304196c0] Pure channel mapping detected: 5
[Parsed_pan_4 @ 0x7f8d304193c0] Pure channel mapping detected: 4
[Parsed_pan_3 @ 0x7f8d30419080] Pure channel mapping detected: 3
[Parsed_pan_2 @ 0x7f8d30418d40] Pure channel mapping detected: 2
[Parsed_pan_1 @ 0x7f8d30418a20] Pure channel mapping detected: 1
[Parsed_pan_0 @ 0x7f8d304182c0] Pure channel mapping detected: 0
Output #0, mov, to '/Users/kev/Movies/5_1_Sterero.mov':
  Metadata:
    major_brand     : qt  
    minor_version   : 537199360
    compatible_brands: qt  
    encoder         : Lavf56.40.101
    Stream #0:0(eng): Video: prores (apch) (apch / 0x68637061), yuv422p10le, 1920x1080, q=2-31, 200 kb/s, 24 fps, 12288 tbn, 24 tbc (default)
    Metadata:
      creation_time   : 2015-10-17 18:55:33
      handler_name    : Apple Alias Data Handler
      encoder         : Lavc56.60.100 prores
    Stream #0:1: Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, 1 channels (FL), s32, 1152 kb/s (default)
    Metadata:
      encoder         : Lavc56.60.100 pcm_s24le
    Stream #0:2: Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, 1 channels (FR), s32, 1152 kb/s
    Metadata:
      encoder         : Lavc56.60.100 pcm_s24le
    Stream #0:3: Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, mono, s32, 1152 kb/s
    Metadata:
      encoder         : Lavc56.60.100 pcm_s24le
    Stream #0:4: Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, 1 channels (LFE), s32, 1152 kb/s
    Metadata:
      encoder         : Lavc56.60.100 pcm_s24le
    Stream #0:5: Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, 1 channels (BL), s32, 1152 kb/s
    Metadata:
      encoder         : Lavc56.60.100 pcm_s24le
    Stream #0:6: Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, 1 channels (BR), s32, 1152 kb/s
    Metadata:
      encoder         : Lavc56.60.100 pcm_s24le
    Stream #0:7: Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz, downmix, s32, 2304 kb/s
    Metadata:
      encoder         : Lavc56.60.100 pcm_s24le
Stream mapping:
  Stream #0:1 (pcm_s24le) -> pan (graph 0)
  Stream #0:1 (pcm_s24le) -> pan (graph 0)
  Stream #0:1 (pcm_s24le) -> pan (graph 0)
  Stream #0:1 (pcm_s24le) -> pan (graph 0)
  Stream #0:1 (pcm_s24le) -> pan (graph 0)
  Stream #0:1 (pcm_s24le) -> pan (graph 0)
  Stream #0:1 (pcm_s24le) -> pan (graph 0)
  Stream #0:0 -> #0:0 (prores (native) -> prores (native))
  pan (graph 0) -> Stream #0:1 (pcm_s24le)
  pan (graph 0) -> Stream #0:2 (pcm_s24le)
  pan (graph 0) -> Stream #0:3 (pcm_s24le)
  pan (graph 0) -> Stream #0:4 (pcm_s24le)
  pan (graph 0) -> Stream #0:5 (pcm_s24le)
  pan (graph 0) -> Stream #0:6 (pcm_s24le)
  pan (graph 0) -> Stream #0:7 (pcm_s24le)
Press [q] to stop, [?] for help
frame=   14 fps=1.1 q=-0.0 size=   10567kB time=00:00:01.00 bitrate=86563.8kbitsframe=   26 fps=2.0 q=-0.0 size=   23341kB time=00:00:01.50 bitrate=127471.3kbitframe=   38 fps=2.8 q=-0.0 size=   36133kB time=00:00:02.00 bitrate=148002.7kbitframe=   49 fps=3.4 q=-0.0 size=   47881kB time=00:00:02.50 bitrate=156896.6kbitframe=   59 fps=4.0 q=-0.0 size=   58482kB time=00:00:02.52 bitrate=190012.1kbitframe=   70 fps=4.6 q=-0.0 size=   70029kB time=00:00:03.00 bitrate=191226.8kbitframe=   81 fps=5.1 q=-0.0 size=   81443kB time=00:00:03.50 bitrate=190623.1kbitframe=   92 fps=5.6 q=-0.0 size=   92871kB time=00:00:04.00 bitrate=190199.1kbitframe=  103 fps=6.1 q=-0.0 size=  104378kB time=00:00:04.50 bitrate=190015.0kbitframe=  115 fps=6.6 q=-0.0 size=  116801kB time=00:00:05.00 bitrate=191366.2kbitframe=  120 fps=6.8 q=-0.0 Lsize=  125425kB time=00:00:05.00 bitrate=205496.6kbits/s    
video:119787kB audio:5625kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.010789%    
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

Carl Eugen Hoyos
Kevin Wells <kevwells <at> hotmail.co.uk> writes:

> Hi, I am trying to specify a single mono channel to be
> named 'Center' when viewed in Quicktime player, I know
> that technically specifying FC is mono, but in my user
> case I need it to actually be named 'Center', not
> 'Mono'.

Please explain the usecase.

Carl Eugen

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

speedyrazor
> To: [hidden email]
> From: [hidden email]
> Date: Mon, 26 Oct 2015 08:17:17 +0000
> Subject: Re: [FFmpeg-user] Specify FC instead of mono‏
>
> Kevin Wells <kevwells <at> hotmail.co.uk> writes:
>
> > Hi, I am trying to specify a single mono channel to be
> > named 'Center' when viewed in Quicktime player, I know
> > that technically specifying FC is mono, but in my user
> > case I need it to actually be named 'Center', not
> > 'Mono'.
>
> Please explain the usecase.
>
> Carl Eugen
>
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Hi Carl, thanks for replying.
We deliver Quicktime Prores files with embedded audio to various VOD platforms that MUST be labeled in this very specific way, if any channels are named 'mono' then they fail the file.

Kind regards.

     
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

Moritz Barsnick
On Mon, Oct 26, 2015 at 09:15:05 +0000, Kevin Wells wrote:
> We deliver Quicktime Prores files with embedded audio to various VOD
> platforms that MUST be labeled in this very specific way, if any
> channels are named 'mono' then they fail the file.

Can you please provide a very short file with a similar/identical
channel layout where the labels are correct? (And one with the
incorrect ones, while you're at it.)

Moritz
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

speedyrazor
> Date: Mon, 26 Oct 2015 10:30:23 +0100
> From: [hidden email]
> To: [hidden email]
> Subject: Re: [FFmpeg-user] Specify FC instead of mono‏
>
> On Mon, Oct 26, 2015 at 09:15:05 +0000, Kevin Wells wrote:
> > We deliver Quicktime Prores files with embedded audio to various VOD
> > platforms that MUST be labeled in this very specific way, if any
> > channels are named 'mono' then they fail the file.
>
> Can you please provide a very short file with a similar/identical
> channel layout where the labels are correct? (And one with the
> incorrect ones, while you're at it.)
>
> Moritz
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Hi Mortiz, thanks for your reply, I have emailed you directly with a small example.
Where / how can I supply a small sample to this list?
Kind regards.    
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

Carl Eugen Hoyos
In reply to this post by speedyrazor
Kevin Wells <kevwells <at> hotmail.co.uk> writes:

> We deliver Quicktime Prores files with embedded audio
> to various VOD platforms that MUST be labeled in this
> very specific way,

Could you name the platforms?
It would be useful for the (future, possible) commit message.

Carl Eugen

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

speedyrazor
> To: [hidden email]
> From: [hidden email]
> Date: Mon, 26 Oct 2015 10:36:36 +0000
> Subject: Re: [FFmpeg-user] Specify FC instead of mono‏
>
> Kevin Wells <kevwells <at> hotmail.co.uk> writes:
>
> > We deliver Quicktime Prores files with embedded audio
> > to various VOD platforms that MUST be labeled in this
> > very specific way,
>
> Could you name the platforms?
> It would be useful for the (future, possible) commit message.
>
> Carl Eugen
>
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Hi Carl, Amazon Prime and Google Play, among others.
Kind regards,Kevin    
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

Moritz Barsnick
In reply to this post by speedyrazor
On Mon, Oct 26, 2015 at 10:29:31 +0000, Kevin Wells wrote:
> Hi Mortiz, thanks for your reply, I have emailed you directly with a small example.

I have shared it here:
https://dl.dropboxusercontent.com/u/16955557/ffmpeg-QT-wrong_audio_tags.zip

> Where / how can I supply a small sample to this list?

If you don't have Dropbox, you can use e.g.
http://www.datafilehost.com/

Moritz
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

speedyrazor
In reply to this post by Carl Eugen Hoyos
> To: [hidden email]
> From: [hidden email]
> Date: Mon, 26 Oct 2015 08:17:17 +0000
> Subject: Re: [FFmpeg-user] Specify FC instead of mono‏
>
> Kevin Wells <kevwells <at> hotmail.co.uk> writes:
>
> > Hi, I am trying to specify a single mono channel to be
> > named 'Center' when viewed in Quicktime player, I know
> > that technically specifying FC is mono, but in my user
> > case I need it to actually be named 'Center', not
> > 'Mono'.
>
> Please explain the usecase.
>
> Carl Eugen
>
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Hi Carl, related to the same issue is this here:

https://trac.ffmpeg.org/ticket/2865#comment:9

Same as my requirement, in that channels 7+8 are separate mono's, instead of a stereo. In this case ffmpeg is not able to flag the mono channel 7 and mono channel 8 as DL and DR respectively. So when delivering to the VOD platforms, if you are delivering 8 mono's then this would also become an issue. Currently ffmpeg can flag 7+8 as DL+DR if 7+8 is a stereo, but not if they are mono's. Thought it was worth mentioning here, just in case.

Kind regards.    
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

speedyrazor
In reply to this post by Moritz Barsnick
> Date: Mon, 26 Oct 2015 11:55:59 +0100
> From: [hidden email]
> To: [hidden email]
> Subject: Re: [FFmpeg-user] Specify FC instead of mono‏
>
> On Mon, Oct 26, 2015 at 10:29:31 +0000, Kevin Wells wrote:
> > Hi Mortiz, thanks for your reply, I have emailed you directly with a small example.
>
> I have shared it here:
> https://dl.dropboxusercontent.com/u/16955557/ffmpeg-QT-wrong_audio_tags.zip
>
> > Where / how can I supply a small sample to this list?
>
> If you don't have Dropbox, you can use e.g.
> http://www.datafilehost.com/
>
> Moritz
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Hi Mortiz, thats great, thanks for sharing the link.
Let me know if you need anything else, testing patches, more samples, etc.
Kind regards.    
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

Moritz Barsnick
On Tue, Oct 27, 2015 at 13:31:30 +0000, Kevin Wells wrote:
> Let me know if you need anything else, testing patches, more samples, etc.

With my means and the (very) little knowledge of the MOV format I have,
I couldn't yet detect the difference in those files. I suspect it's in
the atoms, perhaps. Unfortunately, AtomicParsley can only dissect MP4
files, not MOV files.

You can only hope someone else with more knowledge of the format has a
look.

A good summary of this issue, together with samples, would be good in
trac.

Moritz
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

speedyrazor
> Date: Tue, 27 Oct 2015 14:39:42 +0100
> From: [hidden email]
> To: [hidden email]
> Subject: Re: [FFmpeg-user] Specify FC instead of mono‏
>
> On Tue, Oct 27, 2015 at 13:31:30 +0000, Kevin Wells wrote:
> > Let me know if you need anything else, testing patches, more samples, etc.
>
> With my means and the (very) little knowledge of the MOV format I have,
> I couldn't yet detect the difference in those files. I suspect it's in
> the atoms, perhaps. Unfortunately, AtomicParsley can only dissect MP4
> files, not MOV files.
>
> You can only hope someone else with more knowledge of the format has a
> look.
>
> A good summary of this issue, together with samples, would be good in
> trac.
>
> Moritz
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Hi Mortiz, this has already been done a little while ago, exact same issue as me:

https://trac.ffmpeg.org/ticket/2865#comment:9

Hope someone can help, would be an extremely handy thing to be able to do in ffmpeg.
Kind regards.    
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

Carl Eugen Hoyos
In reply to this post by Moritz Barsnick
Moritz Barsnick <barsnick <at> gmx.net> writes:

> With my means and the (very) little knowledge of
> the MOV format I have, I couldn't yet detect the
> difference in those files. I suspect it's in the
> atoms, perhaps.

The chan atom to be precise.

Carl Eugen

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

Kieran O Leary
In reply to this post by Moritz Barsnick
On Tue, Oct 27, 2015 at 1:39 PM, Moritz Barsnick <[hidden email]> wrote:

> On Tue, Oct 27, 2015 at 13:31:30 +0000, Kevin Wells wrote:
>> Let me know if you need anything else, testing patches, more samples, etc.
>
> With my means and the (very) little knowledge of the MOV format I have,
> I couldn't yet detect the difference in those files. I suspect it's in
> the atoms, perhaps. Unfortunately, AtomicParsley can only dissect MP4
> files, not MOV files.
>
> You can only hope someone else with more knowledge of the format has a
> look.
>

Perhaps mediatrace would be worth a shot? https://mediaarea.net/mediatrace/
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

Moritz Barsnick
On Tue, Oct 27, 2015 at 14:17:45 +0000, Kieran O Leary wrote:
> Perhaps mediatrace would be worth a shot? https://mediaarea.net/mediatrace/

Ah, I didn't realize mediainfo could spit out details about the atoms.
It can indeed...

If the samples in the mentioned ticket
https://trac.ffmpeg.org/ticket/2865

notably SD_IVTC_8channel_ProResHQ_test.mov (from ffmpeg, incorrect)
and     SD_IVTC_8channel_ProResHQ_test_withT3.7.8_labels.mov (from QT Player, correct)

expose exactly the same behavior, I can only say this with regards to
the difference of the files (ignoring the developers' analysis of
whether this can be fixed):

I believe the audio channels in question differ as such:
The "C" center channel:

00000D38        Channels (24 bytes)
00000D38         Header (8 bytes)
00000D38          Size:                             24 (0x00000018)
00000D3C          Name:                             chan
00000D40         Version:                           0 (0x00)
00000D41         Flags:                             0 (0x000000)
00000D44         ChannelLayoutTag:                  6553601 (0x00640001)
00000D48         ChannelBitmap:                     0 (0x00000000)
00000D4C         NumberChannelDescriptions:         0 (0x00000000)

vs.

00000D8C        Channels (44 bytes)
00000D8C         Header (8 bytes)
00000D8C          Size:                             44 (0x0000002C)
00000D90          Name:                             chan
00000D94         Version:                           0 (0x00)
00000D95         Flags:                             0 (0x000000)
00000D98         ChannelLayoutTag:                  0 (0x00000000)
00000D9C         ChannelBitmap:                     0 (0x00000000)
00000DA0         NumberChannelDescriptions:         1 (0x00000001)
00000DA4         ChannelLabel:                      3 (0x00000003)
00000DA8         ChannelFlags:                      0 (0x00000000)
00000DAC         Coordinates (0):                   0.000
00000DB0         Coordinates (1):                   0.000
00000DB4         Coordinates (2):                   0.000

Similar for the two other channels: QT seems to use "ChannelLabel" (3
here, 38 and 39 for the two others channels in the sample), which
ffmpeg does not. (Those two are different from your samples anyway,
ffmpeg detects them as DL and DR instead of "downmix".)

I have no idea how to fix this and won't dive into it either. ;-)

Moritz
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

speedyrazor
> Date: Tue, 27 Oct 2015 17:42:35 +0100
> From: [hidden email]
> To: [hidden email]
> Subject: Re: [FFmpeg-user] Specify FC instead of mono‏
>
> On Tue, Oct 27, 2015 at 14:17:45 +0000, Kieran O Leary wrote:
> > Perhaps mediatrace would be worth a shot? https://mediaarea.net/mediatrace/
>
> Ah, I didn't realize mediainfo could spit out details about the atoms.
> It can indeed...
>
> If the samples in the mentioned ticket
> https://trac.ffmpeg.org/ticket/2865
>
> notably SD_IVTC_8channel_ProResHQ_test.mov (from ffmpeg, incorrect)
> and     SD_IVTC_8channel_ProResHQ_test_withT3.7.8_labels.mov (from QT Player, correct)
>
> expose exactly the same behavior, I can only say this with regards to
> the difference of the files (ignoring the developers' analysis of
> whether this can be fixed):
>
> I believe the audio channels in question differ as such:
> The "C" center channel:
>
> 00000D38        Channels (24 bytes)
> 00000D38         Header (8 bytes)
> 00000D38          Size:                             24 (0x00000018)
> 00000D3C          Name:                             chan
> 00000D40         Version:                           0 (0x00)
> 00000D41         Flags:                             0 (0x000000)
> 00000D44         ChannelLayoutTag:                  6553601 (0x00640001)
> 00000D48         ChannelBitmap:                     0 (0x00000000)
> 00000D4C         NumberChannelDescriptions:         0 (0x00000000)
>
> vs.
>
> 00000D8C        Channels (44 bytes)
> 00000D8C         Header (8 bytes)
> 00000D8C          Size:                             44 (0x0000002C)
> 00000D90          Name:                             chan
> 00000D94         Version:                           0 (0x00)
> 00000D95         Flags:                             0 (0x000000)
> 00000D98         ChannelLayoutTag:                  0 (0x00000000)
> 00000D9C         ChannelBitmap:                     0 (0x00000000)
> 00000DA0         NumberChannelDescriptions:         1 (0x00000001)
> 00000DA4         ChannelLabel:                      3 (0x00000003)
> 00000DA8         ChannelFlags:                      0 (0x00000000)
> 00000DAC         Coordinates (0):                   0.000
> 00000DB0         Coordinates (1):                   0.000
> 00000DB4         Coordinates (2):                   0.000
>
> Similar for the two other channels: QT seems to use "ChannelLabel" (3
> here, 38 and 39 for the two others channels in the sample), which
> ffmpeg does not. (Those two are different from your samples anyway,
> ffmpeg detects them as DL and DR instead of "downmix".)
>
> I have no idea how to fix this and won't dive into it either. ;-)
>
> Moritz
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Thats good work finding the differences, now we just need someone kind enough who knows how to change and action this.
I can only offer testing, examples, etc..

Kind regards.

     
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

Carles Vila
Hi, I'm in the same boat. Would be very useful to fix this.

It was mentioned before that Amazon Prime and Google play ask for ProRes
for their VOD platforms.
For the sake of completeness I'd like to add iTunes and Netflix. So it's a
de facto standard for VOD delivery I would say.It all stems from the iTunes
specification
I can share spec docs if anyone is interested

On 28 October 2015 at 08:16, Kevin Wells <[hidden email]> wrote:

> > Date: Tue, 27 Oct 2015 17:42:35 +0100
> > From: [hidden email]
> > To: [hidden email]
> > Subject: Re: [FFmpeg-user] Specify FC instead of mono‏
> >
> > On Tue, Oct 27, 2015 at 14:17:45 +0000, Kieran O Leary wrote:
> > > Perhaps mediatrace would be worth a shot?
> https://mediaarea.net/mediatrace/
> >
> > Ah, I didn't realize mediainfo could spit out details about the atoms.
> > It can indeed...
> >
> > If the samples in the mentioned ticket
> > https://trac.ffmpeg.org/ticket/2865
> >
> > notably SD_IVTC_8channel_ProResHQ_test.mov (from ffmpeg, incorrect)
> > and     SD_IVTC_8channel_ProResHQ_test_withT3.7.8_labels.mov (from QT
> Player, correct)
> >
> > expose exactly the same behavior, I can only say this with regards to
> > the difference of the files (ignoring the developers' analysis of
> > whether this can be fixed):
> >
> > I believe the audio channels in question differ as such:
> > The "C" center channel:
> >
> > 00000D38        Channels (24 bytes)
> > 00000D38         Header (8 bytes)
> > 00000D38          Size:                             24 (0x00000018)
> > 00000D3C          Name:                             chan
> > 00000D40         Version:                           0 (0x00)
> > 00000D41         Flags:                             0 (0x000000)
> > 00000D44         ChannelLayoutTag:                  6553601 (0x00640001)
> > 00000D48         ChannelBitmap:                     0 (0x00000000)
> > 00000D4C         NumberChannelDescriptions:         0 (0x00000000)
> >
> > vs.
> >
> > 00000D8C        Channels (44 bytes)
> > 00000D8C         Header (8 bytes)
> > 00000D8C          Size:                             44 (0x0000002C)
> > 00000D90          Name:                             chan
> > 00000D94         Version:                           0 (0x00)
> > 00000D95         Flags:                             0 (0x000000)
> > 00000D98         ChannelLayoutTag:                  0 (0x00000000)
> > 00000D9C         ChannelBitmap:                     0 (0x00000000)
> > 00000DA0         NumberChannelDescriptions:         1 (0x00000001)
> > 00000DA4         ChannelLabel:                      3 (0x00000003)
> > 00000DA8         ChannelFlags:                      0 (0x00000000)
> > 00000DAC         Coordinates (0):                   0.000
> > 00000DB0         Coordinates (1):                   0.000
> > 00000DB4         Coordinates (2):                   0.000
> >
> > Similar for the two other channels: QT seems to use "ChannelLabel" (3
> > here, 38 and 39 for the two others channels in the sample), which
> > ffmpeg does not. (Those two are different from your samples anyway,
> > ffmpeg detects them as DL and DR instead of "downmix".)
> >
> > I have no idea how to fix this and won't dive into it either. ;-)
> >
> > Moritz
> > _______________________________________________
> > ffmpeg-user mailing list
> > [hidden email]
> > http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> Thats good work finding the differences, now we just need someone kind
> enough who knows how to change and action this.
> I can only offer testing, examples, etc..
>
> Kind regards.
>
>
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

Carl Eugen Hoyos
Carles Vila <cvilad <at> gmail.com> writes:

> Hi, I'm in the same boat. Would be very useful to fix this.

> It was mentioned before that Amazon Prime and Google play
> ask for ProRes for their VOD platforms.

How is this related to the fact that the mov muxer can't
be told how to mark mono channels in the chan atom?

Carl Eugen

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

speedyrazor
In reply to this post by Carl Eugen Hoyos
> To: [hidden email]
> From: [hidden email]
> Date: Tue, 27 Oct 2015 14:08:06 +0000
> Subject: Re: [FFmpeg-user] Specify FC instead of mono‏
>
> Moritz Barsnick <barsnick <at> gmx.net> writes:
>
> > With my means and the (very) little knowledge of
> > the MOV format I have, I couldn't yet detect the
> > difference in those files. I suspect it's in the
> > atoms, perhaps.
>
> The chan atom to be precise.
>
> Carl Eugen
>
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Hi Carl, now we've established this issue, is there a proper way to go about trying to get this addressed?
Although there is one already, should I create an up-to date trac issue?    
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|

Re: Specify FC instead of mono‏

Carl Eugen Hoyos
Kevin Wells <kevwells <at> hotmail.co.uk> writes:

> Hi Carl, now we've established this issue,

I believe it was established months (or years?) ago.

> is there a proper way to go about trying to get
> this addressed?

You can either send a patch or wait until somebody
else sends one.

> Although there is one already, should I create an
> up-to date trac issue?

(Please don't)
What is not up-to-date about the existing ticket?

Carl Eugen

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
12