View Bug Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002245DCP-o-maticBugspublic2022-05-06 18:022024-01-13 10:11
ReporterCarsten Assigned Tocarl  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Platform64-bitOSWindowsOS Version10
Product Version2.14.x 
Target Version2.16.x 
Summary0002245: 3D DCP creation fails when separate L/R files have unequal number of frames
Description

Obviously, a condition that needs to be catched - a friend just reported this error to me, and as a blind guess, I suggested to check wether both files have identical number of frames. He checked it, and indeed, one had a single frame more. After trimming it away, 3D-DCP creation worked.

I guess the easiest way to solve this is to check both files and report this condition - or trim silently. The question is only - can we always assume that the issue is at the end of the file? If we silently trim, the problem may be at the beginning, and then the L/R sequence slips, without the user knowing it. So, I guess 'some' report (maybe in warnings) would be useful, so the user at least gets notified that there may be an issue. Is it complicated to check equal number of frames on import of source footage?

TagsNo tags attached.
Branch
Estimated weeks required
Estimated work requiredUndecided

Activities

Carsten

2022-05-06 18:02

manager  

DCP3d.jpg (66,650 bytes)   
DCP3d.jpg (66,650 bytes)   

carl

2022-05-09 00:16

administrator   ~0005012

Last edited: 2022-05-09 00:16

It's not easy to be sure on the exact lengths of all content at import... there are headers, but they can be wrong.

I think this particular case was fixed in v2.15.188 - 86c9cd50e1b73e6d89db312f2ee58e85ff270194 - I suppose we could backport that fix and make a new 2.14.x but at this point it would probably be easier for your friend to upgrade to 2.16.x. Is that possible, or does something keep them on 2.14.x?

Carsten

2022-05-09 11:37

manager   ~0005014

He told me he had the issue initially with 2.14.59, but then also tested 'a current version' with the same result - no idea what exactly that means. 2.15..188 is close enough to 2.16.x...

Whatever, easy to test this myself.

Carsten

2023-09-19 12:48

manager   ~0005951

I think this issue is resolved.

carl

2023-09-19 13:42

administrator   ~0005952

Thanks!

Bug History

Date Modified Username Field Change
2022-05-06 18:02 Carsten New Bug
2022-05-06 18:02 Carsten Status new => assigned
2022-05-06 18:02 Carsten Assigned To => carl
2022-05-06 18:02 Carsten File Added: DCP3d.jpg
2022-05-09 00:16 carl Note Added: 0005012
2022-05-09 00:16 carl Note Edited: 0005012
2022-05-09 00:16 carl Status assigned => feedback
2022-05-09 11:37 Carsten Note Added: 0005014
2022-05-09 11:37 Carsten Status feedback => assigned
2022-05-11 19:38 carl Status assigned => feedback
2022-05-12 08:56 carl Target Version 2.16.11 => 2.16.x
2022-05-12 08:56 carl Estimated work required => Undecided
2023-09-19 12:48 Carsten Note Added: 0005951
2023-09-19 12:48 Carsten Status feedback => assigned
2023-09-19 13:42 carl Status assigned => resolved
2023-09-19 13:42 carl Resolution open => fixed
2023-09-19 13:42 carl Note Added: 0005952
2024-01-13 10:11 carl Status resolved => closed