Recording desktop issue

[wernerh]

Hi Sergey,

I am experiencing this issue again and having little success in resolving it. I'm using the RVCamRecorder recording the desktop of four monitors.

Do you have any suggestions on what may cause this or what I can try to fix it?

[Sergey Tkachenko]

I am sorry for the delay.
1) Is video from this camera displayed correctly in TRVCamView (and the problem is only in recording)?
2) Does this problem exist, if you record scaled video? Try assigning in RVCamera.FFMpegProperty:
UseVideoScale = True
VideoWidth=1280
VideoHeight=720

[wernerh]

1) Yes problem is only in recording. It displays correctly in TRVCamView
2) I tried with your suggested properties but the problem still exists.

[Sergey Tkachenko]

What are your versions:
1) RVMedia
2) FFmpeg
3) Delphi
What's the frame size (width and height)?
What's video format (of video steam and container)? Does the problem happen with different file formats?

[wernerh]

1) RVMedia: 9.1
2) FFmpeg: unsure, but likely older around 2020.
3) Delphi: 11.2
Frame size: 1920 x 1080
What's video format (of video steam and container)? rvvfMJPEG
Does the problem happen with different file formats? yes

I happened to go into Windows display settings and rearranged the monitor displays and it started working fine again.

[Sergey Tkachenko]

Well, RVCamera can write MJpeg itself, without RVCamRecorder and FFmpeg, but it can write video frames only at their original side.

MJpeg is a just a sequence of Mpeg images and delimiters written in a single file. It's not a good format for screen recording, because adjacent frames for screen recording are usually almost identical, and more advanced video formats saves only differences,

If you want me to investigate the problem further, I need more details.
Probably, the problem occurs only when your desktop has certain size. When you rearrange displays, the total size is changed, so the problem appears/disappears. I need to know the exact total size of your desktop when the problem occurs.

Also, it may be a problem of certain FFmpeg version, probably it does not happen in newer versions.