2017.R1 EDGE storage

I’m using (and customizing) the MediaPlaybackViewer sample.

When Opening XPCO Database from folder , created with 2107.R1 recording server, if the Camera has EDGE storage recordings I see two different cameras in database: one with regular recording and another with only the EDGE recording portion.

With Database coming from 2016 recording server even if there are EDGE storag e recordings I see, correctly, only one merged database.

I noted that now the tables has different sources and a new metadata tag are written in cache.xml and config.xml like this:

fd6718f8-00c8-4cab-bfa5-26610361b3e5

How with MIP SDK can resolve this issue?

Thanks,

Agostino.

There is a difference in the design introduced in 2017R1 to improve edge storage usage. In 2017R1 the merge of edge and regular recording happen at runtime, merge happens in the client.

If you do not login to the server, but instead stops the server and reads the files directly, you will have to merge the footage in your coding.

Thank you Bo for your response.

Can you post a sample of code or a documentation that explain how to merge footage at runtime?

Agostino.

This was actually introduced in 2016R3 (I said 2017R1). It is the Scalable Video Quality Recording (SVQR) feature. The concept is to record constanly at a lower bitrate and then upon event or user request retrieve higher quality video from the edge recording enabled device.

While this is automatically retrieving the right video for all clients inlcuding MIP SDK based clients (under login), there is unfortunately no documentation on how to best merge information when you are working with orphaned or exported files in the MIP SDK.

Resurrecting this thread…I’m having issues exporting edge footage using DBExporter class. Footage recorded in Milestone is fine, but the export is basically empty when I select a time range including only edge retrieved video. Has there been any progress on this?