Restore per-game capture duration settings

[harukaze5719]

In before 1.9.0, CapFrameX could save and automatically apply different capture duration settings for each game. When a game was detected, the app would automatically load the previously configured capture time for that specific game. This feature seems removed in v1.9.0. Only global setting.

[RodroG-85]

I haven't tested v1.9 yet, but IF this was removed, please consider adding it again.

[DevTechProfile]

Let's be honest, this feature is very niche, isn't it? I rather would like to keep it removed. The UI is bloated, especially on the Capture tab.

[harukaze5719]

Let's be honest, this feature is very niche, isn't it? I rather would like to keep it removed. The UI is bloated, especially on the Capture tab.

Yeah it is niche, not for majarity. But really useful for media, tester. Testing different games, even 10s of.

[RodroG-85]

Let's be honest, this feature is very niche, isn't it? I rather would like to keep it removed. The UI is bloated, especially on the Capture tab.

Yes, it's a niche feature. But as @harukaze5719 mentioned, it was also an advanced and useful capture feature for tech reviewers who need to test large groups of games via custom benchmark scenes/sequences. I agree the new UI is quite bloated, but removing this doesn't add or detract much in this regard. That said, I also understand @DevTechProfile position to remove it...

[DevTechProfile]

Yes, it's a niche feature. But as @harukaze5719 mentioned, it was also an advanced and useful capture feature for tech reviewers who need to test large groups of games via custom benchmark scenes/sequences.

Do you have an example? When it comes to custom game scenes, why should you use different benchmark durations?

[RodroG-85]

Yes, it's a niche feature. But as @harukaze5719 mentioned, it was also an advanced and useful capture feature for tech reviewers who need to test large groups of games via custom benchmark scenes/sequences.

Do you have an example? When it comes to custom game scenes, why should you use different benchmark durations?

Yes, I do. For example, I don't use the same duration for all the custom scenes for different games. 30s can be enough for a set custom scene, but not enough for a different game/sequence to gather a representative, valid, or reliable idea of the performance/smoothnes in a given game or 3D application. It depends on the specific workloads of the testing sequence. Also, for example, if you use CX to capture/monitor performance metrics during a built-in benchmark run, some may take 60, 120, 180, or 30 seconds; different duration lengths.

For me, it's easy to see the usefulness of this "niche" but advanced capture feature. Each tech reviewer or benchmarker has their own testing methods and may use different durations, or the same one, depending on the game or characteristics of the testing workload.

That said, I don't want to continue arguing about this matter. If you still see it as an unreasonable or unnecessary capture feature that significantly clutters the UI, I understand and trust your judgment. You are the dev and designer. :)

[DevTechProfile]

The feature is back with 1.9.1.

[RodroG-85]

The feature is back with 1.9.1.

Thank you, @DevTechProfile . Best as always!