You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear Kirill, excellent project !! I am using you Client sharp in .net console application, what do you recommend me to decode H264 frame in console in order to avoid use WritableBitmap to generate the frame? FFmpeg.Autogen use other type of Frame Class
#102
Open
Ogost22 opened this issue
Nov 16, 2020
· 0 comments
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Ogost22
changed the title
Dear Kirill, excellent proyect !! I am using you Client sharp in .net console aplication, what do you recomend me to decode H264 frame in consule in order to avoid use writablebitmap to generate the frame? FFmpeg.autogen use other type of Frame Objetct
Dear Kirill, excellent project !! I am using you Client sharp in .net console application, what do you recommend me to decode H264 frame in console in order to avoid use WritableBitmap to generate the frame? FFmpeg.Autogen use other type of Frame Class
Nov 16, 2020
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: