# Clarification on TX2 Max HW Encode Resolution

**URL:** <https://forums.developer.nvidia.com/t/clarification-on-tx2-max-hw-encode-resolution/62434>\
**Category:** Jetson TX2\
**Created:** [June 20, 2018, 8:10pm UTC](https://forums.developer.nvidia.com/t/clarification-on-tx2-max-hw-encode-resolution/62434 "2018-06-20T20:10:58Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![greg2](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@greg2](https://forums.developer.nvidia.com/u/greg2)\
**Post date:** [July 17, 2018, 11:48pm UTC](https://forums.developer.nvidia.com/t/clarification-on-tx2-max-hw-encode-resolution/62434/21 "2018-07-17T23:48:00Z")

</div>

> [@DaneLLL](#):
>
> Hi danieel, Greg2,  
> For gstreamer implementation, the best case is to have nvcamerasrc as input source. It is for Bayer sensor and with video/x-raw(memory:NVMM). If it is not your source, we suggest you use MMAPIs, which has NvBuffer implementation.

Unfortunately we’re not able to use nvcamerasrc because our image isn’t taken directly from a camera, but rather through a series of proprietary protocols, HW, & SW where raw buffers are eventually made available to an app on the Jetson, which after doing additional manipulation will eventually push the buffer into the pipeline using an appsrc. So that pipeline is where we’re doing the encoding and where this 4k x 4k would need to happen. I don’t think we can use nvcamerasrc for something as convoluted and complicated as that.

For your suggestion, you mean like through TMA with the NvVideoEncoder like 01\_sample\_encode example uses? We have that implementation in our code base, but we’re not actively using it because we didn’t see any real improvements over our gstreamer pipeline using OMX. Should we ideally be seeing an improvement using that over gstreamer?

---

<div class="post-metadata">

**Author:** ![DaneLLL](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/danelll/32/14043_2.png) [@DaneLLL](https://forums.developer.nvidia.com/u/DaneLLL)\
**Post date:** [July 19, 2018, 9:24am UTC](https://forums.developer.nvidia.com/t/clarification-on-tx2-max-hw-encode-resolution/62434/22 "2018-07-19T09:24:52Z")

</div>

Hi greg2,  
For your case, you will need nvvidconv to put CPU buffers(video/x-raw) into dma buffers(video/x-raw(memory:NVMM)).

It should be same for MMAPIs. You can create dma buffers by NvBuffer APIs, but still need to copy your data in.

---

<div class="post-metadata">

**Author:** ![nadeemm](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/nadeemm/32/367020_2.png) [@nadeemm](https://forums.developer.nvidia.com/u/nadeemm)\
**Post date:** [October 18, 2021, 6:29pm UTC](https://forums.developer.nvidia.com/t/clarification-on-tx2-max-hw-encode-resolution/62434/23 "2021-10-18T18:29:37Z")

</div>

Closed on October 18, 2021, 6:29pm UTC



[Previous page](https://forums.developer.nvidia.com/t/clarification-on-tx2-max-hw-encode-resolution/62434.md?page=1)
