LtmmPlay and DVR to play camera IP

Hi,

I want to use my Camera IP with our DVR,

I play my Camera IP with LtmmPlay without problem. The URL to connect my Camera IP is URL: "rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0"
My probleme is when i use our composant DVR, it's not work. this my code, i use Delphi XE2:

procedure TForm12.Button1Click(Sender: TObject);
Var punk: IUnknown; pDvrSink: ILMDVRSink; Hr: HResult;
begin
  ltmmPlay.AutoStart:= False;
  ltmmPlay.sourcefile:= 'rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0';
  punk:= ltmmPlay.GetSubObject(ltmmPlay_Object_SourceFilter);
  if (punk <> NIL) then begin
     Hr:= punk.QueryInterface(IID_ILMDVRSink, pDvrSink);
     punk:= NIL; //Release
     if SUCCEEDED(Hr) then Begin
         pDvrSink.StartChangingAttributes;
         pDvrSink.FolderCount:= 1;
         pDvrSink.BaseName:= 'Capture.LBL';
         pDvrSink.FolderName[0]:= 'C:\Temp';
         pDvrSink.SetBufferSize(0, 5, 102400000);
         pDvrSink.StopChangingAttributes(FALSE);
         pDvrSink:= NIL; //Release
     End;
  end;
  ltmmPlay.Run;
end;

The pDvrSink is always NIL, what's the problem?

Hello,

I do not think the PlayCtrl is designed to use the DVR Buffer. The PlayCtrl is designed to take compressed streams or files and decode them for rendering (typically to the screen). For writing an RTSP stream to a DVR buffer, you should use the ConvertCtrl. You would set the SourceFile to the RTSP stream and the TargetFile to the output LBL file such as 'C:\Temp\Buffer.lbl'. You can still set the DVR Sink options if you wish to have the LRC files in a different location that the same directory or the various other options provided there.

The LEADTOOLS DVR format allows for simultaneous read and write operations. This will allow you to record the DVR buffer from the IP camera and view that data with only a single connection to the IP device. It is possible for You to set the PlayCtrl and CaptureCtrl to the same RTSP stream if necessary. Often, the IP camera cannot afford multiple connections for the same application, so writing to DVR and playing back from the DVR is preferred.

OK, Thank for your response,

I tested with LtmmConvert.
- SourceFile: rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0
- TargetFormat: ltmmConvert_TargetFormat_DVR_PROGRAM
- TargetFile: C:\capture.lbl
- Compression Video: LEAD H264 Encoder
- Preview: False

It's well work but the consumption of my CPU is 60%.

I have 8 Cameras IP.
If i want use 8 Cameras IP, i must use 8 ltmmConvert.
1 * ltmmConvert = CPU 60%
8 * ltmmConvert = CPU 60% * 8 = 480% ?????

This test is with my PC:
- CPU Intel Core 2 T6670 @ 2,2Ghz
- Ram 2Go
- Windows 7 32bits
- Resolution camera IP for capture: 704x576

How should I manage this consumption CPU if :
- I use Up 8 camera IP ?
- I use Camera 2, 3, 4,... Megapixel ?

Hello,

By setting a specific video compression, you are telling the LEADTOOLS library to recompress the incoming data. If the RTSP stream contains H.264 or MPEG-4 compressed video data, it is not required that you recompress it. The MPEG-2 Transport and MPEG-2 Program multiplexers support these two compressions, so you can specify "No Recompression" with the demo (which translates to a compressor index of '-1' in code). The RTSP Source filter will demultiplex the audio and video streams, and then the multiplexer will re-index the compressed data out to file. Neither the demuxing nor the remuxing is CPU intensive, but decoding and re-encoding the data with H.264 especially will require a good deal of CPU usage. H.264 and MPEG-4 are CPU intensive compressions. By not recompressing, you will also reduce the amount of memory required by the application.