Recherche avancée

Sur d’autres sites (8451)

• fftp server stream server error- connection to tcp:10.10.X.X timeout=0 faild no route to host

  1er juillet 2023, par slowmonk

  When attempting to stream the webcam using RTSP, I encountered persistent timeout issues.

  


  https://hub.docker.com/r/aler9/rtsp-simple-server

  


  docker run -p 6020:8000 aler9/rtsp-simple-server:latest
2023/07/01 20:15:24 INF MediaMTX v0.23.7
2023/07/01 20:15:24 INF [RTSP] listener opened on :8554 (TCP), :8000 (UDP/RTP), :8001 (UDP/RTCP)
2023/07/01 20:15:24 INF [RTMP] listener opened on :1935
2023/07/01 20:15:24 INF [HLS] listener opened on :8888
2023/07/01 20:15:24 INF [WebRTC] listener opened on :8889 (HTTP)

$ sudo ffmpeg -f v4l2 -framerate 24 -video_size 480x480 -i /dev/video0 -f rtsp -rtsp_transport tcp rtsp://192.168.XXX.XXX:8554/webCamStream


  


  following error occur

  


  ffmpeg version 4.4.2-0ubuntu0.22.04.1 Copyright (c) 2000-2021 the FFmpeg developers
  built with gcc 11 (Ubuntu 11.2.0-19ubuntu1)
  configuration: --prefix=/usr --extra-version=0ubuntu0.22.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
  libavutil      56. 70.100 / 56. 70.100
  libavcodec     58.134.100 / 58.134.100
  libavformat    58. 76.100 / 58. 76.100
  libavdevice    58. 13.100 / 58. 13.100
  libavfilter     7.110.100 /  7.110.100
  libswscale      5.  9.100 /  5.  9.100
  libswresample   3.  9.100 /  3.  9.100
  libpostproc    55.  9.100 / 55.  9.100
[video4linux2,v4l2 @ 0x5642e55137c0] The V4L2 driver changed the video from 480x480 to 640x480
[video4linux2,v4l2 @ 0x5642e55137c0] The driver changed the time per frame from 1/24 to 1/30
Input #0, video4linux2,v4l2, from '/dev/video0':
  Duration: N/A, start: 46142.014949, bitrate: 147456 kb/s
  Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 640x480, 147456 kb/s, 30 fps, 30 tbr, 1000k tbn, 1000k tbc
Stream mapping:
  Stream #0:0 -> #0:0 (rawvideo (native) -> mpeg4 (native))
Press [q] to stop, [?] for help
[tcp @ 0x5642e55e34c0] Connection to tcp://10.10.1068:9988?timeout=0 failed: No route to host
Could not write header for output file #0 (incorrect codec parameters ?): No route to host
Error initializing output stream 0:0 --


  


