View Issue Details

IDProjectCategoryView StatusLast Update
0000671madVRbugpublic2021-07-06 08:40
Reporterkasper93 Assigned Tomadshi  
PrioritynormalSeveritymajorReproducibilityalways
Status assignedResolutionopen 
Summary0000671: Please use ADL2_Display_ModeTimingOverrideX2_Set instead of ADL2_Display_ModeTimingOverride_Set
DescriptionHi,

madHcCtrl uses older ADL2_Display_ModeTimingOverride_Set variant which uses ADLDetailedTiming to define timings, problem is this struct uses short type for every value and notably for sPixelClock which simply overflows with high refresh rate monitors... ADLDetailedTimingX2 will easily work with higher values.

For example adding custom mode 2560x1440p120 fails with "The GPU driver rejected this mode, for unknown reasons.", well the reason is quite obvious now :)

Docs: https://gpuopen-librariesandsdks.github.io/adl/group__T__OVERRIDEAPI.html#gaef3a32f0a31afd35cdd8e884224d0024 at least it is documented... I almost started reverse engineering this ADL, before looking at the doc ;p

Thanks,
Kacper
TagsNo tags attached.
madVR Versionv0.92.17
Media Player (with version info)MPC-HC
Splitter (with version info)LAV 0.75.0.3
Decoder (with version info)LAV 0.75.0.3
DecodingSoftware
Deinterlacingnone (progressive)
DXVA2 Scaling Activeno
Aero / Desktop CompositionOn
Problem occurs with modeall modes
GPU ManufacturerAMD
GPU Model5700xt
GPU Driver Version21.5.2

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2021-07-06 00:12 kasper93 New Issue
2021-07-06 08:40 madshi Assigned To => madshi
2021-07-06 08:40 madshi Status new => assigned