|
|
| Karel |
 Posted: Mar 17 2003, 06:31 PM |
 |
|
Unregistered
|
I often use the scan video streams for errors, but it's quite tricky to know where in the avi file are the wrong frames (hex adress) ;(I often replace wrong frames with a hex editor, from another copy of my bad avi)
So it would be useful (at least for me  ) to display the adress next to the frame number...
|
|
| Pamel |
| Posted: Mar 19 2003, 01:30 AM |
|
|
matroska team member
Group: Moderators
Posts: 151
Member No.: 1353
Joined: 15-December 02
|
This would also (indirectly) show how much space each frame is taking up. I don't know how useful to the more than a handful of people, but it shouldn't be hard to hard to implement since you already get the offset from the index, right?
--------------------
Please take anything I say with many many grains of salt. I can't tell the difference between my AVI and a hole in the ground. |
|
| Karel |
| Posted: Mar 19 2003, 04:25 AM |
|
|
Unregistered
|
| QUOTE (Pamel @ Mar 18 2003, 07:30 PM) | | This would also (indirectly) show how much space each frame is taking up. I don't know how useful to the more than a handful of people, but it shouldn't be hard to hard to implement since you already get the offset from the index, right? |
Yes... but what if the index is corrupted and you rebuild it using re-derive key-frame ? I had to do that : it took me hours to figure where were the wrong frames (virtualdub masked 95% of the whole video), correct the header of a single frame chunk using my hex editor... and so on. 
And I think it would help having directly the real adress in vdub.
As this feature *seems* easy to implement, why not implementing it ? (okay, I'm perhaps the only one interested ?  ) |
|
