Opened 8 years ago

Last modified 7 years ago

#490 assigned defect

50p footage not handled correctly by perian 1.2 (1.1.4 working)

Reported by: masterseb Owned by: astrange
Priority: normal Milestone: Needs Feedback From User
Component: Codec Version: 1.2
Severity: normal Keywords:


50p HDV footage (standard quicktime codec) ist not played back correctly in quicktime and final cut pro. without perian you would need an external 50p decoder. it works fine in perian 1.1 (up to 1.14) but the picture starts to get bab in perian 1.2 and 1.2.1. in detail: the movement is not smooth, there is some kind of motion blur. here is a file for you to play around with

Change History (7)

comment:1 Changed 8 years ago by masterseb

sorry. forgot link. see next ticket. please delete this one!!!

comment:2 Changed 8 years ago by gbooker

Deleted next one. Next time just add it to this one, like I did in this comment:

comment:3 Changed 7 years ago by astrange

  • Milestone set to 1.3
  • Owner set to astrange
  • Status changed from new to assigned

The file plays out of order because the ffmpeg compatibility hack broke valid files with ctts atoms (and this is one). We either need to detect ctts properly (and ask for API for that if it doesn't exist) or add 'mp2v' where it mentions kMPEG2VisualCodecType in FFusion.

But the file is missing an aspect ratio atom, so mplayer plays it at 16:9 (1024x576) and QT plays it at 720x576, even with that fixed. Did FCP really create it like that?

comment:4 Changed 7 years ago by astrange

  • Milestone changed from 1.3 to 1.2.2

comment:5 Changed 7 years ago by astrange

I have a patch but now the sample link is dead.

comment:6 Changed 7 years ago by astrange

(In [1301]) FFusion: Split out setting PACKED_QUICKTIME_KNOWS_ORDER into a function and support HDV1 (MPEG-2 in MOV)

The sample link in the HDV bug is dead so I can't test this.

Refs #490

comment:7 Changed 7 years ago by astrange

  • Milestone changed from 1.2.2 to Needs Feedback From User

Actually it probably didn't fix it (that was for a different fourcc which might not even have made sense). So we do need that sample.

Note: See TracTickets for help on using tickets.