-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for gpu_direct in ffmepg ffmpeg plugin #967
Add support for gpu_direct in ffmepg ffmpeg plugin #967
Conversation
bb33c6b
to
14f6669
Compare
few basic tests done building running on default / GPU enabled mode seems to work fine [in#0/mtl_st20p @ 0x56812e879dc0] Input file #0 (0): on GPU enabled mode no obvious errors / framedrops |
also MTL: 2024-09-10 12:48:09, rv_alloc_frames rv_framebuffer_in_gpu_direct_vram frames are allocated in vram |
Introduces suport for experimental MTL_GPU_DIRECT feature to enhance the performance of the FFmpeg ST20p plugin by enabling direct GPU memory access. Update ffmpeg README.md -- include build instructions and description of the feature Modify build_ffmpeg_plugin.sh -- Add support for building with GPU_DIRECT
14f6669
to
d815791
Compare
1a51e16
to
1da9ca1
Compare
There is no information on how to get the appropriate driver and device index |
5842342
to
f5c6fb4
Compare
there is no easy way to find this information tbh outside zero level library Added it as a log for the user to see -- fail to initialize |
4f951a4
to
cec0235
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code review completed
Add support for gpu_direct in ffmepg ffmpeg plugin
Introduces suport for experimental MTL_GPU_DIRECT
feature to enhance the performance of the FFmpeg
ST20p plugin by enabling direct GPU memory access.
Update ffmpeg README.md
-- include build instructions and description of
the feature
Modify build_ffmpeg_plugin.sh
-- Add support for building with GPU_DIRECT