That way your text will appear in the same format).Ĭodec_long_name=H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
SSF VIDEO FILE WINDOWS
The above command results in a txt file being created with the following information… (remember when saving these from Linux to use in Windows – you have to change the encoding from Unix to Windows. To do this I will use the GREP utility that is not as easy to get done in Windows.įfprobe -show_streams -count_frames -pretty /home/david/Desktop/14263902.SSF > /home/david/Desktop/Stream-FrameCount.txt The reason is that in the second part, I am going to only output specific information into a text file.
However, if you use it from the command line, you can see whats going on and get the information you require.Īlthough its possible to do the first bit here in Windows, I chose to do both in Linux. Its similar to a lot of video information tools and is actually used as a backend for a few of them. This program, that comes along with FFmpeg, attempts to open an input file and then probe it for information. I have been using FFmpeg for a while but this seemed to be a job for FFprobe.
SSF VIDEO FILE HOW TO
Was it possible to analyze the original SSF before wrapping it into an avi and how to deal with the other camera that appeared to have an incorrect frame rate? The result to all this was that I now had a correct piece of video that I could analyze effectively. Scrubbing through the Video in Virtualdub (Imaged blurred on purpose)ĭue to the timecodes being removed from the new avi, in order for it to play correctly, a frame rate needs to be established.įor Ch03, this was the total frames (4518) divided by the duration of the video in seconds (201). I also compared and verified the raw data was present in both the SSF and the new avi.
The I frames were also identified in the GOP structure. The resulting files played and scrubbed perfectly within Virtualdub when using the ffmpeg input driver. I told FFmpeg to wrap the video using avi (-vcodec copy -f avi) but to ignore the audio (-an) and most importantly to rewrite the Presentation Time Stamp (-vsync drop). Inform : 352*288 (1.222), AVC (PAL) (1 Ref Frames)įormat profile : settings : 1 Ref FramesĪs both SSF’s had been identified as H264 streams I used FFMPEG to wrap up the video into a standard avi container.įFMPEG -i filename.ssf -an -vsync drop -vcodec copy -f avi out.avi MediaInfo gives us some useful information: The conclusion here is that those AVI’s are not worth much and are pretty unreliable. For some reason the transcoding process has slowed it down – Its got the frame rate wrong! The footage has been transcoded, the duration’s have changed and when reviewing Ch05, it plays very slowly. I finally compared the raw data from the avi’s to that in the original SSF’s. Both had a GOP structure of IPPPP.Ĭh03 – 4513 Frames, 22FPS, 3 minutes 25 secondsĬh05 – 2509 Frames, 12FPS, 3 minutes 29 seconds Upon the creation of the new avi’s, these were examined in Gspot and MediaInfo. Both avi’s were Divx 5.0 format with the DX50 4CC code. By selecting this, the interface displays the time duration of the selected SSF file.īy reviewing the SSF Files I recorded that:Ĭh03 had a time duration of 3 minutes 21 seconds,Ĭh05 had a time duration of 3 minutes 19 seconds The third icon down gives the ability to export an ‘avi’. This was an obvious concern and required further inspection. One of the cameras also appeared to skip frames. I couldn’t move forward and count the image changes. This caused problems when trying to establish frame rate. I noted that when paused and using the frame fw function, I could only move approx.
Although this can cause a problem if viewing a number of cameras, its actually better when we come to start analyzing the video.Įffective playback using the BKplayer seems to be rather hit and miss. It would appear that although the player supports multicamera playback, the person conducting the export in this case has created a file for each camera.
0 kommentar(er)
