Can this library be used to decode H.26x packets?

[zipswich]

The typical use of this library is to use a video source URI to create FFmpegMediaSource and feed MediaPlaybackItem to MediaPlayer.
Is it possible to feed raw H.264/H.265 to the decoders under the hood, get the decoded frames for rendering, or get MediaPlaybackItem to feed to MediaPlayer?
The library does not seem to be able to handle recording. Please correct me on this. I do not want to obtain two streams from the server: one for display and one for recording. I want to use one stream for both recording and display. If I can feed raw H.26x packets to decoders, I should be able to achieve it.
I am new to the library, so please forgive my ignorance.

[brabebhin]

Hi
The library doesn't do this out of the box but you can probably fork it and modify it so that it does.

But this won't be an easy task.

[zipswich]

I have finally gotten a little bit of luck with the following code:

var config = new MediaSourceConfig();
config.FFmpegOptions["loglevel"] = "debug";
config.FFmpegOptions["debug"] = "true";
FFmpegMediaSource ffmpegSource = await FFmpegMediaSource.CreateFromStreamAsync(
        new CircularStream(_circularBufferFFmpeg),
        config);
MyMediaPlayerElement.Source = ffmpegSource.CreateMediaPlaybackItem();
MyMediaPlayerElement.MediaPlayer.Play();

_circularBufferFFmpeg has Annex B H.264 NAL units. The video shows up and looks perfect. However, it lasts for only a few seconds. FFmpeg stops requesting data from the provided stream in a few seconds despite the stream having plenty of data and being ready to provide it upon request.

This may be beyond the scope of FFmpegInteropX. I wonder if anyone could offer a tip on how to debug FFmpeg under the hood to just get a clue about why it stops requesting data in a few seconds.

[brabebhin]

You're probably triggering the EOF logic

[zipswich]

I tried every possible way in CircularStream to inform the caller that the size of the stream is infinite. I wish FFmepg could surface more details about what is going on under the hood. This should conclude my exploration.

[brabebhin]

Have you checked the debug output window in visual studio? Usually ffmpeg is very chatty

[zipswich]

Yes. This is why I have the following code:

config.FFmpegOptions["loglevel"] = "debug";
config.FFmpegOptions["debug"] = "true";

Unfortunately, I saw nothing.