OSD in DVRRDK 03.00.00.00

The data flow for the progressive demo was modified such that OSD is done for only the encoded streams and not the preview streams. The rationale for the change is :

1. We migrated to a better Tamper Detect algorithm in RDK 3.0. The Tamper detect must be performed on the raw captured video frame before applying OSD.

2. There was a requirement that there should be ability to apply different OSD on primary and secondary channels.

Based on these the DEMO_VCAP_VENC_VDEC_VDIS_PROGRESSIVE  usecase was modified such that OSD is applied only on the encoded streams and not on the preview streams.

Requiring the OSD on preview also requires usecase modification.

Hi Badri,

Thank You for this information.

Can You give us an advice how toachive the former behavior ?

Best regards Holger

Do you require SCD/TD functionality in your application. Based on your reply we will revert back on options.

Hi Badri,

we need Tamper detection in our application and we must be able to

insert the number of the camera in every capture channel and the running time.

This was running well in version 02.80 but we did not used Tamper detection

in this version.

Any idea ?

We will revert to you by end of this week on the modified usecase file to enable OSD on preview.

Hi Badri,

Verry nice, Thank You for the support !

Best regards Holger

Hi all,

I did read that a version DVRRDK03.50.xx.xx is available now. I have not seen this version.

How does this handle the capture side OSD, Have You changed it to the behavior of version 02.80.00.xx ?

The OSD is not added on preview in RDK 3.5 also and the reason is as follows:

1. OSD should be added after Tamper detect to prevent tamper from being wrongly detected due to OSD window.

2. Customers want different OSD on primary and secondary channels and option to not have OSD on preview channels.

3. Adding OSD on preview introduces additional 30% load on DSP for 16 channels which prevents running tamper detect on DSP.

4. The same effect of OSD on preview channels can be realised by application using FBDEV and does not require SW OSD.

Ok, I understand the reasons for this.

But we want insert the camera # for every captured channel, and this number must be recorded.

I think the only way to do this is to insert on capture side ?

But we want insert the camera # for every captured channel, and this number must be recorded

 - Do you mean you want the encoded frame to have the captured channel number ? If so this is already the default behaviour.

We want to show and record a text for every channel. The text must appear in the upper left corner of every channel.

I have already done this with versio. 02.80.00.xx and it works well with different fonts and font sizes.

But we did not used tamper detection in this case.

e.g.

CAM 1 for camera 1,

CAM 2 for camera 2,

...

CAM 15 for camera 15

In RDK 3.5 you can record the text but it will not show the text in preview. Can you use FBDEV to display the same text on preview ? If that is not possible then a data flow modification is required but that will affect tamper detection.

Yes, that is a good idea to splitt the recorded text and the displayed text. I think I have seen the recorded text  also in version 03.00.00.xx.

I used my project stack based on version 02.80.00.xx in version 03.00.00.xx and I was supprised that I can record inserted OSD but I was not able to see on display.

I will test your proposal. By the way, is version 03.50.xx.xx available for everybody ?