It works ok, but i have several problems with the audio from the video files stored.
I think that's a compression/codec issue but:
1. The file is stored as .h264 in the NVR, but I can't play through VLC. I need to tweek VLC to see the video but can't hear the audio!
The only way to see and listen the files is only through a player provided in the mini cd (Hangzhou Xiongmai Technology Co.,LTD.-Video Player)... Is any way to convert it easily with pc?
I have converted the files with a software provided by xiongmai but... the audio is horrible (Hangzhou Xiongmai Technology Co.,LTD.-Video Conver)
2. When I use the android app Xmeye, it download .mp4 video... but, again, can't hear the audio neither with the xmeye app nor with xmplayer.
If i download it on my pc.... still can't hear nothing with VLC (but can't play it with their player).
Could you help me?
That's an iXVR, that can store pre-encoded streams from IP cameras, also can encode streams from analogue cameras.
What type of camera is the source of the video?
This is the media info:
General
Complete name : C:\Users\Win10\Desktop\NVR_02_20190522_09.50.00-10.00.00[R][@17c29][0].h264
Format : AVC
Format/Info : Advanced Video Codec
File size : 51.7 MiB
Video
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L3.2
Format settings : CABAC / 1 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 1 frame
Format settings, GOP : M=1, N=50
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
OK, so that's an h.264 video stream, no mention of an audio stream.
Do you have a small sample of a file with video and audio that you'd be comfortable sharing?
So it looks like not encoded in a way that VLC recognises.
That's not unusual - video/audio files have lots of internal structural variety, different players can give different results with different cameras.
This file appears to be in a proprietary format, presumably deliberately so such that you are forced to use the XM app.
Unhelpfully, there is no codec ID as the format hint.
The usual Linux media players Xplayer and VLC don't recognise the file format without being forced.
Mpv media player did not play the file either - which is surprising since it generally automatically plays anything it's given.
Looking at the media info - there is no indication of an audio stream in the file.
See below, with also a file from my helmet cam for comparison.
Code:
alastair@PC-I5 ~/tmp $ ll NVR*
-rw-rw-r-- 1 alastair alastair 54198272 May 28 16:12 'NVR_02_20190522_09.50.00-10.00.00[R][@17c29][0].h264'
alastair@PC-I5 ~/tmp $ mediainfo NVR*
General
Complete name : NVR_02_20190522_09.50.00-10.00.00[R][@17c29][0].h264
Format : AVC
Format/Info : Advanced Video Codec
File size : 51.7 MiB
Video
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L3.2
Format settings : CABAC / 1 Ref Frames
Format settings, CABAC : Yes
Format settings, ReFrames : 1 frame
Format settings, GOP : M=1, N=50
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
alastair@PC-I5 ~/tmp $ mediainfo *545*
General
Complete name : FILE0545.AVI
Format : AVI
Format/Info : Audio Video Interleave
File size : 154 MiB
Duration : 2 min 1 s
Overall bit rate : 10.6 Mb/s
Video
ID : 0
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 1 Ref Frames
Format settings, CABAC : Yes
Format settings, ReFrames : 1 frame
Codec ID : H264
Duration : 2 min 1 s
Bit rate : 10.5 Mb/s
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 60.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.190
Stream size : 151 MiB (99%)
Audio
ID : 1
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : FF-2
Duration : 2 min 0 s
Bit rate : 128 kb/s
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 32.0 kHz
Frame rate : 31.250 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 1.85 MiB (1%)
Alignment : Split accross interleaves
Interleave, duration : 32 ms (1.92 video frames)
alastair@PC-I5 ~/tmp $
The NVR file can be transcoded, with many complaints about invalid data, into usable video (kitchen scene, not the same as the Android app file) with ffmpeg by forcing the decoder to be h264
ffmpeg also does not find an audio stream, either automatically or by forcing a few of the more common audio codecs from the very many available.
The file from the Android app plays with all the media players I tried, but again does not show an audio stream.
Code:
alastair@PC-I5 ~/tmp $ mediainfo *.mp4
General
Complete name : n-b8452da1409254d5,ch2_s-20190524123000_e-124000.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 96.1 MiB
Duration : 9 min 59 s
Overall bit rate : 1 344 kb/s
Writing application : Lavf57.56.100
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L3.2
Format settings : CABAC / 1 Ref Frames
Format settings, CABAC : Yes
Format settings, ReFrames : 1 frame
Format settings, GOP : M=1, N=12
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 9 min 59 s
Bit rate : 1 343 kb/s
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 15.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.097
Stream size : 96.0 MiB (100%)
alastair@PC-I5 ~/tmp $
It would be interesting to hear what other members say about these files.
I'm less well versed in video formats than some.
Yes, widely used in the OEM market.
A couple of months back I bought at low cost an AHB7808R-MH-V3 board to replace a slightly earlier version in a QVIS DVR where the Sata interface had failed, then re-sold on eBay.
I thought the newest firmware with the reworked user interface worked pretty well, and the board handled some good combinations of IP and analogue cameras.
Not very securely built firmware though, easily hackable.
I think any answer would be guessing quite a bit, if you mean the XVR firmware.
The XM firmware does have a reasonable way of matching up the firmware being applied with the model number of what it's being applied to and rejecting on a mismatch.
Unbricking via the serial interface isn't too difficult, but does need a level of familiarity with the techy details.
It's very similar to how Dahua operates at the bootloader level - and I've often wondered why - but never asked.
The current firmware, with the 2 interface designs, is available here : Hangzhou Xiongmai Technology Co.,LTD.-8ch 1080N AHD DVR Board(V3)
But what I would guess at is that the video encoding of the camera will likely determine the structure of the video files that the NVR is mostly just storing.
And I wouldn't be surprised if the camera firmware is also a Xiongmaitech product, again it's widely used.
What does the camera web GUI say for the model number and the firmware version?
