ffprobe cache

[rudnypc]

When the cache is true, can we save the ffprobe stream result? Every request to the same file with different resolution (maybe the same too), the ffprobe is running again.

[m1k1o]

Hmm, it should not do again. Is the cache file there?

[m1k1o]

I tried it, got media local cache hit and no ffprobe running. Do you use global or local cache? Do you see this entry in log?

[rudnypc]

I'm using cache inside the vod tag, Should I put this cache outsite?

[m1k1o]

I'm using cache inside the vod tag,

Correct.

Found some issue, when cache does not contain keyframes (if selected) when accesssing master playlist.

[rudnypc]

The ffprobe now is starting from the master and each profile. Before ffprobe was only started from the profile.

[m1k1o]

They should share the same cache. But I think, the problem is race condition. When master profile starts ffprobe, it takes some time. If some profile starts in meanwhile, it does not see cache entry and starts again. It does not know, that other ffprobe is in progress, since every profile has its own manager started.

[rudnypc]

sorry, now that I made a mistake, the cache is working now

[rudnypc]

Ok, but when I set the cache is true, the generator doesn't use the ffprobe keyframe

[m1k1o]

Another problem is, that when the cache exists, even without keyframes, it does not generate them. I think that should be fixed too. So if you have valid cache without keyframes, it won't generate them additionally.