ISSUES and TODOS

[bennylp]

COMMON:

1. Protect video features inside #if PJMEDIA_HAS_VIDEO

PJMEDIA:

1. Should we have unique format_id for each RGB format?
2. Endianness in pixel representation
3. Videoport only buffers 1 frame
4. More advanced frame format?:
   • buffer capacity size
5. what pjmedia_vid_param fields are initialized by default_param()? Can app expect all fields will be initialized with default values, and ready to be used?
6. duplicate fps and frame_rate in pjmedia_format and pjmedia_vid_param
7. The "*fmt" in pjmedia_vid_dev_info is bad for pjmedia_vid_dev_get_info(), because user then may modify modify the pointer.
8. Similarly the "detail*" in pjmedia_format is bad for the same reason.
9. Test with planar YUV formats
10. audiodev xxx-Direct features
11. WMME-dev extended format not yet ported
12. SDL video resize (take a look at SDL's add-on libraries: ​SPriG or ​SDL_gfx)
13. Clean up the usage of PJ_EUNKNOWN in video stream/codec
14. ffmpeg_codecs.c contains codecs that doesn't have RTP packetization support, e.g: divx/mpeg4 (for AVI play), somehow those codecs shouldn't be listed in the SDP

PJSUA-LIB

1. non-blocking transport creation
2. optional SRTP with duplicated media lines
3. call hold status should be calculated from the direction of *all* media streams (currently only the first audio)
4. allow call with zero audio (e.g. video only)?

[ming]

(In [3401]) Fixed #1184:

• Move the AVI playback from pjmedia-test to new aviplay.c sample application
• Take the input file from cmdline
• Synchronize audio and video
• Remove all codecs related hardcodes from the file

Re #1193: (no. 6: duplicate fps and frame_rate in pjmedia_format and pjmedia_vid_param)

• Remove the frame_rate in pjmedia_vid_param
• Use pjmedia_format's fps in videoport, sdl_dev, and colorbar_dev
• Prevent overflow in ptime calculation from frame_rate