<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body fpstyle="1" ocsi="0">
I mentioned this problem on the ffmpeg developpers mailing-list.<br>
I sent a sample video.<br>
This is what I was told:<br>
<br>
The first 37 bytes look similar to a video stream but are invalid for a hevc video, making auto-detection more difficult. Not sure if this should be fixed, could you tell us the name of the IP camera?<br>
<b>Could this be a bug in openrtsp?<br>
</b><br>
Thank you for the sample, Carl Eugen<br>
<br>
00000000 00 00 00 01 67 4d 00 32 9d a8 0a 00 2d 69 b8 08 |....gM.2....-i..|<br>
00000010 08 0a 00 00 03 00 02 00 00 03 00 51 08 00 00 00 |...........Q....|<br>
00000020 01 68 ee 3c 80 00 00 00 01 40 01 0c 01 ff ff 01 |.h.<.....@......|<br>
<br>
"67" and "4d" are not valid, neither is "ee" in the second "NAL".<br>
00 00 00 01 4 01 is the actual start of the video stream.<br>
<br>
<br>
<br>
<br>
<br>
________________________________________<br>
De : live-devel [live-devel-bounces@us.live555.com] de la part de Nicolas Julien [nicolas.julien@cdvi.com]<br>
Date d'envoi : lundi 21 septembre 2020 11:46<br>
À : LIVE555 Streaming Media - development & use<br>
Objet : Re: [Live-devel] Record a H265 stream from IP camera to file<br>
<br>
I found the solution.<br>
You must name the file with the extension .h265.<br>
With the right extension, the conversion with ffmpeg works perfectly !<br>
<br>
________________________________________<br>
De : live-devel [live-devel-bounces@us.live555.com] de la part de Nicolas Julien [nicolas.julien@cdvi.com]<br>
Date d'envoi : lundi 21 septembre 2020 11:06<br>
À : LIVE555 Streaming Media - development & use<br>
Objet : Re: [Live-devel] Record a H265 stream from IP camera to file<br>
<br>
Hi,<br>
<br>
I tested the command lines.<br>
openrtsp generates the raw files as expected :<br>
<br>
Started playing session<br>
Receiving streamed data...<br>
Outputting data from the "video/H265" subsession to "video-H265-2-00010-00020"<br>
Outputting data from the "video/H265" subsession to "video-H265-3-00020-00030"<br>
Outputting data from the "video/H265" subsession to "video-H265-4-00030-00040"<br>
etc...<br>
<br>
<br>
Unfortunately the conversion with ffmpeg does not work because the program detects a lot of errors :<br>
<br>
[h264 @ 03965300] no frame!<br>
[h264 @ 03965300] missing picture in access unit with size 4840<br>
[h264 @ 03965300] data partitioning is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.<br>
[h264 @ 03965300] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel@ffmpeg.org)<br>
<br>
________________________________________<br>
De : live-devel [live-devel-bounces@us.live555.com] de la part de Ross Finlayson [finlayson@live555.com]<br>
Date d'envoi : vendredi 11 septembre 2020 13:41<br>
À : LIVE555 Streaming Media - development & use<br>
Objet : Re: [Live-devel] Record a H265 stream from IP camera to file<br>
<br>
> On Sep 11, 2020, at 8:52 PM, Nicolas Julien <nicolas.julien@cdvi.com> wrote:<br>
><br>
> Any idea why this is not working?<br>
<br>
The error message says why:<br>
<br>
> Warning: we don't implement a QuickTime Video Media Data Type for the "H265" track, so we'll insert a dummy "????" Media Data Atom instead. A separate, codec-specific editing pass will be needed before this track can be played.<br>
<br>
Specifically, our implementation of outputting “.mp4”-format files does not yet handle writing “.mp4”-format files that contain H.265 video. (See the “if” statement in “liveMedia/QuickTimeFileSink.cpp”, starting at line 644.)<br>
<br>
One way you can overcome this problem is to instead record a raw H.265 video file, *not* a “.mp4”-format file. I.e. run:<br>
openrtsp -b 200000 -u admin admin -v -d 10 -w 2560 -h 1440 -f 15 rtsp://192.168.1.64:554/Streaming/Tracks/101?transportmode=unicast&replaymode=onvifreplay<br>
i.e., without the “-4” option, and without stdout redirection.<br>
<br>
This will give you a video file, named something like “VIDEO-1-H265”, which you can rename as “test.h264” (note, with a “.h264” filename suffix, even though the data is H.265). Then use “ffmpeg” to convert this to a “.mp4”-format file, e.g.<br>
ffmpeg -i test.h264 -c copy test.mp4<br>
<br>
<br>
Ross Finlayson<br>
Live Networks, Inc.<br>
http://www.live555.com/<br>
<br>
<br>
_______________________________________________<br>
live-devel mailing list<br>
live-devel@lists.live555.com<br>
http://lists.live555.com/mailman/listinfo/live-devel<br>
<br>
_______________________________________________<br>
live-devel mailing list<br>
live-devel@lists.live555.com<br>
http://lists.live555.com/mailman/listinfo/live-devel<br>
<br>
_______________________________________________<br>
live-devel mailing list<br>
live-devel@lists.live555.com<br>
http://lists.live555.com/mailman/listinfo/live-devel<br>
</body>
</html>