# Camera input - Nvidia librargus and OpenKCam

**URL:** <https://discourse.julialang.org/t/camera-input-nvidia-librargus-and-openkcam/22501>\
**Category:** General Usage\
**Created:** [March 29, 2019, 2:12pm UTC](https://discourse.julialang.org/t/camera-input-nvidia-librargus-and-openkcam/22501 "2019-03-29T14:12:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/johnh/32/3615_2.png) [@johnh](https://discourse.julialang.org/u/johnh)\
**Post date:** [March 29, 2019, 2:12pm UTC](https://discourse.julialang.org/t/camera-input-nvidia-librargus-and-openkcam/22501/1 "2019-03-29T14:12:07Z")

</div>

I read that Nvidia development boards us an API called libargus to read in camera data

> **[getting-started-jetpack-camera-api.pdf](https://on-demand.gputechconf.com/gtc/2016/webinar/getting-started-jetpack-camera-api.pdf)**
>
> 1315.41 KB

This is based on OpenKCam [OpenKCam Overview - The Khronos Group Inc](https://www.khronos.org/openkcam)  
I can imagine reading camera data ‘properly’ is important in many fields - from astronomy, to wind tunnel studies (PIV data) to microscopy and many points between.  
Thoughts please.