Bug 402932

Summary: Framerate displayed in UI is bad compared to framerate possible when shooting a video
Product: [Applications] kamoso Reporter: Nate Graham <nate>
Component: generalAssignee: Aleix Pol <aleixpol>
Status: RESOLVED FIXED    
Severity: normal CC: anvariom
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Nate Graham 2019-01-06 16:16:03 UTC
Kamoso from git master

With my hardware, the frame rate rate displayed in Kamoso is terrible: less than one FPS. But when Kamoso takes a video, the video itself winds up with a very reasonable framerate! The framerate displayed in Cheese is fine too. The in-app display in Kamoso should match what's possible with video capture and in Cheese.
Comment 1 Nate Graham 2019-01-09 23:11:08 UTC
Having used Kamoso a lot lately, I note that this is only sometimes reproducible: sometimes the framerate is abysmal, and sometimes it's fine. Generally the first time I launch Kamoso after not using it for a day or so, the framerate is bad, but then at some point while I'm repeatedly launching it while testing patches, I suddenly notice that the framerate is normal.
Comment 2 Nate Graham 2019-01-09 23:29:19 UTC
Found a way to semi-reproduce:

1. Open Kamoso -> displayed video framerate is < 1 FPS
2. Open effects gallery drawer: framerate of video behind drawer becomes normal
3. Close drawer: some of the time, the framerte of the video reverts again
4. Open and close drawer repeatedly: framerate of video becomes normal for a while, including after closing and re-opening the app

The trick for me is that the framerate of the main video is always normal while the Effects Gallery drawer is open.
Comment 3 Nate Graham 2019-02-15 18:42:29 UTC
Hmm, now I can no longer reproduce this myself...
Comment 4 Aleix Pol 2019-02-16 00:54:02 UTC
Woohoo! fixed x'D

I have never seen it myself.
Comment 5 Nate Graham 2019-03-04 16:23:16 UTC
Let's call it fixed! I'll re-open if I can repro again or encounter anyone else who can.
Comment 6 Nate Graham 2019-04-08 15:06:58 UTC
*** Bug 364123 has been marked as a duplicate of this bug. ***