Search results

Hi, Phil. Your suggested approach is the same as mine but, it is still unknown info about recording system maker, model, settings and whatever can help to evaluate the file authenticity, including sample recordings. All of that and other info will be requested during lawsuit, but for while the...

Complimentary info: 8- Field "Creation Time" in "File Properties Object": 2016-2-11 10:23:12.686 (five days after accident). This field, according Advanced Systems Format (ASF) Specification, Revision 01.20.03, edited by Microsoft Corporation (December 2004), "specifies the date and time of...

Sirs, After deeper checking and compiling information that was posted during this thread, that´s what is relevant: 1- ASF format video file (wmv file) made by a 4-channel dash cam recorder. Unknown maker, model and settings 2- frame rate: 4 FPS. That´s what happens when video is played 3-...

To whom it can concern: FFDSHOW is configurable video and audio decoder and can be set to show many data of frame and file during video playing. Of course, the player will have to be configured to use FFDSHOW as decoder. (thanks to user Jagabo on videohelp forum)

Hi all. At this moment, I think that a video editor that showed only encoded frames (nothing like Vegas Pro :) ) and exhibited low level data related to each frame( index data, payload data, ASF format structure fields and others) might unveil something useful. To use a hex editor would demand...

No doubt that 30FPS header info may be a trick to impress the noobs, and, if so, such information may not be considered an evidence that the wmv video was tampered or, in some way, not original. "Do try to find out what cam this is as that will help the knowledgeable folks here help you-...

Sorry, but I didn´t get why would be needed to tell the player to handle it like a 30FPS file if the file indeed is 4FPS and in the header is also specified such a frame rate (4FPS). With a specification in the header of 4FPS and existing 4 encoded frames per second, video is played with the...

I´ve just discovered that Vegas Pro interpolates (virtual) frames in order to comply to the FPS specified in the project. Vegas Pro is not the appropriate tool for this, so it made me get erroneous conclusions, but not all is lost. I´ve checked that wmv file with ASFBin 1.8 and discovered that...

That segment that "surprisingly" is missing will justify a bunch of questions to the video recorder maker in order to make clear that such phenomenum unlikely (impossibily) would has happen due involuntary reasons. This will be taken in consideration. For while, this and my hypothesis are only...

Exactly, but although it is something that easily comes to anyone´s mind, it has to be technically proved. The help you all, here and in other "forums" (fora), have given is priceless and made possible to me get at the present point. Although there are many questions to be asked yes, now I...

The good part in this case is this WMV was presented as an evidence by the other party, a transportation company that owns the bus that has crashed my client´s vehicle.

> One more information to be checked: if timestamp in the video is correct. That´s my #2 hypothesis. A lot of questions is to be made to the other party during the lawsuit in order to make the truth arises. For while, I´ve got some clues (to be further checked) that lead me to consider this...

Nope! This is also one more fact that makes this WMV file suspicious. Accident happened on february, 6th 2016 and "modified" date is 11th. In the WMV header file, field "Creation Time" contains "2016-2-11 10:23:12.686 " Some possibilities: 1) this WMV file was resulted of an edition that was...

Yes, I´ve got what you said, but there´s not any information of this kind, unfortunately. I´ve already inspected the file with a hex editor. Sure! This and other questions are already prepared to be asked during lawsuit.

No metadata at all. To check this was one of the first things I did. I still find astonishing the fact of some cam makers intentionally record repeated frames, so wasting mass memory room, just to fake a higher fps.

Hi, Sawmaster. Yes, this video was provided as a legal evidence and the most important stretch is no longer there, allegedly due some recording failure or other unknown reason. A video that presents 2 scenes per second but is officialy, according file header, a 30 FPS video, with 15 repeated...

You mean that such a low end cam captures and digitalize in a very low rate (like 2 FPS) and intentionally records several identical frames (with same image)?

Hi, Jokiin. Yes, it´s also possible that´s a low end video recording system with a very low FPS rate (probably 2!). So, the original file had an extent cut off and finally it was saved with a set of parameters that result in a 30FPS file.

Hi, All. I hope that´s the most appropriate forum here, since it seems to be the more technically skilled. Most of 4-channel dash cam recorders claims a 30FPS frequency, some with more than that, other with at least 15FPS. I couldn´t find a vehicular system that recorded at very low rates as 2...