Ticket #1048 (closed defect: fixed)
Packed bitstream results in inaccurate seeking
| Reported by: | Plorkyeran | Owned by: | TheFluff |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.1.8 |
| Component: | Video | Version: | devel |
| Severity: | major | Keywords: | |
| Cc: | Platform: | All | |
| Sub Component: | VProvider - FFMS |
Description (last modified by Plorkyeran) (diff)
With VFW video generated with packed bitstream enabled and then muxed into matroska, different methods of seeking can produce different images for the same frame number when using FFMS2. With the attached script and this video:
- Use ctrl-2 to jump to the end of the only subtitle line in the file
- Seek to the next frame. Note that it is frame 5151 and the titlecard remains visible.
- Framestep forward at least 10 frames to clear frame 5151 from the cache.
- Jump directly to frame 5151. Note that it is no longer the title card.
Jumping to frame 5150 via Jump to and then framestepping produces identical results.
Attachments
Change History
comment:2 Changed 2 years ago by TheFluff
- Status changed from accepted to closed
- Resolution set to invalid
Not a bug in Aegisub, same thing happens with FFMS2 regardless of application. Most likely related to this FFMS bug: http://code.google.com/p/ffmpegsource/issues/detail?id=3
One workaround is to use an AVI and the AVS provider.
comment:3 Changed 2 years ago by verm
- Status changed from closed to reopened
- Resolution invalid deleted
- Description modified (diff)
Re-open this until it's fixed upstream or we fix it in Aegisub.
comment:4 Changed 2 years ago by Plorkyeran
- Keywords vfr removed
- Summary changed from VFR video is not frame-accurate to Packed bitstream results in inaccurate seeking
- Description modified (diff)
- Sub Component set to AProvider - FFMS
comment:5 Changed 2 years ago by Plorkyeran
- Sub Component changed from AProvider - FFMS to VProvider - FFMS
Note: See
TracTickets for help on using
tickets.


Mine.