# set\_number\_pipeline Source: [https://docs.qualcomm.com/doc/80-PK177-134/topic/qape_set_number_pipeline.html](https://docs.qualcomm.com/doc/80-PK177-134/topic/qape_set_number_pipeline.html) Sets the pipeline number. By calling this API the system will pick up the number of top threads to do their task placement and schedule. set_number_pipeline()Copy to clipboard ## Parameters | **Parameters** | **API type** | **Data type** | **Description** | | --- | --- | --- | --- | | number\_of\_pipeline\_thread | Java | long | Defines how many pipeline tasks this application wants
to set. The range of parameters is 0 to the maximum number of pipeline
threads | | number\_of\_pipeline\_thread | Native | unit32 | Defines how many pipeline tasks this application wants
to set. The range of parameters is 0 to the maximum number of pipeline
threads | | ret\_val | Native | int8\_t& | On success this is the actual return value from the API.



| | | | | | ## Returns | **Return** | **API type** | **Data type** | **Description** | | --- | --- | --- | --- | | response | Java | int | | | response | Native | qesdk\_transaction\_status | See [QESDK transaction status for Native APIs](https://docs.qualcomm.com/doc/80-PK177-134/topic/native_qesdk_class.html) for usage details. Use qesdk\_transaction\_status to confirm API call invocation. If successful, use the `ret` value for the actual API return value object. | | | | | | **Parent Topic:** [QAPE subsystem APIs](https://docs.qualcomm.com/doc/80-PK177-134/topic/qape_apis.html) Last Published: Nov 14, 2024 [Previous Topic get\_max\_number\_of\_pipeline\_thread](https://docs.qualcomm.com/bundle/publicresource/80-PK177-134/topics/qape_get_max_number_of_pipeline_thread.md) [Next Topic reset\_number\_pipeline](https://docs.qualcomm.com/bundle/publicresource/80-PK177-134/topics/qape_reset_number_pipeline.md)