This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AV Server restart time optimization



Hi,

I am working one IP CAM project with Appro 3.0 SDK. In which I need to optimize the Av Server restart time by configuring resolution frame rate and bit rate dynamically. 

Currently the SDK supports the dynamic configuration for Frame rate and bit rate.

I have tried to modify the Av server global variables for width height parameters and tried to restart encoder thread with new width height parameter, but it doesn't helped me.

Any help will be appreciated.

  • you can dynamically set frame rate and bit rate with this SDK.

    What are original and modified parameter for your encoder thread? and what are error when you change that parameter? 

  • Hi Nikunj,

                    I found the support for frame rate and bit rate, and is working fine. Also I used the same method for rate control also.

    Now I am able to change resolution dynamically.

    What I did is

    1. Changed the MEM_LAYOUT maximum video use case at the time of initialization.
    2. changed the width height value to the resize algorithm as well as the out buffer (To the next task - encode) dynamically.
    3. And then restarted the Encode thread and Stream thread with new width height values dynamically.
    4. To reflect the resolution change in streamer, I restarted wis-streamer.

    (Dynamically in the sense, when user calls the API corresponds to resolution, the variable in AV server is also getting updated.Used the method used for FPS and bit rate)

    Now am facing  CMEMK Error: get_phys: Unable to find phys addr for 0x4d06d506

    The above print comes on console and after some time, the AV server starts normally.

    This is happening in the case of Tri-stream only.

    Thanks for your replay.      

  • Your approach is right. But after AV server starts if you getting CMEMK Error, that means there is some parameter mismatching with your cmemk.ko 

    Check parameters that you are passing to cmemk.ko module during insmod or modprobe.

    best luck

  • Thanks Nikunj,

                      I can check the same.