• Nginx rtmp module - on_publish fires multiple time instead of once

  29 juillet 2017, par Stephen Wright

  This is copy and pasted from the bug report I created on the rtmp-module by Arut, I am not completely sure if it is a bug or me not understanding how the module works, I have read the whole directives of module as from https://github.com/arut/nginx-rtmp-module/wiki/Directives

  Proper explanation, if code is not displayed properly I will edit and fix

  Hi, been using the module and finding it very very good !

  Think I have found a issue though, although it may be me misunderstanding the directives.

  Essentially I wish to fire a script (/usr/local/bin/make_thumbnail.sh) which creates a thumbnail automatically from a stream (using ffmpeg), the idea is to have this done for every stream as soon as it is published in order to create a function a bit like twitch tv where the streamer will not have to specify any thumbnail image, authenticated users simply start a stream (which will later be authenticated but is not yet) The script does also write data into the database however this stage works fine and I don’t believe the issue is related, if I comment out these lines then the thumbnail creation still works and my issue continues.

  Initially this was done using the "exec" command as I believe I mis-read the documentation and I believe the exec command doesn’t work for my problem as ". When publishing stops the process is terminated." does this mean it will continually execute until stream stops ?

  I have started using the exec_publish command to try and fix this issue however the same issue seems to occur. The entire script repeats approximately every 15-17 seconds, a new thumbnail is created and a new database entry is create with all the correct information.

  Below is the nginx.conf line. Please ignore if indentation is incorrect couldn’t see a way to indent blocks of code and it’s late here, assume all code is indented correctly unless you believe that could be the issue in which case I will post it indented as early as I can.

  application live {
  
  allow play all;
  
  live on;
  
  record all;
  
  record_path /var/stream/video_recordings/;
  
  record_unique on; 
  
  hls on;
  
  hls_nested on;
  
  hls_path /var/stream/HLS/live;
  
  hls_fragment 10s;
  
  
  
  #on publish create thumbnail using first second of stream and save in 
  
  /var/stream/video_recordings/thumbnails
  
  exec_publish usr/local/bin/make_thumbnail.sh $name;

  The rest can be pasted or attached if needed but is working nginx config for rtmp + website

  The most simple version of the make_thumbnail..sh is pasted below, I have omitted the variables that I have used for database entryys obviously but as the script works without fail from terminal I believe this to be an nginx issue (if I run the command manually under the nginx user e.g. sudo -u nginx /usr/local/bin/make_thumbnail.sh with a name the same as any running stream, it works and only executes once as would expect, all permissions in script are ok and tested.

  make_thumbnail.sh

  #!/bin/bash
  
  
  
  TIME=$(date +%s)
  
  NAME=$1 
  
  echo "time: "
  
  FILENAME=${TIME}_${NAME}
  
  
  
  ffmpeg -i rtmp://192.168.0.98:1935/live/$1 -vframes 1 -s 150x150 -ss 10 -
  
  strftime 1 /var/stream/video_recordings/thumbnails/"$FILENAME.jpg";
  
  
  
  #Writes path to video into database
  
  mysql --user=$DB_USER --password=$DB_PASSWD $DB_NAME << EOF
  
  INSERT INTO $TABLE3 (thumbnailfile) VALUES ('$FILENAME');
  
  set @last_id_in_thumbnails = LAST_INSERT_ID();
  
  INSERT INTO $TABLE (created_at, updated_at, thumnailID) VALUES 
  
  (NOW(),NOW(),@last_id_in_thumbnails);
  
  SET @last_id_in_livestreams = LAST_INSERT_ID();
  
  INSERT INTO $TABLE2 (created_at, updated_at, filename,liveID) VALUES 
  
  (NOW(),NOW(),'$FILENAME',@last_id_in_livestreams); 
  
  EOF

  I have not got the nginx rtmp logs installed, I can obviously do this however some of the logs appear in the nginx error.log, strangely the latest stream I tried did not update in the access log, however I think this is because I did not attempt to connect to it via any method. I don’t fully understand the error.log, in my stupidity I decided to use nginx with which I am quite inexperienced and I am finding it very difficult to troubleshoot this issue, it appears to me that as part of the RTMP protocol or my streaming software (OBS) is either directly pinging the rtmp stream or is being pinged by the server to ensure the connection is still there. And this ping is

  I have left a stream running from approx 4 minutes without interacting with the server, streaming software, computer running the stream, I have ensured the internet connection is constant as my first though was the connection dropped, however on inspecting the database the executing is done always after at least 11 seconds however usually this is 16, I can’t seem to figure out how to select the closest dates from the database however there has been at least a few 17 second differences (potentially when
  I am unsure if this is an issue or if it is intended behavior but I do require this to finish a university degree, I’m not asking for answers but if it is a legitimate issue then I would be happy to spend as much time I can commit to it if some insight into what is causing it, or if there is a workaround I believe it should be documented somewhere, I have googled into making any exec commands run only once on publish

  I can’t seem to pinpoint where in the log the issue is happening however think it is something to do with the below exceprts I would attach the file but can’t seem to select all lines after the timestamp upon starting a stream

  2017/07/26 18:17:35 [info] 1451#0: *2229 exec: starting managed child 
  
  'ffmpeg', client: 192.168.0.78, server: 0.0.0.0:1935
  
  2017/07/26 18:17:35 [info] 1451#0: *2412 client connected '192.168.0.98'
  
  2017/07/26 18:17:35 [info] 1451#0: *2412 connect: app='live' args='' 
  
  flashver='LNX 9,0,124,2' swf_url='' tc_url='rtmp://192.168.0.98:1935/live' 
  
  page_url='' acodecs=4071 vcodecs=252 object_encoding=0, client: 
  
  192.168.0.98, server: 0.0.0.0:1935
  
  2017/07/26 18:17:35 [info] 1451#0: *2412 createStream, client: 192.168.0.98, 
  
  server: 0.0.0.0:1935
  
  2017/07/26 18:17:35 [info] 1451#0: *2412 play: name='newname' args='' 
  
  start=-2000 duration=0 reset=0 silent=0, client: 192.168.0.98, server:  
  
  0.0.0.0:1935
  
  2017/07/26 18:17:36 [info] 1451#0: *2410 recv() failed (104: Connection  
  
  reset by peer), client: 192.168.0.98, server: 0.0.0.0:1935
  
  2017/07/26 18:17:36 [info] 1451#0: *2410 disconnect, client: 192.168.0.98, 
  
  server: 0.0.0.0:1935
  
  2017/07/26 18:17:36 [info] 1451#0: *2410 deleteStream, client: 192.168.0.98, 
  
  server: 0.0.0.0:1935
  
  2017/07/26 18:17:36 [notice] 1451#0: signal 17 (SIGCHLD) received
  
  2017/07/26 18:17:36 [notice] 1451#0: unknown process 10487 exited with code 
  
  0
  
  2017/07/26 18:17:36 [info] 1451#0: *2229 exec: child 10487 exited; ignoring, 
  
  client: 192.168.0.78, server: 0.0.0.0:1935
  
  
  
  ver: 0.0.0.0:1935
  
  2017/07/26 18:17:41 [info] 1451#0: *2229 exec: starting managed child 
  
  'usr/local/bin/make_thumbnail.sh', client: 192.168.0.78, server:  
  
  0.0.0.0:1935
  
  2017/07/26 18:17:41 [info] 1451#0: *2413 client connected '192.168.0.98'
  
  2017/07/26 18:17:41 [info] 1451#0: *2413 connect: app='live' args='' 
  
  flashver='LNX 9,0,124,2' swf_url='' tc_url='rtmp://192.168.0.98:1935/live' 
  
  page_url='' acodecs=4071 vcodecs=252 object_encoding=0, client: 
  
  192.168.0.98, 
  
  server: 0.0.0.0:1935
  
  2017/07/26 18:17:41 [info] 1451#0: *2413 createStream, client: 192.168.0.98, 
  
  server: 0.0.0.0:1935
  
  2017/07/26 18:17:41 [info] 1451#0: *2413 play: name='newname' args='' 
  
  start=-2000 duration=0 reset=0 silent=0, client: 192.168.0.98, server: 
  
  0.0.0.0:1935
  
  2017/07/26 18:17:43 [info] 1451#0: *2229 exec: starting managed child 
  
  'ffmpeg', 
  
  client: 192.168.0.78, server: 0.0.0.0:1935
  
  2017/07/26 18:17:43 [info] 1451#0: *2414 client connected '192.168.0.98'
  
  2017/07/26 18:17:43 [info] 1451#0: *2414 connect: app='live' args='' 
  
  flashver='LNX 9,0,124,2' swf_url='' tc_url='rtmp://192.168.0.98:1935/live' 
  
  page_url='' acodecs=4071 vcodecs=252 object_encoding=0, client: 
  
  192.168.0.98, 
  
  server: 0.0.0.0:1935
  
  @

• Elacarte Presto Tablets

  14 mars 2013, par Multimedia Mike — General

  I visited an Applebee’s restaurant this past weekend. The first thing I spied was a family at a table with what looked like a 7-inch tablet. It’s not an uncommon sight. However, as I moved through the restaurant, I noticed that every single table was equipped with such a tablet. It looked like this :

  
  
  

  For a computer nerd like me, you could probably guess that I was be far more interested in this gadget than the cuisine. The thing said “Presto” on the front and “Elacarte” on the back. Putting this together, we get the website of Elacarte, the purveyors of this restaurant tablet technology. Months after the iPad was released on 2010, I remember stories about high-end restaurants showing their wine list via iPads. This tablet goes well beyond that.

  How was it ? Well, confusing, mostly. The hostess told us we could order through the tablet or through her. Since we already knew what we wanted, she just manually took our order and presumably entered it into the system. So, right away, the question is : Do we order through a human or through a computer ? Or a combination ? Do we have to use the tablet if we don’t want to ?

  Hardware
  When picking up the tablet, it’s hard not to notice that it is very heavy. At first, I suspected that it was deliberately weighted down as some minor attempt at an anti-theft measure. But then I remembered what I know about power budgets of phones and tablets– powering the screen accounts for much of the battery usage. I realized that this device needs to drive the screen for about 14 continuous hours each day. I.e., the weight must come from a massive battery.

  The screen is good. It’s a capacitive touchscreen, so nice and responsive. When I first spied the device, I felt certain it would be a resistive touchscreen (which is more accurately called a touch-and-press-down screen). There is an AC adapter on the side of the tablet. This is the only interface to the device :

  
  
  

  That looks to me like an internal SATA connector (different from an eSATA connector). Foolishly, I didn’t have a SATA cable on me so I couldn’t verify.

  User Interface
  The interface options are : Order, Games, Neighborhood, and Pay. One big benefit of accessing the menu through the Order option is that each menu item can have a picture. For people who order more by picture than text description, this is useful. Rather, it would be, if more items had pictures. I’m not sure there were more pictures than seen in the print menu.
  
  For Games, there were a variety of party games. The interface clearly stated that we got to play 2 free games. This implied to me that further games cost money. We tried one game briefly and the food came.

  2 more options : Neighborhood– I know I dug into this option, but I forget what it was. Maybe it discussed local attractions. Finally, Pay. This thing has an integrated credit card reader. There is no integrated printer, though, so if you want one, you will have to request one from a human.

  Experience
  So we ordered through a human since we didn’t feel like being thrust into this new paradigm when we just wanted lunch. The staff was obviously amenable to that. However, I got a chance to ask them a lot of questions about the particulars. Apparently, they have had this system for about 5 months. It was confirmed that the tablets do, in fact, have gargantuan batteries that have to last through the restaurant’s entire business hours. Do they need to be charged every night ? Yes, they do. But how ? The staff described this several large charging blocks with many cables sprouting out. Reportedly, some units still don’t make it through the entire day.

  When it was time to pay, I pressed the Pay button on the interface. The bill I saw had nothing in common with what we ordered (actually, it was cheaper, so perhaps I should have just accepted it). But I pointed it out to a human and they said that this happens sometimes. So they manually printed my bill. There was a dollar charge for the game that was supposed to be free. I pointed this out and they removed it. It’s minor, I know, but it’s still worth trying to work out these bugs.

  One of the staff also described how a restaurant doesn’t need to employ as many people thanks to the tablet. She gave a nervous, awkward, self-conscious laugh when she said this. All I could think of was this Dilbert comic strip in which the boss realizes that his smartphone could perform certain key functions previously handled by his assistant.

  Not A New Idea
  Some people might think this is a totally new concept. It’s not. I was immediately reminded of my university days in Boulder, Colorado, USA, circa 1997. The local Taco Bell and Arby’s restaurants both had touchscreen ordering kiosks. Step up, interact with the (probably resistive) touchscreen, get a number, and step to the counter to change money, get your food, and probably clarify your order because there is only so much that can be handled through a touchscreen.

  What I also remember is when they tore out those ordering kiosks, also circa 1997. I don’t know the exact reason. Maybe people didn’t like them. Maybe there were maintenance costs that made them not worth the hassle.

  Then there are the widespread self-checkout lanes in grocery stores. Personally, I like those, though I know many don’t. However, this restaurant tablet thing hasn’t won me over yet. What’s the difference ? Perhaps that automated lanes at grocery stores require zero external assistance– at least, if you do everything correctly. Personally, I work well with these lanes because I can pretty much guess the constraints of the system and I am careful not to confuse the computer in any way. Until they deploy serving droids, or at least food conveyors, there still needs to be some human interaction and I think the division between the human and computer roles is unintuitive in the restaurant case.

  I don’t really care to return to the same restaurant. I’ll likely avoid any other restaurant that has these tablets. For some reason, I think I’m probably supposed to be the ideal consumer of this concept. But the idea will probably perform all right anyway. Elacarte’s website has plenty of graphs demonstrating that deploying these tablets is extremely profitable.