Hi Tim, I have had a quick look at the two types of SEC file I have in my archive. From a SRD-1670 I have a file that presents itself as Cam6. At the end of the file is the index with each index marker starting with 05 80 80. From a SRD-852D I have a file that presents itself as Cam1. At the end of the file is the index with each index marker starting with 00 80 80. Its a guess that the first byte is the stream identifier. Prior to the index I cannot find any footer and by previewing a set of mpeg slices, I cannot identify the GOP hex.

What is a BU file? Video file created with a Samsung DVR, such as a CCTV (closed circuit television) recording system; contains surveillance video in a proprietary Samsung format that can only be played back on Samsung devices or with Samsung's video software. Bu files contain surveillance video in a proprietary Samsung format and are playable on Samsung devices or with Samsung's video software. When you are trying to open a.BU file on Windows, Mac, media players, iOS, other portable devices, you will get the info that BU files are not supported by them.

They will be there somewhere but it would take some considerable time to pull the files apart! The index markers may only be used within their export so I may be leading you down the wrong path! If this is something you do crack, please feel free to let me know and I can share throughout the community. Good luck and apologies I couldn’t help any further, Spready. Can some kind soul help me with this one, (I think this is the DVR (SRD-440 DVR)) (the security software is set to record at 12 frames per second) The video clip is a few seconds over 2 minutes long. The SEC file plays in the “exe” provided, but the quality is atrocious.

I want to see what the file looks like in a different player. That solved getting it into a format I can play (vob/mpg) and it does look much clearer than loaded into the provided “exe” player, I am still trying to master the framerate and aspect switches, I am very much a beginner, some of the examples I have found generate buffer underrun, others don’t change the framerate, the people in the clip are still zipping about.

Trying to change from 12 to 24 frames, and the video is “letterbox” when I think it should be 4:3, so it’s very short stumpy people zipping about may this numpty beg an example for each issue? (I have about 40 clips I need to convert this way, with more created ever other day, so I’d really like to be able to get my head around it all.) thanks, RB. OK, just to clear up some recent threads The Samsung DVR used here was an SRD-440. RB kindly sent me a file to test and he sent me a.BU file with an associated.db2 file.

This was a bit of a surprise as in all older Samsung DVR’s, the.bu files can only be played back in the DVR. I mentioned this here, It appears that Samsung have caught on, and the BU file is now playable due to it being a H264/AVC Stream conforming to a standard profile. I have updated the IFSEC Post mentioned above to highlight this change. Back to RB’s stream and the challenge was to get these files viewable in WMV format. They were all field based, at 704×288.

Tablica umnozheniya a4 2015. The speed of playback is controlled by the Samsung software, using the.db2 file. As such, the metadata and timing information in the video stream was wrong. This caused speed issues and then quality issues when attempting to correct this. As a result, I found it necessary to force an input rate and generate a new Presentation Time Stamp BEFORE the input file. The following FFmpeg string did the job ffmpeg -r 12 -fflags genpts -i FILE.bu -vf scale=704:528 -sws_flags lanczos -q:v 2 FILE.wmv Remember, this is for preview – analysis would be completed differently due to the scaling, the interpolation method, and the WMV compression! As its likely that RB may have quite a few.bu files in a folder, I placed this into a batch file to transcode the whole lot within a few minutes more on batch files coming in a new post soon! You should be able to view them with the associated.exe player that should have come with the.sec files.