‎Changelog

← Older revision Revision as of 17:54, 21 March 2019 (2 intermediate revisions by the same user not shown)Line 330: Line 330:     ==<font color="blue">Firmware images</font>== ==<font color="blue">Firmware images</font>== −* [https://community.elphel.com/files/393/20180511/ '''20180511''']+* [https://community.elphel.com/files/393/20190321/ '''20190321''']  +* [https://community.elphel.com/files/393/20180511/ 20180511]  * [https://community.elphel.com/files/393/20180416/ 20180416] * [https://community.elphel.com/files/393/20180416/ 20180416] −* [https://community.elphel.com/files/393/20180406/ 20180406]      ===Changelog=== ===Changelog=== −  <font size='1'>'''==20180511=='''+  <font size='1'>'''==20190321=='''  + * overall minor changes  +  * fixed photofinish demo  + '''==20180511=='''    * added cron program   * added cron program    * multi cameras control interface   * multi cameras control interface Oleg

‎Notes

← Older revision Revision as of 18:20, 20 March 2019 (11 intermediate revisions by the same user not shown)Line 6: Line 6:  ==Notes== ==Notes==    −* In situations when streaming across middleboxes (switches and other devices) make sure the camera link is the slowest one.+* '''In situations when streaming across middleboxes (switches and other devices) make sure the camera link to the closest network device is the slowest one or keep the image size small enough so it does not overflow any middlebox's buffers'''.  * Example congestion situatation: * Example congestion situatation: −  ''camera <-- 1000Mbps --> Gigabit switch <-- 100Mbps (PC NIC limited) --> PC''+  <font size=2>'''camera''' <-- 1000Mbps --> '''Gigabit switch''' <-- 100Mbps (PC NIC limited) --> '''PC'''</font>    PC might not get all the packets depending on switch's buffers sizes (e.g. for netgear GS105 has 128kB which gets overflowed at image sizes 200+kB)   PC might not get all the packets depending on switch's buffers sizes (e.g. for netgear GS105 has 128kB which gets overflowed at image sizes 200+kB)  * Setting link speed examples: * Setting link speed examples: Line 15: Line 15:  * dump UDP packets log on the camera (tcpdump if installed): * dump UDP packets log on the camera (tcpdump if installed):    tcpdump -i eth0 -n udp port <someport> -w packets.pcap   tcpdump -i eth0 -n udp port <someport> -w packets.pcap  +* log network packets on PC:  + '''wireshark''' works fine  * live555 is used by vlc and mplayer while gstreamer is standalone * live555 is used by vlc and mplayer while gstreamer is standalone    As UDP has no congestion control there might be several workarounds:   As UDP has no congestion control there might be several workarounds: Line 21: Line 23:  * Patching live555 options: * Patching live555 options:    1. Stick close to [https://tools.ietf.org/html/rfc4585 RFC4585] and [https://tools.ietf.org/html/rfc6679 RFC6679], also checkout [https://tools.ietf.org/html/rfc8087 RFC8087] & [https://tools.ietf.org/html/rfc8311 RFC8311]?   1. Stick close to [https://tools.ietf.org/html/rfc4585 RFC4585] and [https://tools.ietf.org/html/rfc6679 RFC6679], also checkout [https://tools.ietf.org/html/rfc8087 RFC8087] & [https://tools.ietf.org/html/rfc8311 RFC8311]? −  2. In live555 make RTCP RR reports sent out by the receiver for every 50 (or any other number) packets received - implement handling this info in the sender (camera)+  2. Make RTCP RR reports sent out by the receiver for every 50 (or any other number) packets received - implement handling this info in the sender (camera)    Implementing 2:   Implementing 2:       <font size=2>'''RTCP.c:'''      <font size=2>'''RTCP.c:''' Line 41: Line 43:                   '''// here fRTCPInstanceForMultiplexedRTCPPackets is just reused'''                  '''// here fRTCPInstanceForMultiplexedRTCPPackets is just reused'''                   fRTCPInstanceForMultiplexedRTCPPackets->sendReport();                  fRTCPInstanceForMultiplexedRTCPPackets->sendReport(); −     }+            } − }</font>+        }</font>  +* Patching gstreamer:  + First, need to find how to make gstreamer send RR reports. Then proceed as with live555.     ==Other links== ==Other links==  +* [https://www.dataexpedition.com/support/notes/tn0021.html Loss, Latency, and Speed] - some general info  +* [https://tools.ietf.org/html/rfc4585 RFC4585]: Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)  +* [https://tools.ietf.org/html/rfc6679 RFC6679]: Explicit Congestion Notification (ECN) for RTP over UDP  +* [https://tools.ietf.org/html/rfc8087 RFC8087]: The Benefits of Using Explicit Congestion Notification (ECN)  +* [https://tools.ietf.org/html/rfc8311 RFC8311]: Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation     [[Category:393]] [[Category:393]] Oleg

‎Notes

← Older revision Revision as of 18:17, 20 March 2019 (8 intermediate revisions by the same user not shown)Line 8: Line 8:  * In situations when streaming across middleboxes (switches and other devices) make sure the camera link is the slowest one. * In situations when streaming across middleboxes (switches and other devices) make sure the camera link is the slowest one.  * Example congestion situatation: * Example congestion situatation: −  ''camera <-- 1000Mbps --> Gigabit switch <-- 100Mbps (PC NIC limited) --> PC''+  <font size=2>'''camera''' <-- 1000Mbps --> '''Gigabit switch''' <-- 100Mbps (PC NIC limited) --> '''PC'''</font>    PC might not get all the packets depending on switch's buffers sizes (e.g. for netgear GS105 has 128kB which gets overflowed at image sizes 200+kB)   PC might not get all the packets depending on switch's buffers sizes (e.g. for netgear GS105 has 128kB which gets overflowed at image sizes 200+kB)  * Setting link speed examples: * Setting link speed examples: Line 15: Line 15:  * dump UDP packets log on the camera (tcpdump if installed): * dump UDP packets log on the camera (tcpdump if installed):    tcpdump -i eth0 -n udp port <someport> -w packets.pcap   tcpdump -i eth0 -n udp port <someport> -w packets.pcap  +* log network packets on PC:  + '''wireshark''' works fine  * live555 is used by vlc and mplayer while gstreamer is standalone * live555 is used by vlc and mplayer while gstreamer is standalone    As UDP has no congestion control there might be several workarounds:   As UDP has no congestion control there might be several workarounds: Line 21: Line 23:  * Patching live555 options: * Patching live555 options:    1. Stick close to [https://tools.ietf.org/html/rfc4585 RFC4585] and [https://tools.ietf.org/html/rfc6679 RFC6679], also checkout [https://tools.ietf.org/html/rfc8087 RFC8087] & [https://tools.ietf.org/html/rfc8311 RFC8311]?   1. Stick close to [https://tools.ietf.org/html/rfc4585 RFC4585] and [https://tools.ietf.org/html/rfc6679 RFC6679], also checkout [https://tools.ietf.org/html/rfc8087 RFC8087] & [https://tools.ietf.org/html/rfc8311 RFC8311]? −  2. In live555 make RTCP RR reports sent out by the receiver for every 50 (or any other number) packets received - implement handling this info in the sender (camera)+  2. Make RTCP RR reports sent out by the receiver for every 50 (or any other number) packets received - implement handling this info in the sender (camera)    Implementing 2:   Implementing 2:       <font size=2>'''RTCP.c:'''      <font size=2>'''RTCP.c:''' Line 41: Line 43:                   '''// here fRTCPInstanceForMultiplexedRTCPPackets is just reused'''                  '''// here fRTCPInstanceForMultiplexedRTCPPackets is just reused'''                   fRTCPInstanceForMultiplexedRTCPPackets->sendReport();                  fRTCPInstanceForMultiplexedRTCPPackets->sendReport(); −     }+            } − }</font>+        }</font>  +* Patching gstreamer:  + First, need to find how to make gstreamer send RR reports. Then proceed as with live555.     ==Other links== ==Other links==  +* [https://www.dataexpedition.com/support/notes/tn0021.html Loss, Latency, and Speed] - some general info  +* [https://tools.ietf.org/html/rfc4585 RFC4585]: Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)  +* [https://tools.ietf.org/html/rfc6679 RFC6679]: Explicit Congestion Notification (ECN) for RTP over UDP  +* [https://tools.ietf.org/html/rfc8087 RFC8087]: The Benefits of Using Explicit Congestion Notification (ECN)  +* [https://tools.ietf.org/html/rfc8311 RFC8311]: Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation     [[Category:393]] [[Category:393]] Oleg

Created page with "==About== * 10393 series * /usr/bin/str ==Notes== * In situations when streaming across middleboxes (switches and other devices) make sure the camera link is the slowest on..."

New page

==About==

* 10393 series
* /usr/bin/str

==Notes==

* In situations when streaming across middleboxes (switches and other devices) make sure the camera link is the slowest one.
* Example congestion situatation:
''camera <-- 1000Mbps --> Gigabit switch <-- 100Mbps (PC NIC limited) --> PC''
PC might not get all the packets depending on switch's buffers sizes (e.g. for netgear GS105 has 128kB which gets overflowed at image sizes 200+kB)
* Setting link speed examples:
ethtool -s eth0 speed 100 duplex half autoneg off
ethtool -s eth0 speed 1000 duplex full autoneg off
* dump UDP packets log on the camera (tcpdump if installed):
tcpdump -i eth0 -n udp port <someport> -w packets.pcap
* live555 is used by vlc and mplayer while gstreamer is standalone
As UDP has no congestion control there might be several workarounds:
1. patch live555 and gstreamer
2. slow down camera link
* Patching live555 options:
1. Stick close to [https://tools.ietf.org/html/rfc4585 RFC4585] and [https://tools.ietf.org/html/rfc6679 RFC6679], also checkout [https://tools.ietf.org/html/rfc8087 RFC8087] & [https://tools.ietf.org/html/rfc8311 RFC8311]?
2. In live555 make RTCP RR reports sent out by the receiver for every 50 (or any other number) packets received - implement handling this info in the sender (camera)
Implementing 2:
<font size=2>'''RTCP.c:'''
if (fSource != NULL && fSource->RTPgs() == RTCPgs) {
// We're receiving RTCP reports that are multiplexed with RTP, so ask the RTP source
// to give them to us:
fSource->registerForMultiplexedRTCPPackets(this);
} else {
'''// need to register our RTCP instance here it will be passed to MultiFramedRTPSource.c which receive RTP packets'''
'''// just reused the instance for multiplexed packets'''
fSource->registerForMultiplexedRTCPPackets(this);
}
'''MultiFramedRTPSource.c:'''
receptionStatsDB().noteIncomingPacket(...)
'''// insert after this line something like:'''
int pnum = receptionStatsDB().totNumPacketsReceived();
if ((pnum%50)==0){
if (fRTCPInstanceForMultiplexedRTCPPackets!=NULL){
'''// here fRTCPInstanceForMultiplexedRTCPPackets is just reused'''
fRTCPInstanceForMultiplexedRTCPPackets->sendReport();
}
}</font>

==Other links==

[[Category:393]]
[[Category:streamer]]
[[Category:str]]
[[Category:gstreamer]]
[[Category:rtsp]]
[[Category:udp]] Oleg

‎Setup

← Older revision Revision as of 21:51, 13 March 2019 (2 intermediate revisions by the same user not shown)Line 77: Line 77:     ==<font color="blue">Setup</font>== ==<font color="blue">Setup</font>==  +  +* Poky 2.4 Rocko (Kubuntu 16.04)  +<font size='2'>  + git clone -b '''rocko''' https://git.elphel.com/Elphel/elphel393.git  + cd elphel393  + ./setup.py  + cd poky  + . ./oe-init-build-env  + bitbake u-boot device-tree linux-xlnx core-image-elphel393  +</font>  +  * Poky 2.6 Thud (Kubuntu 18.04) * Poky 2.6 Thud (Kubuntu 18.04)  <font size='2'> <font size='2'> −  git clone -b thud https://git.elphel.com/Elphel/elphel393.git+  git clone -b '''thud''' https://git.elphel.com/Elphel/elphel393.git    cd elphel393   cd elphel393    ./setup.py   ./setup.py Oleg

‎Live RTSP stream

← Older revision Revision as of 18:33, 13 March 2019 Line 91: Line 91:  * careful with streams at higher resolution than 1920x1088 * careful with streams at higher resolution than 1920x1088  * 10353 - works * 10353 - works −* <b>10393 - doesn't have a streamer yet</b>+* <b>10393 - works</b>  =====native resolution===== =====native resolution=====  <font size='2'> <font size='2'> Oleg

← Older revision Revision as of 00:35, 3 March 2019 (2 intermediate revisions by the same user not shown)Line 1: Line 1:  <!--{{Manual Header}} --> <!--{{Manual Header}} --> − +[[Image:Elphel_andrey_oleg_olga.jpeg|270px|thumb|left|Elphel team]]  Elphel is a technology company doing research and development in the field of high-performance digital cameras, image processing, 3D imaging and machine learning. Elphel is a technology company doing research and development in the field of high-performance digital cameras, image processing, 3D imaging and machine learning. −   Elphel imaging systems are primarily used for for scientific applications that require designs to be user-modifiable at all levels - from the hardware and FPGA code to the system and application software. Since the start of the company in 2001, Elphel was adhering to the FLOSS practice for the code and now applies CERN Open Hardware License to all electronic boards and mechanical CAD files. Elphel cameras are used in many National Laboratories, and universities in USA, European Union and other countries. Elphel imaging systems are primarily used for for scientific applications that require designs to be user-modifiable at all levels - from the hardware and FPGA code to the system and application software. Since the start of the company in 2001, Elphel was adhering to the FLOSS practice for the code and now applies CERN Open Hardware License to all electronic boards and mechanical CAD files. Elphel cameras are used in many National Laboratories, and universities in USA, European Union and other countries.    Line 40: Line 39:  fax: (801) 812-8267 fax: (801) 812-8267    −site: [http://www.elphel.com www.elphel.com]+site: [https://www.elphel.com https://www.elphel.com]           ---- ---- −''Free Software and Open Hardware. Elphel, Inc., 2005''+''Free Software and Open Hardware. Elphel, Inc., {{CURRENTYEAR}}'' Andrey.filippov

Andrey.filippov uploaded File:Elphel andrey oleg olga.jpeg

New page

== Licensing ==
{{CC }} Andrey.filippov

← Older revision Revision as of 00:22, 3 March 2019 Line 1: Line 1: −{{Manual Header}}+<!--{{Manual Header}} -->    −The Elphel, Inc. was formed in 2001. The basic goals of the project are development and manufacturing of high speed reconfigurable network cameras. Members of the development team are from America, China, Russia, Ukraine, Switzerland and the UK. The main principles of development - Free Software and Open Hardware.+Elphel is a technology company doing research and development in the field of high-performance digital cameras, image processing, 3D imaging and machine learning.  +   +Elphel imaging systems are primarily used for for scientific applications that require designs to be user-modifiable at all levels - from the hardware and FPGA code to the system and application software. Since the start of the company in 2001, Elphel was adhering to the FLOSS practice for the code and now applies CERN Open Hardware License to all electronic boards and mechanical CAD files. Elphel cameras are used in many National Laboratories, and universities in USA, European Union and other countries.  +   +Starting with Google Books and later Google Street View projects we introduced JP4 – JPEG-based (and so compatible with the standard libraries) image compression that preserves raw Bayer data of the image sensors. Raw Bayer mosaic is a preferred format for image processing including various types of end-to-end DNN.  +   +Elphel cameras offer unprecedented combination of high performance and complete openness at all levels – from mechanical and circuit design, FPGA RTL code up to all levels of the system and application software. All the design files are publicly available at Elphel web sites and through the popular GitHub repository. These features make Elphel products attractive for scientific research and innovative products. Elphel technology has been referenced in over a hundred scientific publications, and at least six US patent applications that use or reference Elphel products.  +   +Since 2012 Elphel has been developing methods of precise camera calibration and designing photogrammetric multiple-view cameras with thermally compensated SFE resulting in 0.05 pix reprojection error for 5 MPix sensors. We developed modified checkerboard pattern where each edge consists of 2 arcs - this modification from traditional straight lines checkerboard makes power spectrum uniform and improves accuracy of the indirect measurement of the PSF for subsequent optical aberration correction of the acquired images.  +   +From 2016 till present we are working on very long range 3D reconstruction and achieved 0.05 pix disparity resolution by combining several technology components developed by Elphel.  +   +* Use of multiple image sensors (4+) instead of conventional binocular stereo.  +* Advanced calibration, frequency-domain rectification, aberration correction, filtering, and 2D phase correlation.  +* Training and inference of the Deep Neural Network to predict the depth map from 2D correlation results. DNN analyzes context, extracts object edges, separates background, fuses depth map with textures.  +   +Elphel MNC393-XCAM camera is a narrow baseline 3D perception system providing 10% ranging accuracy at 2000 m, by utilizing the achieved 0.05 pix disparity resolution.    −More detailed information about Elphel, Inc. can be found at the official web-site [http://www.elphel.com www.elphel.com]. You can also find the latest versions of all the necessary software for the Elphel network cameras on [http://sourceforge.net/projects/elphel/ SourceForge].      '''Contacts:''' '''Contacts:''' Andrey.filippov

Oleg changed visibility of 2 revisions on page File:Txt.jpg: content hidden, edit summary hidden and username hidden Inappropriate comment or personal information

Oleg

← Older revision Revision as of 21:26, 28 February 2019 Line 11: Line 11:  Elphel, Inc. Elphel, Inc.    −1405 W. 2200 S., Suite 205+1455 W. 2200 S., Suite 205     West Valley City, Utah 84119 West Valley City, Utah 84119 Line 19: Line 19:  email: info@elphel.com email: info@elphel.com    −Toll-free: (888) 3 ELPHEL+<!--Toll-free: (888) 3 ELPHEL -->     phone: (801) 783-5555 phone: (801) 783-5555 −  −phone: (801) 252-7457      fax: (801) 812-8267 fax: (801) 812-8267 Andrey.filippov

‎Latency tests

← Older revision Revision as of 21:56, 21 February 2019 (2 intermediate revisions by the same user not shown)Line 157: Line 157:  * Receive rtsp stream and re-stream as rtp: * Receive rtsp stream and re-stream as rtp:    gst-launch-1.0 -e rtspsrc location='rtsp://192.168.0.9:554' latency=0 ! udpsink host=127.0.0.1 port=5000   gst-launch-1.0 -e rtspsrc location='rtsp://192.168.0.9:554' latency=0 ! udpsink host=127.0.0.1 port=5000  +* Receive rtsp stream then re-stream as rtp and display at the same time  + gst-launch-1.0 -e rtspsrc location='rtsp://192.168.0.37:554' latency=0 ! rtpjpegdepay ! jpegdec ! timeoverlay ! tee name=t ! queue ! xvimagesink t. ! jpegenc ! rtpjpegpay ! udpsink host=127.0.0.1 port=5000  To play that rtp with vlc one would need an sdp file (somefile.sdp): To play that rtp with vlc one would need an sdp file (somefile.sdp):    v=0   v=0 Line 168: Line 170:    gst-launch-1.0 udpsrc uri=udp://127.0.0.1:5000 ! rtpjpegdepay ! jpegdec ! autovideosink   gst-launch-1.0 udpsrc uri=udp://127.0.0.1:5000 ! rtpjpegdepay ! jpegdec ! autovideosink     +=Latency tests=  +==Test 1: vlc relative to gstreamer==  +* Camera:  + <font size=2>elphel393~# /usr/bin/str</font>  +* PC, console 1 - restream and display at the same time:  + <font size=2>~$ gst-launch-1.0 -e rtspsrc location='rtsp://192.168.0.9:554' latency=0 ! rtpjpegdepay ! jpegdec ! timeoverlay ! tee name=t ! queue ! xvimagesink t. ! jpegenc ! rtpjpegpay ! udpsink host=127.0.0.1 port=5000</font>  +* PC, console 2 - run vlc:  + <font size=2>~$ vlc test.sdp --network-caching=0</font>  +where ''test.sdp'':  + <font size=2>v=0  + m=video 5000 RTP/AVP 26  + c=IN IP4 127.0.0.1  + a=rtpmap:26 JPEG/90000</font>     [[Category:393]] [[Category:393]]  [[Category:353]] [[Category:353]] Oleg

‎Latency tests

← Older revision Revision as of 21:56, 21 February 2019 (4 intermediate revisions by the same user not shown)Line 146: Line 146:  * I did some benchmarks; a Core 2 Quad Q6600 (2.4 Ghz) is not powerful enough for h264 encoding @fullHD resolution (using 4 treads). * I did some benchmarks; a Core 2 Quad Q6600 (2.4 Ghz) is not powerful enough for h264 encoding @fullHD resolution (using 4 treads).    −==Useful links==+=Useful links=  * [http://wiki.oz9aec.net/index.php/Gstreamer_cheat_sheet GStreamer cheat sheet] * [http://wiki.oz9aec.net/index.php/Gstreamer_cheat_sheet GStreamer cheat sheet]  * [http://processors.wiki.ti.com/index.php/Example_GStreamer_Pipelines Example GStreamer pipelines] * [http://processors.wiki.ti.com/index.php/Example_GStreamer_Pipelines Example GStreamer pipelines]  * [https://coaxion.net/blog/2014/01/gstreamer-dynamic-pipelines/ GStreamer dynamic pipelines] * [https://coaxion.net/blog/2014/01/gstreamer-dynamic-pipelines/ GStreamer dynamic pipelines]  * [https://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/section-dynamic-pipelines.html Dynamic pipelines] * [https://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/section-dynamic-pipelines.html Dynamic pipelines]  +  +=Some other examples=  +* Simply playing stream  + gst-launch-1.0 -v playbin uri=rtsp://192.168.0.9:554 uridecodebin0::source::latency=0  +* Receive rtsp stream and re-stream as rtp:  + gst-launch-1.0 -e rtspsrc location='rtsp://192.168.0.9:554' latency=0 ! udpsink host=127.0.0.1 port=5000  +* Receive rtsp stream then re-stream as rtp and display at the same time  + gst-launch-1.0 -e rtspsrc location='rtsp://192.168.0.37:554' latency=0 ! rtpjpegdepay ! jpegdec ! timeoverlay ! tee name=t ! queue ! xvimagesink t. ! jpegenc ! rtpjpegpay ! udpsink host=127.0.0.1 port=5000  +To play that rtp with vlc one would need an sdp file (somefile.sdp):  + v=0  + m=video 5000 RTP/AVP 26  + c=IN IP4 127.0.0.1  + a=rtpmap:26 JPEG/90000  +  +To play with vlc:  + vlc somefile.sdp --network-caching=0  +To play with gstreamer (sdp is not required):  + gst-launch-1.0 udpsrc uri=udp://127.0.0.1:5000 ! rtpjpegdepay ! jpegdec ! autovideosink  +  +=Latency tests=  +==Test 1: vlc relative to gstreamer==  +* Camera:  + <font size=2>elphel393~# /usr/bin/str</font>  +* PC, console 1 - restream and display at the same time:  + <font size=2>~$ gst-launch-1.0 -e rtspsrc location='rtsp://192.168.0.9:554' latency=0 ! rtpjpegdepay ! jpegdec ! timeoverlay ! tee name=t ! queue ! xvimagesink t. ! jpegenc ! rtpjpegpay ! udpsink host=127.0.0.1 port=5000</font>  +* PC, console 2 - run vlc:  + <font size=2>~$ vlc test.sdp --network-caching=0</font>  +where ''test.sdp'':  + <font size=2>v=0  + m=video 5000 RTP/AVP 26  + c=IN IP4 127.0.0.1  + a=rtpmap:26 JPEG/90000</font>     [[Category:393]] [[Category:393]]  [[Category:353]] [[Category:353]] Oleg

‎Test 1: vlc relative to gstreamer

← Older revision Revision as of 21:22, 21 February 2019 (3 intermediate revisions by the same user not shown)Line 146: Line 146:  * I did some benchmarks; a Core 2 Quad Q6600 (2.4 Ghz) is not powerful enough for h264 encoding @fullHD resolution (using 4 treads). * I did some benchmarks; a Core 2 Quad Q6600 (2.4 Ghz) is not powerful enough for h264 encoding @fullHD resolution (using 4 treads).    −==Useful links==+=Useful links=  * [http://wiki.oz9aec.net/index.php/Gstreamer_cheat_sheet GStreamer cheat sheet] * [http://wiki.oz9aec.net/index.php/Gstreamer_cheat_sheet GStreamer cheat sheet]  * [http://processors.wiki.ti.com/index.php/Example_GStreamer_Pipelines Example GStreamer pipelines] * [http://processors.wiki.ti.com/index.php/Example_GStreamer_Pipelines Example GStreamer pipelines]  * [https://coaxion.net/blog/2014/01/gstreamer-dynamic-pipelines/ GStreamer dynamic pipelines] * [https://coaxion.net/blog/2014/01/gstreamer-dynamic-pipelines/ GStreamer dynamic pipelines]  * [https://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/section-dynamic-pipelines.html Dynamic pipelines] * [https://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/section-dynamic-pipelines.html Dynamic pipelines]  +  +=Some other examples=  +* Simply playing stream  + gst-launch-1.0 -v playbin uri=rtsp://192.168.0.9:554 uridecodebin0::source::latency=0  +* Receive rtsp stream and re-stream as rtp:  + gst-launch-1.0 -e rtspsrc location='rtsp://192.168.0.9:554' latency=0 ! udpsink host=127.0.0.1 port=5000  +* Receive rtsp stream then re-stream as rtp and display at the same time  + gst-launch-1.0 -e rtspsrc location='rtsp://192.168.0.37:554' latency=0 ! rtpjpegdepay ! jpegdec ! timeoverlay ! tee name=t ! queue ! xvimagesink t. ! jpegenc ! rtpjpegpay ! udpsink host=127.0.0.1 port=5000  +To play that rtp with vlc one would need an sdp file (somefile.sdp):  + v=0  + m=video 5000 RTP/AVP 26  + c=IN IP4 127.0.0.1  + a=rtpmap:26 JPEG/90000  +  +To play with vlc:  + vlc somefile.sdp --network-caching=0  +To play with gstreamer (sdp is not required):  + gst-launch-1.0 udpsrc uri=udp://127.0.0.1:5000 ! rtpjpegdepay ! jpegdec ! autovideosink  +  +=Latency tests=  +==Test 1: vlc relative to gstreamer==  +* Camera:  + elphel393~# /usr/bin/str  +* PC, console 1 - restream and display at the same time:  + ~$ gst-launch-1.0 -e rtspsrc location='rtsp://192.168.0.9:554' latency=0 ! rtpjpegdepay ! jpegdec ! timeoverlay ! tee name=t ! queue ! xvimagesink t. ! jpegenc ! rtpjpegpay ! udpsink host=127.0.0.1 port=5000  +* PC, console 2 - run vlc:  + ~$ vlc test.sdp --network-caching=0  +where ''test.sdp'':  + v=0  + m=video 5000 RTP/AVP 26  + c=IN IP4 127.0.0.1  + a=rtpmap:26 JPEG/90000     [[Category:393]] [[Category:393]]  [[Category:353]] [[Category:353]] Oleg

← Older revision Revision as of 01:45, 20 February 2019 (One intermediate revision by the same user not shown)Line 146: Line 146:  * I did some benchmarks; a Core 2 Quad Q6600 (2.4 Ghz) is not powerful enough for h264 encoding @fullHD resolution (using 4 treads). * I did some benchmarks; a Core 2 Quad Q6600 (2.4 Ghz) is not powerful enough for h264 encoding @fullHD resolution (using 4 treads).    −==Useful links==+=Useful links=  * [http://wiki.oz9aec.net/index.php/Gstreamer_cheat_sheet GStreamer cheat sheet] * [http://wiki.oz9aec.net/index.php/Gstreamer_cheat_sheet GStreamer cheat sheet]  * [http://processors.wiki.ti.com/index.php/Example_GStreamer_Pipelines Example GStreamer pipelines] * [http://processors.wiki.ti.com/index.php/Example_GStreamer_Pipelines Example GStreamer pipelines]  * [https://coaxion.net/blog/2014/01/gstreamer-dynamic-pipelines/ GStreamer dynamic pipelines] * [https://coaxion.net/blog/2014/01/gstreamer-dynamic-pipelines/ GStreamer dynamic pipelines]  * [https://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/section-dynamic-pipelines.html Dynamic pipelines] * [https://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/section-dynamic-pipelines.html Dynamic pipelines]  +  +=Some other examples=  +* Simply playing stream  + gst-launch-1.0 -v playbin uri=rtsp://192.168.0.9:554 uridecodebin0::source::latency=0  +* Receive rtsp stream and re-stream as rtp:  + gst-launch-1.0 -e rtspsrc location='rtsp://192.168.0.9:554' latency=0 ! udpsink host=127.0.0.1 port=5000  +To play that rtp with vlc one would need an sdp file (somefile.sdp):  + v=0  + m=video 5000 RTP/AVP 26  + c=IN IP4 127.0.0.1  + a=rtpmap:26 JPEG/90000  +  +To play with vlc:  + vlc somefile.sdp --network-caching=0  +To play with gstreamer (sdp is not required):  + gst-launch-1.0 udpsrc uri=udp://127.0.0.1:5000 ! rtpjpegdepay ! jpegdec ! autovideosink  +     [[Category:393]] [[Category:393]]  [[Category:353]] [[Category:353]] Oleg

Andrey.filippov uploaded a new version of File:103992 assy.tar.gz

New page

== Licensing ==
{{CERN OHLv1.1 }} Andrey.filippov

Andrey.filippov uploaded a new version of File:103992 gerber.tar.gz

New page

== Licensing ==
{{CERN OHLv1.1 }} Andrey.filippov

Andrey.filippov uploaded a new version of File:103992 sch.pdf

New page

== Licensing ==
{{CERN OHLv1.1 }} Andrey.filippov

← Older revision Revision as of 20:54, 1 February 2019 (2 intermediate revisions by the same user not shown)Line 1: Line 1:  {| class="wikitable" {| class="wikitable" −|+This page lists Elphel papers and other papers, patents, PhD/MS/BS theses that use or reference Elphel products. Links to full text publications are provided where available.+|+This page lists Elphel papers and other papers, patents, PhD/MS/BS theses that use or reference Elphel products.<br/> Links to the full text publications are provided where available.  |- style="font-style: italic; text-align:center;" <!-- color: green;"--> |- style="font-style: italic; text-align:center;" <!-- color: green;"-->  ! Year   ! Year    ! Citation/link ! Citation/link  ! Comments ! Comments  +|-  +|2019  +|[https://patents.google.com/patent/US20190020829A1  Nebiker, Stephan. "Stereo Image Capturing System." U.S. Patent Application No. 16/070,120.]  +|Elphel Eyesis referenced in the "Description"  |- |-  |2019 |2019 Line 37: Line 41:  |Luo, Z. C., et al. "The effect of deformation twins on the quasi-cleavage crack propagation in twinning-induced plasticity steels." Acta Materialia 150 (2018): 59-68. |Luo, Z. C., et al. "The effect of deformation twins on the quasi-cleavage crack propagation in twinning-induced plasticity steels." Acta Materialia 150 (2018): 59-68.  |Used Ephel camera in experimental setup |Used Ephel camera in experimental setup  +|-  +|2018  +|[http://www.web3d.org/sites/default/files/attachment/node/2281/edit/Web3D%20Design%20Print%20Scanning%20Use%20Cases.pdf Anita Havele. "Design Printing and Scanning: Web3D Makers Making More!" BOF Presentation at SIGGRAPH (2018).]  +|Demonstrated multiple Elphel X3D applications  |- |-  |2018 |2018 Andrey.filippov

‎RTSP

← Older revision Revision as of 21:05, 31 January 2019 (7 intermediate revisions by the same user not shown)Line 151: Line 151:  </font> </font>  ====RTSP==== ====RTSP====  +* Streams with either '''w''' or '''h''' >2040 might not get played - not supported by live555 often used by various media players. But there's a [https://git.elphel.com/Elphel/live555_patch live555_patch].  * turn on: * turn on:  <font size='2'> <font size='2'> Line 162: Line 163:    rtsp://192.168.0.9:560   rtsp://192.168.0.9:560  </font> </font>  +  ====GStreamer==== ====GStreamer====  <font size='2'> <font size='2'>  + gst-launch-1.0 -v playbin uri=rtsp://192.168.0.9:554 uridecodebin0::source::latency=0  +or    gst-launch-1.0 souphttpsrc is-live=true location=http://192.168.0.9:2323/mimg ! jpegdec ! xvimagesink     gst-launch-1.0 souphttpsrc is-live=true location=http://192.168.0.9:2323/mimg ! jpegdec ! xvimagesink    </font> </font> Oleg