Recherche avancée

Sur d’autres sites (3539)

• tests/fate-run : Ensure that THREADS=random is actually random

  19 septembre 2023, par Andreas Rheinhardt

  tests/fate-run : Ensure that THREADS=random is actually random
  From the documentation of GNU awk [1] :
  
  "In most awk implementations, including gawk, rand() starts generating
  
  numbers from the same starting number, or seed, each time you run awk.45
  
  Thus, a program generates the same results each time you run it. The
  
  numbers are random within one awk run but predictable from run to run.
  
  This is convenient for debugging, but if you want a program to do
  
  different things each time it is used, you must change the seed to a
  
  value that is different in each run. To do this, use srand()."
  This commit does exactly this.
  [1] : https://www.gnu.org/software/gawk/manual/html_node/Numeric-Functions.html#index-rand_0028_0029-function
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] tests/fate-run.sh

• 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


• How can I use FFMPEG to extract a specific color from a video and put it over alpha ?

  28 février 2024, par Michael Macha

  I have a rendered animation which looks great, but my original file was not saved properly and has lost some of the data. I can quickly get that data back, if I can extract a specific color from the rendered video to a new file or image sequence, over either a key color or preferably transparency.

  


  Since I'm hand animating this, it's important that I automate as much as possible. I think FFMPEG could come to the rescue here and help me retrieve that data.

  


  My current line is this :

  


  ffmpeg -i ./"Light Bleeder Twirl Above.mp4" -vf "colorkey=0xe1eff9:0.1:0.1,format=rgba" -c:a copy ./out%04d.png


  


  Here, E1EFF9 is the color I'm after. It successfully extracts the handful of frames to PNG files, but it copies all of the data, not just E1EFF9.

  


  I'm not sure why colorkey isn't doing what I want it to. If someone could provide some insight, it would be much appreciated.

  


  Addendum : So, my idea worked in principle ; I did a chroma key with Kdenlive and color-to-alpha'd the black to transparency after a manual rescale. It isn't exactly the same, but it's very close and saves a lot of time. I still feel like it should most certainly have worked with FFMPEG, much faster, and would still like to know what was wrong with my script.