Quantcast

Prores 444 being detected by quicktime as 422?

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Prores 444 being detected by quicktime as 422?

Sam Marrocco
I seem to be unable to generate a 444 prores .mov file that quicktime
player will indentify as 444. QT Player claims the movie is 422.

Several misc. sources (one of which is
http://transcoding.wordpress.com/2012/01/29/prores-ffmpeg/) quote
examples of using the arg "-pix_fmt yuv444p10le" to generate 444 prores
quicktime movies. However, whenever I use yuv444p10 or yuv444p10le
ffmpeg presents the error:

Incompatible pixel format 'yuv444p10le' for codec 'prores',
auto-selecting format 'yuv422p10le'

I have tried various source qt movies of 8 bit uncompressed, 10 bit
uncompressed, 422 prores and 444 prores. The output movie is created,
but is always 422 (in Quicktime Player) and ffmpeg displays the
"imcompatible pixel format" message.

I have been told that ffmprobe identifies the file as 444, but quicktime
player identifies the output files as 422.

I am using an ffmpeg win32 static build on Windows 7, 64-bit OS.

CommandLine:
ffmpeg-20120903-git-5d55830-win64-static\bin\ffmpeg.exe" -i
"C:\Server\Jobs\Conversion\FlameOutput_Quicktimes\Car_10BitRGBUncompressedTC.mov"
-vcodec prores -profile 3 -pix_fmt yuv444p10le -f mov
"C:\Server\Jobs\Conversion\FlameOutput_Quicktimes\Car_10BitRGBUncompressedTC\Car_10BitRGBUncompressedTC.mov"

ffmpeg version N-44123-g5d55830 Copyright (c) 2000-2012 the FFmpeg
developers
   built on Sep  2 2012 20:27:20 with gcc 4.7.1 (GCC)
   configuration: --enable-gpl --enable-version3 --disable-pthreads
--enable-runtime-cpudetect --enable-avisynth --enable-bzlib
--enable-frei0r --enable-libass --enable-libcelt
--enable-libopencore-amrnb --enable-libopencore-amrwb
--enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libnut
--enable-libopenjpeg --enable-librtmp --enable-libschroedinger
--enable-libspeex --enable-libtheora --enable-libutvideo
--enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis
--enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid
--enable-zlib
   libavutil      51. 70.100 / 51. 70.100
   libavcodec     54. 55.100 / 54. 55.100
   libavformat    54. 25.104 / 54. 25.104
   libavdevice    54.  2.100 / 54.  2.100
   libavfilter     3. 15.102 /  3. 15.102
   libswscale      2.  1.101 /  2.  1.101
   libswresample   0. 15.100 /  0. 15.100
   libpostproc    52.  0.100 / 52.  0.100
[mov,mp4,m4a,3gp,3g2,mj2 @ 0000000001e92f40] Stream #1: not enough
frames to estimate rate; consider increasing probesize
[mov,mp4,m4a,3gp,3g2,mj2 @ 0000000001e92f40] Stream #2: not enough
frames to estimate rate; consider increasing probesize
[mov,mp4,m4a,3gp,3g2,mj2 @ 0000000001e92f40] Stream #3: not enough
frames to estimate rate; consider increasing probesize
[mov,mp4,m4a,3gp,3g2,mj2 @ 0000000001e92f40] Stream #4: not enough
frames to estimate rate; consider increasing probesize
[mov,mp4,m4a,3gp,3g2,mj2 @ 0000000001e92f40] Stream #5: not enough
frames to estimate rate; consider increasing probesize
Guessed Channel Layout for  Input Stream #0.2 : mono
Guessed Channel Layout for  Input Stream #0.3 : mono
Guessed Channel Layout for  Input Stream #0.4 : mono
Guessed Channel Layout for  Input Stream #0.5 : mono
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from
'C:\Server\Jobs\Conversion\FlameOutput_Quicktimes\Car_10BitRGBUncompressedTC.mov':
   Metadata:
     major_brand     : qt
     minor_version   : 537199360
     compatible_brands: qt
     creation_time   : 2012-09-05 14:37:36
   Duration: 00:00:01.00, start: 0.000000, bitrate: 1195269 kb/s
     Stream #0:0(eng): Video: rawvideo (raw  / 0x20776172), rgb24,
1920x1080, 1194393 kb/s, SAR 1:1 DAR 16:9, 24 fps, 24 tbr, 24 tbn, 24 tbc
     Metadata:
       creation_time   : 2012-09-05 14:37:36
       handler_name    : Linux Alias Data Handler
       timecode        : 01:02:03:06
     Stream #0:1(eng): Data: none (tmcd / 0x64636D74)
     Metadata:
       creation_time   : 2012-09-05 14:37:36
       handler_name    : Libquicktime Time Code Media Handler
       timecode        : 01:02:03:06
     Stream #0:2(eng): Audio: adpcm_ima_qt (ima4 / 0x34616D69), 48000
Hz, mono, s16, 192 kb/s
     Metadata:
       creation_time   : 2012-09-05 14:37:36
       handler_name    : Linux Alias Data Handler
     Stream #0:3(eng): Audio: adpcm_ima_qt (ima4 / 0x34616D69), 48000
Hz, mono, s16, 192 kb/s
     Metadata:
       creation_time   : 2012-09-05 14:37:36
       handler_name    : Linux Alias Data Handler
     Stream #0:4(eng): Audio: adpcm_ima_qt (ima4 / 0x34616D69), 48000
Hz, mono, s16, 192 kb/s
     Metadata:
       creation_time   : 2012-09-05 14:37:36
       handler_name    : Linux Alias Data Handler
     Stream #0:5(eng): Audio: adpcm_ima_qt (ima4 / 0x34616D69), 48000
Hz, mono, s16, 192 kb/s
     Metadata:
       creation_time   : 2012-09-05 14:37:36
       handler_name    : Linux Alias Data Handler
Please use -profile:a or -profile:v, -profile is ambiguous
Incompatible pixel format 'yuv444p10le' for codec 'prores',
auto-selecting format 'yuv422p10le'
Output #0, mov, to
'C:\Server\Jobs\Conversion\FlameOutput_Quicktimes\Car_10BitRGBUncompressedTC\Car_10BitRGBUncompressedTC.mov':
   Metadata:
     major_brand     : qt
     minor_version   : 537199360
     compatible_brands: qt
     encoder         : Lavf54.25.104
     Stream #0:0(eng): Video: prores (apch) (apch / 0x68637061),
yuv422p10le, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 24 tbn, 24 tbc
     Metadata:
       creation_time   : 2012-09-05 14:37:36
       handler_name    : Linux Alias Data Handler
       timecode        : 01:02:03:06
     Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, mono,
s16, 128 kb/s
     Metadata:
       creation_time   : 2012-09-05 14:37:36
       handler_name    : Linux Alias Data Handler
Stream mapping:
   Stream #0:0 -> #0:0 (rawvideo -> prores)
   Stream #0:2 -> #0:1 (adpcm_ima_qt -> libvo_aacenc)
Press [q] to stop, [?] for help
Multiple frames in a packet from stream 2
frame=   24 fps=7.6 q=0.0 Lsize=   32783kB time=00:00:01.01
bitrate=265370.0kbits/s
video:32764kB audio:16kB subtitle:0 global headers:0kB muxing overhead
0.007305%


Any suggestions would be appreciated.









--


Sam Marrocco
Chief Technical Officer
248-548-2500 Main
248-910-3344 Cell
 
"Just because no one understands you doesn't make you an artist."

 RINGSIDE CREATIVE | INTEGRATED MEDIA STUDIO™
http://www.ringsidecreative.com

Find us on Facebook.

Please consider the environment before printing this email.
 
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Prores 444 being detected by quicktime as 422?

Carl Eugen Hoyos
Sam Marrocco <smarrocco <at> ringsidecreative.com> writes:

> Incompatible pixel format 'yuv444p10le' for codec 'prores',
> auto-selecting format 'yuv422p10le'

Only the slower alternative prores encoder "prores_kostya"
supports yuv444.

Carl Eugen

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

Re: Prores 444 being detected by quicktime as 422?

rogerdpack2
>> Incompatible pixel format 'yuv444p10le' for codec 'prores',
>> auto-selecting format 'yuv422p10le'
>
> Only the slower alternative prores encoder "prores_kostya"
> supports yuv444.

His question was, even using prores_kostya with yuv444p10le, the
resultant file shows as yuv44p10le in ffmpeg, but in QT Player, it
says "yuv420p" when playing it.
So my question is...do any files say yuv422 when played in QT Player?
-r
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Prores 444 being detected by quicktime as 422?

Carl Eugen Hoyos
Roger Pack <rogerdpack2 <at> gmail.com> writes:

> >> Incompatible pixel format 'yuv444p10le' for codec 'prores',
> >> auto-selecting format 'yuv422p10le'
> >
> > Only the slower alternative prores encoder "prores_kostya"
> > supports yuv444.
>
> His question was, even using prores_kostya with yuv444p10le, the
> resultant file shows as yuv44p10le in ffmpeg, but in QT Player, it
> says "yuv420p" when playing it.

Apart from the fact that this is hard to believe, I was unable to
find that claim in the original mail.

Carl Eugen

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

Re: Prores 444 being detected by quicktime as 422?

Sam Marrocco


On 9/8/2012 6:27 PM, Carl Eugen Hoyos wrote:
>
> Apart from the fact that this is hard to believe, I was unable to
> find that claim in the original mail.
>
>


Roger may be "intermingling" knowledge of a thread on ffmpeg zeranoe
(http://ffmpeg.zeranoe.com/forum/viewtopic.php?f=7&t=707&sid=3274fe1a5efcc0021653f967447f9057)
and this thread but he is correct.
It may be hard to believe but every quicktime that I have tried to
convert in ffmpeg using yuv444p10le and prores or prores_kostya results
in a prores quicktime that ffmpeg indentifies as 444 yet is identified
as 422 by quicktime player.

Carl is the first person to suggest that ffmpeg cannot create yuv444
(which helps the mystery a bit).



Sam Marrocco
Chief Technical Officer
248-548-2500 Main
248-910-3344 Cell
 
"Just because no one understands you doesn't make you an artist."

 RINGSIDE CREATIVE | INTEGRATED MEDIA STUDIO™
http://www.ringsidecreative.com

Find us on Facebook.

Please consider the environment before printing this email.
 
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Prores 444 being detected by quicktime as 422?

Carl Eugen Hoyos
Sam Marrocco <smarrocco <at> ringsidecreative.com> writes:

> Carl is the first person to suggest that ffmpeg cannot
> create yuv444 (which helps the mystery a bit).

I tried very hard to suggest that FFmpeg is able to create
yuv444 ProRes files.
Please provide your failing prores_kostya command line
together with complete, uncut console output.

Carl Eugen

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

Re: Prores 444 being detected by quicktime as 422?

Robert Krüger-2
On Mon, Sep 10, 2012 at 6:17 PM, Carl Eugen Hoyos <[hidden email]> wrote:

> Sam Marrocco <smarrocco <at> ringsidecreative.com> writes:
>
>> Carl is the first person to suggest that ffmpeg cannot
>> create yuv444 (which helps the mystery a bit).
>
> I tried very hard to suggest that FFmpeg is able to create
> yuv444 ProRes files.
> Please provide your failing prores_kostya command line
> together with complete, uncut console output.
>

It does not set the correct fourcc. It should be ap4h but it is apcn
(which is the fourcc for prores 422). Quicktime and other apple
software (like Final Cut) more or less blindly trust the fourcc. I
tried overriding it with -vtag but that didn't work either:

ffmpeg -i /Users/krueger/sample-db/fcp7/prores/[hidden email]
-vcodec prores_kostya -pix_fmt yuv444p10le -vtag ap4h -acodec copy -y
prores4444-vtag.mov
ffmpeg version N-43678-gceb8773 Copyright (c) 2000-2012 the FFmpeg developers
  built on Aug 17 2012 22:28:27 with gcc 4.2.1 (GCC) (Apple Inc. build 5664)
  configuration:
  libavutil      51. 70.100 / 51. 70.100
  libavcodec     54. 53.100 / 54. 53.100
  libavformat    54. 25.100 / 54. 25.100
  libavdevice    54.  2.100 / 54.  2.100
  libavfilter     3. 10.100 /  3. 10.100
  libswscale      2.  1.101 /  2.  1.101
  libswresample   0. 15.100 /  0. 15.100
Guessed Channel Layout for  Input Stream #0.1 : stereo
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from
'/Users/krueger/sample-db/fcp7/prores/[hidden email]':
  Metadata:
    major_brand     : qt
    minor_version   : 0
    compatible_brands: qt
    creation_time   : 2012-09-09 11:49:36
    encoder         : FFmbc 0.7
  Duration: 00:00:02.00, start: 0.000000, bitrate: 104070 kb/s
    Stream #0:0(eng): Video: prores (ap4h / 0x68347061), yuv444p10le,
1920x1080, 101756 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 24k tbc
    Metadata:
      creation_time   : 2012-09-09 11:49:36
      handler_name    : DataHandler
      timecode        : 01:00:00:00
    Stream #0:1(eng): Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz,
stereo, s32, 2304 kb/s
    Metadata:
      creation_time   : 2012-09-09 11:49:36
      handler_name    : DataHandler
Codec 0x0 is not in the full list.
    Stream #0:2(eng): Data: unknown_codec (tmcd / 0x64636D74)
    Metadata:
      creation_time   : 2012-09-09 11:49:36
      handler_name    : DataHandler
      timecode        : 01:00:00:00
Output #0, mov, to 'prores4444-vtag.mov':
  Metadata:
    major_brand     : qt
    minor_version   : 0
    compatible_brands: qt
    encoder         : Lavf54.25.100
    Stream #0:0(eng): Video: prores (apcn / 0x6E637061), yuv444p10le,
1920x1080, q=2-31, 200 kb/s, 24k tbn, 23.98 tbc
    Metadata:
      creation_time   : 2012-09-09 11:49:36
      handler_name    : DataHandler
      timecode        : 01:00:00:00
    Stream #0:1(eng): Audio: pcm_s24le (in24 / 0x34326E69), 48000 Hz,
stereo, 2304 kb/s
    Metadata:
      creation_time   : 2012-09-09 11:49:36
      handler_name    : DataHandler
Stream mapping:
  Stream #0:0 -> #0:0 (prores -> prores_kostya)
  Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help
frame=   48 fps=2.4 q=0.0 Lsize=   18088kB time=00:00:02.00
bitrate=74015.7kbits/s
video:17523kB audio:563kB subtitle:0 global headers:0kB muxing
overhead 0.013850%
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Prores 444 being detected by quicktime as 422?

Robert Krüger-2
On Mon, Sep 10, 2012 at 7:07 PM, Robert Krüger <[hidden email]> wrote:

> On Mon, Sep 10, 2012 at 6:17 PM, Carl Eugen Hoyos <[hidden email]> wrote:
>> Sam Marrocco <smarrocco <at> ringsidecreative.com> writes:
>>
>>> Carl is the first person to suggest that ffmpeg cannot
>>> create yuv444 (which helps the mystery a bit).
>>
>> I tried very hard to suggest that FFmpeg is able to create
>> yuv444 ProRes files.
>> Please provide your failing prores_kostya command line
>> together with complete, uncut console output.
>>
>
> It does not set the correct fourcc. It should be ap4h but it is apcn
> (which is the fourcc for prores 422). Quicktime and other apple
> software (like Final Cut) more or less blindly trust the fourcc. I
> tried overriding it with -vtag but that didn't work either:
>
looking at the code, it looks as if Prores 4444 is not modeled as a
profile at all (see variable prores_profile_info), so it never sets
the correct fourcc.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Prores 444 being detected by quicktime as 422?

Carl Eugen Hoyos
In reply to this post by Robert Krüger-2
Robert Krüger <krueger <at> lesspain.de> writes:

> It does not set the correct fourcc. It should be ap4h but it is apcn
> (which is the fourcc for prores 422). Quicktime and other apple
> software (like Final Cut) more or less blindly trust the fourcc. I
> tried overriding it with -vtag but that didn't work either:

Did you find out what else is missing?
(Binary comparison)

Carl Eugen

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

Re: Prores 444 being detected by quicktime as 422?

Robert Krüger-2
On Wed, Sep 12, 2012 at 1:28 AM, Carl Eugen Hoyos <[hidden email]> wrote:

> Robert Krüger <krueger <at> lesspain.de> writes:
>
>> It does not set the correct fourcc. It should be ap4h but it is apcn
>> (which is the fourcc for prores 422). Quicktime and other apple
>> software (like Final Cut) more or less blindly trust the fourcc. I
>> tried overriding it with -vtag but that didn't work either:
>
> Did you find out what else is missing?
> (Binary comparison)
>
No, my next step would have been to correct the fourcc and see if
Final Cut behaves correctly. Other than that, I would not know what to
look for. Pixel format seems to be OK, as it is detected correctly by
ffmpeg when running it on the resulting file. I can try a hack to get
the correct fourcc in there and check the above.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Prores 444 being detected by quicktime as 422?

Carl Eugen Hoyos
In reply to this post by Robert Krüger-2
On Tuesday 11 September 2012 10:04:07 am Robert Krüger wrote:

> > It does not set the correct fourcc. It should be ap4h but it is apcn
> > (which is the fourcc for prores 422). Quicktime and other apple
> > software (like Final Cut) more or less blindly trust the fourcc. I
> > tried overriding it with -vtag but that didn't work either:
>
> looking at the code, it looks as if Prores 4444 is not modeled as a
> profile at all (see variable prores_profile_info), so it never sets
> the correct fourcc.

Thank you for analyzing this - I simply didn't understand the problem;-)
(I couldn't believe it was not reported before and not tested originally.)
Could you test attached patch? It contains some guessing.

Thank you, Carl Eugen

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

patchprores444.diff (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Prores 444 being detected by quicktime as 422?

Robert Krüger-2
On Wed, Sep 12, 2012 at 10:33 AM, Carl Eugen Hoyos <[hidden email]> wrote:

> On Tuesday 11 September 2012 10:04:07 am Robert Krüger wrote:
>
>> > It does not set the correct fourcc. It should be ap4h but it is apcn
>> > (which is the fourcc for prores 422). Quicktime and other apple
>> > software (like Final Cut) more or less blindly trust the fourcc. I
>> > tried overriding it with -vtag but that didn't work either:
>>
>> looking at the code, it looks as if Prores 4444 is not modeled as a
>> profile at all (see variable prores_profile_info), so it never sets
>> the correct fourcc.
>
> Thank you for analyzing this - I simply didn't understand the problem;-)
> (I couldn't believe it was not reported before and not tested originally.)
> Could you test attached patch? It contains some guessing.
>

I'll test the patch immediately. Just a quick update: I hacked the
codec not to override the fourcc if it is set on the command line and
the result was detected as Prores 4444 bei Quicktime but the alpha
information was lost. I verified by making a clip with alpha,
exporting it via final cut as prores 4444 and using the resulting clip
in a final cut sequence as an overlay, which worked. Then I transcoded
the exported clip using ffmpeg into 4444 using the hack and used that
clip as an overlay and alpha was gone. If a one-frame-sample of prores
4444 with alpha would help, I can make a trac issue and attach it.

I'll post the results of testing your patch next.

Regards,

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

Re: Prores 444 being detected by quicktime as 422?

Robert Krüger-2
On Wed, Sep 12, 2012 at 11:14 AM, Robert Krüger <[hidden email]> wrote:
> On Wed, Sep 12, 2012 at 10:33 AM, Carl Eugen Hoyos <[hidden email]> wrote:
>> On Tuesday 11 September 2012 10:04:07 am Robert Krüger wrote:
>>
>>
>> Thank you for analyzing this - I simply didn't understand the problem;-)
>> (I couldn't believe it was not reported before and not tested originally.)
>> Could you test attached patch? It contains some guessing.
>>
I don't know if I am doing anything wrong but the patch does not apply
to a clean git head here, although the patch file looks ok (not
mangled by mail client):

alejandro:ffmpeg krueger$ git pull
Already up-to-date.
alejandro:ffmpeg krueger$ git status
# On branch master
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
# patchprores444.diff
# prores4444_with_transparency_ffmpeg.mov
nothing added to commit but untracked files present (use "git add" to track)
alejandro:ffmpeg krueger$ git apply --check patchprores444.diff
error: patch failed: libavcodec/proresenc_kostya.c:43
error: libavcodec/proresenc_kostya.c: patch does not apply
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Prores 444 being detected by quicktime as 422?

Carl Eugen Hoyos
In reply to this post by Robert Krüger-2
Robert Krüger <krueger <at> lesspain.de> writes:

> I hacked the codec not to override the fourcc if it is
> set on the command line and the result was detected as
> Prores 4444 bei Quicktime but the alpha information was
> lost.

The encoder currently does not support alpha...

> I verified by making a clip with alpha

... which is related to the fact that the decoder does not
support it because afaik we don't have a sample.

Please provide a sample, Carl Eugen

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

Re: Prores 444 being detected by quicktime as 422?

Carl Eugen Hoyos
In reply to this post by Robert Krüger-2
Robert Krüger <krueger <at> lesspain.de> writes:

> alejandro:ffmpeg krueger$ git apply --check patchprores444.diff

$ patch -p1<patchprores444.diff
(I still don't speak git)

Carl Eugen

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

Re: Prores 444 being detected by quicktime as 422?

Robert Krüger-2
In reply to this post by Carl Eugen Hoyos
On Wed, Sep 12, 2012 at 11:47 AM, Carl Eugen Hoyos <[hidden email]> wrote:

> Robert Krüger <krueger <at> lesspain.de> writes:
>
>> I hacked the codec not to override the fourcc if it is
>> set on the command line and the result was detected as
>> Prores 4444 bei Quicktime but the alpha information was
>> lost.
>
> The encoder currently does not support alpha...
>
>> I verified by making a clip with alpha
>
> ... which is related to the fact that the decoder does not
> support it because afaik we don't have a sample.
>
> Please provide a sample, Carl Eugen
The sample I have is one frame long and 220k in size. How do you want
me to give it to you?
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Prores 444 being detected by quicktime as 422?

Robert Krüger-2
In reply to this post by Carl Eugen Hoyos
On Wed, Sep 12, 2012 at 11:48 AM, Carl Eugen Hoyos <[hidden email]> wrote:
> Robert Krüger <krueger <at> lesspain.de> writes:
>
>> alejandro:ffmpeg krueger$ git apply --check patchprores444.diff
>
> $ patch -p1<patchprores444.diff
OK, thanks.

Patch works. The resulting file looks good and is recognized by
Quicktime as Prores 4444. Thanks!
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Prores 444 being detected by quicktime as 422?

Carl Eugen Hoyos
In reply to this post by Robert Krüger-2
Robert Krüger <krueger <at> lesspain.de> writes:

> > The encoder currently does not support alpha...
> >
> >> I verified by making a clip with alpha
> >
> > ... which is related to the fact that the decoder does not
> > support it because afaik we don't have a sample.
> >
> > Please provide a sample, Carl Eugen
>
> The sample I have is one frame long and 220k in size.
> How do you want me to give it to you?

If you don't want to send it to this list (or via pm)
and don't want to open a ticket yourself (I will do it),
please upload as explained on http://ffmpeg.org/bugreports.html

Please also add the sample as rgba png, so the developers
know what it should look like.

Thank you, Carl Eugen

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

Re: Prores 444 being detected by quicktime as 422?

Robert Krüger-2
On Wed, Sep 12, 2012 at 1:06 PM, Carl Eugen Hoyos <[hidden email]> wrote:

> Robert Krüger <krueger <at> lesspain.de> writes:
>
>> > The encoder currently does not support alpha...
>> >
>> >> I verified by making a clip with alpha
>> >
>> > ... which is related to the fact that the decoder does not
>> > support it because afaik we don't have a sample.
>> >
>> > Please provide a sample, Carl Eugen
>>
>> The sample I have is one frame long and 220k in size.
>> How do you want me to give it to you?
>
> If you don't want to send it to this list (or via pm)
> and don't want to open a ticket yourself (I will do it),
> please upload as explained on http://ffmpeg.org/bugreports.html
>
> Please also add the sample as rgba png, so the developers
> know what it should look like.
>
I opened http://ffmpeg.org/trac/ffmpeg/ticket/1728 .

Let me know if there's anything else that I can provide.

Regards,

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