Recherche avancée

Sur d’autres sites (7162)

• when use idb and ffmepg to record video, Appium Session lose

  6 septembre 2023, par azhi

  When use Appium to start the session and open app in iOS, connection will lost after using idb and ffmepg command to record video in java process. At the same time, Xcode will occur connection lost issue. If i open WDA again by manual in iPhone, tests again and connection will be normal. I tied switching port for WDA, unluckily it's the same result. Have any ideas for this, graceful for advice.

  


  test normal when use this way to record video.

  


  Appium log :

  
[Xcode] xcodebuild exited with code '65' and signal 'null' [HTTP] —> GET /session/f70eef73-ef99-4341-822f-d285d74a8614/timeouts [HTTP] {} [debug] [AppiumDriver@8f28] Encountered internal error running command : NoSuchDriverError : A session is either terminated or not started [debug] [AppiumDriver@8f28] at asyncHandler (/opt/homebrew/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/protocol.js:315:15) [debug] [AppiumDriver@8f28] at /opt/homebrew/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/protocol.js:518:15 [debug] [AppiumDriver@8f28] at Layer.handle [as handle_request] (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/layer.js:95:5) [debug] [AppiumDriver@8f28] at next (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/route.js:144:13) [debug] [AppiumDriver@8f28] at Route.dispatch (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/route.js:114:3) [debug] [AppiumDriver@8f28] at Layer.handle [as handle_request] (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/layer.js:95:5) [debug] [AppiumDriver@8f28] at /opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:284:15 [debug] [AppiumDriver@8f28] at param (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:365:14) [debug] [AppiumDriver@8f28] at param (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:376:14) [debug] [AppiumDriver@8f28] at Function.process_params (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:421:3) [debug] [AppiumDriver@8f28] at next (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:280:10) [debug] [AppiumDriver@8f28] at logger (/opt/homebrew/lib/node_modules/appium/node_modules/morgan/index.js:144:5) [debug] [AppiumDriver@8f28] at Layer.handle [as handle_request] (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/layer.js:95:5) [debug] [AppiumDriver@8f28] at trim_prefix (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:328:13) [debug] [AppiumDriver@8f28] at /opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:286:9 [debug] [AppiumDriver@8f28] at Function.process_params (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:346:12) [debug] [AppiumDriver@8f28] at next (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:280:10) [debug] [AppiumDriver@8f28] at jsonParser (/opt/homebrew/lib/node_modules/appium/node_modules/body-parser/lib/types/json.js:113:7) [debug] [AppiumDriver@8f28] at Layer.handle [as handle_request] (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/layer.js:95:5) [debug] [AppiumDriver@8f28] at trim_prefix (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:328:13) [debug] [AppiumDriver@8f28] at /opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:286:9 [debug] [AppiumDriver@8f28] at Function.process_params (/opt/homebrew/lib/node_modules/appium/node_modules/express/lib/router/index.js:346:12) [HTTP] GET /session/66e1fdca-4e8c-418e-a0d1-6d98779b874c/screenshot


• avcodec/h264_mp4toannexb_bsf : refactor start_code_size handling

  18 mai 2023, par Zhao Zhili

  avcodec/h264_mp4toannexb_bsf : refactor start_code_size handling
  start_code_size depends on whether PS comes from out-of-band or
  
  in-band. Make the code more readable.
  Signed-off-by : Zhao Zhili <zhilizhao@tencent.com>
  

  • [DH] libavcodec/h264_mp4toannexb_bsf.c

• Can ffmpeg RTSP video stream be exchanged without an RTSP server ? [closed]

  17 décembre 2023, par natedogg

  I have two Ubuntu devices connected directly together via wired Ethernet (no router). One device (the sender) has a camera that I want to stream over RTSP, and the second device (the reciever) needs to process and view the RTSP stream. Is it possible to do this without an explicit RTSP server running on the sender ?

  


  Here is my test setup :

  


  


  • Sender

    


    

    • Static IP : 192.168.1.1/24

    


    • ffmpeg command : ffmpeg -f v4l2 -i /dev/video0 -pix_fmt yuv420p -f rtsp -rtsp_transport udp rtsp://192.168.1.2:12345/test

    


    


  


  • Receiver

    


    

    • Static IP : 192.168.1.2/24

    


    • ffmpeg command : ffplay rtsp://192.168.1.1:12345/test

    


    


  


  


  Each machine can ping the other successfully, and both devices have their firewalls disabled. However, I get connection refused errors when trying to run each command. For resource reasons, I'm trying to avoid running an RTSP server if it isn't necessary.

  


  # Sender error
Connection to tcp://192.168.1.2:12345?timeout=0 failed: Connection refused
Could not write header for output file #0 (incorrect codec parameters ?): Connection refused
Error initializing output stream 0:0 --


  


  # Receiver error
Connection to tcp://192.168.1.2:12345?timeout=0 failed: Connection refused
Connection to tcp://192.168.1.2:12345?timeout=0 failed: Connection refused