The AVI writer writes malformed big AVIs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 786
- Forks
- 267
- PR merge metrics
- No merged PRs in 30d
Description
See these threads:
- [Not able to open full length of large AVI file.](http://imagej.1557.x6.nabble.com/Not-able-to-open-full-length-of-large-AVI-file-tt4496180.html)
- [AVI re-opening problem](http://imagej.1557.x6.nabble.com/AVI-re-opening-problem-tt5014442.html)
According to Michael Schmid, the issue is that the `AVI_Writer` plugin only writes AVI 1.0, not 2.0, which does not support files larger than 2GB.
According to Frank Shaffer, one workaround is to run through the bogus AVI files through VirtualDub first before using them elsewhere.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the AVI_Writer plugin and reviewing how it writes AVI 1.0 files, then read the linked discussions for the large-file failure details. Done means large AVI files no longer become malformed or unusable when they exceed 2GB, with validation against the reported reopening and length problems.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100