[SOLVED] MJPEG Stream for herospeed (S2L33M_IMX322_W_6.1.34.1)

I don't know the answer to your question @7aman. This firmware s2l33m_imx322_W_7.1.25.1.zip MAY be for your camera and MAY help you resolve your issue (ALWAYS research and be very careful before applying firmware though). Have you tried accessing the stream using ONVIF?
 
  • Like
Reactions: 7aman
Suggestion - though not guaranteed to work, but easy to try :
Use ONVIF Device Manager (sourceforge.net) to find the camera, and check the URL at the bottom of the Live Video page for the URL in use.
Plus check the profile page to confirm it's the MJPEG codec that's in use.
 
  • Like
Reactions: 7aman
Suggestion - though not guaranteed to work, but easy to try :
Use ONVIF Device Manager (sourceforge.net) to find the camera, and check the URL at the bottom of the Live Video page for the URL in use.
Plus check the profile page to confirm it's the MJPEG codec that's in use.
ODM is using RTSP:
rtsp://192.168.1.172:80/0

I need MJPEG stream that is using "http".

In Both "Profiles" and "Video streaming", video encoding is jpeg:

mjpeg.JPG
mjpeg2.JPG
 
I don't know the answer to your question @7aman. This firmware s2l33m_imx322_W_7.1.25.1.zip MAY be for your camera and MAY help you resolve your issue (ALWAYS research and be very careful before applying firmware though). Have you tried accessing the stream using ONVIF?
I tested all possible MJPEG stream URL, after upgrading to this version. Still no success.
Is ONVIF forcing manufacturers to implement some basic features, such as a unique URL or path to show mainstream video?

I found that in Dahua there are two ways to take a snapshot:
1) Private:
IPADDRESS/cgi-bin/snapshot.cgi
2) ONVIF:
IPADDRESS/onvifsnapshot/media_service/snapshot?channel=1&subtype=0

both work on most of Dahua IP Cameras.
Is the second one implemented on other well-known brands? Is it an ONVIF rule?
 
Eureka!!
I binwalked firmware file (.fls).
Code:
ls -la _S2L33M_IMX322_W_6.1.34.1.fls.extracted/ubifs-root/282501161/user/www/
drwxrwxrwx 1 root root  512 Jul 10 17:29 .
drwxrwxrwx 1 root root  512 Jul 10 17:29 ..
drwxrwxrwx 1 root root  512 Jul 10 17:29 avideo
drwxrwxrwx 1 root root  512 Jul 10 17:29 config
drwxrwxrwx 1 root root  512 Jul 10 17:29 css
drwxrwxrwx 1 root root  512 Jul 10 17:29 disk
drwxrwxrwx 1 root root  512 Jul 10 17:29 events
-rwxrwxrwx 1 root root 9662 Jul 10 17:29 favicon.ico
-rwxrwxrwx 1 root root 3599 Jul 10 17:29 frame.html
drwxrwxrwx 1 root root  512 Jul 10 17:29 help
drwxrwxrwx 1 root root  512 Jul 10 17:29 image
drwxrwxrwx 1 root root  512 Jul 10 17:29 images
-rwxrwxrwx 1 root root 4272 Jul 10 17:29 index.htm
-rwxrwxrwx 1 root root 4270 Jul 10 17:29 index.html
-rwxrwxrwx 1 root root 3927 Jul 10 17:29 install.html
drwxrwxrwx 1 root root  512 Jul 10 17:29 js
drwxrwxrwx 1 root root  512 Jul 10 17:29 lang
-rwxrwxrwx 1 root root  737 Jul 10 17:29 live.html
drwxrwxrwx 1 root root  512 Jul 10 17:29 localconfig
-rwxrwxrwx 1 root root 3534 Jul 10 17:29 macinstall.html
drwxrwxrwx 1 root root  512 Jul 10 17:29 menu
drwxrwxrwx 1 root root  512 Jul 10 17:29 network
drwxrwxrwx 1 root root  512 Jul 10 17:29 playback
drwxrwxrwx 1 root root  512 Jul 10 17:29 plugin
lrwxrwxrwx 1 root root   13 Jul 10 17:29 snap.jpg -> /tmp/snap.jpg
-rwxrwxrwx 1 root root  692 Jul 10 17:29 ssl_cert.pem
-rwxrwxrwx 1 root root  887 Jul 10 17:29 ssl_key.pem
drwxrwxrwx 1 root root  512 Jul 10 17:29 system

There is a file named "snap.jpg" and also a file named "live.html"

Solution is:
http://192.168.1.168/live.html

:)