Uploaded image for project: 'FreeSWITCH'
  1. FreeSWITCH
  2. FS-9863

video_width/video_height unset with playback application

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: core
    • Labels:
      None
    • CPU Architecture:
      x86-64
    • Kernel:
      Linux
    • Userland:
      GNU/Linux
    • Distribution:
      Debian
    • Distribution Version:
      Debian 8 jessie
    • Compiler:
      gcc
    • FreeSWITCH GIT Revision:
      82e4901d7c05689b10bed7445d8e8c49743329e1
    • GIT Master Revision hash::
      82e4901d7c05689b10bed7445d8e8c49743329e1

      Description

      https://freeswitch.org/jira/browse/FS-9553 introduced some unexpected behavior that led to the video_width/video_height channel variables being unset when they were previously available.

      This is due to the CF_VIDEO_PAUSE_READ flag being set in video_write_thread (src/switch_core_media.c:5902), which leads to an early exit in switch_core_session_read_frame (src/switch_core_media.c:13569), before video_width/video_height have a chance to be set later in switch_core_session_read_frame.

      The affected dial plan looks something like this:
       
          <extension name="fs-test">
            <condition field="destination_number" expression="^testest$">
              <action application="answer"/>
              <action application="video_decode" data="on"/>
              <action application="playback"
                data="/path/to/greeting.mp4"/>
              <action application="video_write_overlay" data="/path/to/overlay_${video_width}x${video_height}.png center-bot 0"/>
            </condition>
          </extension>

        Attachments

          Activity

            People

            • Assignee:
              mikej Mike Jerris
              Reporter:
              j0sh Josh Allmann
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: