![](\"http:\/\/www.axis.com\/products\/cam_214\/img\/214_left.jpg\")
<\/p>\n<\/p>\n
I have been waiting for one of these for years. A network PTZ camera that does true standards based streaming. Most of the others from Linksys, DLink and so on seem like they fit the bill but their flavor of “MPEG-4” is only codec deep (if even that) and requires playback to be handled with their proprietary ActiveX or Java players. <\/p>\n
Not so with the Axis 214<\/a> which not only serves true MPEG-4 content but it is playable with QuickTime and any other player that can handle a standard RTSP MPEG-4 stream. This also means that the streams can be reflected by QuickTime\/Darwin Streaming Server to allow for a much larger audience than the camera itself can handle.<\/p>\n Unfortunately, getting it to work with the QuickTime Streaming Server but in the end it was well worth it.<\/p>\n In the interest of saving the rest of the world some time I am posting an email message from Kyle Robertson from Apple’s Streaming Server User’s Listserv<\/a> that was immensely helpful. First step is to log into the camera’s web interface and change one of the Secondly you need to log into the Darwin web interface and mount the stream Once you do this and enable the relay you will see the SDP file get created You don’t need to bother with manually uploading the SDP file from the Hope that helps! I have been waiting for one of these for years. A network PTZ camera that does true standards based streaming. Most of the others from Linksys, DLink and so on seem like they fit the bill but their flavor of “MPEG-4” is only codec deep (if even that) and requires playback to be handled with … Continue reading Axis 214 PTZ Camera, a dream come true..<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-1458","post","type-post","status-publish","format-standard","hentry","category-streaming-and-multi-media"],"_links":{"self":[{"href":"https:\/\/www.walking-productions.com\/notslop\/wp-json\/wp\/v2\/posts\/1458","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.walking-productions.com\/notslop\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.walking-productions.com\/notslop\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.walking-productions.com\/notslop\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.walking-productions.com\/notslop\/wp-json\/wp\/v2\/comments?post=1458"}],"version-history":[{"count":0,"href":"https:\/\/www.walking-productions.com\/notslop\/wp-json\/wp\/v2\/posts\/1458\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.walking-productions.com\/notslop\/wp-json\/wp\/v2\/media?parent=1458"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.walking-productions.com\/notslop\/wp-json\/wp\/v2\/categories?post=1458"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.walking-productions.com\/notslop\/wp-json\/wp\/v2\/tags?post=1458"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n
\nHey Shawn,
\nOver the span of a year I think I have it dialed.
\nFirstly you have two choices, you can use the mpeg4 encoder built into the
\ncamera, or you can use an external encoder such as VLC and convert the mjpeg
\nstream to mpeg4. This may prove a better method in the future as you could
\nconvert into H.264, but right now I think the built in encoder is best.<\/p>\n
\nfiles. You need to edit the \/etc\/rtspd\/rtspd.conf file and change the
\ntimeout value (default is 60 seconds). Changing it to ‘0’ will mean no
\ntimeout. This one had me stumped for a while!! If you don’t do that the
\nstream will reflect for 60 secs and then cut out.<\/p>\n
\nto be reflected. Go to ‘Relay settings’, ‘other relay’ and create a new one.
\nEnter the camera’s IP address. The mount point should be something like
\nthis: \/mpeg4\/1\/media.amp . Put in the cameras root user\/pass. Under the
\ndestination we want it to reflect the stream locally because it is running
\non the server that will be doing the feeds. I set the IP to 127.0.0.1 . Make
\nit an announced SDP, give it a name, and a system user\/pass if you haven’t
\nmade the group access file writeable to all.<\/p>\n
\nin the \\Movies directory of your Darwin server. Simply open that file with a
\nmedia program capable of reading .SDP files (quicktime) and tadaaa! If you
\ndon’t use HTTP streaming the stream is located at:
\nrtsp:\\\\servername\\filename.sdp:554 . I have had better accessibility using
\nstreaming over HTTP however.<\/p>\n
\ncamera. The only limitation I have run into so far (and it is a big one), is
\nthat Darwin will not reflect streams from more than one camera source. i.e.
\nIt will reflect all the feeds from one camera or camera server, but as soon
\nas you ask it to reflect another stream from a separate IP it fails. It only
\nseems to be able to do one at a time.<\/p>\n
\n-Kyle<\/p>\n","protected":false},"excerpt":{"rendered":"