0001695: GUI shows wrong trim value when content and DCP frame rates different

ID	Project	Category	View Status	Date Submitted	Last Update

0001695	DCP-o-matic	Bugs	public	2019-12-18 15:09	2023-12-22 22:33

Reporter	overlookmotel	Assigned To
Priority	normal	Severity	minor	Reproducibility	sometimes
Status	acknowledged	Resolution	open
Platform	Mac	OS	OS X	OS Version	10.14
Product Version	2.14.15

Summary	0001695: GUI shows wrong trim value when content and DCP frame rates different
Description	I suspect this may be related to (0001694)[https://dcpomatic.com/mantis/view.php?id=1694]. Sometimes, the GUI displays wrong number of frames in trim where DCP and content are different frame rates. e.g.: Open project and import 25fps content Set frame rate of DCP to 24fps Set trim end to e.g. 1 second, 18 frames Click "Set" Value displayed in GUI switches to 1 second, 17 frames Value of `TrimEnd` in `metadata.xml` is correctly calculated based on 1s18f (i.e. it's correct, but value shown in GUI is wrong) I'm afraid I can't find an example to reproduce this right now, but I've seen it a few times since updating from DOM 2.14.8 to 2.14.17. Had never seen it before with 2.14.8.
Tags	No tags attached.

Branch
Estimated weeks required
Estimated work required

Date Modified	Username	Field	Change
2019-12-18 15:09	overlookmotel	New Bug
2019-12-27 17:09	overlookmotel	Note Added: 0003688
2023-12-22 22:33	carl	Status	new => acknowledged

overlookmotel 2019-12-27 17:09 developer ~0003688	This problem still persists in versions of DCP-o-matic including fix for 0001694. So it wasn't related after all. I'll make a repro case next time I come across it.