[Ffmpeg-devel] ffmpeg & postprocess_internal.h (colorspace issue)

Kris A. Wotipka kris
Sun Jul 24 17:33:45 CEST 2005

Apologies and thanks for the input.  By the time I learn enough C to 
understand the code, the problem will no longer be an issue since we 
will probably be into some direct to brain transfer system with our 
entertainment.  It truly is a shame that wonderful programs such as 
these will forever be locked into the hands of those who can program but 
not write documentation.

I as an engineer understand the issues of composite routing, syncing, 
latency, etc of the traditional studio system.  Whenever someone who 
wants to learn asks, I always try to explain it in real world terms and 
then hand them one of Grass Valleys wonderful manuals.

I am not knocking the talents of those involved because from looking at 
the program and trying to see how things flow people have put lots of 
effort into this program.  Now, if some brave soul would like to rewrite 
the docs, others may not become as testy when presumed "newbie" 
questions are posted.

All this started with me trying to save an educational-access non-profit 
station a few bucks.  I know what the commercial version of this costs 
and they cannot afford that.  However, once I got this working, I was 
going to suggest that they donate the portion they could afford to this 
cause and they were happy with that.

For the record, I never wanted anyone to do it for me.  I am very happy 
with RTFM.  However if I have to go learn the programming from scratch, 
I might as well write the code to do the job in the first place.

Sorry folks

Michael Niedermayer wrote:
> Hi
> On Sunday 24 July 2005 05:43, Kris A. Wotipka wrote:
>>Just realized that you are the one who wrote the postprocess_internal
>>source.  Can you tell me what the line
>>/// select between full y range (255-0) or standart one (234-16)
>>#define FULL_Y_RANGE    0x8000                  // 32768
>>is for?  You can reply here or off list but it is making my brain hurt.
> this really is off topic, learn c, or accept that you dont understand it, 
> theres no sense in explainng what that single line does as even if you 
> understand that single line it alone wont help you
>>  I am understanding now that I need to go to the YUV space with this
>>now.  I am still trying to figure out the -pix_fmt yuvj420p is all
>>about.  I am having a hard time finding docs on it. 
> there probably are not many docs about it, learn c and read the source :)
> [...]
>>Also, I am trying to figure out the compile sequence for this.  Should I
>>compile the libpostproc then libavcodec then ffmpeg or if I make changes
>>say to something in libavcodec do I need to recompile ffmpeg.
> make dep ; make
> and read the manual for make
> [...]

More information about the ffmpeg-devel mailing list