Diagnosing FLV problems using FLVmeta's flvdump

compared with
Current by Roger G. Coram
on Apr 13, 2011 13:23.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
* Compare with Roger's migration approach to see if both solutions identify the same files as broken (i.e. validate the approaches)
* Solution specific to FLV, but general approach and liklihood of deconstruction code for different container formats suggests the approach will be applicable more widely if not the specific implementation |
| *Detailed Evaluation*\\ | |
| *Detailed Evaluation* \\ | * Not a resolution but provides a more direct indication of the problem.
* We'll need to verify that the same issue is apparent over a larger dataset. If it is indeed the case we could potentially begin to investigate recovering data from each file.
* Further analysis of the files will be necessary, possibly involving contact with the original supplier (i.e. if the strange frame-headers are indeed software-specific artifacts they may be able to provide input).
Not a resolution but provides a more direct indication of the problem.
We'll need to verify that the same issue is apparent over a larger dataset. If it is indeed the case we could potentially begin to investigate recovering data from each file.
Further analysis of the files will be necessary, possibly involving contact with the original supplier (i.e. if the strange frame-headers are indeed software-specific artifacts they may be able to provide input). |
| *Issue* | [AQuA:Player stops part way through some of the performances]\\ |
| *Tool* (link) | [http://code.google.com/p/flvmeta/|http://code.google.com/p/flvmeta/] ([http://code.google.com/p/flvmeta/source/browse/branches/1.0.x/flvdump.c|http://code.google.com/p/flvmeta/source/browse/branches/1.0.x/flvdump.c]) |