New timelines: Cuts are wrong for multi-part items #820

Closed
opened 2012-06-05 15:41:11 +00:00 by rlx · 7 comments
Owner
see <https://0xdb.org/0056172/editor/01:15:40>
rlx added the
backend
label 2012-06-05 15:41:11 +00:00
rlx added this to the 12.03 milestone 2012-06-05 15:41:11 +00:00
j was assigned by rlx 2012-06-05 15:41:11 +00:00
rlx added the
defect
label 2012-06-05 15:41:11 +00:00
Author
Owner

here it's easier to see that the cuts for part 2 start too early: https://0xdb.org/0338751/editor/01:28:15.680

here it's easier to see that the cuts for part 2 start too early: <https://0xdb.org/0338751/editor/01:28:15.680>
Author
Owner

Also, it seems that for antialias timelines of multipart items, what is displayed from 16:00 on is the timeline from 17:00 on

Also, it seems that for antialias timelines of multipart items, what is displayed from 16:00 on is the timeline from 17:00 on
Author
Owner

And for singlepart items, at 16:00, the antialias timeline seems to switch to slitscan - see https://0xdb.org/0082398/editor/00:16:00

And for singlepart items, at 16:00, the antialias timeline seems to switch to slitscan - see <https://0xdb.org/0082398/editor/00:16:00>
Author
Owner

The item 0338751 (two-part) has 164 large antialias tiles, and 163 tiles (which is correct) for all other modes

The item 0338751 (two-part) has 164 large antialias tiles, and 163 tiles (which is correct) for all other modes
Author
Owner

For the file 00 4b 42 66 c1 d0 ad f1, timelineantialias64p16.jpg is missing

For the file 00 4b 42 66 c1 d0 ad f1, timelineantialias64p16.jpg is missing
Author
Owner

So it looks like this bug was introduced in oxtimelines, changeset 2, line 328, in the "remove tiles from previous run" section

So it looks like this bug was introduced in oxtimelines, changeset 2, line 328, in the "remove tiles from previous run" section
rlx added the
major
critical
labels 2012-06-06 10:51:13 +00:00
Author
Owner

To fix the broken default timelines as quickly as possible, we should run one anitialias + cut detection pass for all items with new timelines, and then start over

To fix the broken default timelines as quickly as possible, we should run one anitialias + cut detection pass for all items with new timelines, and then start over
j added the
fixed
label 2012-06-10 09:14:22 +00:00
j closed this issue 2012-06-10 09:14:22 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: 0x2620/pandora#820
No description provided.