Opened 3 years ago

Closed 18 months ago

Last modified 4 months ago

#13838 closed bug (invalid)

BeScreenCapture fps regression (compared to 15 months ago)

Reported by: smallstepforman Owned by: Barrett
Priority: normal Milestone:
Component: Kits/Media Kit Version: R1/Development
Keywords: BeScreenCapture Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by diver)

I am using BeScreenCapture 2.3.1 to create a developer timeline video, and have noticed a major regression compared to 15 months ago (BeScreenCapture 2.02). With hrev51660 (latest as of 8/Dec/2017, both 32 and 64 bit versions), I can only capture 1600x1200@2fps. 15 months ago (videos from Sep 2016), on the exact same hardware/screen resolution (32 bit version of Haiku only), I was able to get 1600x1200@10fps, which is a factor of 5 regression (10fps vs 2fps).

MacBookPro 11.3, running Haiku from USB2 hard disk. Intel i7-4870HQ (4 core, 8 thread), 16Gb RAM, nVidia GT750M (VESA)

capture session 10fps vs capture session 2fps

Attachments (1)

screenshot1.png (38.7 KB ) - added by smallstepforman 3 years ago.
capture session 10fps vs capture session 2fps

Download all attachments as: .zip

Change History (10)

by smallstepforman, 3 years ago

Attachment: screenshot1.png added

capture session 10fps vs capture session 2fps

comment:1 by smallstepforman, 3 years ago

patch: 01

comment:2 by diver, 3 years ago

Component: ApplicationsKits/Media Kit
Description: modified (diff)
Owner: changed from nobody to Barrett

Does it work with BeScreenCapture 2.02 on current hrev?

comment:3 by jackburton, 3 years ago

This could also be a BeScreenCapture problem. I opened a ticket on BeScreenCapture ticket tracker here:

https://github.com/jackburton79/bescreencapture/issues/24

in reply to:  1 ; comment:4 by jackburton, 3 years ago

Replying to smallstepforman: Could you comment on the BeScreenCapture ticket ?

Last edited 3 years ago by jackburton (previous) (diff)

in reply to:  4 comment:5 by smallstepforman, 3 years ago

Replying to jackburton:

Could you comment on the BeScreenCapture ticket ?

Real life interfering with computer access - will attempt his as soon as I can (possibly during the next weekend).

comment:6 by pulkomandy, 3 years ago

patch: 10

comment:7 by jackburton, 2 years ago

I think this ticket can be closed. There is a BeScreenCapture ticket following this problem here: https://github.com/jackburton79/bescreencapture/issues/24

comment:8 by waddlesplash, 18 months ago

Resolution: invalid
Status: newclosed

comment:9 by nielx, 4 months ago

Milestone: Unscheduled

Remove milestone for tickets with status = closed and resolution != fixed

Note: See TracTickets for help on using tickets.