rdp / screen-capture-recorder-to-video-windows-free

a free open source windows "screen capture" device and recorder (also allows VLC/ffmpeg and others to capture/stream desktop/audio)
https://github.com/rdp/screen-capture-recorder-to-video-windows-free/releases
Other
2.06k stars 456 forks source link

Causes VLC to record upside down and causes audio to drop out sporadically #157

Open bakertaylor28 opened 2 years ago

bakertaylor28 commented 2 years ago

When using this to screen-record with VLC using MP4 format on windows 10, this causes the screen to record upside down for some unapparent reason and causes the audio to drop in and out.

rdp commented 2 years ago

I don't know why vlc dislikes it...could try ffmpeg...

On Wed, Mar 9, 2022 at 2:39 PM bakertaylor28 @.***> wrote:

When using this to screen-record with VLC using MP4 format on windows 10, this causes the screen to record upside down for some unapparent reason and causes the audio to drop in and out.

— Reply to this email directly, view it on GitHub https://github.com/rdp/screen-capture-recorder-to-video-windows-free/issues/157, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAADBUFBC7JHI76WJOETR4DU7ELCNANCNFSM5QKZE6PQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you are subscribed to this thread.Message ID: @.*** com>

rdp commented 1 year ago

I tried with vlc playing a "live stream" and it worked OK?

rdp commented 1 year ago

saving to file fails, viewing in VLC succeeds?

bakertaylor28 commented 1 year ago

saving to file fails, viewing in VLC succeeds? I tried with vlc playing a "live stream" and it worked OK?

As stated, VLC will write to file, but the file itself rendered upside down and the audio was unstable going in and out. I got with Microsoft on this, and they were able to trace it to the Windows 10 DEP (Data Execution Prevention) modules. Turning off DEP solved the problem, but represents a security issue in the Windows 10 environment. This likely means the code needs to be rewritten to conform to Windows 10 DEP API specifications such that it doesn't execute in RAM, or else update the Readme to indicate the package may not be compatible with Windows 10 depending upon OS Config.