Recherche avancée

Sur d’autres sites (8015)

• ClickOnce Deployment looking for manifest signature on an nuget sourced .exe (FFMPEG #) as if it is a .csproj output. Deployment fails

  9 octobre 2019, par M_Ryce

  I have a C# forms app which utilizes the nuget package "FFMPEG Sharp" (Nuget Github) to generate video from a sequence of images.

  Unlike most nuget packages which simply pull in a .dll, installing FFMPEG Sharp places an "FFMPEG" folder into the .csproj root directory, in addition to bringing the appropriate .dll into "packages"

  Inside this folder are a few FFMPEG artifacts and a /bin folder containing FFMPEG executables. According to the project’s Github readme, this /bin directory needs to be specified in the app.config.

  From Github Readme example :

  <appsettings>
  
    <add key="ffmpegRoot" value="C:\ffmpeg\bin\"></add>
  
  </appsettings>`

  Adjusting the above to work in alignment with the default location Nuget placed the dependency artifacts :

  <appsettings>
  
    <add key="ffmpegRoot" value="..\..\FFMPEG\bin"></add>
  
  </appsettings>`

  Everything related to this dev effort has been smooth sailing, until I tried to utilize the existing Clickonce deployment for the app. The FFMPEG folder in my .csproj root wasn’t making it to the build output and therefore the application’s call to the FFMPEG .exe was throwing a null reference error. Understandable result, given that I had not set up any method of ensuring the FFMPEG artifacts made it to the build output with the same folder structure as existed on my local dev box.

  To counter this, I set a POST-build command to XCOPY....

  XCOPY "$(SolutionDir)MyApp\FFMPEG" "$(TargetDir)FFMPEG" /S /Y /I

  ...the nuget-provisioned FFMPEG artifacts into the build output root, and adjusted the config setting accordingly (see below)

  <appsettings>
  
    <add key="ffmpegRoot" value=".\FFMPEG\bin"></add>
  
  </appsettings>`

  This worked like a dream when building/running locally. The XCOPY succeeded in placing FFMPEG folder contents into the compiled solution’s Debug/Release bin and the updated config referenced them. No errors.

  Attempting to deploy with the .NET ClickOnce tool has created a rather befuddling error though.

  (Apologies for formatting ugliness below. I tried but didn’t succeed. The important parts are in bold)

  ERROR SUMMARY
  Below is a summary of the errors, details of these errors are listed later in the log.
  Activation of https://MySite/MyApp/Install/MyApp.application resulted in exception. Following failure messages were detected :
  + Downloading https://MySite/MyApp/Install/Application Files/MyApp/FFMPEG/bin/x86/ffmpeg.exe.deploy did not succeed.
  + The remote server returned an error : (404) Not Found.
  COMPONENT STORE TRANSACTION FAILURE SUMMARY
  No transaction error was detected.
  WARNINGS
  The manifest for this application does not have a signature. Signature validation will be ignored.
  * The manifest for this application does not have a signature. Signature validation will be ignored.
  OPERATION PROGRESS STATUS
  * [10/8/2019 2:03:37 PM] : Activation of https://MySite/MyApp/Install/MyApp.application has started.
  * [10/8/2019 2:03:37 PM] : Processing of deployment manifest has successfully completed.
  * [10/8/2019 2:03:37 PM] : Installation of the application has started.
  * [10/8/2019 2:03:37 PM] : Processing of application manifest has successfully completed.
  * [10/8/2019 2:03:40 PM] : Found compatible runtime version 4.0.30319.
  * [10/8/2019 2:03:40 PM] : Request of trust and detection of platform is complete.
  ERROR DETAILS
  Following errors were detected during this operation.
  * [10/8/2019 2:03:40 PM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
  - Downloading https://MySite/MyApp/Install/Application Files/MyApp/FFMPEG/bin/x86/ffmpeg.exe.deploy did not succeed.*

  ...

  My interpretation of this is that the ClickOnce deployment is treating the Nuget-sourced .exe’s as if they are compiled code from this very project, and checking for a signed manifest.

  This ClickOnce deployment was not set up by me, and had not needed to account for such external artifacts existing in the output previously. I do not believe turning off signed assemblies is an option for me, for security reasons.

  Is there a way to make ClickOnce deployments ignore a specific .exe when checking for signed manifests ? I think the "correct" intended usage is for FFMPEG to be pre-installed on the machine as a stand-alone application, but This is not an option for me at this time. I will need FFMPEG to be brought in by the ClickOnce.

• What does the output of `ffmpeg` mean ?

  25 juillet 2024, par Alex

  I am converting a file, and here is the output. This question has a partial answer here, so I am asking about the parts not covered by it. I've adjusted the width of the terminal to preserve the output history

  



  [olpc@laptop ~] ffmpeg -i input -c:a copy -s 384x216 output
ffmpeg version N-68778-g5c7227b Copyright (c) 2000-2014 the FFmpeg developers
  built on Dec 29 2014 22:12:54 with gcc 4.9.2 (GCC)

...

frame=2   fps=0.0 q=0.0  size=     0kB time=00:00:00.00 bitrate=   0.0kbits/s
frame=3   fps=2.0 q=0.0  size=     0kB time=00:00:00.00 bitrate=   0.0kbits/s
frame=5   fps=2.4 q=0.0  size=     0kB time=00:00:00.00 bitrate=   0.0kbits/s
frame=8   fps=2.9 q=0.0  size=     0kB time=00:00:00.00 bitrate=   0.0kbits/s
frame=10  fps=2.8 q=0.0  size=     0kB time=00:00:00.00 bitrate=   0.0kbits/s
frame=12  fps=2.9 q=0.0  size=     0kB time=00:00:00.00 bitrate=   0.0kbits/s
frame=13  fps=2.8 q=0.0  size=     0kB time=00:00:00.02 bitrate=  16.5kbits/s
frame=16  fps=3.1 q=0.0  size=     0kB time=00:00:00.48 bitrate=   0.8kbits/s
frame=19  fps=3.2 q=0.0  size=     0kB time=00:00:00.48 bitrate=   0.8kbits/s
frame=21  fps=3.2 q=0.0  size=     0kB time=00:00:00.48 bitrate=   0.8kbits/s

...

frame=687 fps=0.6 q=29.0 size=  1245kB time=00:00:22.84 bitrate= 446.5kbits/s
frame=688 fps=0.6 q=29.0 size=  1246kB time=00:00:22.84 bitrate= 446.7kbits/s
frame=689 fps=0.6 q=29.0 size=  1248kB time=00:00:22.84 bitrate= 447.5kbits/s
frame=690 fps=0.6 q=29.0 size=  1249kB time=00:00:22.84 bitrate= 447.8kbits/s
frame=691 fps=0.6 q=29.0 size=  1249kB time=00:00:22.84 bitrate= 448.0kbits/s
frame=692 fps=0.6 q=29.0 size=  1251kB time=00:00:22.84 bitrate= 448.7kbits/s
frame=693 fps=0.6 q=29.0 size=  1252kB time=00:00:22.84 bitrate= 448.8kbits/s
frame=694 fps=0.6 q=29.0 size=  1253kB time=00:00:22.84 bitrate= 449.1kbits/s
frame=695 fps=0.6 q=29.0 size=  1254kB time=00:00:22.84 bitrate= 449.7kbits/s
frame=696 fps=0.6 q=29.0 size=  1255kB time=00:00:22.84 bitrate= 449.9kbits/s
frame=697 fps=0.6 q=29.0 size=  1256kB time=00:00:22.84 bitrate= 450.2kbits/s
frame=698 fps=0.6 q=29.0 size=  1256kB time=00:00:22.84 bitrate= 450.3kbits/s
frame=699 fps=0.6 q=29.0 size=  1258kB time=00:00:22.84 bitrate= 451.0kbits/s
frame=699 fps=0.6 q=29.0 size=  1258kB time=00:00:22.87 bitrate= 450.5kbits/s
frame=701 fps=0.6 q=29.0 size=  1261kB time=00:00:23.31 bitrate= 443.1kbits/s


  



  The second segment took 20 seconds : 1 second per each line until the last one, and the last one took 6 seconds before being displayed. This pattern is repeating for the entire length of the file. The way I understand it is, that there is a control frame in the video every 15 frames, and while there is no control frame the video is processed at 1fps.

  



  Now, my question is : what is time referring to ? It seems to refer to the time in the video, but why does it stand still for the first 13 frames, and then creep up by 0.03 second, before jumping by 0.44 seconds ?

  



  Also, how can the bitrate jump from 0.0 to 16.5 back to 0.8 ? (the above lines all updated one second apart). I mean, if after 7 seconds the bitrate is 16.5kbit/s, then it must have updated at least 105.5kbits. That means that even if it processes nothing the next second, the bit rate would be at least 13.2kbit/s after the next (8th) second.

  



  Finally, what does q stand for ?

  


• How can I capture real time command line output of x265.exe with Python ?

  29 février 2020, par LeeRoermond

  I would like to write a GUI for x265.exe which presents a better (more humanized) real time progress .

  Here’s the code I used to capture subprocess’s output :

  import subprocess
  
  
  
  cmd = r'ping www.baidu.com -n 4'
  
  popen = subprocess.Popen(cmd, stdout = subprocess.PIPE ,stderr=subprocess.STDOUT ,shell=True)
  
  while True:
  
      next_line = popen.stdout.readline()
  
      if next_line == b'' and popen.poll() != None:
  
          break
  
      else:
  
          print(next_line.decode('ascii').replace('\r\n','\n') , end='')

  It performs perfectly with ’ping’.

  However ,when I swiched to ’x265’ command ,thing goes to wired.

  For example, If I replaced string variable 'cmd' into "x265 --y4m --crf 21 --output output.hevc input.y4m" in the preceding code.Theoretically , it should gives out the following output in lines arranged in order of time :

  y4m  [info]: 1920x1080 fps 24000/1001 i420p10 frames 0 - 100 of 101
  
  x265 [info]: Using preset ultrafast & tune none
  
  raw  [info]: output file: C:\temp\output.hevc
  
  x265 [info]: Main 10 profile, Level-4 (Main tier)
  
  x265 [info]: Thread pool created using 16 threads
  
  x265 [info]: Slices                              : 1
  
  x265 [info]: frame threads / pool features       : 4 / wpp(34 rows)
  
  x265 [info]: Coding QT: max CU size, min CU size : 32 / 16
  
  x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
  
  x265 [info]: ME / range / subpel / merge         : dia / 57 / 0 / 2
  
  x265 [info]: Keyframe min / max / scenecut / bias: 23 / 250 / 0 / 5.00
  
  x265 [info]: Lookahead / bframes / badapt        : 5 / 3 / 0
  
  x265 [info]: AQ: mode / str / qg-size / cu-tree  : 1 / 0.0 / 32 / 1
  
  x265 [info]: Rate Control / qCompress            : CRF-21.0 / 0.60
  
  x265 [info]: tools: strong-intra-smoothing lslices=6 deblock
  
  
  
  [1.0%] 1/101 frames, 6.289 fps, 7217.8 kb/s
  
  [25.7%] 26/101 frames, 59.23 fps, 299.23 kb/s
  
  [45.5%] 46/101 frames, 66.76 fps, 322.81 kb/s  
  
  [69.3%] 70/101 frames, 73.30 fps, 224.53 kb/s
  
  [93.1%] 94/101 frames, 77.05 fps, 173.67 kb/s   
  
  
  
  x265 [info]: frame I:      1, Avg QP:23.45  kb/s: 7098.44 
  
  x265 [info]: frame P:     25, Avg QP:25.71  kb/s: 311.24  
  
  x265 [info]: frame B:     75, Avg QP:28.33  kb/s: 23.89   
  
  x265 [info]: consecutive B-frames: 3.8% 0.0% 0.0% 96.2% 
  
  
  
  encoded 101 frames in 1.22s (82.58 fps), 165.06 kb/s, Avg QP:27.64

  But the truth is, those output block in the middle part which indicates the real time progress will not be captured every specific it updated . popen.stdout.readline() command will be blocked until progress goes to 100% and then output altogether. Obviously that’s not what I want.

  ( ↓ I mean by this part)

  [1.0%] 1/101 frames, 6.289 fps, 7217.8 kb/s
  
  [25.7%] 26/101 frames, 59.23 fps, 299.23 kb/s
  
  [45.5%] 46/101 frames, 66.76 fps, 322.81 kb/s  
  
  [69.3%] 70/101 frames, 73.30 fps, 224.53 kb/s
  
  [93.1%] 94/101 frames, 77.05 fps, 173.67 kb/s   

  Could anyone help me fiture out what’s going on and how to fix it to achieve my goal ?

  Thanks a lot.